On 23 Nov 2020, at 13:24, Bob Proulx <b...@proulx.com> wrote:
> Jaroslaw Rafa wrote:
>> Dnia 23.11.2020 o godz. 10:18:39 D'Arcy Cain pisze:
>>> After the first message was accepted all of the rest
>>> were silently dropped as duplicates due to a very standard procmail
>>> recipe:
>>>
>>> :0 Wh: msgid.lock
>>> | formail -D 65536 $HOME/.msgid.cache
>>
>> Who uses that? It's not normal to get email duplicates and it usually
>> means that mail system is not functioning properly. They should find the
>> cause of the duplicates and eliminate it instead of hiding symptoms...
>
> Although I have been using procmail since the inception of it I have
> always found this type rule problematic. Because for me it keeps the
> wrong message. If I am sent a direct copy and a mailing list copy
> then the copy I want is the mailing list copy.
Since my list filters looked at the to and CC headers this wasn't an issue.
> But so many people use Gmail these days that they have gotten used to
> the way Gmail does things. And Gmail de-duplicates and saves the
> first message with any particular message-id that arrives. And then
> displays a "mailbox" showing a view of the current tag being
> displayed. It's a very different paradigm from having separate
> mailbox folders for different topics.
I don't use Gmail much, but my primary sort criteria now is a series of smart
searches in Mail.app.
List mail al goes into a single "List" mailbox, then a smart search shows me,
for example, all the postfix-users messages as a virtual mailbox.
The means that I rarely see the messages sent directly to me instead of the
list because I don't generally read the "list" mailbox directly. Every now and
then I archive all the list messages which takes them out of the smart
mailboxes. (I could automate that action, but I haven't for reasons).
--
'Witches just aren't like that,' said Magrat. 'We live in harmony
with the great cycles of Nature, and do no harm to anyone, and
it's wicked of them to say we don't. We ought to fill their bones
with hot lead.'
