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

Send spam reports using the same account it was received on #16

Open
dermoth opened this issue Jun 19, 2021 · 2 comments
Open

Send spam reports using the same account it was received on #16

dermoth opened this issue Jun 19, 2021 · 2 comments

Comments

@dermoth
Copy link

dermoth commented Jun 19, 2021

Providers seems to recognize their own mail as when I send reports from another account they tend to bounce, and they never did sending back from the same account.

I have multiple account and when I forward to SC the default sending account is used. While it may be hard to figure out which account received an email if they get moved around, a fairly simple and usually correct approach is to just use the outbound server for the account the mails are currently located in.

Since afaik you can't select multiple mails from different accounts (unless there is some merged folder features like outlook I don't know about) multiple sends should be able to easily follow the same rule.

@RobbyZ
Copy link

RobbyZ commented Jul 2, 2022

This would be a vital enhancement for people using the registrar contact method

@pscdodd
Copy link

pscdodd commented Feb 20, 2023

This is still true today, the extension seems to use the first account in the list as the "from" address. As a workaround, you can change the account you are sending from by selecting it in the from menu (at least if you are not using the Quick spamcop option.
Note: The mails are still sent, but from the wrong account. This is very confusing, and may result in multiple submissions of the same mail.

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

3 participants