Failure: <class 'twisted.mail.smtp.SMTPDeliveryError'>: 554 No recipients accepted firstname.lastname@example.org: 554 5.7.1 <unknown[10.250.48.135]>: Client host rejected: Access denied >>> MAIL FROM:<email@example.com> <<< 250 2.1.0 Ok >>> RCPT TO:<firstname.lastname@example.org> <<< 554 5.7.1 <unknown[10.250.48.135]>: Client host rejected: Access denied I was, however, able to send mail using |Mail -v| from the command line as cltbld. I'm going to guess that something changed that requires the From: be a valid email address; is that correct? Can I use email@example.com to help in email filtering?
Trying is faster than asking I suppose. firstname.lastname@example.org bounces as well. I'll try just email@example.com; alternately, is there an IP whitelist/blacklist?
Ok, my Mail -v to firstname.lastname@example.org was accepted for delivery, but I haven't received it yet. Checked postini and it isn't there. I've got a hunch this is related to the mv.m.c -> build.m.o move; I'll look to see what smtp server I need to set.
/etc/mail/sendmail.cf has the same checksum as pm02's, relaying off mail.build.mozilla.org. Mail -v to email@example.com from pm02 didn't arrive. Wondering if this is a moz-specific thing; trying to send to external email.... which worked. I'm going to guess there's some internal email address validator on mail.build.m.o that has either been turned on recently, or that behaves differently towards build.m.o than mv.m.c... could you investigate?
Sigh, emails to firstname.lastname@example.org just arrived, which points to something on the tinderbox.m.o side. I think.
It's an IP whitelist, yes. IPs inside the colo and the office are allowed to send mail there, from outside are not. The new build network has a new IP range that didn't previously exist. I'll get it added to the whitelists.
Assignee: server-ops → justdave
Got that added, try it again now?
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.