Well, one thing that Courier _could_ do when it encounters an
unresolvable MX record would be to try the next MX record in the series.
The original post said that the MX records look like this:
MX 8 n.n.n.n. MX 10 mail.foobar.com.
In this case, Courier could try using the "mail.foobar.com." record after the "n.n.n.n." record fails to resolve, instead of immediately erroring out.
I'll second this -- I too have been having no end of grief dealing with non-rfc-1035 compliant domains and it's driving us up the wall.
At the very least, make it a bofh flag.
best, Jeff
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
