Robert Breithuber schrieb: > i have lots of entries in ..mailman/logs/smtp-failure like this: > > Jan 27 22:26:39 2004 (29932) delivery to [EMAIL PROTECTED] failed with code > 450: <[EMAIL PROTECTED]>: Recipient address rejected: Domain not found
Makes sense: | [EMAIL PROTECTED] thomas]$ host sushu.net | Host sushu.net not found: 2(SERVFAIL) | [EMAIL PROTECTED] thomas]$ host -t mx sushu.net | Host sushu.net not found: 2(SERVFAIL) Seems the DNS-service for sushu.net is down and does not reply to queries. > since weeks now every 15min (!) Yes. "450" is a *temporary* failure, so Mailman or your MTA will try again to deliver the mail. It will do it every x minutes or hours (as it was configured), and it will try it x days long (as it was configured) before bouncing the mail as undeliverable. > any ideas what may go wrong? is this not a case for bounce processing? No, not yet. If a mail can temporarily not be delivered, delivery is tried again and again (normally the retry time is becoming longer after each failure) until a time limit of about four days is reached. The mail is finally bounced then. Perhaps sushu.net will be able to fix it DNS before the timeout - then all mail will be delivered there, and the owner will be quite thankful that his mail is not lost and bounced. -thh ------------------------------------------------------ Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
