Something happened Tuesday night (maybe it was the flip from June to
July), but the anti-virus program that all mail runs through started
flagging everything as infected, and so nothing came through at all. I
have it set to write the mail to a file rather than dump it, so now I
have the task of sifting through over 2MB of mbox to figure out what
is good and what isn't. I probably won't get to it until Friday, so if
you've sent something to the list since yesterday, please re-send it
if you'd rather not wait for me to find it and re-post it to the list.
I've also noticed that this clogged some log files, and it will take
me a while to clean them up, so mail may be erratic for the near future.
-- Ed Leafe
Ed Leafe wrote:
> Something happened Tuesday night (maybe it was the flip from June to
> July), but the anti-virus program that all mail runs through started
> flagging everything as infected, and so nothing came through at all. I
> have it set to write the mail to a file rather than dump it, so now I
> have the task of sifting through over 2MB of mbox to figure out what
> is good and what isn't. I probably won't get to it until Friday, so if
> you've sent something to the list since yesterday, please re-send it
> if you'd rather not wait for me to find it and re-post it to the list.
Glad to know it wasn't me!
I noticed similar behavior on lists hosted at python.org, too. I host
some lists and they don't appear to have been affected. What anti-virus
are you using? I use clam, controlled by amavisd.
I'm willing to donate an hour or two to the cause of sifting through the
mail file if you want.
Paul
On Jul 2, 2009, at 11:02 AM, Paul McNett wrote:
> I noticed similar behavior on lists hosted at python.org, too. I host
> some lists and they don't appear to have been affected. What anti-
> virus
> are you using? I use clam, controlled by amavisd.
It's also clam. I haven't had time to investigate, but until I can
get it all working again, Windows users are going to have to protect
themselves. ;-)
-- Ed Leafe