How funny — it looks like the folks who run FEMA’s internet services don’t have an email server designated for the organization (see for yourself here), meaning that any and all email sent to an @fema.gov address is bouncing back as destination unknown. Seeing as a bunch of the email addresses on FEMA’s contact page live at fema.gov, it’s not only embarrassing, it’s another small measure of how the organization doesn’t quite seem to know what it’s doing.
(For those of you who aren’t such internet geeks, the best brick-and-mortar analogy for this is that it’s as if FEMA doesn’t have a mailbox or mailroom — right now, from the internet, there’s no way to get email to the organization at all. And for those of you who are big internet geeks, you probably know that the relevant RFC says that if there’s no MX record for a domain name, mail transport agents should fallback to using an A record — but the machine that lives at the A record address for fema.gov doesn’t have an SMTP server running, so the fallback is also falling flat on its face.)
I worked for FEMA until a few months ago so I wanted to point out some inaccuracies in you posting. When DHS was created all the component agency email addresses were converted to @dhs.gov so the government would see a cost savings by consolidating email servers. As a result there is no longer a need for @fema.gov addresses since all communication is now firstname.lastname@dhs.gov. Internally @fema.gov still works but the MX record was removed for fema.gov so external communication requires @dhs.gov.
• Posted by: Nate on Oct 14, 2005, 5:40 PMNate, your comment would be a perfect explanation if it weren´t for the fact that there are addresses on FEMA´s contact page that use @fema.gov. Alas.
• Posted by: Jason on Oct 16, 2005, 8:49 AM