Corrupted emails

Discussion, support and announcements for third party applications that work with MailEnable.
Post Reply
gjharris
Posts: 1
Joined: Tue Jan 14, 2014 4:08 pm

Corrupted emails

Post by gjharris »

My company (Thales) is using MailEnable Professional in a product currently
under development and have observed what appear to be instances of MailEnable
corrupting inbound emails.

The particular scenario under which this occurs is specifically when emails
are received where every line (the low level SMTP header lines as well
as the email content) is terminated with just a LF(line feed), i.e. not <CR><LF>.

I am aware that use of LF only as a line ending is considered to be non standard,
but unfortunately the system that generates these emails is an external system
and cannot be changed, so this is beyond our control.

It appears that MailEnable tries to correct the LF characters back to <CR><LF>
but in doing so inserts some extra erroneous <CR><LF><TAB> characters into
the email.
We have used WireShark to confirm that what comes in to the mail server is OK
(except that the line endings are all LF) but that what subsequently goes
to our mail client has had the erroneous <CR><LF><TAB> characters inserted.

Is this a known issue with MailEnable that can be fixed or is there some other
explanation as to why it is happening?
Are there are any settings we can change to fix this.
If we could stop MailEnable trying to put the CR back I think this might work for us.

Regards.

Gary.

Admin
Site Admin
Posts: 1127
Joined: Mon Jun 10, 2002 6:31 pm
Location: Melbourne, Victoria, Australia

Re: Corrupted emails

Post by Admin »

Hi,

This is a post of the solution that was determined in case others hit this requirement - MailEnable will try to fix emails with just a linefeed, since they are not valid and generally blocked by most mail servers. A lot of email clients will also not view them properly (if at all). You can try to change the handling of the repair attempt though, which involves adding the following Windows registry keys:

For 64bit servers:

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Mail Enable\Mail Enable\Connectors\SMTP]
"Repair Bad LF"=dword:00000001
"Fix Sender Header Length"=dword:00000000

For 32bit servers:

[HKEY_LOCAL_MACHINE\SOFTWARE\Mail Enable\Mail Enable\Connectors\SMTP]
"Repair Bad LF"=dword:00000001
"Fix Sender Header Length"=dword:00000000

I believe the tab is being inserted since it thinks the email line is too long, and is trying to wrap it (it thinks it is processing the headers, so inserting the tab is needed).

Post Reply