Solved

Having trouble sending to some domains

Posted on 2011-03-25
15
270 Views
Last Modified: 2012-05-11
We have SBS2008, which was migrated from SBS2003 and working fine for about a year. Outlook 2007 is the client and OWA has the same results. Recently, we are sending e-mail to some domains and they are not receiving them - most domains work fine. We are using our ISP as the Smart Host on Exchange, but even when we change to DNS, the e-mail doesn't get there. I've turned on logging and the logs show that the e-mail was sent. There is nothing in the SMTP queue.

We are not showing up on any blacklists.

We are also using GFI to add a disclaimer to the end of every e-mail.

What tools can I use to troubleshoot this?
0
Comment
Question by:notacomputergeek
15 Comments
 
LVL 10

Expert Comment

by:Hutch_77
Comment Utility
Telnet is the best I can think of in combination with MX toolbox to get all the information of the other domain
Telnet into their mailserver on port 25 and see if it lets you pass an email through manually.

If it does not reject then you are looking at a DNS issue somewhere
0
 
LVL 12

Expert Comment

by:FDiskWizard
Comment Utility
Never assume the other side knows what they're saying. "Not getting the email" can mean a lot of things. I've had many companies block us because our email passes through our parent company outside of the US.

Besides TELNET host 25, there is a small utility called Bmail.exe that is easier to use. You just provide Subject, etc.... and I would suggest using the -H option to force headers.
If there is an error talking to the server, it will show you on the command line.

Run either from your actual mail server, so that you have the same scenario.


0
 
LVL 41

Expert Comment

by:Amit
Comment Utility
Check this link,

http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_26909143.html

There is a very good article from Alan. That can help you out.
0
 
LVL 13

Author Comment

by:notacomputergeek
Comment Utility
I can telnet into mail.mydomain.com and send a message and it is received. I have also configured another personal account using Microsoft Mail on a Windows XP computer to send with mail.mydomain.com and it is received. I can also log into my Smart Host webmail and send from there and it is received.

bmail will not install on my 64-bit server.

So, I think the problem is on my Exchange server. I know the Outlook client is communicating with the Exchange server, because I can see it in the SMTP logs. Once at the server it looks like it's been sent, but goes nowhere.
0
 
LVL 13

Author Comment

by:notacomputergeek
Comment Utility
Just to clarify, mail.mydomain.com is an AT&T server (Smart Host), not our Exchange server.
0
 
LVL 10

Expert Comment

by:Hutch_77
Comment Utility
I know what your problem is.

The clients are using your exchange server to send rather than the smart host, and because your MX records would point to that server it is being blocked.
0
 
LVL 10

Expert Comment

by:Hutch_77
Comment Utility
Doh hit submit to quick.

I had a client before that setup the Exchange to store email and imap or pop using a hosted solution.. Wh I didnt know but they wanted it that way.  Problem was when people would fiddle with outlook they would set their exchange to primary and it would then send all email using exchange which works great for internal and even for a lot of external until you get to a client that uses a spam protection or looks for proper MX records and you get this problem.  When they reply to it he address it goes to the hosted solution and this works and all internal email stays internal.  
0
How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

 
LVL 13

Author Comment

by:notacomputergeek
Comment Utility
Not sure I follow. The clients' Outlook accounts are set up as an Exchange account and Exchange is set up to send through the Smart Host.

Can you elaborate on your answer?
0
 
LVL 10

Expert Comment

by:Hutch_77
Comment Utility
Ok I misunderstood.  I was under the impression that the clients hit the hosted email and stored in exchange.

Do you have an external account you can send emails to and see what happens?  do you have email sitting int he q's that are not releasing?

And the OWA is that a hosted OWA orr is that actually on your exchange server you tested from?
0
 
LVL 13

Author Comment

by:notacomputergeek
Comment Utility
This client is using POP and AT&T to host e-mail. I think it's mainly to not have their e-mail open to the whole world and let AT&T's servers filter alot of incoming junk. It also allows their company to function (e-mail-wise) if they lose connection to the internet or the server goes down.

What are the solutions?
0
 
LVL 13

Author Comment

by:notacomputergeek
Comment Utility
Yes, I have an external account I've been using for testing (2 actually at different domains). No e-mail in the queues, unless there's another place other than the Queue Viewer. Yes, OWA is our Exchange server.
0
 
LVL 1

Expert Comment

by:vagedis23
Comment Utility
Make sure your reverse dns record (PTR record) for your mail server is avaiable on the internet. Somers mail servers perform à reverse lookup when they receive an email from another mail server. The ip adres must be resolvable back to the same name your mail server has in your MX record.

If you do not host your dns yourself, talk to your ISP. They can create the PTR record for you

Good luck !
0
 
LVL 10

Expert Comment

by:Hutch_77
Comment Utility
ok I read webmail as OWA but that is a different service.  at this point I would talk with ATT and see if they made any changes.  

If it was working yesterday or a week ago and you made no changes then it should still work unless ATT mad e a change.  It appears the break is between your smarthost and your exchange server.
0
 
LVL 13

Accepted Solution

by:
notacomputergeek earned 0 total points
Comment Utility
I went ahead and reconfigured the server this weekend to receive e-mail directly and not use AT&T mail servers/POP3. Changed DNS and got AT&T to change rDNS PTR. I still had the same problem. E-mail was not being delivered to any @cox.net or domain hosted by Network Solutions. These are the ones I could verify. Talked to NS and they said our domain was blacklisted and would put in a request to unblock. I called COX and they apparently don't block domains, but the tech support offered to do some tests. After changing the SPAM setting in our COX account from "automatically delete" to "allow it, but mark as SPAM", a test e-mail came into the COX Inbox, but was tagged as SPAM. I did further tests to confirm this, but apparently the GFI disclaimer added to every one of our emails was causing it to be flagged as SPAM by some mail servers. I disabled the GFI disclaimer on the server and added the same disclaimer to my signature in Outlook and it was not detected as SPAM. Without talking to GFI, I can only assume that the HTML encoding on the disclaimer was triggering it as SPAM. Here is the disclaimer:
The information and any attachments contained in this email message may
be privileged, confidential, and protected by law from disclosure. If you are
not the intended recipient, any dissemination or copying is strictly prohibited
by federal law. If you think that you may have received this email message
in error, please notify the message sender at the email address above and
destroy this message.

Pretty staight forward, but causing a problem. What I don't know is why it's apparently worked for at least 6 months and now doesn't. It's possible companies have tightened up their mail servers due to excessive SPAM. All e-mail is flowing fine this morning, except for one @sbcglobal.net that was blocked. I contacted AT&T and they were able to unblock it.

I will wait to close this, in case there are further comments.

0
 
LVL 13

Author Closing Comment

by:notacomputergeek
Comment Utility
Discovered solution on my own.
0

Featured Post

Don't lose your head updating email signatures!

Do your end users still have the wrong email signature? Do email signature updates bore you or fill you with a sense of dread? You can make this a whole lot easier on yourself by trusting an Exclaimer email signature management solution. Over 50 million users do...so should you!

Join & Write a Comment

Disabling the Directory Sync Service Account in Office 365 will stop directory synchronization from working.
Following basic email etiquette rules will help you write a professional email and achieve a good, lasting impression with your contacts.
In this video we show how to create a User Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Mailb…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

771 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now