12 Jul 2010 23:19
Re: MSA not requiring SMTP AUTH on SMTP (HELO)
> I was doing some log parsing and noticed something odd. On our MSA > service, we want to require SMTP AUTH over an encrypted channel for any > and all connections. All seemed to be working well, until I saw the > following log entry: > 12-Jul-2010 08:23:32.82 4753.0dd1.8106 tcp_submit tcp_meritmail EES 5 local.user1@... rfc822;local.user2@... user2@... 20 /opt/sun/comms/messaging64/data/queue/tcp_meritmail/012/ZZh034G29rfhp.00 0L5G00ETQ2F73750@... <1B748474396348DE959D15DE907ABDCB <at> Staff001> sunmsg Staff001 (ceas145-NNN.ceas.wmich.edu [141.218.145.NNN]) -1 3 'spamfilter1:YiLYDO1a17P5DQUg2DzbXw==, addheader, keep' 0 > Where is the A modifier code? There isn't one because authorization wasn't used. According to the configuration material you provided, you don't require authentication on tcp_sibmit, so... > Here is the slave log entry.... > 08:23:31.93: Sending : "220 smtp.wmich.edu -- Server ESMTP (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 64bit))" > 08:23:31.93: Received : "EHLO Staff001" Note the use of EHLO here. The fact this command was given and accepted makes this an ESMTP connection.(Continue reading)
RSS Feed