Solved

MS Exchange STMP outbound sends "QUIT" after it receives the 1st E3210 Invalid Recipient message

Posted on 2009-04-02
5
851 Views
Last Modified: 2013-11-30
Hi.

This has had me puzzled, this is occuring with the emails that we are sending to @charter.net.

Basicly if we send a batch of ~30 emails they will process fine until charters server replys with a " 511 5.1.1 Invalid recipient: <xxxxx@charter.net> E3210"

At this point the exchange server just sends the "QUIT" command and applies this error to all remaining messages (weither its good or not):
"<deleted.org #5.1.1 smtp;511 5.1.1 Invalid recipient:<xxxxx@charter.net> E3210>"

This happens to all of the remaining messages.

The log SMTP looks like this:

216.33.127.20       OutboundConnectionCommand       3/31/2009       17:16:42       RCPT       -       TO:<xxxxx@charter.net>
216.33.127.20       OutboundConnectionResponse       3/31/2009       17:16:42       -       -       511 5.1.1 Invalid recipient: <xxxxx@charter.net> E3210
216.33.127.20       OutboundConnectionCommand       3/31/2009       17:16:42       QUIT       -       -
216.33.127.20       OutboundConnectionResponse       3/31/2009       17:16:42       -       -       221 2.0.0 imp07 charter.net closing connection

Any ideas?
0
Comment
Question by:rottenit
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
5 Comments
 
LVL 15

Expert Comment

by:abhaigh
ID: 24077027
I'd contact them to find out what they are running on their border and let them know that you are having an issue sending to them.
0
 

Author Comment

by:rottenit
ID: 24077122
I have tried to contact them, they will not respond.

I have also tried the following tests:

(I pre-veriied by hand the emails below against there SMTP server)
10 emails with 1 known bad address = all emails rejected
10 emails with 0 known bad address = all emails accepted

From the SMTP logs it really looks like our exchange server is the one terminating the connection.

I should have included that in the original post.
0
 
LVL 15

Accepted Solution

by:
abhaigh earned 500 total points
ID: 24077323
Searching Google for "Invalid recipient: E3210" shows at least one other site having similar issues in sending to 'charter.net'

Another link suggests turning on Pipeline tracing (http://technet.microsoft.com/en-us/library/bb125018.aspx) in order to determine if the mail has been modified by any transport agent before leaving your exchange system

I'm wondering if they aren't employing some funky form of greylisting that is configured to reject any and all messages being sent in bulk if one of the addresses is bogus

And I would certainly think that this problem is being caused by their setup, not yours. If there was something amiss with your setup you would be experiencing issues sending to far more than just one domain
0
 

Author Comment

by:rottenit
ID: 24077437
Thanks for finding that, I tried a few searchs but didn't hit that keyword combination.

From what I can tell the  Pipeline tracing  is only avaliable on Exchange 2007, I should have but didnt state that we are using SBS 2003 which has Exchange 2003.

As far as the greylisting that sounds like a viable option, this was working fine up until a couple of weeks ago (Seems to coinside with the post you linked to).

Normaly we forward to a smarthost at our hosted anti-spam provide (Spamsoap reseller for mxlogic) but they will use different outbound SMTP servers on there end which is causing an invalid SPF record for us. Charter started to reject all of our messages because of this so I created a SMTP connector to just deal with charter 1 to 1.
0

Featured Post

[Webinar] Code, Load, and Grow

Managing multiple websites, servers, applications, and security on a daily basis? Join us for a webinar on May 25th to learn how to simplify administration and management of virtual hosts for IT admins, create a secure environment, and deploy code more effectively and frequently.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
CAL for Disabled accounts 4 58
exchange 2013 10 39
How to use File,History in Excel 2016 for Windows? 5 44
Exchange 2010 - SBS 2011 - Public calenders 4 31
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
Phishing attempts can come in all forms, shapes and sizes. No matter how familiar you think you are with them, always remember to take extra precaution when opening an email with attachments or links.
In this video we show how to create an Accepted Domain 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 Mail Flow >> Ac…
To show how to generate a certificate request 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 Servers >> Certificates…

752 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