Solved

Exchange 07 bounces one domain even after BypassedSenderDomain list

Posted on 2007-11-14
13
578 Views
Last Modified: 2008-02-01
I have an x64 box running Exchange 07.  In front of it I have a spam server running MailScanner off Ubuntu.  Typically when the linux server bounces something and I add it to the white list, when it tries to relay to Exchange, Exchange then bounces it back to the spam server.  Whenever this has happened in the past, I simply added the mail servers coming in on that bouncing domain (it comes in blocks of entire domains, for all intents and purposes here) to the BypassedSenderDomains list and then it went through fine.  

Now I have found one domain that this doesn't work on.  The incoming mail, I see when I grep for the domain in the mail.log, is bouncing off of at least 5 different servers, usually 3-4 per email before it gets to the spam filter.  The filter then white lists and passes to Exchange, but even though I have added all 5 servers to the BypassedSenderDomains list, Exchange continues to bounce these messages back to spam.

Anyone have an idea?  I'm fresh out and could use a hand.
0
Comment
Question by:Telstar-Networks
  • 6
  • 6
13 Comments
 
LVL 104

Expert Comment

by:Sembee
ID: 20285251
What is bouncing the messages on? Which test is it failing on?

Simon.
0
 
LVL 22

Expert Comment

by:ATIG
ID: 20288418
is this being bounced by your spam box or exchange server..... do you have the antispam agents running on your EX server?
0
 
LVL 1

Author Comment

by:Telstar-Networks
ID: 20290756
I'm not certain what exactly it is failing on.  I do have anti-spam running, but since I had the same issue with all other domains added to BypassedSenderDomains, I'm not sure why this isn't working.  I set sender ID to allow the mail to go through with a stamp, but am waiting for a test to happen.  It is most assuredly the Exchange server that is bouncing, not the spam box in front of it.  I would like to get a copy of the bounced but they never show up.  Checking DNS stuff, it returns that the guy who set this box up apparently never set it to allow null senders, which (if I recall correctly) are used exclusively for error messages on bounce.  Any able to direct me to where I can enable that?  I inherited this machine and am not terribly well versed with Exchange.
0
 
LVL 22

Expert Comment

by:ATIG
ID: 20290776
have you tried disabling your spam agents on exchange, then testing
0
 
LVL 1

Author Comment

by:Telstar-Networks
ID: 20290837
The only one with any actual config done, other than sender ID which I set to stamp and continue processing (still waiting for test), is Sender Rep.  Which shouldn't have anything to do with it.  I'm not entirely sure what this domain's setup is who we can't receive mail from, but initial connection starts with webmail.problemdomain.com, goes to problemdomain03.com, then to 1 of 3 other servers (which all end in .net instead of .com).   Obviously Exchange is not liking this, but the Sender Rep would only flag it as spam and act accordingly.  I currently have it set up to forward all flagged spam to a quarantine box which has no email showing up at all from problemdomain.com
0
 
LVL 22

Expert Comment

by:ATIG
ID: 20290848
you never know, you can always enable it back.......
0
How does your email signature look on mobiles?

Do your employees use mobile devices to reply to emails? With mobile becoming increasingly important to the business world, it is in your best interest to make sure that your email signature looks great across all types of devices.

 
LVL 22

Expert Comment

by:ATIG
ID: 20290852
and you dont have an ndr ?
0
 
LVL 1

Author Comment

by:Telstar-Networks
ID: 20290894
That's true.  It will be my next step should setting sender ID to stamp and continue fails.  

No ndr either.  Once Exchange bounces it back to the spam box, it basically disappears.  Like I said, I don't really know why this happens.  The best I can figure is because null recipient isn't working properly, though I can't find where to enable it.  Though, on the odd side, failures internal to the domain return errors, so it is possible it has something to do with the spam box why outside senders aren't returned errors.
0
 
LVL 1

Author Comment

by:Telstar-Networks
ID: 20291074
Well that did not work, but the error I can grep changed from unable to relay, to External Client does not have permissions to submit to this server.  (550 5.7.1).

In minimal research, it seems that there is an issue with the ms-exch-smtp-submit permission, but checking under server config and hub transport, default, then permission groups, anonymous users is checked.
0
 
LVL 22

Expert Comment

by:ATIG
ID: 20291148
that allows submission but not relay which is appears to be treating it as
0
 
LVL 22

Accepted Solution

by:
ATIG earned 500 total points
ID: 20291155
0
 
LVL 1

Author Comment

by:Telstar-Networks
ID: 20291271
Well, the relay is technically coming from the spam box, which already has a connector set up.  It works for everything but this domain.  The relay setup also only allows local IP addresses.
0
 
LVL 1

Author Comment

by:Telstar-Networks
ID: 20301996
Well, not sure why still, but setting up an SMTP connector to it worked.  Thanks for the help.
0

Featured Post

Want to promote your upcoming event?

Attending an event? Speaking at a conference? Or exhibiting at a tradeshow? Easily inform your contacts by using a promotional banner in your email signature. This will ensure your organization’s most important contacts are in the know.

Join & Write a Comment

Resolve DNS query failed errors for Exchange
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 Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
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…

705 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

19 Experts available now in Live!

Get 1:1 Help Now