[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RFC 2047 in headers
From: |
Jean Louis |
Subject: |
Re: RFC 2047 in headers |
Date: |
Tue, 3 Nov 2020 23:12:05 +0300 |
User-agent: |
Mutt/+ (1036f0e) (2020-10-18) |
* Sergey Poznyakoff <gray@gnu.org.ua> [2020-11-03 22:28]:
> Jean Louis <bugs@gnu.support> ha escrit:
>
> > > though. Can you tell me why is it needed?
> >
> > It is for sending emails.
> >
> > There is difference if I address person with person's name or with
> > email address only.
>
> I'm not asking about the need ofr encoding. That's self-evident.
>
> I'm asking why do you need the --content-name option for the textual
> part.
To name the files.
There are different email readers, including Google that may show the
name of the attachment. Naming files helps the recipient to understand
what will be read or why it is there. Use case is not only with
alternative, what if it is not alternative and what if there are
multiple files?
Re: not getting content names, Jean Louis, 2020/11/03
- Re: not getting content names, Sergey Poznyakoff, 2020/11/03
- Re: not getting content names, Jean Louis, 2020/11/03
- Re: not getting content names, Sergey Poznyakoff, 2020/11/03
- Re: RFC 2047 in headers, Jean Louis, 2020/11/03
- Re: RFC 2047 in headers, Sergey Poznyakoff, 2020/11/03
- Re: RFC 2047 in headers,
Jean Louis <=
- Re: RFC 2047 in headers, Sergey Poznyakoff, 2020/11/04
- Re: RFC 2047 in headers, Jean Louis, 2020/11/04