At 2:59 PM -0400 2006-07-11, Harold Goldstein wrote:
> yes, exactly ... sorry about not being more specific ... i am wondering if
> anyone else has this experience oft he list =-owner being spammed in this
> manner
Yup. Happens to me all the time.
> and if there is anyway to guard ag
Patrick Bogen sent the message below at 13:08 7/11/2006:
>On 7/11/06, Dragon <[EMAIL PROTECTED]> wrote:
>>Such "obfuscation" is virtually useless. It is a pretty trivial
>>exercise to write a Perl program to collect e-mail addresses from
>>such schemes (I could do it in a matter of less than an ho
Patrick Bogen wrote:
>
>FWIW, the mini-turing-test ideas seem fairly reasonable, if you build
>in enough variations.
>E.g.,:
>[EMAIL PROTECTED] (remove fish)
Yes, but what do you do when [EMAIL PROTECTED] threatens to sue
you over all the spam she gets because you published her address? :-)
--
On 7/11/06, Dragon <[EMAIL PROTECTED]> wrote:
> Such "obfuscation" is virtually useless. It is a pretty trivial
> exercise to write a Perl program to collect e-mail addresses from
> such schemes (I could do it in a matter of less than an hour to cover
> all of the common variations). Same goes for
Ron Brogden sent the message below at 12:47 7/11/2006:
>Most lists seem to display the real address anyway so I am not sure how much
>this obfuscation step really helps:
>
>http://mail.python.org/mailman/listinfo/mailman-users
>
>"Mailman-Users list run by barry at python.org, brad at python.org,
On Tuesday 11 July 2006 12:39, Patrick Bogen wrote:
> This somehow subverts the purpose of that address, though, which is to
> allow outside persons to easily contact the owner of the list, without
> necessarily knowing anything about the list.
Most lists seem to display the real address anyway so
On 7/11/06, Ron Brogden <[EMAIL PROTECTED]> wrote:
> My personal solution to this issue was to only allow posts to that address
> from the machine itself. After adding that rule to the Exim configuration
> the amount of Mailman injected spam I have to deal with dropped by at least
> 80% percent.
On Tuesday 11 July 2006 07:52, Harold Goldstein wrote:
> here is the header of a spam received this morning by 2 of us listed as
> pptc-announce-owner ...
> it is not being directed to the list itself.
My personal solution to this issue was to only allow posts to that address
from the machine it
On 7/11/06, Harold Goldstein <[EMAIL PROTECTED]> wrote:
> yes, exactly ... sorry about not being more specific ... i am wondering if
> anyone else has this experience oft he list =-owner being spammed in this
> manner and if there is anyway to guard against it.
I think that the usual anti-spam me
At 12:49 PM 7/11/2006, Patrick Bogen wrote:
>On 7/11/06, Mark Sapiro <[EMAIL PROTECTED]> wrote:
>>Is there a question here, or is this perhaps an off-list thread that
>>sudddenly bacame public?
>
>I think Harold is asking why the spam was directed to
>pptc-announce-owner. From the headers (I may or
Patrick Bogen wrote:
>
>I think Harold is asking why the spam was directed to
>pptc-announce-owner. From the headers (I may or may not be
>interpreting correctly), it looks like the message was directly
>addressed to pptc-announce-owner.
Yes. The spam was sent From: "Jeffrey Lyon" <[EMAIL PROTECT
On 7/11/06, Mark Sapiro <[EMAIL PROTECTED]> wrote:
> Is there a question here, or is this perhaps an off-list thread that
> sudddenly bacame public?
Not my doing, this time. It's as new to me as it is to you.
I think Harold is asking why the spam was directed to
pptc-announce-owner. From the head
Harold Goldstein wrote:
>here is the header of a spam received this morning by 2 of us listed as
>pptc-announce-owner ...
>it is not being directed to the list itself.
>i shouldmention that a month ago the list was spammed before i marked to
>discard unauthorized posts
Is there a question here
here is the header of a spam received this morning by 2 of us listed as
pptc-announce-owner ...
it is not being directed to the list itself.
i shouldmention that a month ago the list was spammed before i marked to
discard unauthorized posts
---
14 matches
Mail list logo
