Il 13/09/2015 15:35, Andrei Borzenkov ha scritto:

13.09.2015 21:26, Marco Calistri пишет:

...

Hello,

I notice I'm receiving duplicate messages from opensuse-factory.

I copied below one example of the source of two email which apparently are identical:

Sun, 13 Sep 2015 18:53:05 +0200 (CEST) Subject: Re: [opensuse-factory] Cinnamon stop to work after zypper up with Tumbleweed References: <55F44E4C.9010408@yahoo.com.br> <55F48AE8.5080702@yahoo.com.br> Cc: opensuse-factory@opensuse.org To: marco.calistri@yahoo.com.br From: Fabian Niepelt Message-ID: <55F5A9F1.4000204@takios.de> Date: Sun, 13 Sep 2015 18:53:05 +0200

Sun, 13 Sep 2015 18:53:05 +0200 (CEST) Subject: Re: [opensuse-factory] Cinnamon stop to work after zypper up with Tumbleweed References: <55F44E4C.9010408@yahoo.com.br> <55F48AE8.5080702@yahoo.com.br> Cc: opensuse-factory@opensuse.org To: marco.calistri@yahoo.com.br From: Fabian Niepelt Message-ID: <55F5A9F1.4000204@takios.de> Date: Sun, 13 Sep 2015 18:53:05 +0200

Any clues?

One is sent directly to you, another to list. If you compare full headers, they will be different.

...

Thanks.

Regards,

Hi Andrei, Thanks! I was supposing same reason (To and Cc) then I want to look in the source of the two email messages looking for message ID, thinking it was different but it is the same, for this reason my remove_duplicate_messages plug-in is not removing the duplicated message. Regards, -- Marco Calistri opensuse Tumbleweed 64 bit - Kernel 4.1.6-3-desktop Gnome 3.16.2 Intel® Core™ i5-2410M CPU @ 2.30GHz × 4 - Intel® Sandybridge Mobile -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Il 13/09/2015 15:44, Patrick Shanahan ha scritto:

* Marco Calistri [09-13-15 14:26]:

...

Hello,

I notice I'm receiving duplicate messages from opensuse-factory.

I copied below one example of the source of two email which apparently are identical:

Sun, 13 Sep 2015 18:53:05 +0200 (CEST) Subject: Re: [opensuse-factory] Cinnamon stop to work after zypper up with Tumbleweed References: <55F44E4C.9010408@yahoo.com.br> <55F48AE8.5080702@yahoo.com.br> Cc: opensuse-factory@opensuse.org To: marco.calistri@yahoo.com.br From: Fabian Niepelt Message-ID: <55F5A9F1.4000204@takios.de> Date: Sun, 13 Sep 2015 18:53:05 +0200

Sun, 13 Sep 2015 18:53:05 +0200 (CEST) Subject: Re: [opensuse-factory] Cinnamon stop to work after zypper up with Tumbleweed References: <55F44E4C.9010408@yahoo.com.br> <55F48AE8.5080702@yahoo.com.br> Cc: opensuse-factory@opensuse.org To: marco.calistri@yahoo.com.br From: Fabian Niepelt Message-ID: <55F5A9F1.4000204@takios.de> Date: Sun, 13 Sep 2015 18:53:05 +0200

Any clues?

Apparently the sender decided you could not be trusted to read his reply on the list and sent you a personal copy so you could trash it. A *very* poor choice by the OP. Anyone active on the list or posting on the list should be expected to see replies that appear on the list and does not need a personal copy *unless* specifically requested.

Hi Patrick, I use to answer to "the list" and not to "all" but I see others like to use other method; on the other hand I think there also some limitation to my email client which is not able to "discriminate" two almost identintical email in fact it could be safely delete one since the ID and sent time are exactly the same. Regards, -- Marco Calistri opensuse Tumbleweed 64 bit - Kernel 4.1.6-3-desktop Gnome 3.16.2 Intel® Core™ i5-2410M CPU @ 2.30GHz × 4 - Intel® Sandybridge Mobile -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-09-13 21:20, Patrick Shanahan wrote:

There is no reason to answer to "all" past a convenience for broken clients not recognizing list mail needs response to list and an inconvenience on the reader who in many if not most is being asked for help or information.

There are many clients that do not have a reply-to-list button. For instance, Alpine doesn't, and Thunderbird/Seamonkey did not for many years. Most (All?) webmail clients do not. Tablet's mail do not, or I haven't found one that does. It is best to send only a reply to the list, yes, but also tolerate those that don't, or forget, by applying filtering on the local side to handle direct replies without nuisance ;-) - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlX17IIACgkQja8UbcUWM1w0/gD/Ri1WPioE0Rt+L89S3ErERWlg c5ut89QVEsskt/2le4EA/21lSXhnJ45bNTm5u0WYWa2H6HL5SgSuOFbn9mP0BoYd =+4Mq -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Jan Engelhardt [09-13-15 18:06]:

On Sunday 2015-09-13 23:37, Carlos E. R. wrote:

...

On 2015-09-13 21:20, Patrick Shanahan wrote:

...

There is no reason to answer to "all" past a convenience for broken clients not recognizing list mail needs response to list and an inconvenience on the reader who in many if not most is being asked for help or information.

