email showing as recieved from shared server name not mail.domain.com

[roly]

hi

i've just followed the guide here https://www.directadmin.com/features.php?id=1692 for DA to manage the outbound ip. the /etc/virtual/domainips and /etc/virtual/helo_data files are all correct now. however when i check email headers it's still showing as recieved from the main shared server and not from the sending domain. although spf,dkim and dmarc are all set my emails sent from domains are blocked sending to outlook, but emails sent from domains on the shared server ip are sent to outlook without a problem. I recently moved to a new server and didn't have issues setting this up on previous server, so i'm assuming it's something i have misconfigured but can't figure out where i am going wrong. if anyone has any advice is would be gratefully recieved. i'm using exim 4.5.35.

thanks in advance

 

[roly]

i've checked on mxtoolbox and everything seems to look ok, with the exception of "dmarc policy not eneabled" although i have
"dmarc policy published" which from what i have read should be adequate. these are mxtoolbox results:

SMTP Reverse DNS Mismatch OK - 51.xx.xx.xx resolves to mail.domain.co.uk
SMTP Valid Hostname OK - Reverse DNS is a valid Hostname
SMTP Banner Check OK - Reverse DNS matches SMTP Banner
SMTP TLS OK - Supports TLS.
SMTP Connection Time 0.291 seconds - Good on Connection time
SMTP Open Relay OK - Not an open relay.
SMTP Transaction Time 1.181 seconds - Good on Transaction Time

the session transscript seems to show that i am connecting as mail.domain.co.uk and not the main shared server server name so maybe i was not reading the email headers correctly. so i'm a litle unsure as to why only domains on the main shared server IP can send email to hotmail and not any of the domains on their own dedicated ip addresses.

i don't seem to have any issues with sending to gmail just hotmail. i signed up to SNDS and it shows the ip addresses in question "Blocked due to user complaints or other evidence of spamming" obviously there's no spamming and they're new ip addresses.

 

[Richard G]

"dmarc policy published" which from what i have read should be adequate. these are mxtoolbox results:

If you have a DMARC record published, but policy not enabled, then it's most likely you have no p record in your DMARC or p=none. Which means you do have DMARC but it has no policy enabled. The p=none is mostly use to test of everything will keep working correctly.
After that you can use p=quarantaine or p=reject, start with lower percentage like 30 to see if all keeps going wel.
For percentage you can use the pct=XX like pct=30 for 30 percent.

 

[roly]

Thanks richard that's very helpful. i've implemented that now, so no obvious issues at all that now i can see. as the ip addresses seem to be blacklisted at outlook (not sure if it's because they are new new or prior history) i've contacted them and they have escalated the issue so i shall wait to find out. thanks again

 

[Richard G]

You're welcome.

(not sure if it's because they are new new or prior history)

Can indeed be either. Good they escalated the mail because normally you would get a default answer, and you hae to reply to that first to get a real employee to have a look at things.
They often greylist new and unkown ip's nowadays also which causes mail to get into the spamfolder.

 

[roly]

You're welcome.

Can indeed be either. Good they escalated the mail because normally you would get a default answer, and you hae to reply to that first to get a real employee to have a look at things.
They often greylist new and unkown ip's nowadays also which causes mail to get into the spamfolder.

yes i got the default auto generated email initially, and then once i replied to that i got a real person who said they were escalating the issue up the line. so i will keep my fingers crossed. thanks again

 

[roly]

You're welcome.

Can indeed be either. Good they escalated the mail because normally you would get a default answer, and you hae to reply to that first to get a real employee to have a look at things.
They often greylist new and unkown ip's nowadays also which causes mail to get into the spamfolder.

Hi Richard, just an update. Microsoft have come back to me and implemented mitigation on my ip's. no inidcation as to why they were blacklisted but all good to go now. So a bit of a pain, but Microsoft are fairly responsive.

 

[Richard G]

Hello Roly.
Yep, even if you ask they mostly don't give you any reply as to why it was blacklisted. But you will get your ip's from the blacklist and that is what counts..
P.s. you don't need to quote complete posts to post an answer.

Good to hear they helped you. Keep up to good work!