Hi Ken,
Sorry, I meant what do you think I should do next to try to track down
the source of the spam I can see in the server logs?
Perhaps I can add to what Stefano has said already.
I think you are probably worrying unnecessarily. It is quite normal to
see spam get accepted in your log files. It only truly becomes spam if
James then delivers the queued email to someone's account rather than
killing it somewhere further down the pipeline.
By way of example let's track a recent spam email through my system (for
security I've renamed my actual domain to mydomain.co.uk to avoid blushes).
Looking in my smtpserver-2009-07-25-00-03.log file the first entry I see
is...
25/07/09 00:03:27 INFO smtpserver: Connection from 201.2.193.95
(201.2.193.95)
25/07/09 00:03:31 INFO smtpserver: Successfully spooled mail
Mail1248476610881-182307 from [email protected] on
201.2.193.95 for [[email protected]]
So... at first glance it looks like a spam email has been successfully
received by James and the spammers have won. But this is only half the
story because it hasn't actually been dropped into anyone's mailbox
yet. What you should do now is search your recent log files to see what
happened to this spooled email. In my case since I have the Bayesian
analysis filter setup I notice the following entry in the mailet log
file (mailet-2009-07-25-00-03.log) just after the spam message was
spooled: -
25/07/09 00:03:33 INFO James.Mailet: BayesianAnalysis:
X-MessageIsSpamProbability: 100%; From: [email protected];
Recipient(s): [[email protected]]
From this I know that the email would be ghosted (destroyed) because
that's how I set up the pipeline.
I hope that helps.
Regards,
David Legg
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
