Solved

Nonstandard SMTP line terminator-exchange 2003

Posted on 2004-10-04
6
720 Views
Last Modified: 2010-08-05
I'm having some trouble getting a desktop faxing solution to gel with a customers exchange setup and could use some help.

In a nut shell basically you load the fax client and point it to the customers mail server or to a a server that will accept smtp relays. In this case I have it pointed to the customers Backend exchange server. When you use the fax client to fax from your desktop it encyrpts the message then passes it to the mail server, the mail server should then pass it to the fax servers that will que it up to be faxed. The fax servers are administered by the vendor that provides the service.

When I attempt to send a fax thru the software I immediately get a System Administrator email stating that there was a communication error with the recipients email server bla bla bla Nonstandard smtp line terminator.

Can any of you explain this error to me? I did a google but came up short...

The customer feels that it is not thier issue, but personally I feel like thier server is the one having the problem.

They have a BE xchange server that passes it to a FE xchange server that passes it to a Symantec mail security sever or some such. I know it's nothing to do with relaying, because I can do that all day long it's only when I fax from the client.
Maybe the encryption is causing the problem?

Any help would be appreciated.

Thanks
MM
0
Comment
Question by:MadMikey
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
6 Comments
 
LVL 12

Accepted Solution

by:
BNettles73 earned 500 total points
ID: 12220882


"These options specify whether or not a channel supports the SMTP protocol and what type of SMTP line terminator IMTA expects to see as part of that protocol. nosmtp means that the channel doesn't support SMTP; all the rest of these keywords imply SMTP support.

The selection of whether or not to use the SMTP protocol is implicit for most channels; the correct protocol is chosen by the use of the appropriate channel program or programs. Some gateway systems use the Simple Mail Transfer Protocol (SMTP) described in RFC 821 as a message envelope, while others may not use an envelope format. The result is that all envelope information is derived from the RFC 822 message header, which is present in all cases. The smtp keyword is used to tell the channel master programs to put a batch SMTP header on the message. The nosmtp keyword inhibits the generation of the batch SMTP header. nosmtp is the default.

The keyword smtp is mandatory for all SMTP channels. The keywords smtp_cr, smtp_crlf, and smtp_lf may be used on SMTP channels to specify what character sequences to accept as line terminators. smtp_crlf means that lines must be terminated with a carriage return (CR) line feed (LF) sequence. smtp_lf or smtp means that an LF without a preceding CR is accepted. Finally, smtp_cr means that a CR is accepted without a following LF. It is normal to use CRLF sequences as the SMTP line terminator, and this is what IMTA always generates; this option affects only the handling of incoming material."




You can read this article on what the definition of a line is, concerning SMTP - http://www.imc.org/ietf-smtp/old-archive/msg00218.html


Do you have any restrictions set on the Exchange BE virtual server?
Can you telnet to port 25 from a workstation the fax client software is loaded?
Does the fax software have any debugging level utilities?
Does the software state whether it is or is not compatible with Exchange?
Does the software integrate with the MAPI client? What MAPI client are you using?
What fax software are you using?
Are there any events recorded on the client in the application event logs?


0
 
LVL 1

Author Comment

by:MadMikey
ID: 12248782
BNettles73,

Thanks for the response. After further investigation it appears that thier Symantec mail firewall is the server that is sending back the Nonstandard smtp line terminator message. I guess the fax software is not terminating the email in compliance with the Symantec server. Never had this problem when simply relaying thru an Exchange server.

To answer your questions:

Do you have any restrictions set on the Exchange BE virtual server? Not that I know of
Can you telnet to port 25 from a workstation the fax client software is loaded? Yes
Does the fax software have any debugging level utilities? No
Does the software state whether it is or is not compatible with Exchange? Yes I have loaded this for many customers
that use exchange and never had any problems.
Does the software integrate with the MAPI client? What MAPI client are you using? Yes Outlook
What fax software are you using? Easylink faxlauncher www.easylink.com
Are there any events recorded on the client in the application event logs? Nope

I'm going to send the log file from the symantec server to easylink and see if they can make anything out of this.
If you have any further suggestions please advise.

Thank
MM
0
 
LVL 12

Expert Comment

by:BNettles73
ID: 12249071

a firewall will definitely cause line termination errors, especially if the mail is relayed through the FW ... still early in the day for me ... I'll try to get back to you later in the day ...
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 1

Author Comment

by:MadMikey
ID: 12249202
The mail is definatley being relayed thru the firewall...

Thanks a bunch BNettels73!
0
 
LVL 1

Author Comment

by:MadMikey
ID: 12280640
Turns out this Symatec Firewall is configured to only accept standard or strictly legal line terminators. It can be configured to accept the nonstandard line terminators but would degrade their security. Looks like the software developer is going to have to fix this in thier next release or the customer is going to have to configure the firewall to work with it. Either way I have done my job :)

I'm going to give you the points BNettles73 because your first post put my on track to figuring out what was causing the problem.

Thanks
MM
0
 
LVL 12

Expert Comment

by:BNettles73
ID: 12280855
Thanks! Glad I could help some ...
0

Featured Post

Free eBook: Backup on AWS

Everything you need to know about backup and disaster recovery with AWS, for FREE!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
exchange 2016 suddenly stopped working 15 46
Exchange 2016 and 2010 Co-existence 3 40
Purge \Deleted Items? 2 29
EXCHANGE 2010, EXCHANGE 2013 4 14
Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
In-place Upgrading Dirsync to Azure AD Connect
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question