On 09/08/2012 05:30 AM, Lars M�ller wrote:
On Sat, Sep 08, 2012 at 02:04:26AM +0200, Carlos E. R. wrote:
I see more often than before spam sent to various opensuse email lists, some of them repeatedly with the same from address.
I have not seen any spam from the list lately. Are you sure they're from the list and are not forged senders? When in doubt I look at the headers. With regard to lists, more often than not, the messages turn out to be from somewhere other than a list. Except for all the misconfigured, abandoned and unmaintained Yahoo lists. Look at the headers of several authentic list messages, compare with the spam messages. The Received chain should be the same and unbroken. Broken Received chains are indication of spam. Sources other than the suse.org mail servers are also indications of spam. The rest of the headers should be consistent amongst all the messages. If you're certain that the spam comes from the list, let the list maintainer know. The worst that can happen is that you'll be told it's not from the list.
Any of us list members is able or has to handle this at our individual end.
Spammers on a list are the *list maintainer's responsibility*, /not/ the responsibility the user|subscriber. Failure to maintain clean lists can quickly get the list and domain on several blacklists. In turn, a lot of list subscribers will stop receiving list mail. A lot of blacklists are pretty damned difficult to be removed from. It seems to me that SuSE maintains clean lists. I have not seen spam on this list in a while. I have seen occasional spams some time ago and the spammer was dealt with quickly, presumably because the list maintainer actually reads the list. In re vacation autoresponders: Generally it's the user who is to blame for sending vacation/out-of-office autoreplies. Even half-assed autoresponders have it together enough to have the either the user-settable option of not responding to list traffic or know what a list is and suppress autoresponses. It's the user's responsibility to properly configure his autoresponder so that it suppresses unwanted traffic, such as that to lists. Sometimes a user will come across some old, stupid vacation script in a book and thinks how cool it would be to roll his own but fails to consider the havoc wrought by a script that reponds to _every_ mail message received. Here again, the headers tell the story. Look at normal list message headers and compare to the autoresponder message. Pay particular attention to the From, From: and Sender: headers. If the autoresponder message headers are not the same as the list message headers the autoresponder message did not come from the list but directly from the list subscriber himself. If an autoresponder spews to a list, tell the sender to fix it or else be unsubscribed. Then follow through. If, as is more likely the case, the autoresponder is spewing directly to list posters or subscribers, likely based on the From: header, reply directly to the sender with the whole autoreply quoted and _politely_ ask him to fix his autoresponder and suggest that if he doesn't you will have to blocklist him and notify the list. Most list maintainers consider such autoresponder behaviour to be an abuse of the list and will also warn the sender. But if you're getting some rude challenge-response from an autoresponder demanding you prove you're human before a list message (or any message) will be delivered to the recipient, just block them, drop or reject their messages in filters. These things are offensive and are at least as bad as spam. Users of these things aren't thinking very clearly and probably don't have any friends left. Maybe let the list maintainer know as this is also an abuse of the list: Every other sender on the list also gets these things. The recipient doesn't have his act together enough to accept list messages so he doesn't need to receive them. jd -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org