Thanks for all of the discusison in my previous thread on spam generated by e-mail addresses included in websites. I gained a ton of information which I will be using on my site - attempting to "do it right the first time."
Unfortunately, the reason that discussion arose still exists: the website of the organization I volunteer for has generated TONS of spam. The address the spam is being sent to is actually an alias which is forwarded to five personal addresses. We are in the process of switching hosting providers and I am hoping to solve the spam issue while we're at it. Here's what I'm thinking of doing:
1. Set up a different alias as the organization's e-mail.
2. Use one of the encryption techniques mentioned in my previous thread to "protect" it on the website.
3. Send an e-mail to our mailing list informing people to look on the new webpage and make changes in their address books.
Now, here's where I need advice. It is very likely that some people have our old address in their address books and are not on our mailing list. I was thinking that I could set up an auto-responder for the old address on our new host with a pointer to the webpage with the new address. Then have the e-mail forwarded to a "fake" address (like [email protected]) which would then bounce back to the sender as invalid. However, would spammers take a look at the auto-response and then go look for the new (valid) address on our site or not? I'd like to point "real" people to the new address if at all possible without automatically setting up another spam-fest. (Right now we get 50-75 spams for every "real" request for info.)
Should I try to accomodate those "real people" who send a request to the old address, or will that just start the spam all over again at the new address? Any advice would be greatly appreciated!!
If anything isn't clear, please ask and I'll try to clarify.
Thanks, Jeanie
Unfortunately, the reason that discussion arose still exists: the website of the organization I volunteer for has generated TONS of spam. The address the spam is being sent to is actually an alias which is forwarded to five personal addresses. We are in the process of switching hosting providers and I am hoping to solve the spam issue while we're at it. Here's what I'm thinking of doing:
1. Set up a different alias as the organization's e-mail.
2. Use one of the encryption techniques mentioned in my previous thread to "protect" it on the website.
3. Send an e-mail to our mailing list informing people to look on the new webpage and make changes in their address books.
Now, here's where I need advice. It is very likely that some people have our old address in their address books and are not on our mailing list. I was thinking that I could set up an auto-responder for the old address on our new host with a pointer to the webpage with the new address. Then have the e-mail forwarded to a "fake" address (like [email protected]) which would then bounce back to the sender as invalid. However, would spammers take a look at the auto-response and then go look for the new (valid) address on our site or not? I'd like to point "real" people to the new address if at all possible without automatically setting up another spam-fest. (Right now we get 50-75 spams for every "real" request for info.)
Should I try to accomodate those "real people" who send a request to the old address, or will that just start the spam all over again at the new address? Any advice would be greatly appreciated!!
If anything isn't clear, please ask and I'll try to clarify.
Thanks, Jeanie
Comment