Link to home
Start Free TrialLog in
Avatar of jlavetan
jlavetanFlag for United States of America

asked on

Allowing a fax machine to use smtp relay in Exchange 2003

We have a Panasonic DX-2000 fax machine that has the ability to send faxes through email.  We just upgraded our Exchange server from 5.5 to 2003 and are now having problems getting it to connect.

I have already given our entire network relay access in the SMTP Virtual Server properties.  I can also telnet to the exchange server and relay as the fax machine.

telnet 10.1.1.95 25
EHLO
mail from: cbw-fax@domain.com
250 2.1.0 cbw-fax@domain.com....Sender OK

rcpt to: jasonl@domain.com
250 2.1.5 jasonl@domain.com

data
354 Start mail input; end with <CRLF>.<CRLF>

This is a test.
.
250 2.6.0 <OPUXsl3xbYiMCIqtQvA00000012@opux.domain.com> Queued mail
for delivery

I receive the email a few seconds later...  Is there something I'm missing?

Avatar of Sembee
Sembee
Flag of United Kingdom of Great Britain and Northern Ireland image

First - I don't recommend granting your entire network relay rights on the Exchange server. This leaves your server open to abuse from anything inside and can also cause your server to be an open relay. Lock it down to the IP addresses that need it or force users to authenticate when sending email via SMTP.

How is the fax machine configured to send? Via an IP address or a DNS name?
If you enable SMTP logging on the SMTP virtual server, can you actually see the fax machine trying to connect?

Simon.
Avatar of jlavetan

ASKER

I only enabled the entire network for testing...  I have since only allowed that single IP...

It seems as though the fax machine is quitting prematurely.  It is not transmitting the mail to, rcpt to, or data.  
The following is from the smtp virtual server log...

2006-02-16 14:44:03 10.1.2.4 - SMTPSVC1 OPUX 10.1.1.95 0 HELO - +cbw-fax.cooper.domain.com+(Internet+FAX) 501 0 27 50 0 SMTP - - - -

2006-02-16 14:44:03 10.1.2.4 - SMTPSVC1 OPUX 10.1.1.95 0 QUIT - - 240 15 27 50 0 SMTP - - - -


As a test, try pointing it at your ISPs SMTP server. The message should come back in again.

Simon.
I don't see how that would work...
ASKER CERTIFIED SOLUTION
Avatar of Sembee
Sembee
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
It is definitely an issue with the Exchange server.  When I use our ISP's smtp server, a test fax goes through with no problems.

That was what I hoped it would prove.

What else is on the Exchange server? Anything that scans SMTP traffic? AV, Antispam etc?

Simon.
Nope, nothing...  fresh install...
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
That seems to be the issue...  Sure enough, I tried it by telneting to our exchange server and get a 501 error.  If I take off the +(Internet+FAX), then it works fine.

I can telnet to our ISP's mail server and do:

helo cbw-fax.cooper.domain.com+(Internet+FAX)

So, our ISP's mail server does accept the host name... but Exchange doesn't.  I'll have to check with Panasonic (maker of fax machine) to see if they have a firmware upgrade or something....

Is there a way to force Exchange to accept the host name?
Avatar of marc_nivens
marc_nivens

Unfortunately no, this is hard coded.  Most likely as a security feature, the more restrictive an application is on what it accepts as input generally helps prevent some forms of buffer overflow attacks.  Bottom line is, the fax software is violating the RFC (not Exchange) so thats where the fix needs to come in.  You might try looking through the registry and other settings for this application, perhaps you can modify what it passes for the domain.
It is a stand-alone fax machine...  Looks like a call to Panasonic is in order...

Thanks for you help...
I found the following KB article from Microsoft that solved the issue with Exchange and the hostname... in case anyone else has a similar issue.

http://support.microsoft.com/?id=291828