You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Mauricio Tavares <ra...@gmail.com> on 2011/08/11 20:45:31 UTC
linkedin messages
It seems some people that are in a mailing list I am responsible
for also have linkedin. And every so often we get email from one of
them asking me to join it; it is addressed to a bunch of people
besides that mailing list. Without caring about what is going on their
side, is there a spamassassin rule already for filtering linkedin
stuff or is this the perfect time for me to learn how to make my own
rule?
Re: linkedin messages
Posted by ji...@jidanni.org.
See also https://bugzilla.wikimedia.org/show_bug.cgi?id=29855
Re: linkedin messages
Posted by jdow <jd...@earthlink.net>.
Best put that in your own personal user_prefs. Some people want them.
{^_^}
On 2011/08/13 13:57, jidanni@jidanni.org wrote:
> And even if you are a card carrying member of LinkedIn,
> header J_CANT_STOP Subject =~ /^LinkedIn Network Updates/
> score J_CANT_STOP 222
> is needed, as even LinkedIn staff are unable to stop sending them.
>
Re: linkedin messages
Posted by ji...@jidanni.org.
And even if you are a card carrying member of LinkedIn,
header J_CANT_STOP Subject =~ /^LinkedIn Network Updates/
score J_CANT_STOP 222
is needed, as even LinkedIn staff are unable to stop sending them.
Re: linkedin messages
Posted by Michael Scheidell <mi...@secnap.com>.
On 8/13/11 7:02 AM, Greg Troxel wrote:
> (Also, I forward every bogus invitation toabuse@linkedin.com, and this
> seems to result in them spending a few minutes giving me
> too-hard-to-believe-its-true claim it's not their fault.)
also forward them to return path.. certification@returnpath.net they
get paid to 'certify' that linked in isn't spamming.
enough complaints, and they will stop (unless linked in pays them a
lot.. they we go back to argument about SA scoring all these high
scoring spammers just because linked in pays return path to ignore
complaints).. and, yes, I have gone round and round with return path
about linked in.
they say I must have signed up.. (I said prove it), they could not. it
was a harvested spamtrap address. they said, well, these are not UCE,
they are 'transactional' since it wasn't selling anything, just inviting
me to join. (join what? linked in? a 501C3 non profit charitable
organization? ).. no, a commercial organization.
no, return path should de-certify linked in until they have a button
like the others have' click here to report abuse' /and/or click here to
never get invitations again.
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
>*| *SECNAP Network Security Corporation
* Best Mobile Solutions Product of 2011
* Best Intrusion Prevention Product
* Hot Company Finalist 2011
* Best Email Security Product
* Certified SNORT Integrator
______________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(r).
For Information please see http://www.secnap.com/products/spammertrap/
______________________________________________________________________
Re: linkedin messages
Posted by Greg Troxel <gd...@ir.bbn.com>.
Mauricio Tavares <ra...@gmail.com> writes:
> It seems some people that are in a mailing list I am responsible
> for also have linkedin. And every so often we get email from one of
> them asking me to join it; it is addressed to a bunch of people
> besides that mailing list. Without caring about what is going on their
> side, is there a spamassassin rule already for filtering linkedin
> stuff or is this the perfect time for me to learn how to make my own
> rule?
There are two separate problems. The basic issue seems to be that
linkedin lets users upload address books and then send invitation-spam
to all of them. When those addresses are individuals, that's one thing.
When those addresses are lists, the problem is far worse. I've
explained this to abuse@linkedin.com, and they seem not to care. One
can observe that their rude behavior results in advertising. What's
worse is that the mail is forged From: the user, not linkedin, so it
passes "sender is a list member".
So, there's one debate we could have about marking all linkedin
invitations as spam; to me that's a marginal call. There's a second
debate about removing any whitelist that claims they aren't spam, and I
don't think there's any question that we should remove those whitelists.
Then, it seems that what's spam to a user and what's spam to a
mailinglist are different. I would guess that there is near 100%
agreement that invitations to lists are always spam. I haven't written
a rule, mostly because I don't run mailinglists that suffer from
clueless linkedin users, but what I'd do is basically
(manual config on the list, or match something, to say that it's a
list)
rule to match linked invitations
if LIST and LINKEDIN, score 10 points. Optionally, unsubscribe the
user.
Alternatively, this could be built in to mailman.
(Also, I forward every bogus invitation to abuse@linkedin.com, and this
seems to result in them spending a few minutes giving me
too-hard-to-believe-its-true claim it's not their fault.)
Re: linkedin messages
Posted by Michael Scheidell <mi...@secnap.com>.
On 8/11/11 9:53 PM, Benny Pedersen wrote:
> why do you self post spam here ?
<http://tools.ietf.org/html/rfc3676>
<http://www.hanselman.com/blog/EmailSignatureEtiquetteTooMuchFlair.aspx>
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
>*| *SECNAP Network Security Corporation
* Best Mobile Solutions Product of 2011
* Best Intrusion Prevention Product
* Hot Company Finalist 2011
* Best Email Security Product
* Certified SNORT Integrator
______________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(r).
For Information please see http://www.secnap.com/products/spammertrap/
______________________________________________________________________
Re: linkedin messages
Posted by Benny Pedersen <me...@junc.org>.
On Thu, 11 Aug 2011 14:49:33 -0400, Michael Scheidell wrote:
> oh, I forget, your spam is not 'commercial' its transactional
> (according to return path who certifies that linked in doesn't spam)
might be why google+ needs invite from users that are on google+ ?
so google+ never spammed users :)
PS: if any linkedin maaintainers read here, dont send email to some
users that are not known as users on linkedin, just a shame that this
kills the idear of asking friends to join :(
> Links:
> ------
> [1] http://www.secnap.com/products/spammertrap/
why do you self post spam here ?
Re: linkedin messages
Posted by Michael Scheidell <mi...@secnap.com>.
On 8/11/11 2:45 PM, Mauricio Tavares wrote:
> It seems some people that are in a mailing list I am responsible
> for also have linkedin. And every so often we get email from one of
> them asking me to join it; it is addressed to a bunch of people
> besides that mailing list. Without caring about what is going on their
> side, is there a spamassassin rule already for filtering linkedin
> stuff or is this the perfect time for me to learn how to make my own
> rule?
put this in local.cf (or you ~user prefs) and restart
blacklist_from *@linkedin.com
if linked in would actually put a 'don't ever bug me again' link in the
email, or, even a simple unsubscribe, it would not be all that bad.
(hey linked in.. want me to find someone for you who can put in an unsub
button? seems your programmers can't figure out how to comply with
federal, state and several international laws)
oh, I forget, your spam is not 'commercial' its transactional (according
to return path who certifies that linked in doesn't spam)
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
>*| *SECNAP Network Security Corporation
* Best Mobile Solutions Product of 2011
* Best Intrusion Prevention Product
* Hot Company Finalist 2011
* Best Email Security Product
* Certified SNORT Integrator
______________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(r).
For Information please see http://www.secnap.com/products/spammertrap/
______________________________________________________________________