Closed Bug 1838363 Opened 2 years ago Closed 2 years ago

Bounced emails

Categories

(bugzilla.mozilla.org :: Email Notifications, defect)

defect

Tracking

()

RESOLVED FIXED

People

(Reporter: Webworkr, Unassigned)

Details

User Agent: Mozilla/5.0 (Android 13; Mobile; rv:109.0) Gecko/116.0 Firefox/116.0

Steps to reproduce:

Until June 5, I received emails from Bugzilla at my email address without any problems. I haven't changed anything in the e-mail inbox in the meantime.

Actual results:

But now I receive bounce messages in Bugzilla's login area. I have checked my web hosting configuration and also had my provider look over it. Everything looks fine. Test emails are arriving properly.

They must be false positives. Please check your (Amazon) settings and enable my address to receive again.

Best thanks

Expected results:

The email notifications should work properly.

Change notification emails have been disabled for your account due to issues delivering to your address.


Bounced Emails
Due to issues delivering email to your account, we have temporarily disabled email notifications being sent to it. If you feel like the issue has been resolved, you may reactivate email delivery below. After a maximum of 5 bounces, we will disable logging in to your account and you will need to contact an administrator to reactivate it.


2023-06-12 10:54 CEST
Your Bugzilla account has been disabled due to issues delivering emails to your address.<br> <br> Your mail server said: (failed) Amazon SES did not send the message to this address because it is on the suppression list for your account. For more information about removing addresses from the suppression list, see the Amazon SES Developer Guide at https://docs.aws.amazon.com/ses/latest/DeveloperGuide/sending-email-suppression-list.html<br>


2023-06-12 10:54 CEST
Your Bugzilla account has been disabled due to issues delivering emails to your address.<br> <br> Your mail server said: (failed) Amazon SES did not send the message to this address because it is on the suppression list for your account. For more information about removing addresses from the suppression list, see the Amazon SES Developer Guide at https://docs.aws.amazon.com/ses/latest/DeveloperGuide/sending-email-suppression-list.html<br>


2023-06-12 10:54 CEST
Your Bugzilla account has been disabled due to issues delivering emails to your address.<br> <br> Your mail server said: (failed) Amazon SES did not send the message to this address because it is on the suppression list for your account. For more information about removing addresses from the suppression list, see the Amazon SES Developer Guide at https://docs.aws.amazon.com/ses/latest/DeveloperGuide/sending-email-suppression-list.html<br>


2023-06-12 10:54 CEST
Your Bugzilla account has been disabled due to issues delivering emails to your address.<br> <br> Your mail server said: (failed) Amazon SES did not send the message to this address because it is on the suppression list for your account. For more information about removing addresses from the suppression list, see the Amazon SES Developer Guide at https://docs.aws.amazon.com/ses/latest/DeveloperGuide/sending-email-suppression-list.html<br>

I'll ask our infra team to request removal from Amazon's suppression list.

Just like bug 1822570 you only have a single MX entry for your domain, so any sort of transient infrastructure issue will result in bounces. I strongly suggest you investigate establishing a secondary mail server on a different network from your primary.

Your email address has been removed from Amazon's suppression list, and I've re-enabled bugmail on your account.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED

Thank you for the timely solution

  • By default, multiple email servers per domain are not provided for by my provider. But there is the possibility to store an external mail server as failover. How I implement this, I have to think about it again.

  • Do I have the possibility to access Amazon's suppression list myself?

  • Originally I had contacted bmo-mods@mozilla.com a few days ago. Except for an autoresponder I got no answer. In Bugzilla the corresponding profile is deactivated. Is this email address still actively monitored at this time?

(In reply to Denis Müller [:Webworkr] from comment #5)

Thank you for the timely solution

  • By default, multiple email servers per domain are not provided for by my provider. But there is the possibility to store an external mail server as failover. How I implement this, I have to think about it again.

That's sad to hear. Some senders might treat certain classes of issues as transient and queue message for you (eg. a routing issue), but some issues would been seen as permanent errors resulting in a bounce (eg. if the mail service is briefly not running to apply an update).

Amazon is very strict on the percentage of bounces it will permit before disabling our account, so we have to take a firm approach here.

  • Do I have the possibility to access Amazon's suppression list myself?

No, this list isn't public (I don't have access to it either).

  • Originally I had contacted bmo-mods@mozilla.com a few days ago. Except for an autoresponder I got no answer. In Bugzilla the corresponding profile is deactivated. Is this email address still actively monitored at this time?

It should still be monitored, I'll check with the team.

Has there been any news regarding the bmo-mods-mailbox in the meantime? Why had I not received an answer? Thanks

Flags: needinfo?(glob)

I put measures in place to ensure that questions won't be missed in future.

I believe I answered your questions on this bug; no further action was required.

Flags: needinfo?(glob)

(In reply to :glob ✱ from comment #8)

I put measures in place to ensure that questions won't be missed in future.

I believe I answered your questions on this bug; no further action was required.

Thank you :-)

I have now changed the email address. The new address has 3 mx records. This should hopefully avoid the problem in the future.

Just in case, the old address is still active.

You need to log in before you can comment on or make changes to this bug.