LISTSERV - LSTSRV-L Archives - COMMUNITY.EMAILOGY.COM

Well, fortunately, we should be on R16 in about 3 weeks, so at least some issues will go away.

--Joe

From: LISTSERV Site Administrators' Forum <[log in to unmask]> on behalf of Eric Thomas <[log in to unmask]>
Sent: Thursday, May 29, 2014 6:07 PM
To: [log in to unmask]
Subject: Re: Attachments, 1.8d and Outlook?

If “Language= Exchange” helps, by definition it is a TNEF issue J You might of course be looking at a two-cause symptom with TNEF only being one of the problems. I still recommend disabling TNEF in the RemoteDomain for the LISTSERV host as a best practice because I can see no good whatsoever from doing otherwise. From memory, the “real” MIME parser was added in 1.8e and I think that’s about right looking at the update trail. While MIME support was added in 1997, 1.8e more than tripled the amount of code and the only big bump after that was Unicode support. Running 1.8d (1999), you don’t have full MIME support and there is only so much you can tweak. My gut feeling is that your Mac problem will not go away with the upgrade, but on the other hand you probably can’t do anything about it now either. Ben has better memory than I do and I have the historical source code saved up, but still between the two of us there’s only so much we can do to help you. Not to mention DMARC L

Eric

From: LISTSERV Site Administrators' Forum [mailto:[log in to unmask]] On Behalf Of F J Kelley
Sent: Thursday, May 29, 2014 23:25
To: [log in to unmask]
Subject: Re: Attachments, 1.8d and Outlook?

Well, it is not a TNEF issue that I can tell (or not entirely). We see this on mail from Macs and other non-MS sources.

Here is an example of some of it. It affects more than attachments, simple messages trigger stuff such as below.

Content-Type: multipart/alternative;
boundary="_000_6e10fbe9dd5741a4ba3cdc46356b1a1aBY2PR02MB252namprd02pro_"
MIME-Version: 1.0
X-OriginatorOrg: uga.edu
X-Scanned-By: Digested by UGA Mail Gateway

--_000_6e10fbe9dd5741a4ba3cdc46356b1a1aBY2PR02MB252namprd02pro_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

From: LISTSERV Site Administrators' Forum <[log in to unmask]> on behalf of Eric Thomas <[log in to unmask]>
Sent: Thursday, May 29, 2014 9:21 AM
To: [log in to unmask]
Subject: Re: Attachments, 1.8d and Outlook?

Very interesting! I found a comprehensive explanation to this decade-long mystery here:

http://help.outlook.com/140/gg263346.aspx

It’s a long article so here are the two key snippets:

Do some of your users report that e-mail recipients in external domains can't open their messages that contain a Winmail.dat attachment? If so, the recipients in the external domain are probably using an e-mail client that doesn't support the Transport Neutral Encapsulation Format (TNEF). Microsoft Outlook is one of the few e-mail clients that support TNEF-encoded messages

Hardly a surprise since when this was introduced and everyone clamored for the specifications of this new format, they were proprietary. And now to the really interesting snippet:

Note The rich text message format is completely different from the rich text document format available in Microsoft Word.

I do have all my “RemoteDomains” set to “TNEFEnabled : False,” which must have been the default value as I do not remember ever seeing this option before. More importantly, I never tried to send RTF messages from Outlook because I assumed it to be Word RTF i.e. this kind of stuff:

This is some {\b bold} text.\par

I could think of no reasons to send out formatting data in a Microsoft format that only a few mail clients would understand, when I could use HTML instead. The dreaded WINMAIL.DAT only appears if you use the RTF setting that actually has nothing to do with Word RTF and is a way to encapsulate OLE and InfoPath forms and what not.

I would definitely disable TNEF for the LISTSERV RemoteDomain because there is absolutely no hope of LISTSERV doing anything meaningful with that format. Sure you can use “Language= Exchange” and that will help for recipients that happen to have Outlook but what about recipients who read mail on unix? And messages sent to the LISTSERV address for processing will always have the WINMAIL.DAT processed as a command under 1.8d and from 1.8e it will be filtered, neither of which is what the user had in mind. Of course the user could manually select plain text when sending mail to the LISTSERV address but everyone is better served by turning TNEF off.

Eric

> -----Original Message-----

> From: LISTSERV Site Administrators' Forum [mailto:LSTSRV-

> [log in to unmask]] On Behalf Of F J Kelley

> Sent: Thursday, May 29, 2014 11:52

> To: [log in to unmask]

> Subject: Re: Attachments, 1.8d and Outlook?

> MS tech support has sent this:

> Symptom

> Emails sent from Outlook Live accounts to external listserv show up with

> attachment missing.

> Cause