#AskFedi I’ve been reluctant to ask this but I’m concerned #Proton emails are not making it to my client intentionally.
-
#AskFedi I’ve been reluctant to ask this but I’m concerned #Proton emails are not making it to my client intentionally.
Long story short, I was working to #degoogle with a client but halfway they decided to stay put. We disconnected Proton from their domain. Waited 14 days. And they have not received emails from Proton users.
Is there a trick I’m missing with the disconnection? Ive also seen #Google is starting to suppress custom domains so I’m not sure if it’s an easy fix or more nefarious.
-
#AskFedi I’ve been reluctant to ask this but I’m concerned #Proton emails are not making it to my client intentionally.
Long story short, I was working to #degoogle with a client but halfway they decided to stay put. We disconnected Proton from their domain. Waited 14 days. And they have not received emails from Proton users.
Is there a trick I’m missing with the disconnection? Ive also seen #Google is starting to suppress custom domains so I’m not sure if it’s an easy fix or more nefarious.
@rootschange
My gut reaction:- it can't be DNS
- it's never DNS
- it was DNS
- it's always DNS
-
R relay@relay.infosec.exchange shared this topic
-
#AskFedi I’ve been reluctant to ask this but I’m concerned #Proton emails are not making it to my client intentionally.
Long story short, I was working to #degoogle with a client but halfway they decided to stay put. We disconnected Proton from their domain. Waited 14 days. And they have not received emails from Proton users.
Is there a trick I’m missing with the disconnection? Ive also seen #Google is starting to suppress custom domains so I’m not sure if it’s an easy fix or more nefarious.
@rootschange it is almost impossible to make educated guess here but as someone who manages email for a company I can suspect this:
- some DNS records got changed and weren't changed back. Go check them and take sure everything fits, not just MX records but also SPF/DMARC ones. Check with online tools to be sure.
- if there was some registration made with Proton to connect it with the domain (I am not familiar with it but it works about the same everywhere) then maybe it has to be reverted because Proton "thinks" it is their domain now so they don't route mail outside their system. This is quite typical and might be matter of simply reverting these settings or removing the domain from Proton everywhere.
- if records were changed and then reverted then Proton might have their cache stuck or something. If there are no bounce message errors telling anything (try to send something from Proton and see) then the only way is to contact their support so Proton can see what goes wrong at mail transport level.
-
@rootschange it is almost impossible to make educated guess here but as someone who manages email for a company I can suspect this:
- some DNS records got changed and weren't changed back. Go check them and take sure everything fits, not just MX records but also SPF/DMARC ones. Check with online tools to be sure.
- if there was some registration made with Proton to connect it with the domain (I am not familiar with it but it works about the same everywhere) then maybe it has to be reverted because Proton "thinks" it is their domain now so they don't route mail outside their system. This is quite typical and might be matter of simply reverting these settings or removing the domain from Proton everywhere.
- if records were changed and then reverted then Proton might have their cache stuck or something. If there are no bounce message errors telling anything (try to send something from Proton and see) then the only way is to contact their support so Proton can see what goes wrong at mail transport level.
@rootschange also you have such a great avatar picture
-
@rootschange it is almost impossible to make educated guess here but as someone who manages email for a company I can suspect this:
- some DNS records got changed and weren't changed back. Go check them and take sure everything fits, not just MX records but also SPF/DMARC ones. Check with online tools to be sure.
- if there was some registration made with Proton to connect it with the domain (I am not familiar with it but it works about the same everywhere) then maybe it has to be reverted because Proton "thinks" it is their domain now so they don't route mail outside their system. This is quite typical and might be matter of simply reverting these settings or removing the domain from Proton everywhere.
- if records were changed and then reverted then Proton might have their cache stuck or something. If there are no bounce message errors telling anything (try to send something from Proton and see) then the only way is to contact their support so Proton can see what goes wrong at mail transport level.
@shuro @rootschange all are very valid points, I concur
