>It was explained to me that the other guy's ISP (otherguysisp.com) has >the
>broken domain's entries purposely broken for the first few MX records
>(brokendomain.com). He says that his ISP wants to keep the first few >MX
>records broken, and that the problem is with MY mailserver.
If he broke the mx entries on purpose then ask him where in the RFC it states that type of methadology, or what "best business" practice is he following here.
Keep the first few MX records broken? If they want to break these then tell him to keep them internal, and tell them to run a sandbox DNS solution. If he wants to play the game of interconnectivity then he needs to play along with everyone else, and the standards (and suggestions) provided in the RFC's.
I have ran into admins in the past who have done the same thing. Blame the software I am running because they dont follow the RFC. One big example is IP addresses in the MX record, and then they defend their stance by stating to me "Well I can get mail from everyone else". As it happens everyone else is "Hotmail" or "Yahoo Mail", it is a sad thing that some admins use such services as the "measuring" stick for interconnections.
It is hard sometimes to make idiots that think like this to even see reason. Where I work I am not even the Systems Administrator, it just happens that I have taken some system responsabilities (email being one) because of the staffing issues presented in my department.
My experience so far has been a nightmare, and an uphill battle. Especially since I am a Network Admin and have only dealt with interconnecting networks (BGP, WAN, and private peering) in the past 8 years. In this world if you dont follow the standards, you dont have connectivity. I am glad that some "softie" company in Washington does not deploy routers, or layer 3 switches. Although I remmember one certain RAS server that was assigning ip addresses from a /24 subnet over dial up PPP lines and the MS admin could not figure out why his users where connected to the server and not routing any traffic.
Esperience has taught me to take these issues to the individuals supervisor's, or superiors and reference the RFC to them, explaining where they are not being "net frinedly" and also what solutions they can do in turn [sadly enough you have to think for them also].
I still see no reasoning as to what they are gaining by breaking an MX record. Escept that the guy misconfigured something and now wants to act that it was done like that for some meaningless purpose as to not admit that he had no idea what he was doing.
Good Luck getting those MX records fixed! More than likely they will just ignore reasoning and if it is crucial for your organization to receive email from their hosted domain(s), then you might have to do extra work and host internal zones of their domains for your systems to resolve them properly.
Gerardo A. Gregory Manager Network Administration and Security "King of mispellings, and run on sentences" ------------------------------------------- Affinitas, Corp. One customer|One relationship|One source. Visit us at http://www.affinitas.net
Kirk A Wolff wrote:
First off: Courier-mta is the BEST!
Question: Does courier iterate through all available MX records even if the first few are broken and possibly violate RFC1035?
I have been getting a complaint from someone trying to send an email to me. She gets an error from her mailserver thus:
--------------------------------------------------------------
>>> Mail Delivery Subsystem < [EMAIL PROTECTED] > 1/6/2004 3:43:24 PM The original message was received at Tue, 6 Jan 2004 15:43:14 -0600 (CST) from 12-23-34-45.otherguysisp.com [12.23.34.45] (may be forged) ----- The following addresses had permanent fatal errors ----- < [EMAIL PROTECTED] > (reason: 517-MX records for brokendomain.com violate section 3.3.9 of RFC 1035.) ----- Transcript of session follows ----- ... while talking to mail.! mydomain.net.: MAIL From:< [EMAIL PROTECTED] > SIZE=1911517-MX records for brokendomain.com violate section 3.3.9 of RFC 1035. <<< 517 Invalid domain, see <URL: ftp://ftp.isi.edu/in-notes/rfc1035.txt > 554 5.0.0 Service unavailable
---------------------------------------------------------------
It was explained to me that the other guy's ISP (otherguysisp.com) has the broken domain's entries purposely broken for the first few MX records (brokendomain.com). He says that his ISP wants to keep the first few MX records broken, and that the problem is with MY mailserver.
I am running Courier-mta 0.43.2 and it was compiled on my redhat 8.0 box with the ldap auth module loaded and running.
- Kirk
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
--
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
