Me "spamming" this list...

[Arno Wagner]

--n8g4imXOkfNTN/H1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Dear gnupg-devel list members,

in the last 48 hours (or so) this list has received messages
from my spam-detector about spam being dropped.=20

I am sorry about this, please accept my apology!

I think I should explain what happened, so maybe others can=20
avoid the mistakes I made: I have a very manual spam filter,
that I maintain by just adding to my .procmailrc. For hard spammers
I just drop the mail, for others I had an auto-reply feature.=20
While I was careful all my receipes are restrictive enough not
to be overly trigger-happy, I did not take into account the
possibility for a different kind of error.=20

What I effectively did in one match-expression whas replace the
leading "*" with a "$". As a result this rule appearently matched for
every Email that came in. As a consequence every email to me got a
notification about it being spam and dropped, which also happened to
all the messages telling me there was something wrong on my side.

To make things worse, we had an announced partial network outage=20
on Wednsday (routing tables cleanup) so I was not suspicous about
not getting any email. I was not at work on Wednsday, so I=20
finally found out about the problem when somebody phoned me
Thursday morning.=20

At that time I had about 30 messages telling me about the problem
and about 400 Messages from a mail-loop, that happened despite=20
my measures to prevent loops.

Lessons learned on my side:

  - Don't send out automatic responses to, if the trigger-
    mechanism has a single point-of-failure!

    For the time being I make that: Don't send out any automated
    responses.=20

  - Doing full logging is a very good idea when automatically=20
    deleting messages! =20

    Because I at least got this right, I did not loose any=20
    messages and was able to identify everybody that I needed to
    apologize to.

  - If you screw up, apologize a.s.a.p. to those affected and
    explain what happened!    =20

  - Look at statistics frequently!=20

    My previous set-up gave me one spam-summary per week. That is=20
    not enough, now I am getting a daily summary. =20

  - Make sure you understand the problem!=20

    My mail-loop detection scheme used a field in the header with=20
    a magic number. That is fine for every loop that keeps the=20
    auto-response somewhere in the replys, but this one list-admin=20
    daemon just send me a completely fresh email about not=20
    understanding my command. Practical loop detection is obviously
    more complicated than I thought ....

Once again, please accept my apologies for this incident!

Regards,
Arno

--=20
Arno Wagner, Communication Systems Group, ETH Zuerich, wagner@tik.ee.ethz.ch
GnuPG:  ID: 1E25338F  FP: 0C30 5782 9D93 F785 E79C  0296 797F 6B50 1E25 338F
----
For every complex problem there is an answer that is clear, simple,=20
and wrong. -- H L Mencken





--n8g4imXOkfNTN/H1
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.3 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAjz3VhsACgkQeX9rUB4lM48uLQCghU0zkyXRytpzgoX4B0msXvw2
fIgAn1thxK02W4Ge0jlImr5nVYRRjP88
=tPIM
-----END PGP SIGNATURE-----

--n8g4imXOkfNTN/H1--