Gnus development mailing list
 help / color / mirror / Atom feed
From: Colin Baxter <m43cap@yandex.com>
To: Joseph Mingrone <jrm@ftfl.ca>
Cc: ding@gnus.org
Subject: Re: Mail attachments missing for Safari/Outlook users
Date: Tue, 09 Apr 2019 06:23:47 +0100	[thread overview]
Message-ID: <8736mr69b0.fsf@yandex.com> (raw)
In-Reply-To: <86ftqsj7eb.fsf@phe.ftfl.ca> (Joseph Mingrone's message of "Mon, 08 Apr 2019 22:26:36 -0300")

Dear Joseph,
<#secure method=pgpmime mode=sign>
>>>>> Joseph Mingrone <jrm@ftfl.ca> writes:

    > Colin Baxter <m43cap@yandex.com> writes:
    >> Dear Joseph, <#secure method=pgpmime mode=sign>
    >>>>>>> Joseph Mingrone <jrm@ftfl.ca> writes:

    >> > Hello, Our university switched to Office365/Outlook for mail,
    >> so I > end up sending lots of mail attachments from Gnus to
    >> Outlook > users.  I have been told by about half a dozen users
    >> running > Safari that my attachments do not show up for them.  I
    >> don't have > a Mac, so I cannot easily test this directly, but in
    >> the past, I > have tested the messages that I am sending with
    >> Gnus using tools > like https://www.mimevalidator.net/index.html
    >> and they were > reported as valid.  However, just now I tested
    >> some messages again > and errors are reported.

    >> > Message File: blah.mail Byteplant MIMEValidator V1.2.5.2
    >> Errors: > <LF> linebreak found (line 1) <LF> linebreak found
    >> (line 2) <LF> > linebreak found (line 3) <LF> linebreak found
    >> (line 4) <LF> > linebreak found (...) parser error: too many bad
    >> linebreaks

    >> > I am running Gnus from the Emacs master branch, pulled on >
    >> 2019-03-13.

    >> > Has anyone else come across this problem with Outlook/Safari?
    >> Is > there a workaround other than the telling these users to fix
    >> their > broken software (I am guessing that one of Safari or
    >> Outlook is > the problem)?

    >> Just a thought, what's the setting of your variable
    >> gnus-mime-display-attachment-buttons-in-header? Is it `t'?

    >> I've not had your specific problem, but I've noticed that using
    >> `Attach file' or `Attach external' can produce different
    >> experiences for a recipient on MS-Windows.

    >> Best wishes, Colin.

    > Hi Colin,

    > The variable gnus-mime-display-attachment-buttons-in-header was
    > set to `t'.  I tried setting it to `nil', but the result was the
    > same.

I'm afraid I've run out of ideas of what you might try - except maybe do
nothing! I had a somewhat similar issue when my University
Administration people kept sending me docx files. I couldn't open them,
weren't interest in their contents, so I just ignored them. It didn't
seem to have any significance consequences.

Best wishes,

Colin.

-- 
Colin Baxter
m43cap@yandex.com
---------------------------------------------------------------------
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8
---------------------------------------------------------------------



      reply	other threads:[~2019-04-09  5:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-07 19:00 Joseph Mingrone
2019-04-08  7:44 ` Colin Baxter
2019-04-09  1:26   ` Joseph Mingrone
2019-04-09  5:23     ` Colin Baxter [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8736mr69b0.fsf@yandex.com \
    --to=m43cap@yandex.com \
    --cc=ding@gnus.org \
    --cc=jrm@ftfl.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).