Replies: 1 comment 3 replies
-
We have made some changes in the anti-abuse detection which is responsible for automatically disabling an alias if it turns "rogue". The detection should be much more tolerable now and the possibility of a false positive is now unlikely.
We already have some protections on the sender level. However an attacker can easily change the sender (envelope and header) which makes this detection more difficult. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi!
I have started using the service in the last month heavily, migrating my accounts (i mean other accounts, changing the email adresses to SL alias). I did it in a way, when i still tunneling emails to my main email adress (meaning the content of the emails do not really differ), but in an order, as a basement for future changes. I am still withn the free-account alias-limit with 100+ accounts, so i have alias overlaps. (E.g. why bother giving individual alias to all of my steam games, what using an individual account.. etc)
The migration was the usual, log in, verify email adress if needed, change password, change email, verify new email adress, done.
(I know the bounce decided only on the Email-provider's side, my issue is on the SL side)
During the time of migration i experienced 2 kind of bounced-mail behaviour.
--In the early phase i got a bounce here, and there, but usually the second email gone through. I have recived an individual notification if an individual bounce happened, checked the email in a standalone client, and the confirmation of the other-account's change usually arrived. So if there was a bounce, got a notification mail from that specific bounce.
--The 2nd phase started about a week ago: if a bounce occurs, i do not recive a notification about that bounce. Instead i recive a notification about the used alias being disabled because "several emails bounced". I not have to mention, why it is worse.
Addational info:
I even experienced phase 2 on an alias, what was not recived any bounce before, but only in phase 2.
Once it happened in font of me: i turned back online my alias, in 5 minute it was disabled again.
So my related questions:
What happened that caused the bounce behaviour change? Is there any way to change it back?
If i have reached a limit, what is that limit? Timaframe based, total account bounce based?
Why attacking the alias, is better than attacking the sender on the system level? Why there is no option to choose about this one in the preferences?
Beta Was this translation helpful? Give feedback.
All reactions