Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Have this weird problem after amavis was triggered, mail vanished after cleanup.

Apr 11 15:45:28 smtp postfix/smtpd[19861]: DD66613C04A: client=SENDER.com[66.66.66.666] 

Apr 11 15:45:28 smtp postfix/smtpd[19861]: DD66613C04A: filter: RCPT from SENDER.com[66.66.66.666]: <ailyn@RECIPIENT>: Recipient address trig
gers FILTER smtp-amavis:[127.0.0.1]:10024; from=<tinkerbell@SENDER.com> to=<ailyn@RECIPIENT> proto=ESMTP helo=<mail.SENDER.com> 

Apr 11 15:45:28 smtp postfix/smtpd[19861]: DD66613C04A: filter: RCPT from SENDER.com[66.66.66.666]: <ana@RECIPIENT>: Recipient address trigge
rs FILTER smtp-amavis:[127.0.0.1]:10024; from=<tinkerbell@SENDER.com> to=<ana@RECIPIENT> proto=ESMTP helo=<mail.SENDER.com>

Apr 11 15:45:28 smtp postfix/smtpd[19861]: DD66613C04A: filter: RCPT from SENDER.com[66.66.66.666]: <ana@RECIPIENT>: Recipient address trigge
rs FILTER smtp-amavis:[127.0.0.1]:10024; from=<tinkerbell@SENDER.com> to=<ana@RECIPIENT> proto=ESMTP helo=<mail.SENDER.com>

Apr 11 15:45:28 smtp postfix/smtpd[19861]: DD66613C04A: filter: RCPT from SENDER.com[66.66.66.666]: <jtan@RECIPIENT>: Recipient address trigg
ers FILTER smtp-amavis:[127.0.0.1]:10024; from=<tinkerbell@SENDER.com> to=<jtan@RECIPIENT> proto=ESMTP helo=<mail.SENDER.com> 

Apr 11 15:45:29 smtp postfix/smtpd[19861]: DD66613C04A: filter: RCPT from SENDER.com[66.66.66.666]: <lina@RECIPIENT>: Recipient address trigg
ers FILTER smtp-amavis:[127.0.0.1]:10024; from=<tinkerbell@SENDER.com> to=<lina@RECIPIENT> proto=ESMTP helo=<mail.SENDER.com> 

Apr 11 15:45:29 smtp postfix/smtpd[19861]: DD66613C04A: filter: RCPT from SENDER.com[66.66.66.666]: <lovely@RECIPIENT>: Recipient address tri
ggers FILTER smtp-amavis:[127.0.0.1]:10024; from=<tinkerbell@SENDER.com> to=<lovely@RECIPIENT> proto=ESMTP helo=<mail.SENDER.com>

Apr 11 15:45:39 smtp postfix/cleanup[19711]: DD66613C04A: message-id=<43C3893998E1994B9F56FB6DD0652D1E26329F@mail.SENDER.com>

RBL configuration on postfix.

reject_rbl_client virus.rbl.jp
reject_rbl_client b.barracudacentral.org
reject_rbl_client cbl.abuseat.org
reject_rbl_client zen.spamhaus.org
reject_rbl_client rabl.nuclearelephant.com

No discard on amavis config.

#$final_virus_destiny      = D_DISCARD;
$final_banned_destiny     = D_PASS;
$final_spam_destiny   = D_PASS;
$final_bad_header_destiny = D_PASS;

Also if an RBL or amavis would block the message it should be logging its action.

Filtering via recipient access:

smtpd_recipient_restrictions = hash:/etc/postfix/recipient_access 

Recipient_access entry:

z.com FILTER smtp-amavis:[127.0.0.1]:10024
x.biz FILTER smtp-amavis:[127.0.0.1]:10024
share|improve this question
    
Can you post more information? Which addons are running with amavisd-new? There are any DISCARD rules in amavisd.conf? Are you using DNSRBL with DISCARD options within amavis scope? –  Vinícius Ferrão Apr 14 at 3:37
    
added some info. No rbls or discard on amavis. Also this should be logged if any. –  jmazaredo Apr 14 at 4:02
    
You see the mail being passed to amavisd on port 10024, you should then see amavisd re-inject the mail on port 10025 (or something similar). –  NickW Apr 14 at 8:34
    
no re-inject that is the final log "cleanup" –  jmazaredo Apr 14 at 9:01
    
What method are you using to inject mail into amavisd, content_filter? I see the cleanup after postfix accepts the TLS connection, it connects to localhost, then you see it re-injected afterwards. –  NickW Apr 14 at 9:23
show 3 more comments

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.