Dave - [EMAIL PROTECTED] continues to serve its role up this day .... simple but effective t-shooting steps.
Back to the main question ... Since we all seem to blame DNS (MX records....) for this problem, here's a simple solution I implemented when faced to this problem: Use the culprit to solve the problem - I've seen the same problem on more than one config. and here's my simple solution - Since on an Exchange Srv network, we'd generally have DNS server running locally, just recreate a local MX records and set this local DNS srv as one of the primary DNS srv on your asterisk box and it shud get the headaches off.... HTH ________________________________________ From: Dave Donovan [EMAIL PROTECTED] Sent: Friday, January 25, 2008 5:51 PM To: [email protected] Subject: Re: [on-asterisk] SendMail and exchange server On Jan 25, 2008 5:12 PM, Henry L.Coleman <[EMAIL PROTECTED]> wrote: > Hi all, go a client who wants to send email voice attachments to an > exchange server on the same LAN > the SMTP works for external addresses but not internal. > Any solutions ? > Everything Alex said is good. To that I would add that you should consider what's happening with DNS. Your Asterisk box is doing a DNS query for the MX (mail exchange) record of the domain. If [EMAIL PROTECTED] has resolves to an external address, and the firewall isn't setup to allow hairpin routing you could have a problem. That is DNS is telling Asterisk that the mail server is on the internet rather than indicating, as you say, that it's on the LAN. Back to Alex's point; one way to test relay is to telnet to port 25. From a windows machine: telnet mailserverLANaddress 25 (it should send you a welcome header) (you type) helo henry (most servers don't care what you put, they just want you to say helo) (it should say helo back) (you type) mail from: [EMAIL PROTECTED] (server says something like "sender OK") (you type) rcpt to: [EMAIL PROTECTED] (specify a valid exchange user) (server will confirm with OK or something) (you type) data (you type) testing this email server. TESTING 1-2-3. Is this thing on? (you type) . (just a single period on a line by itself and just press enter) (server will confirm message received and it's being sent.) Telnetting to SMTP servers has been a very helpful diagnostic in my experience. It gets you right to the root of the problem quickly. You just have to learn to speak SMTP. One note. Some antimalware programs prevent workstations from using port 25. I banged my head against the wall for half an hour trying to troubleshoot a mail server only to find out that Mcafee was blocking port 25 from the workstation I was using to test. DOH! I hope that's helpful, Dave > > > Henry L. Coleman > VOIP-PBX.CA Tel: 647-723-5160 / 1-866-415-5355 > http://voip-pbx.ca > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
