missing e-mails from booking.com

[kfam]

Hello, I have an account on my email server that is behind proxmox mail gw.
Since some time I can see that the address is not receiving notifications from booking. I've tried today few times with the account verification link as well as other e-mail notifications and password reset link, but none of them arrives for the email in that domain.
I've created a fresh account in mydomain.eu domain that is working correctly - receives the emails notification from booking, but the same account but in mydomain.pl account that was created earlier (few years) doesn't show even a trace on the mail gateway. Waht can e the issue??

 

[Stoiko Ivanov]

We'd need the logs for that - maybe it got rejected for some other reasons.
If there is no track of booking contacting your mailgateway for the mail to mydomain.pl - make sure the MX record of your domain is setup correctly - and contact booking.com otherwise.

 

[kfam]

Hi Stoiko
I dont think the problem is in MX record since other e-mail (ie from gmail, olx, mxtoolbox) arrive without problems so I have doubts about it.
About the logs I can gladly send you logs, but I wouldn't prefer to put them in forum unencoded/protected.
If I can I can send them to you directly.

 

[Stoiko Ivanov]

Sorry our forum is public - Only the Enterprise support portal (available with Subscription of level Basic or higher) has the option of sharing data privately in general.

maybe you can anonymize them - or reduce them to the attempts from booking.com?

 

[kfam]

ok, ill try

 

[kfam]

ok, so this is the account for which the mails from booking arrive to the mail gateway:
Mar 7 22:51:37 spamfilter postfix/smtpd[2071746]: connect from mailout-108-r2.booking.com[37.10.31.20]
Mar 7 22:51:37 spamfilter postfix/smtpd[2071746]: Anonymous TLS connection established from mailout-108-r2.booking.com[37.10.31.20]: TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256
Mar 7 22:51:38 spamfilter pmgpolicy[2071328]: SPF says pass
Mar 7 22:51:38 spamfilter postfix/smtpd[2071746]: 2AACA211F0: client=mailout-108-r2.booking.com[37.10.31.20]
Mar 7 22:51:38 spamfilter postfix/cleanup[2071751]: 2AACA211F0: message-id=<4TrNKs6J3VzJV@mailrouter-601.fra3.prod.booking.com>
Mar 7 22:51:38 spamfilter postfix/qmgr[1953429]: 2AACA211F0: from=<noreply@mailer.booking.com>, size=42008, nrcpt=1 (queue active)
Mar 7 22:51:38 spamfilter postfix/smtpd[2071746]: disconnect from mailout-108-r2.booking.com[37.10.31.20] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7
Mar 7 22:51:38 spamfilter pmg-smtp-filter[2071625]: 2024/03/07-22:51:38 CONNECT TCP Peer: "[127.0.0.1]:46948" Local: "[127.0.0.1]:10024"
Mar 7 22:51:38 spamfilter pmg-smtp-filter[2071625]: 2133A65EA36EA433E2: new mail message-id=<4TrNKs6J3VzJV@mailrouter-601.fra3.prod.booking.com>#012
Mar 7 22:51:39 spamfilter pmg-smtp-filter[2071625]: 2133A65EA36EA433E2: SA score=0/5 time=0.794 bayes=undefined autolearn=no autolearn_force=no hits=AWL(-0.286),DKIM_SIGNED(0.1),DKIM_VALID(-0.1),DKIM_VALID_AU(-0.1),DKIM_VALID_EF(-0.1),HTML_FONT_LOW_CONTRAST(0.001),HTML_MESSAGE(0.001),KAM_LOTSOFHASH(0.25),KAM_REALLYHUGEIMGSRC(0.5),SPF_HELO_NONE(0.001),SPF_PASS(-0.001),T_SCC_BODY_TEXT_LINE(-0.01),USER_IN_DEF_SPF_WL(-7.5)
Mar 7 22:51:39 spamfilter postfix/smtpd[2071756]: connect from localhost.localdomain[127.0.0.1]
Mar 7 22:51:39 spamfilter postfix/smtpd[2071756]: 31F5C2133B: client=localhost.localdomain[127.0.0.1], orig_client=mailout-108-r2.booking.com[37.10.31.20]
Mar 7 22:51:39 spamfilter postfix/cleanup[2071751]: 31F5C2133B: message-id=<4TrNKs6J3VzJV@mailrouter-601.fra3.prod.booking.com>
Mar 7 22:51:39 spamfilter postfix/qmgr[1953429]: 31F5C2133B: from=<noreply@mailer.booking.com>, size=43245, nrcpt=1 (queue active)
Mar 7 22:51:39 spamfilter postfix/smtpd[2071756]: disconnect from localhost.localdomain[127.0.0.1] ehlo=1 xforward=1 mail=1 rcpt=1 data=1 commands=5
Mar 7 22:51:39 spamfilter pmg-smtp-filter[2071625]: 2133A65EA36EA433E2: accept mail to <userlocal@domain1.eu> (31F5C2133B) (rule: default-accept)
Mar 7 22:51:39 spamfilter pmg-smtp-filter[2071625]: 2133A65EA36EA433E2: processing time: 0.979 seconds (0.794, 0.096, 0)
Mar 7 22:51:39 spamfilter postfix/lmtp[2071752]: 2AACA211F0: to=<userlocal@domain1.eu>, relay=127.0.0.1[127.0.0.1]:10024, delay=1.3, delays=0.21/0.02/0.05/0.98, dsn=2.5.0, status=sent (250 2.5.0 OK (2133A65EA36EA433E2))
Mar 7 22:51:39 spamfilter postfix/qmgr[1953429]: 2AACA211F0: removed
Mar 7 22:51:39 spamfilter postfix/smtp[2071757]: 31F5C2133B: to=<userlocal@domain1.eu>, relay=10.10.10.112[10.10.10.112]:25, delay=0.32, delays=0.05/0.03/0/0.24, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 76F82688213)
Mar 7 22:51:39 spamfilter postfix/qmgr[1953429]: 31F5C2133B: removed

if I send to ie userlocal@domain1.pl - the domains differ only with the .pl/.eu suffix there is no sign of it in the logs (/var/log/mail.log).

 

[Stoiko Ivanov]

if I send to ie userlocal@domain1.pl - the domains differ only with the .pl/.eu suffix there is no sign of it in the logs (/var/log/mail.log).

Then I guess that the issue is with domain1.pl (and booking not sending the mails there) - I'd contact booking and ask them why this does not work...

I hope this helps!

 

[kfam]

Hi Stoiko,
I've called booking.com, and they claim that they have some global issues with the sending emails to some domains.
I hope that it's true, since it's tough to verify without very though access to technical support on their side.
Nevertheless, thank you for the help and time.
Best regards

 

[Stoiko Ivanov]

Hi Stoiko,
I've called booking.com, and they claim that they have some global issues with the sending emails to some domains.
I hope that it's true, since it's tough to verify without very though access to technical support on their side.

hm - I think from your description that you don't see anything in the logs for mails to your domain1.pl from booking would agree with their statement - and booking.com would most likely not say that they are having problems with some emails, if it was not the case (they need that for their business after all).
In my experience such issues are usually resolved within 1-2 Weeks - so you can always try again later!

Thanks for coming back and sharing what they said!