habibie wrote:What exactly does the EATEN option do? Does it take the incoming spam e-mails and send them to /dev/null or reject them?
That's really bad because spammers won't know and keep sending spam e-mails to waste (Internet) resources.gourmet wrote:Normally when email gets eaten it's sent to /dev/null, sender is not notified.habibie wrote:What exactly does the EATEN option do? Does it take the incoming spam e-mails and send them to /dev/null or reject them?
habibie wrote:gourmet wrote:That's really bad because spammers won't know and keep sending spam e-mails to waste (Internet) resources.
Honestly, I don't see it. In order for the spam e-mails to be eaten by SG, they must have been arrived @SG MTA server to waste SG's Internet bandwidth. If SG rejects the spam e-mails, then the only wasted bandwidth is the rejection messages sent to spammer MTA server from SG. So, why waste resources to eat the spam e-mails, if SG can be configured just to reject the spam e-mails (which doesn't take any resources but to reject), AFAICT.gourmet wrote:I strongly disagree with what you said above even though I had that thought before.habibie wrote:Real spammers won't ever care about bounces, so that point isn't valid anyway.gourmet wrote:That's really bad because spammers won't know and keep sending spam e-mails to waste (Internet) resources.
While lurking through the Internet a few years ago, I discovered someone mentioned on how to fight spammers using a dynamic DNS with a local MTA, i.e. sendmail. So, I went ahead to implement such a scheme bysetting up my own e-mail address using a BSD SendMail on my Linux machine with a DynDNS service. This way, I could easily expose my e-mail address to spammers using an FQDN instead of an IP Address. Immediately, I started to get 100+ spam e-mails/hour on my Linux machine. Then, I login into my DnyDNS account and configure my FQDN so that it pointed to 127.0.0.1. I left this setting for a couple of days then reverted back to my IP Address to find out no more incoming spam e-mails. I bet you the admin of such spammers MTA were overwhelmed by a round-robbin bouncing e-mails! If spammers could careless about bounced e-mails, then why my Linux machine no longer received spam e-mails once I reactivated them from a few days of redirection to 127.0.0.1? This also happens with my disposable e-mail addresses from my EndJunk account. Once I reactivated (enabled) after a few days of being disabled, no more incoming spam e-mails.Also these legimate messages keep using SG's bandwidth, even messages won't be forwarded.
habibie wrote:Immediately, I started to get 100+ spam e-mails/hour on my Linux machine. Then, I login into my DnyDNS account and configure my FQDN so that it pointed to 127.0.0.1. I left this setting for a couple of days then reverted back to my IP Address to find out no more incoming spam e-mails.
habibie wrote:So, why waste resources to eat the spam e-mails, if SG can be configured just to reject the spam e-mails (which doesn't take any resources but to reject), AFAICT.
josh wrote:It's open sourcehabibie wrote:At any rate, SpamGourmet services seem to deliver its promise. I just wish SpamGourmet will add an option to bounce incoming spam e-mails so that those who run their own SpamGourmet system can take advantages of it.
Users browsing this forum: Google [Bot] and 108 guests