So, this morning I attempted to retire status1 (unread) and rename status3
(chatting) to unknown.  I also updated the statusauditor so that replies would
be set to 'unknown' instead of 'chatting' and that new bugs would be 'unknown'
instead of 'unread'

Then I noticed that the bug tracker seemed to not be receiving (or sending?
emails anymore).

I reversed my changes to the statusauditor and restored the statuses, but I'm
still getting no email through.

Another test I've done was to edit our procmail script so that it writes to a
file instead of piping to the mailgw (see issue1114), and no mails are being
written either.  So maybe this isn't something at the roundup level.

The bad news is that I'm away for the next couple of days.

On Wed, Aug 19, 2009 at 16:07:39 +0100, Eric Kow wrote:
> test again

This problem seems to have taken care of itself.

I'm not sure what is the cause, but we were experiencing some other
trouble with darcs.net probably related to our gitit troubles.

On Fri, Aug 21, 2009 at 16:23:33 +0000, Eric Kow wrote:
> I'm not sure what is the cause, but we were experiencing some other
> trouble with darcs.net probably related to our gitit troubles.

There appears to be some kind of delay recently between a mailing
go to the bugs@ mailing list and it getting forwarded to the real
email address (which only accepts messages from bugs@, i.e. after
spam filtering).

I think this is not related to my messing around with statuses,
and that I ought to pick OSUOSL's brains on it.

The issue seems to have magically resolved itself

I found this while looking for something else.  It's closed, but it's
probably worth a comment in case it comes up again.

It might be because of client mis-configuration giving invalid mail
headers.  It happened to me a while ago because Return-Path (I think)
was bogus.  Mail typically got through to individual recipients but
was discarded by list software, and specifically bugs@darcs.net.

Thanks! Hope we'll find this in the archives next time :-)