Good Day,
The question is quite straight forward. What should be a best practice to time out a SMTP connection on the RECEIVING side?
Background: We are currently having an issue with a sender that takes 10 minutes to send us an email of about 10 MB. So obviously it is quite slow. Why it is slow, We do not know as we are not in contact with the sender directly (And I'm fairly sure that their IT is gonna turn around and ignore the issue).
We are currently configured to time-out an email if it takes more than 10 minutes to be completed. If it takes 11 minutes, it will be tempfailed and return it to the sender saying that the service was not available and they have to retry.
During the connection there is constant packet transfer, so it's not like the communication gets broken or anything, if we would just raise the time-out from 10 to 20 minutes for example, I'm fairly sure we'd have more successful emails then temp-failed.
Is this a problem? What would be the best practice? We treat millions of emails where I work. So I am fighting with the department that has this configuration in their, because they are scared of the "impact" overall.
But in reality the impact could only be minimal as our receiving mail servers would still treat other emails while waiting for those "20 minutes" to be over. It's not like it will cause a traffic jam as it's only a few emails per day, and many of those are RETRIES from the earlier failures.