Re: Postfix log content
On 05/02/16 13:58, Darac Marjal wrote: On Thu, Feb 04, 2016 at 05:28:54PM +, Tony van der Hoff wrote: Hi, Running Postfix under Jessie. At some time in the past I managed to increase the logging verbosity to track down a problem, which I've solved. I now have a vast amount of data in mail.log, which is obscuring useful messages. I thought it was simply a matter of adding or removing "-v" to the service configuration stanzas in /etc/postfix/master.cf, but on reviewing that file, I see no instances of -v, e.g, smtp inetn-n--smtpd The logged data even includes users passwords in clear, as well as 20-odd lines for each email received (sample attached). Can anyone please suggest any other places to look to reset the default log level This doesn't look like verbose logging to me. I think the problem is just that you have a complex chain of processes for the message to pass through. bendel.d.o connects to you, the message is passed by the greylisting daemon postgrey and is accepted by your system. The message is then forwarded to amavis. At that point postfix is finished with that message. Amavis now checks the message and pronounces it clean. Amavis now connects back to postfix and passes the approved message back in. Postfix delivers the message to the SECOND delivery agent (virtual), which delivers it to your maildir. If you like, you could look at making amavis into what postfix calls a "Before Queue Filter" (and which everyone else calls a milter). There is an amavisd-milter package which will help with that. Basically, instead of accepting the message and THEN checking it for viruses, the message is passed through amavis DURING the smtp session. Postfix will only accept the message if amavis approves it, otherwise the remote host will be told that the message is rejected. This is a nicer solution all around, but it does mean that SMTP sessions will take longer. That is, you might not be able to accept as much mail as you would be able to using amavisd's batch mode. Thanks for he advice; I'll look into it. -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: Postfix log content
On Thu, Feb 04, 2016 at 05:28:54PM +, Tony van der Hoff wrote: Hi, Running Postfix under Jessie. At some time in the past I managed to increase the logging verbosity to track down a problem, which I've solved. I now have a vast amount of data in mail.log, which is obscuring useful messages. I thought it was simply a matter of adding or removing "-v" to the service configuration stanzas in /etc/postfix/master.cf, but on reviewing that file, I see no instances of -v, e.g, smtp inet n - n - - smtpd The logged data even includes users passwords in clear, as well as 20-odd lines for each email received (sample attached). Can anyone please suggest any other places to look to reset the default log level This doesn't look like verbose logging to me. I think the problem is just that you have a complex chain of processes for the message to pass through. bendel.d.o connects to you, the message is passed by the greylisting daemon postgrey and is accepted by your system. The message is then forwarded to amavis. At that point postfix is finished with that message. Amavis now checks the message and pronounces it clean. Amavis now connects back to postfix and passes the approved message back in. Postfix delivers the message to the SECOND delivery agent (virtual), which delivers it to your maildir. If you like, you could look at making amavis into what postfix calls a "Before Queue Filter" (and which everyone else calls a milter). There is an amavisd-milter package which will help with that. Basically, instead of accepting the message and THEN checking it for viruses, the message is passed through amavis DURING the smtp session. Postfix will only accept the message if amavis approves it, otherwise the remote host will be told that the message is rejected. This is a nicer solution all around, but it does mean that SMTP sessions will take longer. That is, you might not be able to accept as much mail as you would be able to using amavisd's batch mode. -- For more information, please reread. signature.asc Description: PGP signature
Postfix log content
Hi, Running Postfix under Jessie. At some time in the past I managed to increase the logging verbosity to track down a problem, which I've solved. I now have a vast amount of data in mail.log, which is obscuring useful messages. I thought it was simply a matter of adding or removing "-v" to the service configuration stanzas in /etc/postfix/master.cf, but on reviewing that file, I see no instances of -v, e.g, smtp inet n - n - - smtpd The logged data even includes users passwords in clear, as well as 20-odd lines for each email received (sample attached). Can anyone please suggest any other places to look to reset the default log level -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England | Feb 4 17:15:20 shell postfix/smtpd[6383]: connect from bendel.debian.org[82.195.75.100] Feb 4 17:15:21 shell postgrey[3528]: action=pass, reason=client whitelist, client_name=bendel.debian.org, client_address=82.195.75.100, sender=bounce-debian-user=lists_0711=vanderhoff@lists.debian.org, recipient=lists_0...@vanderhoff.org Feb 4 17:15:21 shell postfix/smtpd[6383]: 1F3CE1BE17E: client=bendel.debian.org[82.195.75.100] Feb 4 17:15:21 shell postfix/cleanup[6388]: 1F3CE1BE17E: message-id=<1756206109536220492378@MUZAMMIL> Feb 4 17:15:21 shell postfix/cleanup[6388]: 1F3CE1BE17E: resent-message-id= Feb 4 17:15:21 shell postfix/qmgr[2749]: 1F3CE1BE17E: from=, size=5976, nrcpt=1 (queue active) Feb 4 17:15:21 shell postfix/smtpd[6383]: disconnect from bendel.debian.org[82.195.75.100] Feb 4 17:15:21 shell amavis[4031]: (04031-10) ESMTP::10024 /var/lib/amavis/tmp/amavis-20160204T160507-04031-8mnMqrol: -> SIZE=5976 Received: from shell.localdomain ([127.0.0.1]) by localhost (shell.vanderhoff.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP for ; Thu, 4 Feb 2016 17:15:21 + (UTC) Feb 4 17:15:21 shell amavis[4031]: (04031-10) Checking: whMYrWSbGD5d [82.195.75.100] -> Feb 4 17:15:22 shell postfix/smtpd[6393]: connect from localhost[127.0.0.1] Feb 4 17:15:22 shell postfix/smtpd[6393]: 4CCBB1BEE6F: client=localhost[127.0.0.1] Feb 4 17:15:22 shell postfix/cleanup[6388]: 4CCBB1BEE6F: message-id=<1756206109536220492378@MUZAMMIL> Feb 4 17:15:22 shell postfix/cleanup[6388]: 4CCBB1BEE6F: resent-message-id= Feb 4 17:15:22 shell postfix/smtpd[6393]: disconnect from localhost[127.0.0.1] Feb 4 17:15:22 shell amavis[4031]: (04031-10) FWD from -> ,BODY=7BIT 250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 4CCBB1BEE6F Feb 4 17:15:22 shell amavis[4031]: (04031-10) Passed CLEAN {RelayedInbound}, [82.195.75.100]:40280 [125.209.79.51] -> , Queue-ID: 1F3CE1BE17E, Message-ID: <1756206109536220492378@MUZAMMIL>, Resent-Message-ID: , mail_id: whMYrWSbGD5d, Hits: -6.91, size: 5974, queued_as: 4CCBB1BEE6F, 1188 ms Feb 4 17:15:22 shell postfix/smtp[6390]: 1F3CE1BE17E: to=, orig_to=, relay=127.0.0.1[127.0.0.1]:10024, delay=1.4, delays=0.13/0.03/0/1.2, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 4CCBB1BEE6F) Feb 4 17:15:22 shell postfix/qmgr[2749]: 4CCBB1BEE6F: from=, size=6175, nrcpt=1 (queue active) Feb 4 17:15:22 shell postfix/qmgr[2749]: 1F3CE1BE17E: removed Feb 4 17:15:22 shell postfix/virtual[6394]: 4CCBB1BEE6F: to=, relay=virtual, delay=0.17, delays=0.13/0.01/0/0.03, dsn=2.0.0, status=sent (delivered to maildir) Feb 4 17:15:22 shell postfix/qmgr[2749]: 4CCBB1BEE6F: removed