|
|
Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
Hi
Problem:
We have a new server which should have gone live last night. Since we only
have 20 users I recreated the AD accounts, migrated the exchange boxes with
xmerge and basically spent the last month configuring the box to be a similar
as possible to our existing SBS server including the DNS.
All email tests were successful, internal and outgoing external. The last
remaining task was to switch the router SMTP firewall to the new server IP.
After this was done we tried sending emails from external clients, gmail,
hotmail , aol etc and we got this message each time.
PERM_FAILURE: SMTP Error (state 13): 550 5.7.1 Unable to relay for
user[ at ]domain.co.uk
I have double checked the SMTP settings in exchange including relay and they
are as advised on many posts I found on the subject and also identical to the
old server.
The fire wall is disabled.
Any ideas?
|
|
Jason wrote:
[Quoted Text] > Hi
>
> Problem:
>
> We have a new server which should have gone live last night. Since we only
> have 20 users I recreated the AD accounts, migrated the exchange boxes with
> xmerge and basically spent the last month configuring the box to be a similar
> as possible to our existing SBS server including the DNS.
>
> All email tests were successful, internal and outgoing external. The last
> remaining task was to switch the router SMTP firewall to the new server IP.
> After this was done we tried sending emails from external clients, gmail,
> hotmail , aol etc and we got this message each time.
>
> PERM_FAILURE: SMTP Error (state 13): 550 5.7.1 Unable to relay for
> user[ at ]domain.co.uk
>
> I have double checked the SMTP settings in exchange including relay and they
> are as advised on many posts I found on the subject and also identical to the
> old server.
>
> The fire wall is disabled.
>
> Any ideas?
It sounds like this 'router SMTP firewall' is rejecting the messages
before they hit exchange. Is this a true SMTP relay within your
firewall? Have you configured it with the domains you wish to accept
mail for? Can you eloborate on what exactly you have in front of
Exchange? If you tell us your domain name we can do some live tests that
may tell us more.
-- stephen
|
|
"stephen" wrote:
[Quoted Text] > Jason wrote:
> > Hi
> >
> > Problem:
> >
> > We have a new server which should have gone live last night. Since we only
> > have 20 users I recreated the AD accounts, migrated the exchange boxes with
> > xmerge and basically spent the last month configuring the box to be a similar
> > as possible to our existing SBS server including the DNS.
> >
> > All email tests were successful, internal and outgoing external. The last
> > remaining task was to switch the router SMTP firewall to the new server IP.
> > After this was done we tried sending emails from external clients, gmail,
> > hotmail , aol etc and we got this message each time.
> >
> > PERM_FAILURE: SMTP Error (state 13): 550 5.7.1 Unable to relay for
> > user[ at ]domain.co.uk
> >
> > I have double checked the SMTP settings in exchange including relay and they
> > are as advised on many posts I found on the subject and also identical to the
> > old server.
> >
> > The fire wall is disabled.
> >
> > Any ideas?
>
> It sounds like this 'router SMTP firewall' is rejecting the messages
> before they hit exchange. Is this a true SMTP relay within your
> firewall? Have you configured it with the domains you wish to accept
> mail for? Can you eloborate on what exactly you have in front of
> Exchange? If you tell us your domain name we can do some live tests that
> may tell us more.
>
> -- stephen
>
Sure, I have a netgear router. The router seems to be forwarding the
packets to the server as I can see it in the router logs and besides, it
forwards them no problem to the old server. We've reverted back to that now
and its working fine.
Our old server is 192.168.1.100 the fire wall setting directs any SMTP
packets to this server.
The new server is 192.168.1.200. I simply changed the IP address in the
firewall rule to reflect this. All all other ports are working, HTTP, HTTS
etc.
Example of router log:
Wed, 2007-07-04 12:34:28 - TCP Packet - Source:81.92.112.204,48752
Destination:192.168.1.200,25 - [SMTP match]
|
|
Jason wrote:
[Quoted Text] >
> "stephen" wrote:
>
>> Jason wrote:
>>> Hi
>>>
>>> Problem:
>>>
>>> We have a new server which should have gone live last night. Since we only
>>> have 20 users I recreated the AD accounts, migrated the exchange boxes with
>>> xmerge and basically spent the last month configuring the box to be a similar
>>> as possible to our existing SBS server including the DNS.
>>>
>>> All email tests were successful, internal and outgoing external. The last
>>> remaining task was to switch the router SMTP firewall to the new server IP.
>>> After this was done we tried sending emails from external clients, gmail,
>>> hotmail , aol etc and we got this message each time.
>>>
>>> PERM_FAILURE: SMTP Error (state 13): 550 5.7.1 Unable to relay for
>>> user[ at ]domain.co.uk
>>>
>>> I have double checked the SMTP settings in exchange including relay and they
>>> are as advised on many posts I found on the subject and also identical to the
>>> old server.
>>>
>>> The fire wall is disabled.
>>>
>>> Any ideas?
>> It sounds like this 'router SMTP firewall' is rejecting the messages
>> before they hit exchange. Is this a true SMTP relay within your
>> firewall? Have you configured it with the domains you wish to accept
>> mail for? Can you eloborate on what exactly you have in front of
>> Exchange? If you tell us your domain name we can do some live tests that
>> may tell us more.
>>
>> -- stephen
>>
>
> Sure, I have a netgear router. The router seems to be forwarding the
> packets to the server as I can see it in the router logs and besides, it
> forwards them no problem to the old server. We've reverted back to that now
> and its working fine.
>
> Our old server is 192.168.1.100 the fire wall setting directs any SMTP
> packets to this server.
>
> The new server is 192.168.1.200. I simply changed the IP address in the
> firewall rule to reflect this. All all other ports are working, HTTP, HTTS
> etc.
>
> Example of router log:
>
> Wed, 2007-07-04 12:34:28 - TCP Packet - Source:81.92.112.204,48752
> Destination:192.168.1.200,25 - [SMTP match]
OK, so it's nothing fancy, just regular port forwarding in the router
and not some SMTP relay engine within your router?
It's probably worth re-running CEICW and making sure your email domain
is entered correctly. Also check default recipient policy to ensure that
all domains you want to accept mail for are listed.
-- stephen
|
|
PROBLEM SOLVED:
I had forgotten to add the .co.uk domains to the recipient policies. Where
it has domain.local, I needed to add domain.co.uk for each domain we are
using.
"Jason" wrote:
[Quoted Text] > Hi
>
> Problem:
>
> We have a new server which should have gone live last night. Since we only
> have 20 users I recreated the AD accounts, migrated the exchange boxes with
> xmerge and basically spent the last month configuring the box to be a similar
> as possible to our existing SBS server including the DNS.
>
> All email tests were successful, internal and outgoing external. The last
> remaining task was to switch the router SMTP firewall to the new server IP.
> After this was done we tried sending emails from external clients, gmail,
> hotmail , aol etc and we got this message each time.
>
> PERM_FAILURE: SMTP Error (state 13): 550 5.7.1 Unable to relay for
> user[ at ]domain.co.uk
>
> I have double checked the SMTP settings in exchange including relay and they
> are as advised on many posts I found on the subject and also identical to the
> old server.
>
> The fire wall is disabled.
>
> Any ideas?
|
|
|