Originally Posted by email@example.com
Thanks for the reply. I have tried all of that. You know its funny I have spoken with microsoft, posted in microsoft forums, i am currently speaking with support techs on the exchange side and the linux side. The microsoft people blame linux and linux people blame microsoft. The only people that have given me any hard evidence of the way things are happening are the exchange people i have spoken with. I walked into this setup so i have to deal with it. Why can't we get past all this blaming the other guy stuff and get down to some cold hard facts of why this is happening.
Excuse me, but I'm NOT blaming anyone, but I AM pointing to 'cold hard facts'. The facts (as you state them), are the data is coming from a web form correctly. It's being processed correctly, sent to sendmail, who (in turn) is sending it along to the Exchange server
. The EXCHANGE server is not sending the mails out externally...but is processing them INTERNALLY.
That means that Linux/web/sendmail are working correctly, and relaying the mail to Exchange. From there, it's not working correctly...external mail isn't going out. Want to test it? Follow this:
...and let your Sendmail server get out to the Internet. It'll shovel email along using Gmail's SMTP server...if you get emails then, that'll tell you alot. If not, you can run sendmail with VERY verbose logging and get alot more details/clues.
Exchange and Linux are working like this in the real world, more so than i would like to admit. I wish everything was either microsoft or linux, my life as an admin would be a lot easier, but this is not the way the world works. We have narrowed the issue down to a configuration problem with sendmail. I am not completely new with sendmail but still have a hard time understanding it. The problem is in the sendmail config or dns resolution of something in the congig. Thanks for all your help i am going to contact a linux person regaurding this issue.
I've been an admin for a LOT of years, and getting things to work right is always a challenge, even in a homogeneous environment. Where it tends to get complicated is when you throw something proprietary into the mix.
Not sure how you narrowed it down...mind showing us what lead you to this conclusion?? Also, saying sendmail config or dns resolution is a VERY broad answer. Sendmail can be configured in LOTS of different ways, with lots of different options. Again, what do the logs on the Exchange server say?? As I mentioned in my first post, the domain name could be the problem, if it's being processed as server.domain.com, instead of domain.com. I've seen MANY mail configurations die, because the upstream server (Exchange in this case), is CONFIGURED to accept mail from domain.com, and will discard anything else, to keep from acting as an open relay. Again, this can either be dealt with by telling the Exchange server to accept mail from server.domain.com, or by configuring sendmail to use the masquerade option, and making everything show up as domain.com. Either fix will work, and it's not a fault/feature of either system that it works like that. It's just the way mail servers work. The logs can tell you why the external mails are dying, and can be further diagnosed from there.