To address truncated to 28 characters

"Daniel Knierim" <[email protected]> Fri, 15 Jul 2005 20:03:10 -0500
Newsgroups gmane.mail.neomail.general,gmane.spam.detected
Message-ID <[email protected]>
Hi all, 

I've been using NeoMail as supplied by my hosting company (along with
CPanel) for a couple weeks.  

It worked fine, until I tried to send a message to someone with an
address 34 characters long (like '[email protected]').
I believe this was the first time I used that long of an address.

The message was bounced, and the bounce message showed the TO: address
truncated after the 28th character (like first.lastname@truncateddoma').

I re-sent the message, double-checking that the TO: address was correct,
and got the same bounce.

Here's the beginning of the bounce message (I've substituted generic
strings for some stuff I'd rather not publish):

Date: 6/26/2005 18:09:35 -0500
From: Mail Delivery System <[email protected]>
To: [email protected]
Subject: Mail delivery failed: returning message to sender 
This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

 first.lastname@truncateddoma
   unrouteable mail domain "truncateddoma"

------ This is a copy of the message, including all the headers. ------
------ The body of the message is 216681 characters long; only the first
------ 106496 or so are included here.

Return-path: <[email protected]>
Received: from acctname by hostn.hostd.com with local (Exim 4.50)
    id 1DmgFr-0005xV-GG
    for first.lastname@truncateddoma; Sun, 26 Jun 2005 18:09:35 -0500
From: "Daniel Knierim" <[email protected]>
To: first.lastname@truncateddoma
Subject: Follow-up on our phone conversation Thursday
X-Mailer: NeoMail 1.27

<<--snip-->>

My hosting company's support claims this is a limitation of NeoMail.
Can anybody confirm or deny this?

If it's not a NeoMail bug, do you have any suggestions what might be
wrong, or how hosting support can find and fix the problem?
for example what might be wrong in the configuration?

If anybody has figured out a similar address truncation problem, please
explain what it took to fix it.

Thanks
- Daniel K.



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click