Henne Vogelsang wrote:
Hi,
On Saturday, August 12, 2006 at 06:16:32, Rajko M wrote:
Eberhard Moenkeberg a écrit :
If not, the lists will run into the desert because too much answers go wrong, or they will run into starvation because people start unsubscribing because they feel penetrated by double answers (list and private). wether or not you like the new setup you may be aware that it's the very same setup of the suse-e mailing lits, one of the heaviest traffic suse one, so no, people wont go away (not for this reason, at least) The same as "one old list" that was set and software configured in times without privacy concerns doesn't mean it is good. Now they are trying to
jdd wrote: patch holes with a Spam Assassin, but what this can cover is just a part of the problem.
What the heck are you talking about? Why would a reply-to field that is pointing to the list address prevent spam? Youre not making any sense. Please explain.
Henne
If you wouldn't be focused to reaction on recent changes, than my posting will make sense. Reply to filed will prevent nothing, and I didn't refer to that at all in a quoted paragraph. The recent change is inconvenience as I have to edit header for every posting. I really don't want to reply to anybody privately and the TB that has well solved privacy protection, has 2 options: 1. Reply to Sender 2. Reply to All They work both as the name tells for peer to peer mails. With list 1. gives a private email and the 2. all private and the list. The Spam Assassin protects the lists from the spam that some might post to, but contributors are not protected from harvesters. That is what I meant as partially solved problem. What I would like to see is something like what you applied in the mail list archives, overwriting of private mail addresses with xxxxxxxxxx, which is excellent. If that would be possible for mails that list server sends to subscribers, than is solved the second problem of protecting the subscribers. -- Regards, Rajko. Visit http://en.opensuse.org/MiniSUSE