Opened 7 years ago

Closed 7 years ago

#5486 closed Bug/Something is broken (fixed)

Email error message: "loops back to myself"

Reported by: Student/Farmworker Alliance Owned by: Jamie McClelland
Priority: High Component: Tech
Keywords: email Cc: jake@…
Sensitive: no

Description

All email that is attempted to anyone at the domain "@justharvestusa.org" is bounced back with the following error message:

"mail for justharvestusa.org loops back to myself"

Anyone with a @justharvestusa.org address has not been getting any emails since last night.

Change History (4)

comment:1 Changed 7 years ago by Ross

Keywords: email added
Owner: set to Jamie McClelland
Status: newassigned

Hi sfalliance,

This seems quite unusual. I'm assigning it to jamie who should be able to help you.

~/ross

comment:2 Changed 7 years ago by Jamie McClelland

Hi - It seems as though mail is properly flowing now (via mandela) and that mail had been properly flowing during prior days, however, between 8:45 am and 7:00 pm yestereday I see a number of DNS errors in our logs along the lines of:

/var/log/mail.log.0:Mar 20 17:04:22 mandela postfix/smtpd[16749]: warning: numeric domain name in resource data of MX record for justharvestusa.org: 127.0.1.50

That seems to indicate that, during the period specified, when mandela requested the name of the server to deliver mail for justharvest.org (the MX record), the response was 127.0.1.50 instead of mandela.mayfirst.org as it should be (and as it now reports it).

I checked our control panel records, and the MX record for justharvestusa.org was lasted changed in 2008, so I don't think this was do to a change anyone made to our name server records..

However, according to the whois record provided by PIR, it seems as though you moved your domain from Godaddy to Dotster at exactly the same time that this problem was happening. Is that correct? That's a good move - I'm not a fan of Goddady! And, you should be able to make that change without interruption.

But my best guess is that there was a brief period during that transition, when your authoritative name servers were pointing to dotster instead of MFPL and dotster was handing out incorrect DNS records.

Does that seem like a likely explanation?

If so, I'd like to do more follow up to understand why switching registrars would cause a period during which your authoritative name servers would change. That indicates a serious problem, albeit one that is not under our control :(.

jamie

comment:3 Changed 7 years ago by Jamie McClelland

Resolution: fixed
Status: assignedfeedback

I'm assuming this answer resolves the ticket. Feel free to re-open with more questions.

comment:4 Changed 7 years ago by automatic

Status: feedbackclosed

No news is good news (we hope)! Given the lack of feedback, we think this ticket can be closed.

Please login to add comments to this ticket.

Note: See TracTickets for help on using tickets.