Re: scanned several times

Tom Hendrikx <[email protected]> Tue, 06 May 2014 09:30:23 +0200
Newsgroups	gmane.mail.spam.dspam.user
Message-ID	<[email protected]>
On 05/05/2014 07:31 PM, Rick Leir wrote:
> This is what I think is happening. The incoming message was scanned by
> dspam several times, once before it got to our internal mailing list,
> and secondly after the mailing list sent it to me.  Now it has 2 sets of
> dspam headers.
> 
> X-DSPAM-Signature: 5367c3d722001198720193
> ...
> X-DSPAM-Signature: 5367c3de22001657727144
> 
> Now when I retrain the message, and dspam should be looking for nn7144
> in my account, instead dspam looks for nn0193 which is not in my account
> (it is in the account for the mailing list).  The log gets this:
> 
> May  5 13:02:59 hera dspam[2200]: Signature retrieval for
> '5367c3d722001198720193' failed
> 
> We are using Postfix to pipe messages to dspam, and I will look at the
> Postfix doco to help me configure it right, so dspam only sees messages
> when they are going to a real user. 
> 
> Another option would be that dspam could look at all the signatures, not
> just the first one.
> 
> Another option is that dspam could know when it is scanning a message
> destined for a mailing list, and not add headers at that time.
> Thanks
> Rick
> 
> Rick Leir, Senior Developer
> http://CirrusComputing.com/ 
> 


Typically, the mailing list functionality and the end-user funcionality
should be separated. When an incoming message to the mailing list enters
your mail stack, it should be scanned, and if it's spam, it should not
be sent to the mailing list users. typical mailing ;list behaviour. You
can retrain if it was a FP by using that available header. So far so
good for mailing list functionality.

Then the mailing list mail should be sent to end users. If the end user
is using a spam filtering engine (f.i. dspam), the mail server should
make sure to remove stuff that will confuse the filtering process.
Typically, you should remove any dspam (signature) header from incoming
messages, since they aren't added by your setup. I use postfix header
checks to rename DSPAM headers to X-External-Dspam-blahblah to make sure
they don't mess up my system. You should also do this before the mailing
list gets external mail, since some people setup DSPAM for outgoing mail
too, but still add headers.

When you've setup both functionalities in one postfix config, you'd
better be splitting that up. F.i. using a multi instance setup in
Postfix, thus having a dedicated mailing list instance.

Regards,
	Tom

------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
&#149; 3 signs your SCM is hindering your productivity
&#149; Requirements for releasing software faster
&#149; Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce

_______________________________________________
Dspam-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspam-user
signature.asc (application/pgp-signature, 884 B)