RE: Missing smtp delivery log event with smtp_tls_loglevel = 3
- This was right on. Thanks Wietse.
The rsyslogd service had rate limiting enabled by default and the log
lines were getting dropped.
I fixed it by adding the following line to /etc/rsyslog.conf
$SystemLogRateLimitInterval 0 # turn off rate limiting
Senior Systems Engineer, NOC | Next Jump, Inc.
One Kendall Square, STE B2401, Cambridge, MA 02139
P: 617.682.4660 x5574 24/7: 617-682-4665
agage@... | oo.com
Check out our culture video http://nxj.me/nextjump
From: wietse@... [mailto:wietse@...]
Sent: Wednesday, January 30, 2013 5:27 PM
To: Asa Gage
Subject: Re: Missing smtp delivery log event with smtp_tls_loglevel = 3
> I seem to be missing smtp log events regarding delivery status for TLSsyslog uses a connection-less transport. The more logging you turn on,
> enabled mail when smtp_tls_loglevel = 3. I see a ton of TLS data as
> expected, but the actual smtp result is no longer present. Is there
> any explanation for this behavior?
the more events will be lost.
- On Fri, Feb 01, 2013 at 10:39:31AM -0500, Asa Gage wrote:
> This was right on. Thanks Wietse.Still you never need a tls log level greater than 2 when doing
> The rsyslogd service had rate limiting enabled by default and the log
> lines were getting dropped.
> I fixed it by adding the following line to /etc/rsyslog.conf
> $SystemLogRateLimitInterval 0 # turn off rate limiting
trouble-shoots or 1 in production. Log levels 3 and 4 are for
packet-level SSL traffic debugging by Postfix developers, to
diagnose potential issues in the SSL I/O plumbing, not for
general use. If you want to capture traffic, it is better
to use tcpdump not syslog.
While you may not want to have rate limits on syslog for other
reasons, the fix for this problem is to not set a tls log level of
3 or more in either the SMTP client or server.