Sam and others, 

 Below is a further sampling from my logs or a recurring ESMTP 502 error. Of 
note is the same attempted command XXXX. The listed servers are typically 
running various versions of sendmail (typically 8.12.1) or MS. Is this 
commonly seen by anyone else? I am convinced this is a problems with these 
remote servers. But the idea of putting the onus on them to fix things is 
unpalatable to my employeer. Can anyone else verify seeing this in there 
logs, or offer suggestions on how to build my case? 

Jan 27 04:03:23 reckoning courieresmtpd: 
error,relay=::ffff:24.29.99.226,msg="502 ESMTP command error",cmd: XXXX 
nycsmtp1out.rdc-nyc.rr.com 

Jan 27 04:09:06 reckoning courieresmtpd: 
error,relay=::ffff:128.100.10.141,ident="root",msg="502 ESMTP command 
error",cmd: XXXX picton.eecg.toronto.edu 

Jan 27 04:19:49 reckoning courieresmtpd: 
error,relay=::ffff:38.151.68.98,msg="502 ESMTP command error",cmd: XXXX 
ny001.mgusa.com 

Jan 27 04:20:38 reckoning courieresmtpd: 
error,relay=::ffff:128.121.122.47,msg="502 ESMTP command error",cmd: XXXX 
s0244.pm0.net 

Jan 27 04:23:06 reckoning courieresmtpd: 
error,relay=::ffff:143.166.224.253,msg="502 ESMTP command error",cmd: XXXX 
smtp3.us.dell.com
 


Todd D. VanderVeen writes: 

>> Jan 27 08:06:26 reckoning courieresmtpd: started,ip=[::ffff:129.46.64.204]   
>> 
>> Jan 27 08:06:26 reckoning courieresmtpd: 
>> error,relay=::ffff:129.46.64.204,msg="5
>> 02 ESMTP command error",cmd: XXXX warlock.qualcomm.com 
>> 
>> Jan 27 08:06:34 reckoning courieresmtpd: 
>> error,relay=::ffff:129.46.64.204,msg="5
>> 02 ESMTP command error",cmd: XXXXXXXX   
>> 
>> My understanding is as follows. On connecting, a server may attempt
>> various extended smtp commands. A 502 error indicates that while the 
>> server understands esmtp, the particular command is unimplemented. The

>Not exactly.  ESMTP command capabilities are determined from the EHLO 
>response.  
>
>The 502 error indicates that the command received from the client is not a 
>valid ESMTP command.  Certainly there is no such command called 'XXXXXXXX' 
>or 'XXXX' in either the base SMTP protocol, nor any common extension. 
>
>-- Sam 
 

Regards,
Todd VanderVeen
PartNET Systems Manager
801-891-0741

_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to