Well, in the tests I've done there is enough inconsistency to drive you up the wall. *I* send an attachment via Outlook 2010 and it is not part of the received mail. A colleague tested that and the attachment got through. I do not see the "multipart/alternative" sections some are receiving. And *why* this has started? Now? MS dropped a number of patches a few weeks ago, so that might be the cause. Or not. Cripes.
Thanks for the help, "Language= Exchange" seems to resolve the matter, and I'll check further.
--Joe
________________________________________
From: LISTSERV Site Administrators' Forum <LSTSRV-L> on behalf of Eric Thomas <[log in to unmask]>
Sent: Wednesday, May 28, 2014 2:37 PM
To: LSTSRV-L
Subject: Re: Attachments, 1.8d and Outlook?
I doubt this has anything to do with 1.8d though. Granted it strips the dreaded WINMAIL.DAT as well as application/ms-tnef, but so do all versions after that unless you disable it, and these attachments were always unparseable to non-Microsoft clients. What changed since 1.8d is that Microsoft saw the light and started following standards for attachments and fixed the hassle they had created. If OWA does not exhibit the problem, it is unlikely to be due to Exchange. On the other hand, it surprises me that Outlook 2010 would still have the code to generate this. I suggest mailing an attachment from Outlook 2010 to a non-Microsoft account to see what the headers look like.
Eric
> -----Original Message-----
> From: LISTSERV Site Administrators' Forum [mailto:LSTSRV-
> [log in to unmask]] On Behalf Of F J Kelley
> Sent: Wednesday, May 28, 2014 18:58
> To: [log in to unmask]
> Subject: Re: Attachments, 1.8d and Outlook?
>
> Hi again,
> Well so far, I can send attachments from gmail and can use Thunderbird as a
> frontend for the University account without problems. Using Powershell's send-
> mailmessage I can sent attachments to the list from several servers and can
> send from Outlook Web App (OWA). But I cannot send from Outlook 2010 (I can
> read the attachments sent by the others when I use Outlook 2010, I just cannot
> send one -- it is stripped -- or does not display correctly).
>
> I had thought something like this would be showing up elsewhere, but that
> seems not to be the case (of course, how many are still using 1.8d?). Will try the
> "EXCHANGE" option.
>
> Thanks,
> --Joe
>
> ________________________________________
> From: LISTSERV Site Administrators' Forum <LSTSRV-L> on behalf of Eric Thomas
> <[log in to unmask]>
> Sent: Wednesday, May 28, 2014 12:45 PM
> To: LSTSRV-L
> Subject: Re: Attachments, 1.8d and Outlook?
>
> Hmm, maybe it is Outlook doing that then, rather than Exchange. I moved my
> mailbox from a poor IMAP server that wasn't scaling up to my mailbox size :-), to
> Exchange 2007 at about the same time that it was released. I dreaded the
> WINMAIL.DAT syndrome and spent a lot of time double-checking that my
> outbound mail would not be polluted with embarrassing non-compliant
> attachments, but nothing of the sort ever happened to me. I did not use Outlook
> versions older than 2007 though, before that I used VM for regular mail and
> Outlook Express for attachments (of course nowadays almost all regular mail
> contains attachments). Most employees eventually switched to Exchange 2010
> but Outlook 2003 was banned by administrative policy as we did not use Public
> Folders. So my guess is that Outlook 2003 is the culprit then.
>
> Eric
>
> > -----Original Message-----
> > From: LISTSERV Site Administrators' Forum [mailto:LSTSRV-
> > [log in to unmask]] On Behalf Of Shinn Wu
> > Sent: Wednesday, May 28, 2014 17:59
> > To: [log in to unmask]
> > Subject: Re: Attachments, 1.8d and Outlook?
> >
> > Hi Eric,
> >
> > We are using Exchange 2010 for 16.0, and adding that 'Misc-option'
> > solved the attachments were not properly decoded in our site.
> >
> > Shinn
> >
> > On 5/28/2014 8:53 AM, Eric Thomas wrote:
> > > I think this is only for Exchange 2003 and earlier though. I have run every
> > version of Exchange since 2007 and have never needed this option, nor has
> > Exchange generated these attachments.
> > >
> > > Eric
> > >
> > > PS: My favorite new feature in Exchange 2013 is that you cannot even install
> it
> > until you have expunged all Exchange 2003 servers from the organization :-)
> > >
> > >> -----Original Message-----
> > >> From: LISTSERV Site Administrators' Forum [mailto:LSTSRV-
> > >> [log in to unmask]] On Behalf Of Shinn Wu
> > >> Sent: Wednesday, May 28, 2014 17:16
> > >> To: [log in to unmask]
> > >> Subject: Re: Attachments, 1.8d and Outlook?
> > >>
> > >> Hi Joe,
> > >>
> > >> I forgot we are using 16.0. 16.0 also had problem added the line. Sorry.
> > >>
> > >> Shinn
> > >>
> > >> On 5/28/2014 8:13 AM, F J Kelley wrote:
> > >>> Hello and Thanks Shinn, but I don't see that as an option in the 1.8d
> manuals
> > >>> --Joe
> > >>>
> > >>> ________________________________________
> > >>> From: LISTSERV Site Administrators' Forum <LSTSRV-L> on behalf of Shinn
> > Wu
> > >> <[log in to unmask]>
> > >>> Sent: Wednesday, May 28, 2014 11:05 AM
> > >>> To: LSTSRV-L
> > >>> Subject: Re: Attachments, 1.8d and Outlook?
> > >>>
> > >>> Hi Joe,
> > >>>
> > >>> We had the same problem before, and it seemed to disappear after we
> > >>> added the line:
> > >>>
> > >>> Misc-Options= KEEP_EXCHANGE_DATA
> > >>>
> > >>> Hope it will solve your problem.
> > >>>
> > >>> Shinn
> > >>>
> > >>> On 5/28/2014 7:10 AM, F J Kelley wrote:
> > >>>> We are still running 1.8d, and will be for a few more weeks. Beginning
> last
> > >> week (Friday) some users were seeing the MIME encoding for attachments,
> > but
> > >> not the actual attachments. In a few cases, the attachments were not
> > present
> > >> at all. I have tested this and am seeing it with Outlook 2010. There are
> > reports
> > >> it also shows up in Outlook Web App (OWA), but I have not seen this.
> > Outlook
> > >> 2013 seems to be OK. Has anyone else encountered this?
> > >>>> --Joe
> > >>>> ############################
> > >>>>
> > >>>> To unsubscribe from the LSTSRV-L list:
> > >>>> write to: mailto:[log in to unmask]
> > >>>> or click the following link:
> > >>>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-
> > L&A=1
> > >>> ############################
> > >>>
> > >>> To unsubscribe from the LSTSRV-L list:
> > >>> write to: mailto:[log in to unmask]
> > >>> or click the following link:
> > >>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-
> > L&A=1
> > >>>
> > >>> ############################
> > >>>
> > >>> To unsubscribe from the LSTSRV-L list:
> > >>> write to: mailto:[log in to unmask]
> > >>> or click the following link:
> > >>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-
> > L&A=1
> > >> ############################
> > >>
> > >> To unsubscribe from the LSTSRV-L list:
> > >> write to: mailto:[log in to unmask]
> > >> or click the following link:
> > >> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-
> L&A=1
> > > ############################
> > >
> > > To unsubscribe from the LSTSRV-L list:
> > > write to: mailto:[log in to unmask]
> > > or click the following link:
> > > http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
> >
> > ############################
> >
> > To unsubscribe from the LSTSRV-L list:
> > write to: mailto:[log in to unmask]
> > or click the following link:
> > http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
############################
To unsubscribe from the LSTSRV-L list:
write to: mailto:[log in to unmask]
or click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
############################
To unsubscribe from the LSTSRV-L list:
write to: mailto:[log in to unmask]
or click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
|