On Mon, Feb 14, 2011 at 9:01 PM, Victor Duchovni <victor.ducho...@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. :) >> Port 10025 is stated in master.cf: > > The master.cf file is irrelevant. 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
