I believe using the "reply_to = $LIST" setting will help this. Be worried
though, that if this address gets in a spammer's hands that you have road
blocks in place so they can not post to your list directly or indirectly.
This setting will replace any reply-to: already in the headers with the
address of the list. It doesn't do anything with the From: headers though.
Even purge_received cannot help you there.
Dan Liston
"St - Musaic.Net" wrote:
>
> Hi!
>
> Is there any way to have Majordomo to hide the posters address when sending
> to a list? I have clear evidences that some of the very established "Free
> Email Address Here" ISP's use some kind of email extractors on all incoming
> and outgoing mail - thus, when a member post from me@isp1.com, he or she
> might soon find their address spammed if ISP2.COM had a 'candid camera'
> directed to incoming mail of me@isp2.com
>
> One scum company which uses this scheme is http://www.aggies.com They post
> with bogus Compuserve addresses, but love to see the replies sent to
> addresses @aggies.com (which abuse@aggies.com never will close...) (btw,
> I know how to read headers... ;)
>
> I set up an address with just one purpose: To see whether it was extracted.
> I sent email to a bogus @aggies.org address - and lo and behold! Some days
> later, the address received a nice "Turn your e-mail into a virtual cash
> register!" spam. Well, before I get carried on... Is there any way to have
> Majordomo to hide the posters address when sending to a list? I do consider
> to set subscribe_policy to closed, so that I can investigate when users
> with addresses like bob@webopportunity.net or betty@targetshop.com wants
> to be added to a list...
>
> / St
References:
|
|
