Repeating messages with "response to dot-stuffed message expected"
Hi,
one of my users getting "response to dot-stuffed message expected" after having sent an outgoing message to someone else. However, the recipient started complaining about a number of same messages arriving arriving at their site. I check the queue, and deleted it off the queue. Then, it stopped. I reviewed some other forum questions here on the same subject. But, it never mentioned how to deal with that? What am I supposed to do; wait until somebody starts complaining about that. Is there any kind of configuration option that I can say like after the third failed attemp of that type then never try more!
Thanks,
Rami
[652 byte] By [
ramia] at [2007-11-26 18:37:56]

# 1
Hi,
> one of my users getting "response to dot-stuffed
> message expected" after having sent an outgoing
> message to someone else.
This means the connection was prematurely terminated/or hung at the end of the data section. Messaging server sends a '.\r\n' to complete the end of the data segment, and expects a 250 OK back from the destination mail server to confirm that the email has been delivered. If it doesn't receive this in time, the connection is closed and the email is requeued for delivery.
This problem can occur when there is a problem at the destination server end, e.g. slow virus scanning (if they scan/before/accept), slow disk issues etc.
> However, the recipient
> started complaining about a number of same messages
> arriving arriving at their site.
The problem is at their end. Since we couldn't confirm delivery of the email, we resend later. This is the only thing we can do... this can lead to duplicate copies.
> I check the queue,
> and deleted it off the queue. Then, it stopped. I
> reviewed some other forum questions here on the same
> subject. But, it never mentioned how to deal with
> that?
Get the destination server admins to fix their system.
> What am I supposed to do; wait until somebody
> starts complaining about that. Is there any kind of
> configuration option that I can say like after the
> third failed attemp of that type then never try
> more!
You can reduce the time window that email delivery is re-attempted before being discarded as undeliverable, but this is a global setting, so you may be shooting yourself in the foot by changing this. A better option is to get the destination server to fix their system.
Regards,
Shane.