Re: RFC 2047 inspection

Jean Louis ha escrit: > (rcd-mailutils-flt2047 "Č ") > "=?utf-8?Q?=C4=8C_?=" > > And then mail complains that email address is not valid. Quite right, that's not a valid email. flt2047 encodes everything it is given as input. It does not (and is not supposed to) attempt to parse the input in

Re: RFC 2047 in headers

Jean Louis ha escrit: > To name the files. But the textual part is not a *file*. Regards, Sergey

RFC 2047 inspection

This Emacs Lisp function is supposed to give me RFC 2047 by using external command: (defun rcd-mailutils-flt2047 (string &optional encoding q-or-b) (let* ((encoding (or encoding "utf-8")) (q-or-b (or "Q" q-or-b)) (command (format "mailutils flt2047 -c %s -E%s \"%s\"" encodin

Re: RFC 2047 in headers

* Sergey Poznyakoff [2020-11-03 22:28]: > Jean Louis 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 encodi

Re: RFC2047 in headers

* Sergey Poznyakoff [2020-11-03 22:29]: > Jean Louis ha escrit: > > > It looks like you are using Q encoding. But I need B encoding as > > well. Is it possible to get B encoding? > > mailutils flt2047 -EB Really great.

Re: RFC2047 in headers

Jean Louis ha escrit: > It looks like you are using Q encoding. But I need B encoding as > well. Is it possible to get B encoding? mailutils flt2047 -EB

Re: RFC 2047 in headers

Jean Louis 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 --c

Re: RFC2047 in headers

* Sergey Poznyakoff [2020-11-03 21:23]: > Jean Louis ha escrit: > > > Am I supposed to convert the name for email address myself to RFC 2047 > > string? > > Yes, as of version 3.10, mailutils does not do that automatically. You > can use the `mailutils flt2047' command to do that: > > mail -s

Re: RFC 2047 in headers

* Sergey Poznyakoff [2020-11-03 21:12]: > Jean Louis ha escrit: > > > > > And how do I get name for the text part? > > > > That's not possible, currently. It could rather easily be implemented, > though. Can you tell me why is it needed? It is for sending emails. There is difference if I

Re: RFC2047 in headers

Jean Louis ha escrit: > Am I supposed to convert the name for email address myself to RFC 2047 > string? Yes, as of version 3.10, mailutils does not do that automatically. You can use the `mailutils flt2047' command to do that: mail -s Hello \ -E 'set sendmail=sendmail:/home/admin/bin/sen

Re: not getting content names

Jean Louis ha escrit: > > And how do I get name for the text part? > That's not possible, currently. It could rather easily be implemented, though. Can you tell me why is it needed? Regards, Sergey

RFC2047 in headers

While this works: admin-> mail -s Hello -E 'set sendmail=sendmail:/home/admin/bin/sendmail' --content-type=text/plain 'CC ' < text Following does not work: admin-> mail -s Hello -E 'set sendmail=sendmail:/home/admin/bin/sendmail' --content-type=text/plain 'ČC ' < text mail: Cannot parse addres

Re: not getting content names

* Sergey Poznyakoff [2020-11-03 17:30]: > Jean Louis ha escrit: > > > With this version I can the name for HTML part. Name is missing for > > TEXT part. > > Yes, of course. That is intended. First text part ("message body") > is treated specially. And how do I get name for the text part?

Re: not getting content names

Jean Louis ha escrit: > In regards to installation, I am using always stow for packages from I don't know what stow is, so I can't comment on that. Regards, Sergey

Re: not getting content names

Jean Louis ha escrit: > With this version I can the name for HTML part. Name is missing for > TEXT part. Yes, of course. That is intended. First text part ("message body") is treated specially. Regards, Sergey

Re: not getting content names

$ mail --version mail (GNU Mailutils) 3.10-11 [release-3.10-11-g3cab87f05] command: $ mail -s Hello -E "set sendmail=\"sendmail:/home/admin/bin/sendmail\"" --alternative --content-name HTML --content-type=text/html -A /dev/shm/html-file --content-name TEXT --content-type=text/plain s...@exampl

Re: not getting content names

* Sergey Poznyakoff [2020-11-03 14:48]: > Jean Louis ha escrit: > > > mail -s Hello -E "set sendmail=\"sendmail:/home/admin/bin/sendmail\"" > > --alternative --content-name HTML --content-type=text/html -A > > /dev/shm/html-file --content-name TEXT --content-type=text/plain > > s...@example.c

Re: not getting content names

Jean Louis ha escrit: > mail -s Hello -E "set sendmail=\"sendmail:/home/admin/bin/sendmail\"" > --alternative --content-name HTML --content-type=text/html -A > /dev/shm/html-file --content-name TEXT --content-type=text/plain > s...@example.com < text > > I have noticed that I do not get conte

not getting content names

mail -s Hello -E "set sendmail=\"sendmail:/home/admin/bin/sendmail\"" --alternative --content-name HTML --content-type=text/html -A /dev/shm/html-file --content-name TEXT --content-type=text/plain s...@example.com < text I have noticed that I do not get content-name set by using above command.