17 messages in net.sourceforge.lists.courier-users[courier-users] Re: MX Lookup & sending| From | Sent On | Attachments |
|---|---|---|
| Lukas Vesely | May 29, 2002 9:45 am | |
| Anand Buddhdev | May 29, 2002 12:15 pm | |
| Sam Varshavchik | May 29, 2002 2:02 pm | |
| Luc Brouard | May 30, 2002 12:20 am | |
| Lukas Vesely | May 30, 2002 1:34 am | |
| Alexei Batyr' | May 30, 2002 5:33 am | |
| Sam Varshavchik | May 30, 2002 7:05 am | |
| Alexei Batyr' | May 30, 2002 7:48 am | |
| Sam Varshavchik | May 30, 2002 8:19 am | |
| Alexei Batyr' | May 30, 2002 9:03 am | |
| Lukas Vesely | May 30, 2002 10:26 am | |
| Juha Saarinen | May 30, 2002 1:18 pm | |
| Juha Saarinen | May 30, 2002 1:31 pm | |
| Sam Varshavchik | May 30, 2002 2:35 pm | |
| Sam Varshavchik | May 30, 2002 2:35 pm | |
| Alexei Batyr' | May 31, 2002 1:43 am | |
| Lukas Vesely | May 31, 2002 6:13 am |
| Subject: | [courier-users] Re: MX Lookup & sending | |
|---|---|---|
| From: | Alexei Batyr' (leh...@pcmag.ru) | |
| Date: | May 30, 2002 5:33:39 am | |
| List: | net.sourceforge.lists.courier-users | |
Lukas Vesely writes:
On Thu, 30 May 2002, Luc Brouard wrote:
On Wed, May 29, 2002 at 05:02:51PM -0400, Sam Varshavchik wrote:
Anand Buddhdev writes:
I have also seen this, and I posed this question to Sam some time ago. Since he did not come back with a "no", I'm hoping he has put this request on his todo list, and that it will appear in courier soon. Sam, are you working on such a feature?
I have not decided yet.
I think it should be done, that's what MX are for .. moreover when they have the same weight !
Yes, I guess so also! Or at least to have the possibility to turn this feature on.
I agree completely. And have to add some points which IMO need serious revision in MX list creation and using logic.
1. BOFH file option needed, e.g. BOFHBADDNS, with values "reject", "accept" and "notify" (probably some else) similar to BOFHBADMIME. If value is "accept" courieresmtp should send messages to "bad" from RFC 1035 point of view domains without obstruction and courieresmtpd should quietly receive messages from such domains. "Notify" value should force esmtp client and server send additional configurable warning message to postmaster or dnsmaster of "bad" domain.
It's just "protect innocent" policy - user in domain with slightly misconfigured DNS shouldn't account for its dnsmaster errors or tricks (some dnsmasters use IP addresses of MXes instead of FQDN's intentionally, e.g. if their backup MX host doesn't have FQDN).
2. If there is more than one MX for certain domain and only one of them is non-RFC-compliant, courier should use valid MX for sending message instead of bouncing it with "RFC 1035" error.
3. If BOFHCHECKDNS option is on, courieresmtpd rejects mail from some valid domains (e.g. mz.ru, tech.ru, games.dol.ru, home.com, exite.com, maxmail.co.uk) with diagnostic "Domain does not exist". It's caused by misinterpreting error responses from MX list creation functions. I think this diagnostic should only appear if DNS replies with NXDOMAIN status.
Alexei.