--Todd D. VanderVeen wrote on 28.01.2002 13:11 -0700: [...] > 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
Disable the 'fixup' (transparent streammunging) at the PIX: However, be warned that this will disable the PIX firewall's capability to filter ESMTP commands. When fixup is enabled the PIX will only permit the basic SMTP commands specified in RFC 821 to reach your mail server. Anything else is answered by the PIX with the "500 command unrecognized message" to the client and then the PIX sends the server an altered SMTP packet with xxxx in place of the actual command. ESPTM (RFC 1869) is filtered because it may allow some fairly powerful commands to be executed on your mail server that are unecessary for typical internet email exhanges. Someone else may be able to elaborate on the risk of allowing ESMTP, but one example is the VRFY command which will tell the client whether a user account actually exists on the server and sometimes replies with the user's full name. Roland _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
