Ken Frisco
12-20-2001, 02:38 PM
I am unsuccessful in resolving this issue in MS Exchange 5.5 IMS.
This issue occurs on both of my servers hosting the IMS. Running MS Exchange 5.5 SP4 with the latest RPC, MTA, and IMS hot fix from MS.
Exchange 5.5 IMC Patch 2655.55, Exchange 5.5 MTA Patch 2654.89, Exchange 5.5 RPC Patch 2654.51
Situation:
I have 6 custom recipients for a licensee site in South America. I created a distribution list that contains the 6 custom recipients.
I send a message to the DL and the RFC-821 "sender" field is "<>". However, the RFC-822, contains the "From" address.
The problem does not occur if I explicitly address each recipient in the "To" field.
This is the response from the remote domain:
12-Dec-2001 13:48:29 Action: Message Delivery Attempt Failed To: id@idconsultores.com.ar SMTP ID: M2001121214352618921
Last Response: 552 5.7.1 SPAM trap -- too many recipients for an empty source address!
Here is the session log from the IMS: (RFC-821)
12/12/2001 1:48:05 PM : <<< 250 smtpint.millwardbrown.com Hello
12/12/2001 1:48:05 PM : >>> MAIL FROM:<>
12/12/2001 1:48:05 PM : <<< 250 <>... Sender ok <--------Notice the sender field. It is blank...This is bad.
12/12/2001 1:48:05 PM : >>> RCPT TO:<fgiordano@idconsultores.com.ar>
12/12/2001 1:48:05 PM : <<< 250 <fgiordano@idconsultores.com.ar>... Recipient ok
12/12/2001 1:48:05 PM : >>> RCPT TO:<gces@idconsultores.com.ar>
12/12/2001 1:48:05 PM : <<< 250 <gces@idconsultores.com.ar>... Recipient ok
12/12/2001 1:48:05 PM : >>> RCPT TO:<lwaissmann@idconsultores.com.ar>
12/12/2001 1:48:05 PM : <<< 250 <lwaissmann@idconsultores.com.ar>... Recipient ok
12/12/2001 1:48:05 PM : >>> RCPT TO:<ririarte@idconsultores.com.ar>
12/12/2001 1:48:05 PM : <<< 250 <ririarte@idconsultores.com.ar>... Recipient ok
12/12/2001 1:48:05 PM : >>> RCPT TO:<jfaparicio@idconsultores.com.ar>
12/12/2001 1:48:06 PM : <<< 250 <jfaparicio@idconsultores.com.ar>... Recipient ok
12/12/2001 1:48:06 PM : >>> RCPT TO:<id@idconsultores.com.ar>
12/12/2001 1:48:06 PM : <<< 250 <id@idconsultores.com.ar>... Recipient ok
12/12/2001
Any help to resolve this issue would be appreciated.
This issue occurs on both of my servers hosting the IMS. Running MS Exchange 5.5 SP4 with the latest RPC, MTA, and IMS hot fix from MS.
Exchange 5.5 IMC Patch 2655.55, Exchange 5.5 MTA Patch 2654.89, Exchange 5.5 RPC Patch 2654.51
Situation:
I have 6 custom recipients for a licensee site in South America. I created a distribution list that contains the 6 custom recipients.
I send a message to the DL and the RFC-821 "sender" field is "<>". However, the RFC-822, contains the "From" address.
The problem does not occur if I explicitly address each recipient in the "To" field.
This is the response from the remote domain:
12-Dec-2001 13:48:29 Action: Message Delivery Attempt Failed To: id@idconsultores.com.ar SMTP ID: M2001121214352618921
Last Response: 552 5.7.1 SPAM trap -- too many recipients for an empty source address!
Here is the session log from the IMS: (RFC-821)
12/12/2001 1:48:05 PM : <<< 250 smtpint.millwardbrown.com Hello
12/12/2001 1:48:05 PM : >>> MAIL FROM:<>
12/12/2001 1:48:05 PM : <<< 250 <>... Sender ok <--------Notice the sender field. It is blank...This is bad.
12/12/2001 1:48:05 PM : >>> RCPT TO:<fgiordano@idconsultores.com.ar>
12/12/2001 1:48:05 PM : <<< 250 <fgiordano@idconsultores.com.ar>... Recipient ok
12/12/2001 1:48:05 PM : >>> RCPT TO:<gces@idconsultores.com.ar>
12/12/2001 1:48:05 PM : <<< 250 <gces@idconsultores.com.ar>... Recipient ok
12/12/2001 1:48:05 PM : >>> RCPT TO:<lwaissmann@idconsultores.com.ar>
12/12/2001 1:48:05 PM : <<< 250 <lwaissmann@idconsultores.com.ar>... Recipient ok
12/12/2001 1:48:05 PM : >>> RCPT TO:<ririarte@idconsultores.com.ar>
12/12/2001 1:48:05 PM : <<< 250 <ririarte@idconsultores.com.ar>... Recipient ok
12/12/2001 1:48:05 PM : >>> RCPT TO:<jfaparicio@idconsultores.com.ar>
12/12/2001 1:48:06 PM : <<< 250 <jfaparicio@idconsultores.com.ar>... Recipient ok
12/12/2001 1:48:06 PM : >>> RCPT TO:<id@idconsultores.com.ar>
12/12/2001 1:48:06 PM : <<< 250 <id@idconsultores.com.ar>... Recipient ok
12/12/2001
Any help to resolve this issue would be appreciated.