simple-login / app

The SimpleLogin back-end and web app
https://simplelogin.io
GNU Affero General Public License v3.0
5.09k stars 430 forks source link

Ignore/reject as a per-alias setting #1361

Open ploum opened 2 years ago

ploum commented 2 years ago

Currently, ignore/reject is a global setting for one user.

It would be nice to be able to overide it for some aliases.

Usecase: I’ve set "ignore" because I don’t want spammer to know that I’m not receiving their email and if an alias is disabled, it’s because I don’t expect any email on them. But some aliases are old email addresses used by valid person. I want them to be informed that I didn’t received their email.

Redsandro commented 1 year ago

This. :point_up_2:

But it goes in tandem with that other setting, as indicated by the slash in the label:

I find myself constantly changing these settings because I have different preferences for different aliases. Because different aliases have different use cases.

Use case 1: Simply login. When you suddenly receive spam from multiple sources, your address was sold or leaked. You want to one-click disable the alias and silently ignore emails.

Use case 2: Anonymize main email address. When an unwanted contact (e.g. a headhunter) starts sending unsolicited emails, you'll want to block the sender and explicitly bounce ignored emails so they learn a lesson.

It would be helpful to have these intertwined settings on a per-alias basis. I would like the global setting to indicate what the initial setting should be on newly created aliases. Since one probably uses more throw-away accounts to simply login than one has anonymous addresses alter ego's, I would set block alias and ignore emails as the default, but fine-tune my alter ego's to block contacts and explicitly reject emails.

Redsandro commented 1 year ago

Can we get some consideration for this? I have a use case where configuring this setting per domain is desirable.

I purchased a domain and use it with SimpleLogin. Turns out a lot of poor folks still send emails to this domain and I don't get paid to be a switch board employee, so I've turned catch-all off. I really want the senders to know they need to update their address book and I wish for them to receive a bounce. But I definitely do not want to turn on bounces for all my other domains.

Normally I wouldn't care too much, but for some reason most of the recipients are senior citizens and the digital age is cold enough for them. This bothers me.

Since this is about catch-all, configuring this setting per domain in stead of globally or per alias is desirable.

I believe the original catch_all and bounce implementation was done by @nguyenkims and @acasajus. Son Nguyen can you estimate where amending this feature sits on a scale from 'pretty straightforward' to 'disaster'?

nguyenkims commented 1 year ago

@Redsandro this feature isn't complex to implement. We already have a roadmap full of feature to implement though but I'll try to see if we can add it to our todo list. Otherwise if someone can contribute a merge request, we'd be happy to accept it.

bruceleerabbit commented 2 months ago

@Redsandro You might want to watch bug #2180. If that bug gets fixed it might solve some of your problems.