Michael,
> I guess I am still trying to figure out why small (under the size limit),
> not whitelisted, not exempt, not spam lovers, but is backscatter email is
> getting in with a 'Hits: -,' which means amavisd didn't even look at it.
>
> The only thing I can say for every email that got back in is that it is
> backscatter (and if amavisd new doesn't send it to SA, sa vbounce won't see
> it either), and that in the msgs.message-id field, amavisd is recording a
> '1' there. (and I don't see a one in the quarantined message, and I don't
> see duplicate message id's).
Oops, an ugly bug introduced with 2.6.2, turning all message IDs into a '1'
when stored to SQL log. Thanks! Here is a patch:
--- amavisd.orig 2008-12-15 01:50:09.000000000 +0100
+++ amavisd 2009-01-20 22:31:46.000000000 +0100
@@ -19179,5 +19179,5 @@
}
my($m_id) = $msginfo->get_header_field_body('message-id');
- $m_id = parse_message_id($m_id) if $m_id ne ''; # strip CFWS, take #1
+ $m_id = join(' ',parse_message_id($m_id)) if $m_id ne ''; # strip CFWS
my($subj) = $msginfo->get_header_field_body('subject');
my($from) = $msginfo->get_header_field_body('from'); # raw full field
> I don't know where to turn to look.
>
> (I guess a positive bounce_killer_score in amavisd.conf would TRY to add
> 100 points to them? Not subtract?)
Don't know what is the best way to clean up the mess in an SQL database now.
I believe turning all '1' in msgs.message_id into empty fields would work.
Thanks, and sorry for not picking this up sooner.
I'm fighting with Perl 5.8.9 problems.
Mark
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
