Postfix "fatal" message with Amavis-new
Steve Jenkins
of my boxes running Postfix 2.6.5.
I'm now seeing this occasionally in the maillog:
Feb 14 20:42:47 carbonfiber postfix/smtp[19516]: fatal: garbage after
"]" in server description: [127.0.0.1] :10025
Feb 14 20:42:47 carbonfiber postfix/smtp[19517]: fatal: garbage after
"]" in server description: [127.0.0.1] :10025
Feb 14 20:42:47 carbonfiber postfix/smtp[19518]: fatal: garbage after
"]" in server description: [127.0.0.1] :10025
Feb 14 20:42:47 carbonfiber postfix/smtp[19519]: fatal: garbage after
"]" in server description: [127.0.0.1] :10025
Feb 14 20:42:48 carbonfiber postfix/qmgr[17204]: warning: private/smtp
socket: malformed response
Feb 14 20:42:48 carbonfiber postfix/qmgr[17204]: warning: transport
smtp failure -- see a previous warning/fatal/panic logfile record for
the problem description
Feb 14 20:42:48 carbonfiber postfix/master[10978]: warning: process
/usr/libexec/postfix/smtp pid 19516 exit status 1
Feb 14 20:42:48 carbonfiber postfix/master[10978]: warning:
/usr/libexec/postfix/smtp: bad command startup -- throttling
Feb 14 20:42:48 carbonfiber postfix/qmgr[17204]: warning: private/smtp
socket: malformed response
Feb 14 20:42:48 carbonfiber postfix/qmgr[17204]: warning: transport
smtp failure -- see a previous warning/fatal/panic logfile record for
the problem description
Feb 14 20:42:48 carbonfiber postfix/master[10978]: warning: process
/usr/libexec/postfix/smtp pid 19517 exit status 1
Feb 14 20:42:48 carbonfiber postfix/qmgr[17204]: warning: private/smtp
socket: malformed response
Feb 14 20:42:48 carbonfiber postfix/qmgr[17204]: warning: transport
smtp failure -- see a previous warning/fatal/panic logfile record for
the problem description
Feb 14 20:42:48 carbonfiber postfix/master[10978]: warning: process
/usr/libexec/postfix/smtp pid 19518 exit status 1
Feb 14 20:42:48 carbonfiber postfix/qmgr[17204]: warning: private/smtp
socket: malformed response
Feb 14 20:42:48 carbonfiber postfix/qmgr[17204]: warning: transport
smtp failure -- see a previous warning/fatal/panic logfile record for
the problem description
Feb 14 20:42:48 carbonfiber postfix/master[10978]: warning: process
/usr/libexec/postfix/smtp pid 19519 exit status 1
Port 10025 is stated in master.cf:
smtp-amavis unix - - n - 2 smtp
-o smtp_data_done_timeout=1200
-o smtp_send_xforward_command=yes
-o disable_dns_lookups=yes
-o max_use=20
127.0.0.1:10025 inet n - n - - smtpd
-o content_filter=
-o local_recipient_maps=
-o relay_recipient_maps=
-o smtpd_restriction_classes=
-o smtpd_delay_reject=no
-o smtpd_client_restrictions=permit_mynetworks,reject
-o smtpd_helo_restrictions=
-o smtpd_sender_restrictions=
-o smtpd_recipient_restrictions=permit_mynetworks,reject
-o smtpd_data_restrictions=reject_unauth_pipelining
-o smtpd_end_of_data_restrictions=
-o mynetworks=127.0.0.0/8
-o smtpd_error_sleep_time=0
-o smtpd_soft_error_limit=1001
-o smtpd_hard_error_limit=1000
-o smtpd_client_connection_count_limit=0
-o smtpd_client_connection_rate_limit=0
-o receive_override_options=no_header_body_checks,no_unknown_recipient_checks
And this is the content_filter line in main.cf:
content_filter = smtp-amavis:[127.0.0.1]:10024
It must be related to the content filter settings I just added. Anyone
familiar with how all these programs interact got any clues as to what
might be causing this error? Restarting Postfix seems to make the
errors stop for a while, but within a couple hours they are always
back.
Google produced a 2009 discussion on this discussion list re: a
similar error, but I didn't see any resolution. :(
Thanks,
SteveJ
Victor Duchovni
> I'm now seeing this occasionally in the maillog:
>
> Feb 14 20:42:47 carbonfiber postfix/smtp[19516]: fatal: garbage after
> "]" in server description: [127.0.0.1] :10025
You have a transport setting or FILTER action, ... that specifies
[127.0.0.1]:<SPACE>10024 as a nexthop. The error report is from
the smtp(8) delivery agent, which is trying to process the nexthop.
> Port 10025 is stated in master.cf:
The master.cf file is irrelevant.
> And this is the content_filter line in main.cf:
>
> content_filter = smtp-amavis:[127.0.0.1]:10024
This is a different port.
> It must be related to the content filter settings I just added. Anyone
> familiar with how all these programs interact got any clues as to what
> might be causing this error? Restarting Postfix seems to make the
> errors stop for a while, but within a couple hours they are always
> back.
No, it is related to either an exising transport(5) nexthop or access(5)
FILTER entry, or a past one recorded in a queue file (postsuper -r ALL
could help).
--
Viktor.
Steve Jenkins
<Victor....@morganstanley.com> wrote:
> On Mon, Feb 14, 2011 at 08:56:07PM -0800, Steve Jenkins wrote:
>
>> I'm now seeing this occasionally in the maillog:
>>
>> Feb 14 20:42:47 carbonfiber postfix/smtp[19516]: fatal: garbage after
>> "]" in server description: [127.0.0.1] :10025
>
> You have a transport setting or FILTER action, ... that specifies
> [127.0.0.1]:<SPACE>10024 as a nexthop. The error report is from
> the smtp(8) delivery agent, which is trying to process the nexthop.
Hi, Victor. Thanks for the prompt reply and your help, but I have to
admit that your reply went COMPLETELY over my head! But I'm gonna dive
back into the docs and Google using your reply in an attempt to learn
something. :)
Okey-dokey!
>> And this is the content_filter line in main.cf:
>>
>> content_filter = smtp-amavis:[127.0.0.1]:10024
>
> This is a different port.
Yes, it is - but I wanted to be complete in explaining the changes I
made to Postfix, just in case they affected anything. Although, this
is the port that your reply said was the nexthop (I'm looking that up
next to understand that better).
> No, it is related to either an exising transport(5) nexthop or access(5)
> FILTER entry, or a past one recorded in a queue file (postsuper -r ALL
> could help).
Ahhh - I think you may have just solved it. Could it have been an
earlier message that was received when I was tinkering with the
settings (and perhaps didn't have everything sorted yet) that was
sitting in the queue and repeating this error?
The postsuper flush worked (there were 14 messages that successfully
redelivered when I did that). I'm keeping an eye on the maillog since
doing that, and I'm not seeing the message re-occur!
Thanks,
SteveJ