Someone in our company noticed that if a single address in the to was
invalid then coldfusion gets a 550 error from the smtp servers and
incorrectly interprets it as the whole e-mail is bad and don't send it.
We got this response from our E-Mail group in IT:
The problem is with Cold Fusion - not the infrastructure servers. When a
single address is rejected by the infrastructure servers with a 5xx SMTP
response code, Cold Fusion apparently (and incorrectly) takes that as a
failure of the whole message, and aborts the message. If Cold Fusion would
continue with the rest of the recipients and the message text, the message
would be sent to the rest of the users. You can test this by manually
telneting to port 25 on one of the e-mail (smtp) servers , pass the "helo"
and "mail from:" command, then some "rcpt to:" commands, with one of them
being <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED] (which should get your a 550
error), continue with the "data" command, then your message headers and
message and a "." to terminate the message. The valid recipients will
receive the message.
This is not the only problem I've seen with Cold Fusion not conforming to
the RFCs, by the way. We are regularly seeing messages from Cold Fusion
servers with invalid From-addresses. We reject the "mail from" with a 5xx
SMTP response which IS a permanent, fatal error for the entire message.
Instead of bouncing the message as it should, Cold Fusion seems to simply
leave the message in its spool and retry - sometimes as many as 100,000
times per day. Don't know if this is happening on all Cold Fusion servers,
or maybe there is a patch that some servers need to apply, or what, but if
anybody in the Cold Fusion world is familiar with this problem, I would be
most interested in hearing back.
Is it true that CFMX doesn't understand smtp responses properly? Is there a
hotfix for it?
Thanks,
Steve
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
