-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thank you, that appears to have done the trick.
I was getting filled up with a new spam, producing the same type of message, but adding that line to fetchmailrc did the trick. It is gone. I was getting quite angry and frustrated with this nonsense. Until a few days ago, I didn't receive any sort of message like this. Spam came in and was dumped into /dev/null via spamd and procmail. Nothing was getting through. These messages weren't getting through, per se, but they were certainly causing just as much problems as normal spam by filling my box with error messages. What's up with the misconfigured messages all of a sudden? Why wouldn't I have run into this before now? Is something new going on (the originating IP was completely different, as was the Subject, than the previous viagra garbage) On Monday 20 October 2003 08:49 am, Bryan Phinney wrote: > On Monday 20 October 2003 09:11 am, Praedor Atrebates wrote: > <snipped> > > Okay, we don't see the Postfix error code but based upon the text of the > message, my guess is that Postfix is rejecting this message upon the > delivery attempt by Fetchmail, fetchmail is then sending a failure message > to let you know but the message is not being deleted so upon the next poll > attempt, it tries to deliver the message again. > > The fetchmail log should be telling you what the error code is from Postfix > but if I had to guess, I would say it is a 501, fetchmail normally counts > 55? codes as spam rejects by default. [...] - -- "Our ship is in the hands of pilots who are steering directly under full sail for a rock. The whole crew may see this course to violate our liberties in full view if they look the right way." - --Samuel Adams, 1771 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/lATRaKr9sJYeTxgRAgZcAJ47HY0Hu5Mw5Pi/Hcgw3qWy3540yQCgn6yh EA+nw2VbFFmOhU2ta0x/IoE= =JDnX -----END PGP SIGNATURE-----
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
