Hot answers tagged

3

Received: from mail.hpsteaks.com (66.49.60.114.nw.nuvox.net. [66.49.60.114]) - Isn't a reverse lookup of the name mail.hpsteaks.com. The ip address 66.49.60.114 is the ip address that your email server uses for outbound SMTP traffic (and probably all outbound traffic) and is the ip address that destination email servers see as connecting to them for the SMTP ...


2

joeqwerty is absolutely right, but I think this is a good opportunity to also point out another problem. No Received: from mail.hpsteaks.com (66.49.60.114.nw.nuvox.net. [66.49.60.114]) isn't a reverse lookup of the name mail.hpsteaks.com however, it does show that the IP address your exchange server is sending mail from the wrong public IP address. If ...


1

The first thing I would be looking at is the headers of one of these "delayed" messages. That will show you where the delay is. Users like to complain about the network when it is more often than not their fault. Identify where the delay (if any) is coming from then you can work from there.


1

The Microsoft Online Connectivity Analyzer can tell you if there are general deliverability/connectivity issues but it can't tell you the disposition of a particular email sent from a specific sender to a specific recipient. Here are a couple of things you can do: Enable Protocol Logging on your Receive connector and check the SMTP Receive logs. Use the ...


1

Things to check: Is it being blocked by your spam filter? Do the senders have a lot of links and images in there emails? Do these domains send out a lot adds in general? (this can land them on a black list and you may need to manually allow them in your spam filter) I deal with this a lot where I work and it is almost always because the vendor was ...



Only top voted, non community-wiki answers of a minimum length are eligible