Then you need to check with the person who is…
This person would likely get nothing, given I have already changed twice
my email address to get it back to working (with the same email address
as before) and am receiving email again; so I’d rather not bother them
with this.
This bug report is only here to inform you that discourse wrongly
handles delay notifications as bounces, and shows no visual indication
that the email address is completely disabled when it is, after ~20
delay notifications if I try to guess from the amount of mail I usually
receive from this discourse.
I am not particularly looking for work-arounds here, only hoping that
such a situation doesn’t arise again for other people who may not notice
the interruption of the mail either.
If your question is to check that the bounce number actually increased,
I would think the private message I received is explicit in that it
assumes my server bounced, which as far as my logs show it didn’t:
(subject:) Is your email address correct?
We’re sorry, but we’re having trouble reaching you via email. Our last
few emails to you have all bounced back as undeliverable.
Can you make sure your email address is valid and working? You may also
wish to add our email address to your address book / contact list to
improve deliverability.
My SMTP server’s logs are also quite clear that it only went down for
the duration of a reboot.
- Nov 30, 05:13: My server sends first delay notification
- Nov 30, 05:24: Discourse attempts to send its last mail to me
- 06:28: 2nd and 3rd DN sent the same minute
- 08:17: 4th DN
- 12:35: Queue emptied, all mail are delivered, end of the incident…
but discourse doesn’t resume sending any mail, despite no
non-delivery notificaition having been sent