Daniel, > Please help me to understand what are the various reasons for this error. > > In our infrastructure, only few mails get stuck in deferred Q and it > remains in the Q even after 2/3 days.
> We have postfix node in which we configured amavisdfeed (in main.cf) > as content_filter=amavisfeed:[127.0.0.1]:10024 > the amavisd version we use is amavisd-new-2.6.4 (20090625) > $notify_method = 'smtp:[127.0.0.1]:10025'; > $forward_method = 'smtp:[127.0.0.1]:10030'; > > Jul 5 22:22:27 myHostMachine amavis[24264]: (24264-18) > Negative SMTP response to data-dot (<[email protected]>): > Jul 5 22:22:27 myHostMachine amavis[24264]: (24264-18) > (!)FWD via SMTP: <[email protected]> -> > <[email protected]>,BODY=7BIT > 451 4.5.0 No resp. to data-dot, id=24264-18, from MTA([127.0.0.1]:10030): > Yes, we have a custom program that listen to 10030 which consume the > messages. Looks like you custom program on port 10030 is not responding (or not responding in time) after being fed a message and a terminating dot. If you have such messages stuck in a queue (so this problem is repeatable at will by a 'postfix flush'), then either enable debugging in your custom program, or capture a TCP traffic (tcpdump -i lo0 -s 0 -w 0.log 'tcp port 10030') and examine what happened in an SMTP session with wireshark. Mark
