spamassassin-dev November 2011 archive
Main Archive Page > Month Archives  > spamassassin-dev archives
spamassassin-dev: [Bug 6701] masschecks seem to be blocked

[Bug 6701] masschecks seem to be blocked

From: <bugzilla-daemon_at_nospam>
Date: Tue Nov 15 2011 - 02:58:02 GMT
To: dev@spamassassin.apache.org

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6701

--- Comment #5 from John Hardin <jhardin@impsec.org> 2011-11-15 02:58:02 UTC ---
(In reply to comment #4)
> (In reply to comment #3)
> > spamassassin2.zones.apache.org doesn't appear to be able to send email to the
> > dev list. The logs seem to show the mail being accepted by apache's MX (manual
> > test message):
>
> Well, I guess your cron job didn't subscribe to the list. ;)

D'oh!

> > ...but the message never makes it to the list.
>
> They *would* have been held for moderation and handled by Sidney or me. This
> one just came in at 01:41:07 UTC. Mentioning here, but rejecting otherwise for
> now. No news.
>
> From: "Auto Mass-Check Daemon" <automc@ ...>
> Subject: WARN: SpamAssassin ruleqa: daemon on
> spamassassin2.zones.apache.org is down
>
> There have been NO such messages before, though. This one, about 2 hours old,
> is the first ever.
>
> Plus two test messages, sent from automc@ and jhardin@ at 01:49:44 and 01:55:59
> UTC respectively.

All of those were manual tests by me.

Yeah, I grepped the (big) sysloglog on sa2 and saw that nothing was going out
about the daemon the last few days. Troubleshooting. Not sure cron is actually
running automc's crontab. :(

Can you add automc on both the zone VMs as posting-only subscribers to the dev
list?

-- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.