Koozali.org: home of the SME Server

email delivery failure

Dave

email delivery failure
« on: May 19, 2002, 08:17:25 PM »
I have been see email delivery failures logged regarding yahoo and comcast domains.  The specific text of the failure is this:

64.157.4.81 failed after I sent the message./Remote host said: 552 Put ,E=\r\n at the end of Mether, Mtcp, or Msmtp in sendmail.cf if you are using Solaris 2.5 (fixed in 2.5.1). I cannot accept messages with stray newlines.  Many SMTP servers will time out waiting for \r\n.\r\n./

I've tried to find (using find) sendmail.cf and it doesn't appear to exist.  Can anyone point me in the right direction?

Thanks for any help.
Dave

guestHH

Re: email delivery failure
« Reply #1 on: May 19, 2002, 09:23:00 PM »
Hi,

Mitel SME (any version) uses qmail, not sendmail.

Regards,
guestHH

Dave

Re: email delivery failure
« Reply #2 on: May 19, 2002, 10:20:50 PM »
Thanks for the reply.  I was guessing this was a generic message, especially since it is appearing in the email logs on my SME email server.  

Can anyone tell me if this is an error being generated by the recipient email system of if it's comming from my email server?

The main problem is that I can't get email through to just about any yahoo email account.  I've monitored my firewall logs and see no dropped packets nor any timeouts appearing there.  I was hoping this error message is the reason I can't get to yahoo email accounts.

My firewall software is Winroute PRO on WinNT 4.0, at least for now, as soon as I get all this linux stuff figured out, I'm moving my web domain to SME (one server dedicated to web, one to mail and one to firewall services).  

Let me know if there's any additional information I can post that would be helpful.

Thanks,
Dave

guestHH

Re: email delivery failure
« Reply #3 on: May 21, 2002, 11:18:23 AM »
Hi Dave,

For what it's worth, a quick look gave me this:

64.157.4.81 = mta-v11.level3.mail.yahoo.com

So the message is send by yahoo to your SME server telling it that it doesn't like or understands correctly the message that you are sending to yahoo.

How do you send your e-mail?
1. Client workstaton?
2. Client e-mail programm
3. Route of message

Regards,
guestHH

Dave

Re: email delivery failure
« Reply #4 on: May 21, 2002, 07:47:23 PM »
Thanks for the response...

I recently switched from MS Exchange to SME.  Email clients are outlook 2000.  I set up POP and SMTP options in outlook to point to the SME server.  

Route of message?  Not 100% sure what you're asking...  Let me describe my current network.  I have several servers on my network.  Currently, I have one NT PDC for my home users, an NT server based firewall, the SME email server, another SME server that I'm going to use for web services and a 3rd that will eventually replace my NT firewall.  Right now, everything is on the same private network, all my servers are static IP's, all clients are DHCP.  I have one static public IP.  Even though everything is on the same network, I doubt the NT PDC is doing anything with the messages (Exchange is still installed and running, but nothing is accessing it right now).  All machines on the network point to the firewall PC as the primary gateway/router.

The message starts at the client in outlook, goes to the email server and then is routed through the FW to the recieving email system.  

One test I was going to try is using the webmail interface to directly send email from the server rather than use outlook, since the address is a friend of my wife's I asked her to send a test email, I don't know if she's done that yet today.

I appreciate the assistance, please let me know if there's anything else I can provide that would be of help.

Dave

guestHH

Re: email delivery failure
« Reply #5 on: May 27, 2002, 09:52:25 PM »
Hi Dave,

What's the status?

Regards,
guestHH

Dave

Re: email delivery failure
« Reply #6 on: May 28, 2002, 10:52:55 PM »
Well, I don't know if it's 100% resolved or not.  I found a blurb related to firewall setups that suggested certain types of PING not be blocked.  I had initially set my FW to drop all PINGs because I was (and still am) getting LOTS of pings from the internet.  I don't recall the specific type of ping but I flollowed the advice and I seem to be able to send email to Yahoo accounts.

It seemed odd that allowing pings would make a difference but the article mentioned that certain types of internet traffic require this particular type of ping so systems behind a firewall can get time out errors, or something to that effect.  Can you tell me if this kind of change would allow email to be delivered?

Now I have another email related question...  Most of the workstations on my network (it's a home network) use Win98 or ME and I'm becomming increasingly concerned about the security vulnerabilites in MS's Outlook (and most everything else from MS for that matter).  Is there another email client I can use that would be safer and that won't cost an arm and a leg?

I personally use the web interface to email but no one else likes it.  I'd like to use a client that would allow email to stay on the server (that's SMTP as opposed to POP3 right?  POP is a delivery protocol that sends email to the client and removes it from the server, is this accurate?).  Will e-smith be efficient with this type of arrangement?  I have only 4 clients on my network, I have a number of servers but the server count will drop once I get all the problems resolved with using Linux.


Thanks for your input.
Dave

Terry Brummell

Re: email delivery failure
« Reply #7 on: May 29, 2002, 02:08:02 AM »

I personally use the web interface to email but no one else likes it. I'd like to use a client that would allow email to stay on the server (that's SMTP as opposed to POP3 right? POP is a delivery protocol that sends email to the client and removes it from the server, is this accurate?).
/

IMAP is the protocol that you would want to use that allows mail to be left on the server.  And yes, without any option changes most POP3 clients delete messages off the mail server after downloading to the client.  IMP is an IMAP client, and other email clients such as Netscape and Eudora also have IMAP compatability.  

Terry