New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Emails sent to perl6-bugs-followup@perl.org do not replicate on RT ticket #5490
Comments
From @zoffixznetFor example, this email was sent to perl6-bugs-followup@perl.org by Zefram: http://www.nntp.perl.org/group/perl.perl6.compiler/2016/07/msg13370.html However, it was not posted on the RT ticket: https://rt-archive.perl.org/perl6/Ticket/Display.html?id=126119 This is extremely disruptive as the conversation on the ticket splits up and the authors of replies aren't even aware their replies aren't being posted to the original location. -- |
@zoffixznet - Status changed from 'open' to 'new' |
From @cokeOn Wed Jul 27 06:07:08 2016, cpan@zoffix.com wrote:
mails into RT go through a spam queue which occasionally requires human volunteer intervention. It's possible that it just hasn't made it through yet. Also, are we sure it's the followup and not the bugs-bitbucket address that does this? Zefram didn't reply all, he only sent his reply to the address with "followup" in it. -- |
The RT System itself - Status changed from 'new' to 'open' |
From @LLFournIt seems like someone has just done some cleaning of this spam queue On Thu, Jul 28, 2016 at 12:03 AM Will Coleda via RT <
|
From @cokeOn Thu Jul 28 03:07:13 2016, lloyd.fourn@gmail.com wrote:
There was a subtle race condition in the config processing the mailing list that caused some messages to be held - 36 messages hit this issue. All of them were freed and have been processed. Closing this ticket. -- |
@coke - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#128749 (status was 'resolved')
Searchable as RT128749$
The text was updated successfully, but these errors were encountered: