Closed Bug 560315 Opened 15 years ago Closed 15 years ago

Run a MX lookup webservice

Categories

(Mozilla Messaging Graveyard :: Server Operations, defect)

Product:
Mozilla Messaging Graveyard
Component:
Server Operations
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: gozer, Unassigned)

References

(
URL
)

Details

Attachments

(1 file, 1 obsolete file)

version of mx running in production
1.25 KB, text/plain
Details
Attached file Super-simple mx lookup cgi script (obsolete) —
Steal and improve the code on ectoplasm.org a little.
Personally, I'd only return the most preferred servers. Given that it's sorted by preference, it's not so serious, though: My code just always takes the first line and ignores the rest.
FWIW, it works fine for me as-is.
Live and running here: https://live.mozillamessaging.com/dns/mx/example.com
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Nice! With TTL -> cache expiry and no MX -> 404.
Status: RESOLVED → VERIFIED
Seemed like the logical translation of DNS into the HTTP world.
Attaching what I actually ended up running in production.
Attachment #439999 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: