[Mimedefang] RE: MD and fetchmail

[Troy Carpenter]

I have been fighting this battle for some time.  In my case, almost all
my email coming in via fetchmail is SPAM, but since it is my ISP email
account, I get notifications from my ISP on that account and need it.
In my case, Spamassassin is running on these emails and marking them
correctly as SPAM.  Where I would like to beef this up is during
blacklist checking.

Since fetchmail injects the email into sendmail after fetching, in my
case the email appears to come from the loopback IP address.  You may
want to check that you don't have a line that skips Spamassassin if the
relay address is the loopback address (127.0.0.1).

This behavior also prevents the blacklists (Mimedefang and Spamassassin
rules) from seeing the original relay address since it is buried after
the loopback and my ISP's mail server address.  As a result, it is
possible for questionable SPAM to end up, albeit properly tagged, in my
mailbox.

I have yet to attempt to code a solution for this in mimedefang.  It
would involve searching through the received headers for the right one
and getting the IP address from it.

Troy


---- Original Message ----
I've been running MD with great success on my system for almost a year 
now, I still have one  thing that is puzzling me.  In addition to my 
normal incoming SMTP traffic, I run fetchmail to pull down mail from
some 
stray POP accounts.  That mail then runs through my local spooler into
my 
normal inbox.  However, I've noticed that a lot of spam is able to get 
through and it seems it is always the mail I get from fetchmail.  In 
scanning the headers, the X-Scanned-By header is there, but the no 
spamassassin.  If I export the message and hand run it through 
SpamAssassin, all the sirens go off.  My filter is almost stock with
minor 
additions on my end to drop spam messages with high scores so I don't
even 
have to deal with it at the MUA.  Anyone else see this before?