Hello!
On Wed, Nov 24, 2021 at 05:21:10PM +, Jean Louis wrote:
> * Anders Damsgaard [2021-11-22 12:05]:
> > * Globe Trotter via Mutt-users [2021-11-22 00:47:10
> > +]:
> > > What is the recommended way to pretty-print mutt emails? I found a
> > > sourceforge perl script called muttprin
I do use on FreeBSD muttprint:
Name : muttprint
Version: 0.73_5
Installed on : Sun Sep 24 11:32:52 2023 CEST
Origin : print/muttprint
Architecture : FreeBSD:14:amd64
Prefix : /usr/local
Categories : print mail
Licenses : GPLv2
Maintainer : g...
Message-Id: <254061712447...@mail.yandex.ru> - this is how Message-Id
looks like when I receive an e-mail sent from Yandex mail web interface.
When I send a mail via mutt with activated option set hostname =
example.com, my mails have Message-ID: .
Question, what should I write in .muttrc to make m
Ебрашка wrote:
> my mails have Message-ID: . Question, what
> should I write in .muttrc to make my outgoing mails have the same beautiful
> message-ID as Yandex mail?
My first question would be, why do you care what the Message-ID: field
contents look like? Virtually no-one will ever look at i
On Sun, Apr 07, 2024 at 09:23:07AM -0600, Charles Cazabon via Mutt-users wrote:
> Ебрашка wrote:
> > my mails have Message-ID: . Question, what
> > should I write in .muttrc to make my outgoing mails have the same beautiful
> > message-ID as Yandex mail?
>
> My first question would be, why do y
On 7 Apr 2024 18:23 +0200, from anton.sharo...@gmail.com (Anton Sharonov):
>>> For example Message-Id: <43265...@example.com> consisting of random
>>> digits and domain name
>>
>> There's a good reason for that; it help to ensure uniqueness, which prevents
>> problems with threading. By limiting
