Exchange Server SBS 2003

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Hi everyone, having a little problem with an exchange server, before now the original configuration was to use pop3 connectors and drop the mail in the users mailboxes. Thomas had a great idea to use it as a fully fledged email server plus it would allow me to expand my knowledge into a new area(not touched or administered a exchange server before), so ditched the old connectors, changed the mx records on our domian and the revisted the email wizard to get it all going.

Everything went as expected with no errors, so after a little testing(open rely,nslookup etc etc) i started trying to send some emails. Started with internal, all good and then tryed sending email to myself externally all the emails are bouncing with 550 NDR did i miss something.

Now i bet its something really silly but i've been at it all day and still no joy below is the bounce mail message

i would be very grateful if someone could help me in this situation

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Takes a while for the MX records to propagate across the Internet... are you certain it's propagated already?

 

its been 24+ hrs since the mx change

 

Static IP which is reversed to your domain?

Linky

 

Sometimes takes up to 72 hours, but it usually works within 24...

 

Info

so this is my problem?

 

Are you using BT for your outgoing ? If so, have you asked them to configure there SMTPs four your domain to relay through ?

Prepare to now start jumping through hoops to ensure that the whois information for your domain is consistent with the details they have for you. They may start asking for you to change the Billing contact on the domain to the same as the BT account holder (if this is related to your problem, that is)

HTH.

 

no Jak i use bt in the head office and was only using it to send emails to the test account on the exchange server

 

I followed a great article i found on the DP site/forum when I set up exchange on SBS; reverse dns was one of the things to "get right". I'll have a look through the bookmarks and post back....

Have you tried External > Exchange? If so, what happens?

 

External > Exchange - 550 NDR

External < Exchange - Working

 

did i drink too much last night, or does that mean the same?!

 

lol sorry what about

External -> Exchange - 550 NDR

sending emails from the exchange server to external addresses seems ok

 

Would 1 email getting through to the correct mailbox backup this up?

 

Found it;

Linky

Hope it helps.

 

Not necessarily. Depends where the email was sent from and if the SOA DNS server had received the MX update. Do you know what the TTL was on the mx record? That should tell you how long it takes for the update to propogate.

Have you tried sending an email to the server using the Public IP of the server, or telnet into it?

 

Oh Yeah, have you tried testing the email address on DNS Stuff.com? You will almost certainly get told if it's a DNS error on there.

PM me if you can't use the service. I got my boss to pay for an account at work so I can run the test and send you the results if you want? I'm only work for another half hour though.

This may help too!

 

I manage to get it working after following that guide from Boyce but thanks to everyone that replied

 

What was it Thomas?

Simon