Tim Buck writes: > I installed 2.60 rc1 (upgraded from 2.55) yesterday afternoon. Two > of my users today reported several very obvious spam messages got > through; none has on my account. I looked at the offending messages, > and they had no SpamAssassin headers whatsoever; they, for whatever > reason, were not even processed through SA (we use Procmail on an > individual by individual basis to filter mail through SA). > > I couldn't find any reason for this change in behavior, and out of > 28 people who use SpamAssassin, only 2 reported this. I looked at > their .procmailrc and .spamassassin/user_prefs files and didn't > see anything out of the ordinary. > > I even had one user switch back to running spamassassin (the > standalone version) instead of spamc (the client-daemon version), > but it made no difference. > > So I've reverted back to SA 2.55. Anyone else see this behavior?
Sounds like the Dns.pm undefined value problem as well. that will crash if DNS lookups timeout it seems :( will be fixed in rc2, --j. ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0 _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
