On 10/19/2010 9:17 PM, Steve Jenkins wrote:
Thanks for the reply.
Forcing everyone to just check their mail with POP/IMAP was actually what I
was going to resort to if I couldn't figure out a way to do this with just
Postfix config settings. It seems that unless I want to manage a SPAM filter
on my server for everyone (which is not something I want to do) then that's
what I'm going to have to do.
So unless anyone sees anything glaring that I'm doing wrong from my postconf
-n, that's probably what I'm going to end up doing.
Thanks,
SteveJ
-----Original Message-----
From: owner-postfix-us...@postfix.org
[mailto:owner-postfix-us...@postfix.org] On Behalf Of pf at alt-ctrl-del.org
Sent: Tuesday, October 19, 2010 8:04 AM
To: postfix-users@postfix.org
Subject: Re: Fighting Backscatter
On 2010-10-18 9:58 PM, Steve Jenkins wrote:
The instructions at http://www.postfix.org/BACKSCATTER_README.html
seem to only address what to do if MY server is the one being
forged. In the above example, it seems that procom.ca is being
forged. How should I configure my Postfix installation so that I'm
not sending the spam back to the innocent sender? Let me know if you
need me to post my postconf -n again.
"Charles Marcus" October 19, 2010 7:38 AM:
As has been told to you more than once, the correct solution is simple...
1. Stop forwarding spam, or
2. Do not forward *any* emails, period.
The OP can actually do #2. He probably doesn't need to forward any email at
all.
gmail, yahoo, comcast all support POP3'ing third party email accounts,
straight to the mailbox.
Automatic POP3 retrieval...
No forwarding, no bounces.
But I'm not sure about cox support for auto POP3 retrieval.
I don't know if anyone has looked at this or not but you didn't provide
your master.cf. I was told by the dovecot list the other day to add a
"-e" in my master.cf to prevent backscatter, which I wasn't having any
problem with, as a safety precaution. My current dovecot transport in
master.cf is:
dovecot unix - n n - - pipe
flags=DRhu user=mail:mail argv=/usr/libexec/dovecot/deliver
/*-e */-f ${sender} -d ${us...@${nexthop} -m ${extension}
It doesnt matter where you put the -e as long as it is after the
"argv=/usr/libexec/dovecot/deliver" and not between other parameter
definitions.
Jerrale G.
SC Senior Admin
