If you’re ok with “the mail comes directly from me to you, and if you muck about with that then it may end up in your quarantine”, then quarantine is a better end point. If you really want to say “the mail comes directly from me to you”, then reject is likely where you want to get to. Similarly, if there’s something in the chain that mucks about with the message (often the subject) then there may be a DKIM failure but it’s still a legitimate message. For example, if someone is forwarding mail, then it’s likely there’s going to be an SPF failure (particularly if it’s not well set up) but the recipient probably does actually want the email. One thing to consider when deciding between quarantine and reject is that failures can be out of your control. If you upgrade to iCloud+, you can add a custom email domain name you already own to iCloud and use it with iCloud Mail. p=reject, again maybe doing percentage steps, if you’re completely certain that failing mail should never be read by the recipient.p=quarantine with 100%, maybe with other steps in between.p=quarantine with a low percentage just to check that things are ok in practice - if you get lots of issues, then at least it’s (a) likely available in the recipient’s quarantine, and (b) only a small amount of the mail.Do this to make sure that everything that’s going to fail should actually fail, or fix things that you spot that you hadn’t thought about. p=none with rua and/or ruf set (there are tools like Dmarcian that you can use to help process the reports you get).If you had a second paid domain then you'd still have access to that.
For example you'd still have pm.me and pm.ch. The safer course is to do a staged roll-out, e.g.: Your protonmail account would still be a paid account and you'd have access to any other email addresses of yours other than that domain email. If you are really sure you know where all the mail being sent is coming from, and that you’ve set up SPF & DKIM appropriately, then you might go directly to p=reject or p=quarantine. I have been using their service since a few months now, and I really can't recommend it enough.It depends a lot on the specific case. I **highly** recommend using SimpleLogin, and I **highly** recommend taking the very generous premium plan. There is no way to get it back.Īnd for those who are wondering, you can even send emails from an alias straight from your email provider (like Gmail or ProtonMail), to always maintain your privacy even when exchanging with people via email. And once your email account is in the wild, it will stay there forever. The major benefit of using email aliases like SimpleLogin allows, is that in case of a data breach, it's impossible for the hackers to find your other accounts, as you would have a different alias for each account.īreaches take place on a **daily** basis. The premium plan gives instant access to custom domains, which allows you to manage all your custom domains with catch-all rules for example and use them on the fly.
SimpleLogin is one of my favorite go-to products for privacy and security.
0 kommentar(er)
