Well, from that description I would assume the fault is at the destination
server.
The only odd thing is a failure of this sort would normally result in
automatic retries so should mostly go un-noticed. Is that not occurring?
If not send me a more complete copy of the bounce and log entries from msg*.log
so I can see exactly why it's not retrying.
surgemail-support <surgemail-support@netwinsite.com> wrote:
Chris,
Thank you for the prompt follow-up. This is what we have seen in testing:
1) Send the same message via another system
*We have only one secure mail system we use for partner communication, we
have been able to send the same message either later in the day or through a
different user account when we get the connection closed error. Therefore I
don't think it's problem with the message itself.
2) send the same message to a different destination user on the same
domain
*Usually the messages are addressed to 5 or more users at the destination
host, delivery fails to all of the users.
3) send the same message to a different domain.
* Internal accounts are always cc'd on outgoing messages and we have no
issue receiving these messages internally. Also when cc'ing a gmail account
delivery is successful.
I upgraded Surgemail to latest stable release about a month ago and it
has not resolved this issue.
Thank you very much for your time and attention to this matter.
Best,
Ian
