christopherbb
asked on
Delivery to the following recipients has been delayed
(Servers: 2003 SBS)
Our Main PDC crated over the weekend, I have everything backup and running on it except DHCP & DNS. Our exchange server was acting as a DC plus our backup DNS.
On the exchange server, after seizing PDC, Schema, etc, I had to remove maybe 2 of the DNS entries to kill a "round-robin" problem that was keeping me from rejoining the new server install as a domain controller so I could get the repaired server back into the domain.
After all the above history, here is my problem. The exchange server is receiving email, but with outbound I now receive the following error email message after an hour or two.
This is an automatically generated Delivery Status Notification.
THIS IS A WARNING MESSAGE ONLY.
YOU DO NOT NEED TO RESEND YOUR MESSAGE.
Delivery to the following recipients has been delayed.
noone@example.org
However no emails are going out. The only changes I made was sqashing a couple of entries on the exhange server, in the DNS that was causing "round-robin" problems; obviously now I caused something to stop working on outbound email, but am puzzled as to how.
I followed all that was in this post http://www.experts-exchang
At http://forums.techguy.org/
Last info that may or may not be important. The new server install I have yet to promote back to PDC, nor have I got around to reinstalling DNS back on it, I just changed on the backup DNS (exhanger server) to where if you ping the domain, it would now point to the new/temp PDC until I could get everything on the original PDC server back up and online.
Our Fotigate firewall has a static IP address and we have our own mail.example.com domain name we use as well. thanks in advance for any help.
TG Tran
On the Exchange server, how do have DNS configured on the NIC? Is it pointing to itself as the primary DNS? Can you browse the internet from Exchange?
ASKER
Yes I can browse the internet just fine from Exchange. However after looking through the DNS forward lookup zones, I am still seeing some entries that point back to the old PDC (that I will be putting DNS back on towards the end of the week when so many are not using the file server / old PDC) .
Not sure what to look for on which one is critical to sending email.
Not sure what to look for on which one is critical to sending email.
ASKER
about to go home at 5:00pm cst, will be back in office early tomorrow. thanks for looking and welcome any thoughts you may have
(Normally I would stay late working on this, but I stayed for 28 hours straight getting all the critical data, shares, printers back online, going to go sleep)
(Normally I would stay late working on this, but I stayed for 28 hours straight getting all the critical data, shares, printers back online, going to go sleep)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Under advanced Max Hop count is "30"
FQDN is servername.domainname.loca
when I click button "check dns" is says, "The domain name is valid".
Should I remove .local from that? About to read your link, but wanted to get that info back to you.
FQDN is servername.domainname.loca
when I click button "check dns" is says, "The domain name is valid".
Should I remove .local from that? About to read your link, but wanted to get that info back to you.
ASKER
after reading your link, I tried to change the FQDN to mail.companyname.com, I clicked "Check DNS" and it also replied "Valid". I can ping mail.companyname.com and it pings, or at least tries to ping the ip assigned to the wan/internet side of the Fortigate Firewall (we cant actually ping out to anything because pinging is blocked on the firewall).
After making that change I still can not send email out, receiving works fast as ever.
After making that change I still can not send email out, receiving works fast as ever.
ASKER
Oops disregard the last post I made, I meant, "When I ping mail.companyname.com, it tries to ping through the firewall out to the ISP's DNS IP. Our firewalls IP on the wan side is in fact different.
Any FQDN on your SMTP Connector that ends .local is technically invalid and means you are not RFC compliant because when your server talks to another server, the receiving server sees your server as servername.domain.local and will try to resolve that name in DNS and because .local domain names are not internet routeable, they also won't resolve in DNS (apart from internally on your own server), thus you will get rejected.
If you change it to something like mail.domain.com, the problem will go away, as long as mail.domain.com resolves in DNS back to the IP Address that you are sending from.
If you change it to something like mail.domain.com, the problem will go away, as long as mail.domain.com resolves in DNS back to the IP Address that you are sending from.
As you have made the change - please send me a test message to alan @ it-eye.co.uk and I'll see what might be wrong (if anything else is).
Thanks
Thanks
Test message received. Config sounds good if you got past my spam filtering - going to check on server - back shortly.
ASKER
I sent the test email, I CC'ed myself at hotmail. Looking back at SMTP Virtual Server> Delivery Tab> Advanced Button, I clicked on "Configure" and it had the IP of the crashed PDC. I changed that IP to our ISP's DNS. I just restarted MS Information Store, hopefully you will now get that test email?? *crosses fingers*
Your SPF record has way too many Quote marks in it.
It should be:
"v=spf1 mx IP4:xx.xx.xx.xx -all"
But you have:
"v=spf1" "mx:" "IP4:" "xx.xx.xx.xx" "-all"
(Replace xx.xx.xx.xx with your IP Address)
You could also just have:
"v=spf1 mx -all"
It should be:
"v=spf1 mx IP4:xx.xx.xx.xx -all"
But you have:
"v=spf1" "mx:" "IP4:" "xx.xx.xx.xx" "-all"
(Replace xx.xx.xx.xx with your IP Address)
You could also just have:
"v=spf1 mx -all"
ASKER
ok from the responses pouring in we are getting out now. Alan giving you all the credit because you got me where I needed to be where I could change that IP under config to our ISP's DNS IP, which seemed to do the trick.
As one of my users said, he got a puzzled email response from one client wondering why he just got 3 days of emails all at one time, so the proverbial flood gates have opened. Thanks!!
As one of my users said, he got a puzzled email response from one client wondering why he just got 3 days of emails all at one time, so the proverbial flood gates have opened. Thanks!!
ASKER
Just make sure you under SMTP Virtual Server> Delivery Tab> Advanced Button, that you click configure and see what IP is there and if its accurate