On 10-Dec-2008, at 02:41, hofmae wrote:
I think the main problem is that there is one of our adressess in the
return-path. Thats wrong i think, because the spammer sends a
spammail with
one of our adressess in the return-path. The actualy spammail we
don't get
to see...
I think the main p
>>> support <[EMAIL PROTECTED]> 12/11/08 2:52 AM >>>
Prempting some responses:
What about external remote workers?
What about those who email stuff to themselves?
I hear this kind of thing all the time when people moan about spoofing.
On Wed, 2008-12-10 at 12:19 -0500, Kevin Parris wrote:
> You
Prempting some responses:
What about external remote workers?
What about those who email stuff to themselves?
I hear this kind of thing all the time when people moan about spoofing.
On Wed, 2008-12-10 at 12:19 -0500, Kevin Parris wrote:
> You do not have a SpamAssassin problem, you have a Commun
You do not have a SpamAssassin problem, you have a Communigate problem.
Present this issue to your support resources for that product.
The basics of what you want to do are something like this:
When a message is arriving from the internet, and has your own domain in the
Return-path, it should
hofmae a écrit :
> Hi,
>
> thanks a lot.
>
> but the didn't solve anything...
>
> We need the mailer daemon, we cannot just deactivate it.
>
> I think the main problem is that there is one of our adressess in the
> return-path. Thats wrong i think, because the spammer sends a spammail with
> on
sin&ie=utf-8&oe=utf-8&aq=t&rls=org.gentoo:da:official&client=firefox-a
>
> some links to more info
>
> --
> Benny Pedersen
> Need more webspace ? http://www.servage.net/?coupon=cust37098
>
>
>
--
View this message in context:
http://www.nabble.com/Problem-with-faked-return-path-or-something-like-that...%21-tp20925209p20931921.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
On Tue, December 9, 2008 23:37, hofmae wrote:
> i hope someone can help, i surfed the whole web with no answer...
problem is not the fake return path, its problem is that you bounce
invalid recipient, and the spammers know that
> We are using Communigate Pro with Spamassasin, now we have a prob
daemon, wo we
can't block that generally because we need it.
So the major problem is that the spammer is using faked return-path
adresses, and i really don't know how we can fix that problem.
Thanks for your help.
--
View this message in context:
http://www.nabble.com/Problem-with-
