Wesley Peng writes:
> ...
> Shall we use plaintext message in regular email communication?
If somebody use Linux/*BSD, i would like to accept HTML messages with
pleasure! Because most Linux/*BSD users send messages as plaintext. It
was just personal opinion.
Sincerely, Byung-Hee
--
^고맙습니다
Darac Marjal wrote:
> This is where your ~/.mailcap file comes in. This is a great file
> for registering viewers for MIME types. So, for example, I have the
> following in my Mailcap:
...
> application/pdf; pdftotext %s -; copiousoutput
I suggest using the pdftotext -layout option. It can
On 20/03/2020 16:07, Jaroslaw Rafa wrote:
> Dnia 20.03.2020 o godz. 11:48:59 Gerard E. Seibert pisze:
>> When I receive an email, I have two immediate choices to make; either
>> read it or don't read it.
> Let's say I decide to read it, so I press ENTER on the message header.
> If it's plaintext,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 3/20/20 3:29 PM, Ben Lavender wrote:
> I prefer text/plain myself, it gets rid of all the annoying
> marketing images and silly fonts people like to use. It also proves
> a point that modern day marketing of nice long mail signatures with
>
I prefer text/plain myself, it gets rid of all the annoying marketing
images and silly fonts people like to use. It also proves a point that
modern day marketing of nice long mail signatures with company branding
on them can be pointless when milters and antispam services remove most
of them
On Fri, 20 Mar 2020 17:07:00 +0100, Jaroslaw Rafa stated:
>Dnia 20.03.2020 o godz. 11:48:59 Gerard E. Seibert pisze:
>>
>> When I receive an email, I have two immediate choices to make; either
>> read it or don't read it.
>
>Let's say I decide to read it, so I press ENTER on the message
On 3/20/20 11:48 AM, Gerard E. Seibert wrote:
>
> Honestly, I fail to see why receivers of HTML based emails seem to
> feel they have a right to get themselves into a hissy fit and dictate
> what type or form of email is permissible? Who made them GODS?
>
> When I receive an email, I have two
Dnia 20.03.2020 o godz. 11:48:59 Gerard E. Seibert pisze:
>
> When I receive an email, I have two immediate choices to make; either
> read it or don't read it.
Let's say I decide to read it, so I press ENTER on the message header.
If it's plaintext, I continue straight on to reading it.
If it's
On Fri, 20 Mar 2020 08:02:19 -0600, @lbutlr stated:
>On 19 Mar 2020, at 00:16, Philip Paeps wrote:
>> On 2020-03-18 09:51:45 (+0800), Wesley Peng wrote:
>>> Following this guide:
>>> https://useplaintext.email/
>>>
>>> Shall we use plaintext message in regular email communication?
>>
>>
On 19 Mar 2020, at 00:16, Philip Paeps wrote:
> On 2020-03-18 09:51:45 (+0800), Wesley Peng wrote:
>> Following this guide:
>> https://useplaintext.email/
>>
>> Shall we use plaintext message in regular email communication?
>
> You should use what the content of the message needs modulo your
Bob Proulx:
> Wietse Venema wrote:
> > I think this train has left the station almost 30 years ago. The
> > only people who care about plaintext are people who were born before
> > circa 1980, or who are part of some extremist minority.
>
> That isn't required to be a logical OR condition. It is
Wietse Venema wrote:
> I think this train has left the station almost 30 years ago. The
> only people who care about plaintext are people who were born before
> circa 1980, or who are part of some extremist minority.
That isn't required to be a logical OR condition. It is possible for
me to be
On 2020-03-18 09:51:45 (+0800), Wesley Peng wrote:
Following this guide:
https://useplaintext.email/
Shall we use plaintext message in regular email communication?
You should use what the content of the message needs modulo your
recipients' wishes.
I personally prefer to receive plain text
Has anyone considered the absolute want of utility that image data presents for
the blind?
The advantage of plain text is that there are any number of automated assists
that can process it into audio.
--
*** e-Mail is NOT a SECURE channel ***
Do NOT transmit sensitive
On 2020-03-18 09:08, Wietse Venema wrote:
> I think this train has left the station almost 30 years ago. The
> only people who care about plaintext are people who were born before
> circa 1980,
> or who are part of some extremist minority.
Which includes anyone who even _knows_ what comprises
On Wed, Mar 18, 2020 at 03:27:24PM +, Darac Marjal wrote:
On 18/03/2020 02:40, Anton Rieger wrote:
On Wed, Mar 18, 2020 at 02:51:45AM +0100, Wesley Peng wrote:
Hello
Hello
Following this guide:
https://useplaintext.email/
I don't like it's tone but it's mostly ok
Shall we use
On Wed, Mar 18, 2020, at 11:27, Darac Marjal wrote:
> Markdown is a very good step
> towards this, IMO.
Oh the irony...
>From the initial announcement of Markdown by John Gruber
>(https://web.archive.org/web/20040402182332/http://daringfireball.net/projects/markdown/):
" the single biggest
On 2020-03-18 03:40, Anton Rieger wrote:
Do xyz like you see in image1.png.
Lorem Ipsum look at image2.png.
images is not html
and OP asked to do plain text, not remove inline images attachments
/me hiddes before the fire starts burning now
I think this train has left the station almost 30 years ago. The
only people who care about plaintext are people who were born before
circa 1980, or who are part of some extremist minority.
Wietse.
On 2020-03-18 02:51, Wesley Peng wrote:
Shall we use plaintext message in regular email communication?
to make the postfix digest maillist look better yes :=)
Dnia 18.03.2020 o godz. 16:52:10 m...@junc.eu pisze:
> On 2020-03-18 03:40, Anton Rieger wrote:
>
> >Do xyz like you see in image1.png.
> >Lorem Ipsum look at image2.png.
>
> images is not html
>
> and OP asked to do plain text, not remove inline images attachments
inline images != image
Dnia 18.03.2020 o godz. 15:27:24 Darac Marjal pisze:
>
> I'd argue then, that a middle ground is the way forward. Emails should
> be written in a markup language which is both relatively simple (yet
> flexible enough to handle the basic formatting commands) and human
> readable before (and after)
On 2020-03-18 11:27, Darac Marjal wrote:
> There is clearly a desire among users for something more than plain
> text. You often want *emphasis* in flame wars. You want a table in
> reporting your financial results or when listing various things.
> However, I think everyone can agree that
On 18/03/2020 02:40, Anton Rieger wrote:
> On Wed, Mar 18, 2020 at 02:51:45AM +0100, Wesley Peng wrote:
>> Hello
> Hello
>
>>
>> Following this guide:
>> https://useplaintext.email/
> I don't like it's tone but it's mostly ok
>
>>
>> Shall we use plaintext message in regular email communication?
>
Agree!
On 18/3/20 9:51 am, Wesley Peng wrote:
Hello
Following this guide:
https://useplaintext.email/
Shall we use plaintext message in regular email communication?
Thanks
Dnia 18.03.2020 o godz. 02:51:45 Wesley Peng pisze:
>
> Following this guide:
> https://useplaintext.email/
>
> Shall we use plaintext message in regular email communication?
Absolutely. Email basically is, was and should remain plaintext.
Use HTML only when it's absolutely necessary. By
On Wed, Mar 18, 2020 at 02:51:45AM +0100, Wesley Peng wrote:
Hello
Hello
Following this guide:
https://useplaintext.email/
I don't like it's tone but it's mostly ok
Shall we use plaintext message in regular email communication?
I use it regulary, except if I give tutorials in support
Wesley Peng writes:
> Hello
>
> Following this guide:
> https://useplaintext.email/
>
> Shall we use plaintext message in regular email communication?
Yes, why not?
Messages are smaller and more often than not, people are so bad at text
presentation that their mails are plain ugly and hard to
Hello
Following this guide:
https://useplaintext.email/
Shall we use plaintext message in regular email communication?
Thanks
29 matches
Mail list logo
