i signed up on kraken.com and teamviwer.com.
when support wrote emails to me, i can receive their emails. but i do not receive any automatic emails like :
when i should receive 2FA email code (kraken),
or when i should receive email to confirm device is a trusted device (teamviewer).
If there is no record, at all, of an attempted email from their servers, then there is something wrong on their end.
You might try setting an account up using a freemail account so you can inspect the email headers and see if something there can help you.
If you have trouble knowing where in the logs the email should be, you could try the following, as these are the only things that I can think of that would block an email:
This will pull up a lot of emails, but see if any of them look like the from address might be the email you are looking for, then grep for that email address or even just the domain used to see if they ever attempted a retry.
If that doesnât pull anything up, you can check if they are currently blacklisted, as happens even for big companies:
If that doesnât work, then something else is wrong, and likely itâs somehow on their end, so you may need to elevate a ticket to get to someone that review the logs they generate. Possibly there is something they donât like, as certainly Teamviewer is dealing with hordes of scheisters so may have additional protections in place, even on registered accounts.
Note their support emails are likely sent from some completely different server.
I do not understand remark : âRecipient address rejectedâ
I have 1 regular email address and all aliases are catched to it (catch-all in place)
I can well receive emails to needed aliases when i test them through my gmail address.
What can i do to receive in my mailbox those emails ? even if it is in spam folder
I created a new account on kraken.com with gmail address to test.
I well receive automatic emails from Kraken to this gmail address.
With âgmailâ address, i receive emails that contain autorization code"
whith âmailinaboxâ address : same email is not received (neither mailbox, nor spam)
The first situation with @kraken.com is easily understood.
MiaB uses greylisting as a spam control method. With greylisting every new sending domains initial email is âbouncedâ with an error message that when received properly configured sending email servers will simply reque and resend the email. Apparently @kraken.com's email server is not configured to retry sending these emails.
You should be able to add the sending mailserver to the postgrey white list. Details may be found elsewhere on the forum.
The second issue with @teamviewer.com is more obscure though ⌠indications are that it is an issue with your boxes DNS.
How were these email attempts each sent? Did you make one request and receive the two, or did you make two requests and receive one after each request?
for Kraken
when i log on their website, they send email with an authentification code inside.
for Teamviewer
when i log on their website, they send an email with an URL to confirm Browser/device is trusted
as iâm not able to see their email neither in mailbox neither spam folder, for both of them i cannot use those platforms with my mailbox managed on MIAB.
For each provider (kraken or teamviewer) an email from them is sent to me.
For kraken, when i log on their website, i should receive an email which has a â2FAâ code (i do not receive)
For teamviewer, that is the almost the same (link url instead of a 2FA code)
For both of them, with emails managed on MIAB, iâm not able to receive any email (mailbox or spam) while it works well with gmail address.
From your logs you posted two email attempts. Does each of these attempts correlate with a separate log in attempt? In other words, was there a total of two log in attempts, with each attempt generating one email?
If they are sending only one email for each log in attempt, it means their servers are not properly following the published standards on email.
If you are using aliases, and there is a unique alias for each service provider, you might do better by running grep username@example /var/log/mail.log where username is the unique alias for Kraken and seeing if there is any rejected email attempt after rejected message.
If there isnât, then we can work through a solution at least for that service.
What postgrey is doing is filtering out spam by forcing sending servers to follow the published standards on mail servers, and the vast majority of spam servers do not have this capability. The standard states when when receiving a defined response from the receiving server that says âtry back laterâ, the sending server is supposed to try again later. On the retry, postgrey will pass the email and it will be delivered, assuming it passes other checks.
However, some not-spam sending servers are configured to not re-send, and other not-spam sending servers are part of very complex server pools that re-send from different servers each retry. In both cases, we have to change how postgrey handles the email, and usually the solutions are different.
In your case, since you are using an alias, you could create the file /etc/postfix/postgrey_whitelist_recipients and add kraken@example.com to the file, then restart postgrey and postfix.
You may consider slightly changing your email address to something like kraken4francois@example.com. While Iâm not big on security through obscurity, spammers to try guessing things like this.
Note that if you read that Kraken has suffered a breach of email address database, you should switch the account to a different email address and replace the one in the whitelist, because you are about to get spammed.
There is also a kludge that you can use @Anonymous78f
When you log on to to the Kraken website I presume that they show you a message that a â2FAâ code has been sent to your email ⌠and an option to have it resent. Wait 3 minutes and then ask for it to be resent.
This looks more like the output of grep kraken /var/log/mail.log. The retry is going to be some number of minutes after the reject.
The sendera_access solution I proposed on a different thread may not be as good in this case as the above whitelist suggestion. They may forever be using different email addresses including different subdomains.
If youâll notice, the account activation emails from Teamviewer come from a different MTA entirely. As I understand, Postgrey works on a MTA by MTA basis, not specifically the sender.
Could you perhaps test the step where @Anonymous78f is having difficulties ⌠in adding a trusted device?
I had a Teamviewer account years ago, so I went looking for their emails. It seems that they were sending the emails directly from their servers at the time rather than relying on mimecast.com to do so.
@Anonymous78f perhaps you could contact Teamviewer support and inform them that your email provider uses Postgrey, but their email service is not retrying delivery as it should ⌠it may not help, but it cannot hurt.