search

freescout-help-desk / freescout

FreeScout — Free self-hosted help desk & shared mailbox (Zendesk / Help Scout alternative)
https://freescout.net
GNU Affero General Public License v3.0
2.98k stars 489 forks source link

Receiving thousands of UNDELIVERED/BOUNCE messages #3156

Closed jshrek closed 1 year ago

jshrek commented 1 year ago

So this issue, the best that I can figure... when a User is supposed to get notified of a New Conversation by email, but the email is bounced/undelivered, then Freescout repeatedly tries to notify the user by sending this email over and over again.

How to reproduce: For the user, the THERE IS A NEW CONVERSATION - EMAIL is CHECKED/ON When a new convesation comes into that mailbox, Freescout tries to notify them that they have a new conversation. Our email system has hit a limit and EXCEEDED MAX DEFERES AND FAILURES PER HOUR.

Temporary work around to stop this: I have to disable fetching of emails by Freescout for about 24 hours to let the mail server reset.

Here is attached pic of a couple screens..

firefox_2023-07-01_08-19-11

firefox_2023-07-01_08-29-22

I am really not 100% sure what is happening. The above is just my guess. It happened about a month ago as well.

freescout-helpdesk commented 1 year ago

Go to "Manage > Logs > Send Error" and send us error messages you see there.

jshrek commented 1 year ago

There is no specific Send Error option...

logs

Can I export logs and email them to you instead of uploading here?

freescout-helpdesk commented 1 year ago

Fixed in the master branch.

Now FreeScout will not try to resend email notifications on received bounce emails.

jshrek commented 1 year ago

Thank you!

jshrek commented 8 months ago

Okay, I think I have somehow come across a related issue...

This time, an email was assigned to a new user that has not verified their freescout account (did not accept welcome invite), AND also the users gmail inbox is FULL anyways, so now I got 8000 Mail delivery failed: returning message to sender

I am not sure how this is different from the error above that I originally posted.