A spammer could forge those headers and sneak it in. They use the same tactics with other anti-spam solutions.
Dont NP against anti-spam headers. Use something like this: (content|report)\-type(=|:).?((message\/|)(delivery\-|disposition\-|report)(notification|status|))# notification catch-all There are more things you can do, but this is a good core regex to use against automated response messages. Doug Traylor wrote: >> Suppose a client set an autoresponder . If the autoresponder reply the >> spammer , assp will whitelist the spammer ? Is it correct ? Any solution ? >> > > Since the email has passed through ASSP once and now has my ASSP headers, I > simply look for one of those headers in my np list and it gets skipped going > back out. The advantage of the NP list vs. the RedRE is that the outgoing > email, which has already been seen once and processed by ASSP coming in, > will not get added to my not-spam corpus. > > Doug > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Assp-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/assp-user > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
