DPServices
asked on
Troubleshooting email delivery for new domains
Problem receiving email on two newly registered domains
yegendorflawfirm.ca
yegendorflawfirm.com
Internal Exchange 2003 server sp2
Exchange hosts 6 existing domains for email (5 external) - all working fine
New domain added under Recipient Policies and updated
Internal PineApp unit for filtering email
2 new domains added to accept email delivery
Domainsatcost is registrar and is set to use 3rd party hosting:
ns10.primus.ca
ns11.primus.ca
ns12.primus.ca
Primus (ISP) is doing DNS services and mail relay for both new domains
Copy of NDR from an email sent from an @rogers.com account
Sorry, we were unable to deliver your message to the following address.
<*****@yegendorflawfirm.ca
Remote host said: 553 sorry, relay denied. [RCPT_TO]
--- Below this line is a copy of the message.
Received: from [66.94.237.198] by nm2.access.bullet.mail.mud
Received: from [66.94.237.109] by tm9.access.bullet.mail.mud
Received: from [127.0.0.1] by omp1014.access.mail.mud.ya
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 712430.87933.bm@omp1014.ac
Received: (qmail 91120 invoked by uid 60001); 20 Apr 2011 16:14:40 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rogers.com; s=s1024; t=1303316080; bh=ZEIj10JXZWR8DoOqQG4Zl8U
DomainKey-Signature:a=rsa-
s=s1024; d=rogers.com;
h=Message-ID:X-YMail-OSG:R
b=lZOkkXxCYWPLjvhgsJUDPSXy
Message-ID: <211969.88720.qm@web88208.
X-YMail-OSG: NXE8wzEVM1mlbGMkaeO8SvyNFR
8D4_aGtLSTO.YtUEWzkFKQMKi.
Wj6hfAMXcmXrmj77Qv2bB1FynQ
hplAri7B0KxLUvlj0ftTTA7Cf9
iOBuMQn4QwgSRqeQoLTq6XiKER
zB9qqMrk4uNhk949.Q_EqzavV4
kKnJve0VSvRmFwadR3HxxOO_oJ
USR77RQ--
Received: from [206.191.37.194] by web88208.mail.re2.yahoo.co
X-Mailer: YahooMailClassic/12.0.2 YahooMailWebService/0.8.10
Date: Wed, 20 Apr 2011 09:14:40 -0700 (PDT)
From: ******@rogers.com
Subject: test
To: ******@yegendorflawfirm.ca
MIME-Version: 1.0
If I read the NDR correctly the email is making it to our public IP (206.191.37.194) and getting rejected by either our Exchange server or the Pineapp spam unit. I've gone through both with a fine-toothed comb and can't find any problems, however this stuff is not my forte and I'm probably missing something...
Happy to provide more info.
yegendorflawfirm.ca
yegendorflawfirm.com
Internal Exchange 2003 server sp2
Exchange hosts 6 existing domains for email (5 external) - all working fine
New domain added under Recipient Policies and updated
Internal PineApp unit for filtering email
2 new domains added to accept email delivery
Domainsatcost is registrar and is set to use 3rd party hosting:
ns10.primus.ca
ns11.primus.ca
ns12.primus.ca
Primus (ISP) is doing DNS services and mail relay for both new domains
Copy of NDR from an email sent from an @rogers.com account
Sorry, we were unable to deliver your message to the following address.
<*****@yegendorflawfirm.ca
Remote host said: 553 sorry, relay denied. [RCPT_TO]
--- Below this line is a copy of the message.
Received: from [66.94.237.198] by nm2.access.bullet.mail.mud
Received: from [66.94.237.109] by tm9.access.bullet.mail.mud
Received: from [127.0.0.1] by omp1014.access.mail.mud.ya
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 712430.87933.bm@omp1014.ac
Received: (qmail 91120 invoked by uid 60001); 20 Apr 2011 16:14:40 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rogers.com; s=s1024; t=1303316080; bh=ZEIj10JXZWR8DoOqQG4Zl8U
DomainKey-Signature:a=rsa-
s=s1024; d=rogers.com;
h=Message-ID:X-YMail-OSG:R
b=lZOkkXxCYWPLjvhgsJUDPSXy
Message-ID: <211969.88720.qm@web88208.
X-YMail-OSG: NXE8wzEVM1mlbGMkaeO8SvyNFR
8D4_aGtLSTO.YtUEWzkFKQMKi.
Wj6hfAMXcmXrmj77Qv2bB1FynQ
hplAri7B0KxLUvlj0ftTTA7Cf9
iOBuMQn4QwgSRqeQoLTq6XiKER
zB9qqMrk4uNhk949.Q_EqzavV4
kKnJve0VSvRmFwadR3HxxOO_oJ
USR77RQ--
Received: from [206.191.37.194] by web88208.mail.re2.yahoo.co
X-Mailer: YahooMailClassic/12.0.2 YahooMailWebService/0.8.10
Date: Wed, 20 Apr 2011 09:14:40 -0700 (PDT)
From: ******@rogers.com
Subject: test
To: ******@yegendorflawfirm.ca
MIME-Version: 1.0
If I read the NDR correctly the email is making it to our public IP (206.191.37.194) and getting rejected by either our Exchange server or the Pineapp spam unit. I've gone through both with a fine-toothed comb and can't find any problems, however this stuff is not my forte and I'm probably missing something...
Happy to provide more info.
ASKER
Hi MegaNuk,
Yes that checkbox is ticked for both domains in Recipient policy.
As for telnet I was able to send a test email...although a few weird telnet errors:
220 DELL.BrazeauSeller.local Microsoft ESMTP MAIL Service, Version: 6.0.3790.395
9 ready at Wed, 20 Apr 2011 14:07:45 -0400
helo me
250 DELL.BrazeauSeller.local Hello [10.0.0.7]
mail from:administrator@brazeau
500 5.3.3 Unrecognized command
mail from:administrator@brazeau
250 2.1.0 administrator@brazeauselle
rcpt to:administrator@yegendorf
500 5.3.3 Unrecognized command
rcpt to:administrator@yegendorf
501 5.5.4 Invalid Address
rcpt to:administrator@yegendorf
500 5.3.3 Unrecognized command
rcpt to:administrator@yegendorf
501 5.5.4 Invalid Address
rcpt to:administrator@yegendorf
501 5.5.4 Unrecognized parameter:administrator@ye
rcpt to:administrator@yegendorf
250 2.1.5 administrator@yegendorflaw
data
354 Start mail input; end with <CRLF>.<CRLF>
subject:test
testing
.
250 2.6.0 <DELLFRaqbC8wSA1XvpF000000
delivery
The test email was received right away.
Yes that checkbox is ticked for both domains in Recipient policy.
As for telnet I was able to send a test email...although a few weird telnet errors:
220 DELL.BrazeauSeller.local Microsoft ESMTP MAIL Service, Version: 6.0.3790.395
9 ready at Wed, 20 Apr 2011 14:07:45 -0400
helo me
250 DELL.BrazeauSeller.local Hello [10.0.0.7]
mail from:administrator@brazeau
500 5.3.3 Unrecognized command
mail from:administrator@brazeau
250 2.1.0 administrator@brazeauselle
rcpt to:administrator@yegendorf
500 5.3.3 Unrecognized command
rcpt to:administrator@yegendorf
501 5.5.4 Invalid Address
rcpt to:administrator@yegendorf
500 5.3.3 Unrecognized command
rcpt to:administrator@yegendorf
501 5.5.4 Invalid Address
rcpt to:administrator@yegendorf
501 5.5.4 Unrecognized parameter:administrator@ye
rcpt to:administrator@yegendorf
250 2.1.5 administrator@yegendorflaw
data
354 Start mail input; end with <CRLF>.<CRLF>
subject:test
testing
.
250 2.6.0 <DELLFRaqbC8wSA1XvpF000000
delivery
The test email was received right away.
Ok, so it is not exchange then. Try telnet into the pineapp spam unit and perform the same test.
ASKER
I get relay denied errors on the Pineapp unit however I get those errors even for valid domains that the unit currently processes, so I'm not sure if that's a good test or not
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yeah I'm going to reboot everything tonight.. you're probably right about the telnet thing as well...it's quite restrictive on the internal interface. I'll update this post tomorrow.
Thanks.
Thanks.
ASKER
So it was a problem with the Pineapp unit...had to contact their support to resolve but it basically came down to the new domains not taking effect on the unit... their support had to remote in and patch the device.. after another reboot mail was flowing properly!!
Thanks for your help Nuk... good to have another set of 'eyes' on the problem as I was slowly going crazy trying to figure this out!!
Thanks for your help Nuk... good to have another set of 'eyes' on the problem as I was slowly going crazy trying to figure this out!!
Glad it is working. Thanks for the points.
Have you also ticked the box on the email policy to say 'this exchange server is responsible for delivery to this domain'