![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
SMTP is successful because it is simple. Make it too complex, and you make it difficult to send even the simplest messages, and you make interoperability a bit more challenging. I propose: If an SMTP server can't or won't handle a message with a large attachment, then it should (1) drop the attachment, (2) replace it with a message that a large attachment had to be dropped, and (3) maybe also insert a suggestion on how the attachment could be transferred (use FTP, or use compression). The message would still make it to the recipient, but without the attachment. The SMTP server should send a message (a DSN maybe ?) back to the sender to tell him the attachment had to be dropped. Then: The sender and recipient will likely contact each other and find a way to get the large file transferred. There are Web sites that allow individuals to upload files for others to retrieve. If it's really important for individuals to transfer large files, they will find a way. Also: As the capabilities of the technology advances, the limit will be expected to increase, but without any centrally recommended "guideline", which would be a moving target. -- Doug Sauder
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.