amlydiate
asked on
Emails bouncing to new domain email address set up on SBS Server 2011
Hi All,
My client has a 2011 SBS server used mainly for email on "myclient.co.uk" domain. I've been asked to set up some emails for a different domain, let's say "myclient2.co.uk"
So, I've gone into EMC and I've entered "myclient2.co.uk" as an accepted domain (authoratitive) in Hub Transport>Accepted Domains. I've then gone into ADUC and created 4 new users. I've then gone back into EMC and I've created the 4 new mailboxes and linked them to the new users and made sure the new domain email address is the default for each user. I've logged on to OWA as one of the new users and successfully sent an email which I've received in my own email account. I've then gone into the domain control panel for myclient2 with 1and1 and I've created mail.myclient.co.uk and pointed it to the external IP of the mail server and created an MX record pointing to mail. with a pref of 10. When I ping mail.myclient2.co.uk I get the correct IP address come up and MXtoolbox reports everything pointing to the right IP address. However all emails to the new addresses are being bounced almost immediately with "Invalid address" coming from 1and1 mail server.
If this was a DNS propogation delay then surely the ping and MXToolbox would come back from the old 1and1 system rather than from the IP of the server?
Any help gratefully received!
Thanks
Adam
My client has a 2011 SBS server used mainly for email on "myclient.co.uk" domain. I've been asked to set up some emails for a different domain, let's say "myclient2.co.uk"
So, I've gone into EMC and I've entered "myclient2.co.uk" as an accepted domain (authoratitive) in Hub Transport>Accepted Domains. I've then gone into ADUC and created 4 new users. I've then gone back into EMC and I've created the 4 new mailboxes and linked them to the new users and made sure the new domain email address is the default for each user. I've logged on to OWA as one of the new users and successfully sent an email which I've received in my own email account. I've then gone into the domain control panel for myclient2 with 1and1 and I've created mail.myclient.co.uk and pointed it to the external IP of the mail server and created an MX record pointing to mail. with a pref of 10. When I ping mail.myclient2.co.uk I get the correct IP address come up and MXtoolbox reports everything pointing to the right IP address. However all emails to the new addresses are being bounced almost immediately with "Invalid address" coming from 1and1 mail server.
If this was a DNS propogation delay then surely the ping and MXToolbox would come back from the old 1and1 system rather than from the IP of the server?
Any help gratefully received!
Thanks
Adam
Can you include the entire bounceback message with the error numbers?
ASKER
Here you go, names have been changed...
mx-b.kundenserver.de rejected your message to the following e-mail addresses:
Chris (chris@myclient2.co.uk)
mx-b.kundenserver.de gave this error:
<chris@myclient2.co.uk>: invalid address
A problem occurred during the delivery of this message to this e-mail address. Try sending this message again. If the problem continues, please contact your helpdesk.
Diagnostic information for administrators:
Generating server: 2K11SERVER.mydomain.local
chris@myclient2.co.uk
mx-b.kundenserver.de #550 <chris@myclient2.co.uk>: invalid address ##
Original message headers:
Received: from 2K11SERVER.mydomain.local ([fe80::14:b8cf:231:cfc7]) by
2K11SERVER.mydomain.local ([fe80::1c4d:5e8:fc61:6e5a %11]) with mapi id
14.01.0438.000; Tue, 5 Feb 2013 13:35:40 +0000
From: Adam Lydiate <adam@mydomain.co.uk>
To: "Chris" <chris@myclient2.co.uk>
Subject: RE: Test
Thread-Topic: Test
Thread-Index: Ac4DoH1VqB5YMt75QiKg0NPd5M c5mwABS8/g
Date: Tue, 5 Feb 2013 13:35:40 +0000
Message-ID: <39A17EAB256A8C4DAD546A97B 59401F8904 862@2K11SE RVER.mydom ain.local>
References: <9C3DEC633EC96A4896E0E3151 F02B1168C4 81D@2K11SB SSERVER.my client.loc al>
In-Reply-To: <9C3DEC633EC96A4896E0E3151 F02B1168C4 81D@2K11SB SSERVER.my client.loc al>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.13]
Content-Type: multipart/related;
boundary="_004_39A17EAB256 A8C4DAD546 A97B59401F 8904862MyS ERVERdomai nl_";
type="multipart/alternativ e"
MIME-Version: 1.0
mx-b.kundenserver.de rejected your message to the following e-mail addresses:
Chris (chris@myclient2.co.uk)
mx-b.kundenserver.de gave this error:
<chris@myclient2.co.uk>: invalid address
A problem occurred during the delivery of this message to this e-mail address. Try sending this message again. If the problem continues, please contact your helpdesk.
Diagnostic information for administrators:
Generating server: 2K11SERVER.mydomain.local
chris@myclient2.co.uk
mx-b.kundenserver.de #550 <chris@myclient2.co.uk>: invalid address ##
Original message headers:
Received: from 2K11SERVER.mydomain.local ([fe80::14:b8cf:231:cfc7])
2K11SERVER.mydomain.local ([fe80::1c4d:5e8:fc61:6e5a
14.01.0438.000; Tue, 5 Feb 2013 13:35:40 +0000
From: Adam Lydiate <adam@mydomain.co.uk>
To: "Chris" <chris@myclient2.co.uk>
Subject: RE: Test
Thread-Topic: Test
Thread-Index: Ac4DoH1VqB5YMt75QiKg0NPd5M
Date: Tue, 5 Feb 2013 13:35:40 +0000
Message-ID: <39A17EAB256A8C4DAD546A97B
References: <9C3DEC633EC96A4896E0E3151
In-Reply-To: <9C3DEC633EC96A4896E0E3151
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.13]
Content-Type: multipart/related;
boundary="_004_39A17EAB256
type="multipart/alternativ
MIME-Version: 1.0
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Domain has been in place for a few months. I agree it looks like DNS however if I ping mail.myclient2.co.uk It comes back with the correct IP address and when I use MXToolbox and perform a lookup on myclient2.co.uk it responds with the fqdn of the mail server and the correct IP address so if it were DNS surely that wouldn't happen?
ASKER
After all that the pings and the mxtoolbox were just red herrings, 24 hours later and all started working. Yep, DNS issue! Thanks...
Yeah I hate that waiting game!! Glad to know it's working.