From: spinuvit.list@gmail.com (Vitaly S.)
To: ding@gnus.org
Subject: Re: Can not send application attachments.
Date: Thu, 02 Sep 2010 21:45:05 +0200 [thread overview]
Message-ID: <87eidc7wvy.fsf@gmail.com> (raw)
In-Reply-To: <87wrr45nod.fsf@lifelogs.com>
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Thu, 02 Sep 2010 11:54:18 +0200 spinuvit.list@gmail.com (Vitaly S.) wrote:
>
> Vs> I cannot send application attachments. Each time I try C-c C-c with
> VS> application/pdf , image/png or alike, the file is opened in the external
> VS> application and the message is not sent.
>
> You mean `C-c RET f'? Use the Attachments->Attach File menu to be
> certain.
I meant that during sending with message-send-and-exit (C-c C-c) if the email
contains parts with attachments, instead of being sent the pdf file is opened
in acrobat reader and images with evince. Message itself is not
sent. Curiously text/plain and text/html and octet-stream are sent just
fine.
Vitaly.
next prev parent reply other threads:[~2010-09-02 19:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 9:54 Vitaly S.
2010-09-02 12:34 ` Ted Zlatanov
2010-09-02 19:45 ` Vitaly S. [this message]
2010-09-02 20:58 ` Vitaly S.
2010-09-02 21:26 ` Vitaly S.
2010-09-03 17:03 ` Lars Magne Ingebrigtsen
2010-09-02 22:01 ` Ted Zlatanov
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=87eidc7wvy.fsf@gmail.com \
--to=spinuvit.list@gmail.com \
--cc=ding@gnus.org \
/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).