Some emails are not received in time

[Art1]

Hey guys,

in the last couple of days I face issue with receiving emails in time. Some are delivered quickly, others take hours. This is especially bad if you want to sign up somewhere and wait for a verification email.

Anyone facing the same? Any solutions?

Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services

[VincentS]

Hello,
I have been facing this situation already. I have not noticed it recently, but it is maybe because of the solution I chose : I use another email adress for the accounts that send a code by mail… But it’s a pity !

[tcecyk]

there’s been a DANE validation failure in receiving from 6th of July, solved on the 10th.

Can you quote the providers / domains that come in late?

[Art1]

...@jobagent.stepstone.de
...@hivemq.com

these for example

[tcecyk]

hivemq uses sendgrid, their smtp is quick to connect. Easy to test with a user registration.

Murena keeps all evaluations counting towards the spam decision in the mail header (X-Spam / X-Rspamd prefix).

The headers though give no indication that I’m aware of if the mail was graylisted at first receive (causing a delay). Subscribing murena users can ask helpdesk what contributes to the delay.

[tcecyk]

@Art1 with what domain did you sign up at hivemq? in my sample of 1 I noticed murena.io mail gets through quickly, for e.email there is no delivery at all (ouch). But both very likely use the same rspamd system, so I guess the non delivery is due to the spamfilter. Still here’s the example headers for reference

spam x-headers for hivemq

X-Rspamd-Action: no action
X-Spam-Status: No, score=4.29
X-Rspamd-Server: mail01
X-Rspamd-Queue-Id: 13A9B348501B
X-Spam-Level: ****
X-Spamd-Result: default: False [4.29 / 15.00];
        RBL_SENDERSCORE(2.00)[168.245.36.80:from];
        URI_COUNT_ODD(1.00)[3];
        SUSPICIOUS_URL_IN_SUSPICIOUS_MESSAGE(1.00)[];
        FORGED_SENDER(0.30)[cloud@hivemq.com,bounces@em446.hivemq.com];
        BAD_REP_POLICIES(0.10)[];
        MIME_GOOD(-0.10)[multipart/alternative,text/plain];
        MX_GOOD(-0.01)[];
        RBL_SPAMHAUS_BLOCKED(0.00)[168.245.36.80:from];
        TAGGED_FROM(0.00)[14531386-b504-example=murena.io];
        ARC_NA(0.00)[];
        DBL_BLOCKED(0.00)[sendgrid.net:url,hivemq.com:dkim,hivemq.com:email,xvfrnqrh.outbound-mail.sendgrid.net:rdns,xvfrnqrh.outbound-mail.sendgrid.net:helo];
        RCVD_TLS_LAST(0.00)[];
        FUZZY_BLOCKED(0.00)[rspamd.com];
        TO_MATCH_ENVRCPT_ALL(0.00)[];
        R_DKIM_ALLOW(0.00)[hivemq.com:s=m1];
        FROM_HAS_DN(0.00)[];
        DMARC_POLICY_ALLOW(0.00)[hivemq.com,quarantine];
        DKIM_TRACE(0.00)[hivemq.com:+];
        PREVIOUSLY_DELIVERED(0.00)[example@murena.io];
        MID_RHS_MATCH_FROM(0.00)[];
        TO_DN_NONE(0.00)[];
        FROM_NEQ_ENVFROM(0.00)[cloud@hivemq.com,bounces@em446.hivemq.com];
        RCVD_COUNT_TWO(0.00)[2];
        MIME_TRACE(0.00)[0:+,1:+,2:~];
        RWL_MAILSPIKE_POSSIBLE(0.00)[168.245.36.80:from];
        R_SPF_ALLOW(0.00)[+ip4:168.245.0.0/17];
        RBL_NIXSPAM_FAIL(0.00)[168.245.36.80:server fail];
        REDIRECTOR_URL(0.00)[sendgrid.net];
        MISSING_XM_UA(0.00)[];
        ASN(0.00)[asn:11377, ipnet:168.245.0.0/18, country:US];
        RCPT_COUNT_ONE(0.00)[1]

Edit: so I’ve received the hivemq registration to @e.email with a ~36h delay. Not sure, could also be up to sendgrid itself, their status page was busy last few days but not an exact match on timeframe.