ned freed writes: >> In many situations around the world in developing countries, it is >> totally impossible to send a 10MB e-mail because the link will be >> at least break once in the time it takes to send 10MB. As e-mail >> does not resume... > FWIW, RFC 1845 specifies such a mechanism for SMTP. There have been > few implementations, however. Yes, that's a pity. >> There are still many countries which only connection to the >> Internet is a 64kb/s and quite a lot which speed is below 512kb/s >> Developed countries and the IETF need to cater for these emerging >> nations to avoid the digital divide. The IETF has addressed these issues quite well I think, because the standards are there. The IETF doesn't really have a tradition of advocating the use of these standards to service providers. Maybe a job for ISOC (or the UN :-?. >> I think as yahoo being a major e-mail provider it would be good, >> that they become more responsible (they are actively fighting SPAM) >> and use ESMTP when sending their e-mails. It seems they do use >> ESMTP to receive e-mails... Their inbound mailers do support SIZE and also PIPELINING (see below), so yes, it would be nice if they honored your SIZE declaration when sending out messages. Have you tried to ask them why they don't? > ESMTP in general and the SIZE extension in particular do offer > some significant advantages in such situations. Also the PIPELINING extension extension (RFC 2197), which increases the chances for short messages to reach destinations over long and/or congested links. -- Simon. _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf