Hi mouss,
thank you for advise.
but i will not use  :
        reject_invalid_helo_hostname
 reject_non_fqdn_helo_hostname

because a lot of our
clients customer or their friend was rejected because of their mail server
not passed invalid helo hostname and non fqdn.


> Marky
Yehezkiel (SNC) a écrit :
>> Hi all,
>>
>> I have problem with spam that pretending me ( using my account
email )
>> to send spam (Viagra etc ) to my self,
>>
>> I have tested to
http://verify.abuse.net/cgi-bin/relaytest ,
>>
http://www.spamhelp.org/shopenrelay/shopenrelaytest.php
>>
>> and
>>
http://www.antispam-ufrj.pads.ufrj.br/cgi-bin/test-relay.cgi?host_to_test=203.80.8.42
>>
>>
>>
>>
>> result
was my mail server is not open relay.
>>
>> Here is
one of header email that spam pretending as my self to send
>>
email to me :
>>
>>
>>
>>
Received: from smtp.satnetcom.com ([127.0.0.1])
>>
>>                 by localhost (smtp.satnetcom.com
[127.0.0.1])
>> (amavisd-new, port 10024)
>>
>>                 with ESMTP id nYW-uhh-ygdz for
<ma...@satnetcom.com>;
>>
>>                
Fri, 12 Dec 2008 13:04:31 +0800 (CIT)
>>
>>
Received: from amc.bn.to (unknown [85.132.106.26])
> 
>
the IP is listed in zen.spamhaus.org (among other lists).
> 
>> [snip]
>>
>> And also I tested to mail
server of one from this member milis and it
>> was sent ( I do
apologize that I dare to test it ) .
>>
> 
> No
problem, but next time put an explicit message saying who is testing
> what.
> 
> your test mail was successfully
delivered. Up so far, I didn't find the
> need to block mail
forging my address.
> 
>> My question is, is there any
way to stop this problem ? one of method
>> that I know is SPF
but consequence is we have to
>>
>> Use smtp auth
(sasl) to use it if we are not at our network.
>>
>>
>>
>> Please advise from you all if there
is any way to stop this. Thank you
>>
> 
>
start by using
>       reject_invalid_helo_hostname
>
        reject_non_fqdn_helo_hostname
>       reject_rbl_client
zen.spamhaus.org
> 
> only try other approaches if this is
not enough.
>

Reply via email to