I say no.

You won't convince anyone.

If they haven't hidden their identity, then they think they aren't doing anything wrong. As such, they'll consider themselves an innocent victim of misdirected "retaliation." If they have hidden their identity, the source can't be identified beyond a reasonable doubt. Even if you can identify someone who knows they've sinned, your retaliation confirms what they already know, and they are again not convinced.

Whoever made the decision to spam you probably will not be who bears the cost of your retaliation. I haven't worked anywhere that such a decision-maker is also the mail systems maintainer.

Where's the police when you need them?

If you think what they're doing is wrong, send the authorities after them. If that's not going to work, maybe it's not really wrong but merely annoying.

An analogy

When driving, a car behind you is following too closely. Do you slam on the brakes to teach the driver a lesson? This is dangerous. The practice of following too closely isn't illegal (I think), merely annoying. If there's a collision, you'd be partly responsible.

A suggestion

Write a polite but firm letter explaining why you think you should not be getting this mail in the first place and urging the organization to stop emailing others in this fashion. Make phone calls if you want. Try to reach whoever it was that actually made this decision. Explain that this is damaging to the organization's image.

If all else fails,

Meditate. Become one with the fundamental 1 and the fundamental 0. Ponder the nature of truth and falsehood. Take deep breaths and be grateful you sought guidance before seeking vengeance.

In reply to Re: (OT) Is retaliation ethical if a spam source can be identified beyond a reasonable doubt? by kyle
in thread (OT) Is retaliation ethical if a spam source can be identified beyond a reasonable doubt? by leocharre

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.