| To: | Marc Perkel <marc@perkel.com> |
|---|---|
| Subject: | Re: Question about Qmail relating to MX retry processing |
| From: | Uncle George <qmail@gatworks.com> |
| Date: | Fri, 24 Nov 2006 20:35:17 -0500 |
| Cc: | qmail@list.cr.yp.to |
| Delivered-to: | sp-com-lists@consult.net |
| Delivered-to: | gmail-qmail@securepoint.com |
| Delivered-to: | sp.com.list@gmail.com |
| Delivered-to: | mailing list qmail@list.cr.yp.to |
| In-reply-to: | <45679726.9080600@perkel.com> |
| Mailing-list: | contact qmail-help@list.cr.yp.to; run by ezmlm |
| References: | <45676987.2050808@perkel.com> <456789E5.3000508@gatworks.com> <45678E43.5030508@perkel.com> <45679170.1040203@gatworks.com> <45679726.9080600@perkel.com> |
| User-agent: | Mozilla Thunderbird 1.0.2-6 (X11/20050513) |
But Qmail won't send the email to the backup MX? Not sure if i would use NFS as a qmail queue storage. But that another IMHO. Qmail will do the second MX once u close up the service listening on port 25 of the broken machine. For many default qmails, u have about 6 days to disable the port to the broken MTA before the e-mail is deemed undeliverable. There's a spec - everyone else follows the spec - except qmail. I'm sure that there is a spec. I'm not sure why the followers of the RFC spec have not yet chimed in. Do u know where the spec spells this out? |
| Previous by Date: | Re: Question about Qmail relating to MX retry processing, Marc Perkel |
|---|---|
| Next by Date: | Re: Question about Qmail relating to MX retry processing, Uncle George |
| Previous by Thread: | Re: Question about Qmail relating to MX retry processing, Marc Perkel |
| Next by Thread: | Re: Question about Qmail relating to MX retry processing, Charles Cazabon |
| Indexes: | [Date] [Thread] [Top] [All Lists] |