There are many clients that do not have a reply-to-list button. For instance, Alpine doesn't, and Thunderbird/Seamonkey did not for many years. Most (All?) webmail clients do not. Tablet's mail do not, or I haven't found one that does.

Apart from the trivial answer "they forgot implementing it", you must consider the "nomail" feature (as e.g. implemented by GNU mailman), which, in essence, makes it such that you only receive mail *for subthread(s) you participated in*. That, of course, relies on the other party to not withhold mail from individual entities.

How do you participate in a thread which you do not start and cannot see since you have not previously participated in it? Or do you mean that you receive *only* the first post of a thread? I thought my chosen client was quite capable but the only nomail feature I have ever heard of is that I don't receive *mail* unless I fetch it??? But I am fairly new to computers :^).

And that's why Reply-To-List sucks. It's better to have duplicate mails and deal with them somehow, than to have none at all to process.

Reply-To-List only sucks for a client that cannot handle mail properly. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Monday 2015-09-14 02:46, Patrick Shanahan wrote:

...

Apart from the trivial answer "they forgot implementing it", you must consider the "nomail" feature (as e.g. implemented by GNU mailman), which, in essence, makes it such that you only receive mail *for subthread(s) you participated in*. That, of course, relies on the other party to not withhold mail from individual entities.

How do you participate in a thread which you do not start and cannot see since you have not previously participated in it?

* Download mbox file from the list archive. Open with pine, Reply. * Or, if no mbox file exists, make one. (In pine: compose new message, save as draft, edit externally to set In-Reply-To header, continue composing, copy-paste text to quote). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Monday 2015-09-14 13:59, Patrick Shanahan wrote:

* Jan Engelhardt [09-14-15 03:52]:

...

On Monday 2015-09-14 02:46, Patrick Shanahan wrote:

...

...

Apart from the trivial answer "they forgot implementing it", you must consider the "nomail" feature (as e.g. implemented by GNU mailman), which, in essence, makes it such that you only receive mail *for subthread(s) you participated in*. That, of course, relies on the other party to not withhold mail from individual entities.

How do you participate in a thread which you do not start and cannot see since you have not previously participated in it?

* Download mbox file from the list archive. Open with pine, Reply. * Or, if no mbox file exists, make one. (In pine: compose new message, save as draft, edit externally to set In-Reply-To header, continue composing, copy-paste text to quote).

And this necessitates responding to "All" rather than to the list; you have taken the time to manually set "In-Reply-To", why not also "Mail-Followup-To"?

Because I generally have case #1, i.e. mbox archives. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Monday 2015-09-14 14:48, Patrick Shanahan wrote:

So pine does not have the ability to automagically "reply to list"

It does interpret X-Mailing* headers, prints at the end of documents a hyperlink: [ Note: This message contains email list management information ] leading to a subpage with lots of mailto: links that one can use. But that's like, totally irrelevant to the discussion. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-09-13 20:54, Marco Calistri wrote:

I use to answer to "the list" and not to "all" but I see others like to use other method; on the other hand I think there also some limitation to my email client which is not able to "discriminate" two almost identintical email in fact it could be safely delete one since the ID and sent time are exactly the same.

Well, for instance, Gmail server automatically erases what it thinks are duplicates of any email. As the direct reply arrives earlier than the on-list reply, the later is removed. If one replies using a gmail account, your own sent email is thus already in the server, and the copy forwarded by the list is considered a duplicate and silently erased. All that is incorrect. It is better to have all copies, and filter each to the appropriate folder. For instance, you can locate list email because of the header "Mailing-List:". If after that filter acts, there is an email with a "To:" header set to the same list, it is a direct email which you can safely move to another folder with another filter. What remains are direct, off-list, posts. This way you are not bothered by what could be double posts ;-) - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlX16vQACgkQja8UbcUWM1wuVQD+PbnSQgmVP8U7t18C0Pd0XupM 1mDmiZC5Z0rc3oR+5lwA/3KAA0tBMoBN2F3f+FpZVuOsrIxSMOTcw7eppVXR9yHc =R/JR -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-09-14 14:58, Marco Calistri wrote:

Il 13/09/2015 18:30, Carlos E. R. ha scritto:

Yes Carlos, I thought to improve my current filtering and most probably I will do this.

These are my rules in procmail for this mail list, maybe they give you ideas: :0f * ^X-Mailinglist: opensuse-factory | $FORMAIL -bfi 'Reply-To: "OS-fctry" ' :0 aw: $HOME/Mail/.D-locks/_Lists/os-factory.lock | $DELIVER -m _Lists/os-factory ... #Trimmed :0 w: $HOME/Mail/.D-locks/_Lists/in_dups.lock * ^TO_((opensuse-es|opensuse-project|opensuse)@opensuse.org) | $DELIVER -m _Lists/in_dups # Catch all :0 w: $HOME/Mail/.D-locks/_Lists/in_rst.lock | $DELIVER -m _Lists/in_rst Three folders. Notice the "formail" line above: it adds a "reply-to" header to each post, so that reply to list is forced on clients that do not have a reply to list function. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlX2zmMACgkQja8UbcUWM1yx0AD+KuNxO3k19I3fJtvck0CVR5ZI TPtNHRbg8l9i+8Fem1MA/Rdl4wt9dsY43CPTJnE6cQ1Hf0d+sJvG5rMlgSjVDtZH =G7Z4 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org