Server emails end up in spam: DKIM / SPF / DMARC = pass

The only thing I can think of (which I would find odd) is that mailgenius would not support ipv6 and therefore there is a fallback to ipv4.
But I can't imagine mailgenius not to be able to receive ipv6, so I'm probably wrong.

Sorry, hope somebody else can help you here further, I don't work with ipv6 so too little experience with this yet.
Maybe @zEitEr or somebody else have an idea?
 
@peps03 a lot in the mailworld is not working on ipv6 only!

So i think mailtesters to, then only thing is or no mail or server ipv4 adress ...

Microsoft is hmm lot of ipv4 only, where google gmail should do ipv6 but they G. have errors not reachable mailservers on ipv6 to ( see the internetnl test i mentioned to you. ;)

If using phpmail forms most of the time better to use only the smtp part of that for all having problems with that

Technische details:​



Mailserver (MX)Onbereikbaar IPv6-adres
alt3.googlemail.com.2a00:1450:......
alt4.googlemail.com.2a00:1450:....
Click to expand...
 
Last edited:
This is why I've never been much of a fan of SPF, DKIM, and DMARC. (I really can't figure out the point of DMARC.... "nobody could figure out how to use SPF and DKIM so we've created something new that allows you to specify how you want your poorly constructed SPF and DKIM records are viewed")

There's a narrative within the industry that you can somehow control how mail from your server is handled. You can't.

How your mail is handled by providers goes back to IP reputation and content.

Don't get me wrong - a lot of mail servers will hinder or not accept your mail if you don't have valid SPF, DKIM, and DMARC records. But if you think simply having valid SPF, DKIM, and DMARC records is going to put your mail into the recipient's Inbox for viewing, that's just a false thinking.

You can have all the valid SPF, DKIM, and DMARC records you want, if the IP reputation and/or content of your message is poor - your message is not going into the Inbox.

And both IP reputation and content is subjective. One mail server may say your IP has a good reputation another might say it's a bad reputation. One might view your email content as good, another might view it as bad.

Certainly if your IP is listed on many public spam blacklists, that's not going to help your IP reputation. But even if it's not listed that doesn't necessarily give you a clean bill of health.

Want to know why a certain provider isn't delivering your message into your recipient's Inbox? You'll have to ask them. And good luck getting any information from them - assuming you can even find a contact for them.
 
sparek said:
You can have all the valid SPF, DKIM, and DMARC records you want, if the IP reputation and/or content of your message is poor - your message is not going into the Inbox.
Click to expand...
That's only the case on certain providers. We had some servers starting with a poor reputation which we build up to neutral or good reputation.
If you do not have SPF and DKIM and you have a poor reputation ip, you are correct. But you got a way better chance when having correct SPF and DKIM records to build up a good reputation.

We're working for almost 14 years now and there is 1 hidden blacklist which you have to know how to get off, and there is the dynamic filter of Microsoft which is hard to get off some times.
But keeping good policy, loads of hosters here don't have big issues keeping mails out of spamfolders.

In this specific case it's a totally different matter. Because it seems not all systems are accepting ipv6 only mail. The problem here is that the topic starter uses a shared ipv4. So as soon as there is a fallback to ipv4 due to not accepting ipv6 the mail will get into the spambox because the rDNS/PTR is incorrect, which is quite logical.

I'm afraid the only solution might be to either use seperate ipv4 and ipv6 for all customers (too expensive), or only use the ipv4 and ipv6 shared server ip (hostname) for sending mail and not the ipv6 given to the user.
 
No. You only have to take care that their mail A records and the MX record are pointing correctly.
That way they can keep using [email protected] and mail will be send from the ipv4 from the server. So be sure in their SPF record they also have that ipv4 or something like "a mx" in there.

There is also a way that every client can use the hostname, so like vps.domain.com but I wouldn't suggest that as this takes again various customizations. However that is only for mail sending, it wouldn't change their email address either.
 
peps03 said:
Trying this option now.
Does it imply that if a client has a form on their website, that they should update the sender (from) address to the server domainname?

So from: [email protected] to [email protected] ?
Click to expand...
smtp in phpmailer There ofcourse then the useraccount host the server hostname and in the mx record for that domain the server/hostname for example should be ok, that is what we have and use.

But that is with no mail on mail.domain itself, so server / hostname is mailserver for domain and n MX

So that from Richard or this depending on config used
 
You must log in or register to reply here.
Back
Top