Skip to content
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

Ditch default Reply-To configuration #53

Open
antondollmaier opened this issue May 27, 2021 · 0 comments
Open

Ditch default Reply-To configuration #53

antondollmaier opened this issue May 27, 2021 · 0 comments

Comments

@antondollmaier
Copy link

Dear maintainers,

as an introductory note, please do accept my apologies for opening this issue - I'm neither a developer or user reporting, but a sysadmin with a spam problem at hand.

One of our customers is relying on your extension to curate their member area for their customers.

Due to yet unknown circumstances, they managed to send one (yes, a single) sign-up mail to a mailserver with probably a very eager postmaster and protected with the UCEPROTECT blacklist, because we spotted this log message:

status=bounced (host mailgate1.xxx[77.235.x.x] said: 550 Your IP will be reported for abuse - better watch out next time.

Obviously, being blacklisted caused troubles for other customers until outbound mail-traffic was re-routed.

After checking the logs, we found this entry in the PHP mail log:

[27-May-2021 08:55:15 Europe/Berlin] mail() on [/var/www/xxx/htdocs/www.xxxx.de/releases/20210520090655/Packages/Libraries/swiftmailer/swiftmailer/lib/classes/Swift/Transport/SimpleMailInvoker.php:34]: To:xxx@example.com -- Headers: Message-ID: <07517cf69d78dfc259dc753266fade46@www.xxxx.de> Date: Thu, 27 May 2021 08:55:15 +0200 From: xxx <noreply@xxx.de> Reply-To: Sandstorm Usermanagement Package Reply-To Email <test@example.com> MIME-Version: 1.0 Content-Type: multipart/alternative;  boundary="_=_swift_v4_1622098515_dc236545b62d12a3b3333f9125638318_=_" -- Subject: Please confirm your account

Obfuscated are only the recipient, the sender and the hostname in the message-ID. The Reply-To is unaltered - and matches your default settings:

The customer has already been notified about the incident and has been asked to change the defaults as well not to rely on sendmail any more.

For future releases, I'd like to urge you to completely remove the default reply-to setting:

  • if no reply-to is defined, MUA will anyways reply back to the From.
  • if a webmaster specifies a reply-to willigly, they do so on purpose.
  • leaving example.com will also result in wrong-routed responses, if users do not fully pay attention.

I will provide a PR as well, if this is desired.

Thank you very much for considering sane defaults for the webmaster - and please again accept my apologies for opening this issue at all.

Best,
Anton

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

No branches or pull requests

1 participant