Issue Plesk Email - Automated emails take long to receive

[tlatch52]

There is a strange issue I've had lately with my plesk email inboxes. Any kind of verification email like password resets from various websites seem to take forever to receive in my inbox.

Example: Coinbase.com user verification on new devices, email it supposed to send instantly but I receive it hours later by the time is expires.

Normal emails sent back and forth are nearly instant, no different than Gmail or other platform mail. It seems only related to big websites that send out the automated mail.

My spam score setting (spamassasin) on this particular domain is set a little higher than normal, just because I've used this domain for mail over a long period of time. Could that be a reason why these specific types of emails are being held up so long? It's strange though because it lets them to my inbox anyways... just takes forever.

Thanks

 

[Monty]

Step 1: Analyze the headers of such a delayed mail by looking at the "Received:" lines (bottom to top). There you will see at which hop the delay occurred.

Step 2: Analyze the mail logs on your server to see what happened.

 

[tlatch52]

Step 1: Analyze the headers of such a delayed mail by looking at the "Received:" lines (bottom to top). There you will see at which hop the delay occurred.

Step 2: Analyze the mail logs on your server to see what happened.

Hey, thanks for your reply & suggestions.

I compared the logs of two different authentication messages I received - one came in instantly and the other was the one that took hours. Any tips would be appreciated.

1. This one came in nearly instantly as the log states (spam score 1.2/8.0). I believe spam score requirement is default. 11:30AM. This email uses a domain for mail sending that includes the actual robinhood.com domain via sendgrid.net.

2021-10-04 11:30:14	dovecot	service=lda, user=hidden, ip=[]. msgid=<TIVbHhpiQsW-KhAqNsVTIg@ismtpd0178p1iad2.sendgrid.net>: saved mail to INBOX
2021-10-04 11:30:14	spamd[13029]	spamd: result: . 1 - DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,HTML_FONT_LOW_CONTRAST,HTML_MESSAGE,MPART_ALT_DIFF_COUNT,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS,T_FILL_THIS_FORM_SHORT,UNPARSEABLE_RELAY,URIBL_BLOCKED scantime=1.1,size=41523,user=hidden,uid=30,required_score=8.0,rhost=::1,raddr=::1,rport=39006,mid=<TIVbHhpiQsW-KhAqNsVTIg@ismtpd0178p1iad2.sendgrid.net>,autolearn=no autolearn_force=no
2021-10-04 11:30:13	spamd[13029]	spamd: processing message <TIVbHhpiQsW-KhAqNsVTIg@ismtpd0178p1iad2.sendgrid.net> for hidden:30
2021-10-04 11:30:12	postfix/cleanup[15741]	6E324FDDE9: message-id=<TIVbHhpiQsW-KhAqNsVTIg@ismtpd0178p1iad2.sendgrid.net>

2. This one came in at 3:48PM compared to the 6:47AM stated in the logs/header (spam score=-0.7/6.0). This is the email address I use that has a slightly stricter spam score requirement. The main difference I see is that this coinbase.com message uses amazonses.com mail to deliver its messages and the spamd process lists it. However, I'm not sure why it says it was placed in the inbox at the correct time, when it really came in hours later.

2021-10-03 06:47:31	dovecot	service=lda, user=hidden, ip=[]. sieve: msgid=<0100017c42c3c0c1-7e24ea47-b676-49a1-a9fc-b8c7476dd7b3-000000@email.amazonses.com>: stored mail into mailbox 'INBOX'
2021-10-03 06:47:31	spamd[7462]	spamd: result: . 0 - BAYES_00,DATE_IN_PAST_12_24,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,HEADER_FROM_DIFFERENT_DOMAINS,HTML_FONT_LOW_CONTRAST,HTML_MESSAGE,MIME_HTML_ONLY,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,T_KAM_HTML_FONT_INVALID,URIBL_BLOCKED scantime=3.6,size=13222,user=hidden,uid=30,required_score=6.0,rhost=::1,raddr=::1,rport=52568,mid=<0100017c42c3c0c1-7e24ea47-b676-49a1-a9fc-b8c7476dd7b3-000000@email.amazonses.com>,bayes=0.000000,autolearn=no autolearn_force=no
2021-10-03 06:47:27	spamd[7462]	spamd: processing message <0100017c42c3c0c1-7e24ea47-b676-49a1-a9fc-b8c7476dd7b3-000000@email.amazonses.com> for hidden:30
2021-10-03 06:47:27	postfix/cleanup[10941]	D6EFDFC3AD: message-id=<0100017c42c3c0c1-7e24ea47-b676-49a1-a9fc-b8c7476dd7b3-000000@email.amazonses.com>

 

[tlatch52]

For now I just whitelisted *@amazonses.com on my accounts & now many of the previous stalled emails from various websites come through instantly.

Still interested to know why they were delayed though. Is 'spamd' different than 'SpamAssassin'?

 

[mow]

For now I just whitelisted *@amazonses.com on my accounts & now many of the previous stalled emails from various websites come through instantly.

Still interested to know why they were delayed though. Is 'spamd' different than 'SpamAssassin'?

no, that should be spamassassin's perl script running as daemon.

Strange, I usually only have issues caused by greylisting when the sending service has multiple mail-out hosts it cycles through, triggering the deferring each time until it finally uses a host a second time and is let through.