On Mar 25, 2008, at 1:06 PM, Eino Tuominen wrote:
Mark Sapiro wrote:
Well, it does simplify the MTA's job. Instead of all that queueing
and retrying and such, you just have during SMTP (hold on a minute
while I attempt to deliver this to the next hop and return that result to you)*N, a system that doesn't seem to scale well. Either that or you just forget the concept that the originator of a message can ever be informed of a delivery problem.You are missing the point. Of course you can inform of a delivery problem, but only when you really need to do it. Every organisation should know of every recipient within their authority. You should know the recipient if you accept a message for delivery from outside your
domain.
But how would you scale that to the size of say... yahoo? Multiple
data centers around the world, all processing mail for different
domains under yahoo's control... How would one be able to synchronize
all that data from tons of different places like that?
-- Eino Tuominen
Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/japruim%40raoset.c...
Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
--
Jason Pruim Raoset Inc. Technology Manager MQC Specialist 3251 132nd ave Holland, MI, 49424-9337 www.raoset.com japruim@raoset.com