Skip to content

Send response to 550 and 552 #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Mar 15, 2021
Merged

Conversation

ThomasTJdev
Copy link
Owner

PR with own PR from arithmetric#127 .

This PR consist of two main elements - auto response on:

  • SMTP 550 - no recipient found
  • SMTP 552 - mail size exceeds 10 MB

550 - no recipient found

When a person is sending an email, and global catch (@example.com) is not enabled, the email will just disappear - neither the sender nor the email-admin will be notified. If the new "notify"-config is enabled, the sender will be informed, that the recipient does not exists.

Config

notifyEmail: "[email protected]",
notify550: true,

Response

An error occurred while trying to deliver the mail to the following recipients: [email protected]

Your email was rejected. The email address was not found. Please check the receiving email address.

SMTP Reply Code = 550, SMTP Status Code = 5.1.1

552 - mail size exceeds 10 MB

Another problem is when the mail size exceeds AWS's limit on 10MB. This will also fail silently (arithmetric#97, arithmetric#124) - not notifying either the sender or the email-admin. If the new "notify"-config is enabled, the sender will be informed, that the recipient does not exists.

Config

notifyEmail: "[email protected]",
notify552: true,

Response

An error occurred while trying to deliver the mail to the following recipients: [email protected]

Your email was rejected. Please ensure that the size of your mail is less than 10 MB.

SMTP Reply Code = 552, SMTP Status Code = 5.3.4

@ThomasTJdev ThomasTJdev merged commit 58bddc6 into master Mar 15, 2021
@ThomasTJdev
Copy link
Owner Author

Just to inform those of you coming from original branch - this PR has been merged and it works perfectly!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant