'Pull' is relevant within the context of obtaining content from sources
that
you regularly receive content from, it is not a generic email
replacement
protocol.
Sure, I don't really see how fiddling SMTP to allow envelope (+some
headers?) and body to be transported separately - which is what this would
boil down to -
if this is what you think then you have missed the point
the point is the recipients server then retrieves the email body **if** it
passes initial tests (less load on network)
such as the class is acceptable, the origin (country?) is acceptable.
the act of retrieving the mail is in fact a verification of the identity of
the source server
it is this verification that holds the most power. spammers will find it
much harder to hide behind falsified information
if they do their ISP becomes ultimately responsible for allowing them to
spam the network
can have any real advantage. As Phillip suggests, existing
pull protocols can be very useful for certain application swhich currently
use SMTP, "mailing lists" /discussion groups for instance. This is also
done with POP, IMAP and HTTP of course.
not relevant
--
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg