Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Steffen Dettmer (steffendett.de)
Date: Wed May 22 2002 - 02:41:21 CDT
* V K wrote on Wed, May 22, 2002 at 14:02 +1200:
> > In my opinion there should be at least one BIG warning in the
> > subscription confirmation message alerting the user that this list is
> > archived and his E-mail address therefore open to the entire public. I
> > was not aware of this fact as I subscribed.
How many spam mails did you received? 10? 100? I don't think this
is a big issue. Try to delete them... If you have 10.000 or more,
we can start discussing it here...
> Countermeasures are few. Forget protecting the archives as it doesn't
> deal with 2) above. I find the only useful and practical thing is to
> use a bogus email address in From:, as Christopher mentioned.
Well, I use my address in many mailing lists, many postings and
whereever else. But I receive a very few spam postings a day
only. So I do not understand your problem. I don't like bogus
email addresses at all, and I assume your configuration may clash
with other spamfilters that detected you mail as spam or so. I
think the largest problem of spam is the filtering, BTW... You
can use dedicated addresses for each service, i.e.
and change this email when it receives to much spam (just
block/delete the alias from the server). But I think this is much
more work that deleting a few spam mails.
> Using throwaway email addresses and changing them every 2 weeks is
> simply not practical because of the high overhead involved in
> unsubscribing/resubscribing (dealing with the passwords and bla bla).
Isn't the envelope checked only? So it should work as long as the
envelope remains constant. I think this should be possible to
-- Dieses Schreiben wurde maschinell erstellt, es trägt daher weder Unterschrift noch Siegel.
-- To unsubscribe, e-mail: suse-security-unsubscribesuse.com For additional commands, e-mail: suse-security-helpsuse.com Security-related bug reports go to securitysuse.de, not here