T
Tomasz Chmielewski
I have this issue with Outlook 2003 from time to time - it seems to me
that Outlooks ignores the meaning of 5xx SMTP reply codes (permanent
failure), and tries to resend the message again. Although according to
RFCs, it shouldn't.
Here's what happens:
1. Clients attaches a 100 MB file and tries to send it in Outlook
2. SMTP server limit is 20 MB - so upon receiving, SMTP server replies
with a 552 error, and rejects the message.
3. Few minutes later, Outlook sends 100 MB again, it is rejected by the
SMTP server, Outlook sends it again, again, and so on.
What makes things worse, Outlook doesn't give any clear message that
sending the message has failed (at least, not clear to a non-technical
user).
Because of the above, bandwidth costs can go up in no time - just a few
users in a company which want to send a message bigger than allowed, and
Outlook will try to resend the message again and again, hour after hour,
day after day, until someone notices it.
Is there a fix for that in Outlook (or, perhaps - "enable
RFC-compliance" setting)?
that Outlooks ignores the meaning of 5xx SMTP reply codes (permanent
failure), and tries to resend the message again. Although according to
RFCs, it shouldn't.
Here's what happens:
1. Clients attaches a 100 MB file and tries to send it in Outlook
2. SMTP server limit is 20 MB - so upon receiving, SMTP server replies
with a 552 error, and rejects the message.
3. Few minutes later, Outlook sends 100 MB again, it is rejected by the
SMTP server, Outlook sends it again, again, and so on.
What makes things worse, Outlook doesn't give any clear message that
sending the message has failed (at least, not clear to a non-technical
user).
Because of the above, bandwidth costs can go up in no time - just a few
users in a company which want to send a message bigger than allowed, and
Outlook will try to resend the message again and again, hour after hour,
day after day, until someone notices it.
Is there a fix for that in Outlook (or, perhaps - "enable
RFC-compliance" setting)?