From: Andrey Repin <anrdaemon@yandex.ru>
To: ricardo.couto@gmail.com, cygwin@cygwin.com
Subject: Re: RES: email -attach
Date: Sat, 2 Jul 2022 03:14:53 +0300 [thread overview]
Message-ID: <241339745.20220702031453@yandex.ru> (raw)
In-Reply-To: <000601d88d6c$121bdd30$36539790$@gmail.com>
Greetings, ricardo.couto@gmail.com!
> -attach "file1,file2,file3"
That's one file with name "file1,file2,file3".
> -----Mensagem original-----
> De: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
> Enviada em: sexta-feira, 1 de julho de 2022 12:34
> Para: cygwin@cygwin.com
> Cc: ricardo.couto@gmail.com
> Assunto: Re: email -attach
> On 2022-06-22 14:19, ricardo.couto@gmail.com wrote:
>> The package "email" does not works fine with "attach" option when use
>> more than one files to attach.
>> Please, check-it.
> $ email --version
> email - By Dean Jones; Version 3.2.3-git $ email Brian -a
> /etc/email/email.conf -a ~/.email.conf < \
> ~/.email/email.address.book
> works fine for me.
> You may need to use --attach not -attach - man and --help differ!
> --
> Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
> This email may be disturbing to some readers as it contains too much
> technical detail. Reader discretion is advised.
> [Data in binary units and prefixes, physical quantities in SI.]
> --
> Este email foi escaneado pelo Avast antivírus.
> https://www.avast.com/antivirus
--
With best regards,
Andrey Repin
Friday, July 1, 2022 23:56:37
Sorry for my terrible english...
next prev parent reply other threads:[~2022-07-02 0:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 20:19 ricardo.couto
2022-07-01 15:33 ` Brian Inglis
2022-07-01 17:00 ` RES: " ricardo.couto
2022-07-02 0:14 ` Andrey Repin [this message]
2022-07-04 13:23 ` RES: " ricardo.couto
2022-07-04 18:51 ` Brian Inglis
2022-07-04 19:03 ` RES: " ricardo.couto
2022-07-04 20:43 ` Marco Atzeri
2022-07-04 21:18 ` Brian Inglis
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=241339745.20220702031453@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=ricardo.couto@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).