Re: How to stop smtp servers to send us emails
- Hi Wietse,2012/12/7 Wietse Venema <wietse@...>
Pierre-Gilles RAYNAUD:Blogs are often wrong, or worse, they are incomplete (which is what> Hi Wietse,
> On 06/12/12 12:52, Wietse Venema wrote:
> > Pierre-Gilles RAYNAUD:
> >> /etc/postfix$ grep iglobe.be *
> >> client-blacklist:.iglobe.be REJECT 555 Spam not tolerated
> > Why do you have a '.' before the domain?
> > Where is this documented?
> > Wietse
> Found on many posts explaining how to build blacklist or whitelist for
> access restrictions (check_xxxx_access= hash:/yyyyy)
> I don't think it was on postfix website but due to the number of blogs,
> posts using this syntax notation to exclude a domain, I assume, wrongly
> it seems, that statistically, it couldn't be wrong :(
got you into trouble).
When configuring Postfix, you can save time and read the documentation
for the feature that you try to use.
I am not going to dictate here what you should do. RTFM instead.
Thank you for your time and answer.You are right when you are writting that blogs and posts may be incomplete and wrong, but this is not always the caseWithout any critics, the Postfix documentation is done by and for MTA experts, not unexperimented user like me.We (as a small company) have started to use Postfix because we were unhappy with the hosting solution we have been using during 10 years and when we decided to have our own mails server (we called it like this ;) ), we had to get knowledge on this matters and at the first beginning, some blogs were very helpfull when we awere in front a shell prompt in order to do.We have learnt a lot since day 1, reading blogs, posts and the Postfix documentation reference, and also by making mistakes like the one we have just did.By the way, in several months, perhaps we will be able to use to its full extend, some Postfix features we need in the emails area.This will only be possible because someone, You, has created an open source apllication like Postfix.Cheers--PGR
- Le 06/12/2012 06:22, Pierre-Gilles RAYNAUD a écrit :
> Hi Everyone,vy default, parent_domain_matches_subdomains contains
> On 01/12/12 18:19, Noel Jones wrote:
>> On 12/1/2012 11:11 AM, PGR wrote:
>>> Hi Everyone,
>>> I would like to know how to stop/forbid this server to send us their emails
>>> The content of received email is
>>> Received: from web-groupsolweb1.aquaray.com (unknown [188.8.131.52])
>>> by mail.domain.tld (Postfix) with ESMTP
>>> for <info@...>; Fri, 30 Nov 2012 00:56:49 +0100 (CET)
>>> Received: from PC-de-thib (184.108.40.206.rev.sfr.net [220.127.116.11])
>>> by web-groupsolweb1.aquaray.com (Postfix) with SMTP id E4515974A2C
>>> for <info@...>; Tue, 27 Nov 2012 03:59:06 +0100 (CET)
>>> The contain of mail.log
>>> Nov 30 00:56:49 serv001 postfix/smtpd: warning: 18.104.22.168:
>>> address not listed for hostname web-groupsolweb1.aquaray.com
>>> Nov 30 00:56:49 serv001 postfix/smtpd: connect from
>> Add a check_client_access map to reject them. Something like:
>> # main.cf
>> smtpd_client_restrictions =
>> check_client_access hash:/etc/postfix/client_blacklist
>> # client_blacklist
>> 22.214.171.124 REJECT listed in client blacklist
> Both have been done
> /etc/postfix$ grep iglobe.be *
> client-blacklist:.iglobe.be REJECT 555 Spam not tolerated
"smtpd_access_maps". this implies that you should use "iglobe.be"
without a dot.
my recommendation is: use two entries, one with a leadin dot and one
.iglobe.be REJECT ....
iglobe.be REJECT ...
This way, the domain is blocked whatever the value of
note that this check depends on DNS. you can add checks based on the IP
and in that file:
#reject 126.96.36.199 - 188.8.131.52
184.108.40.206/28 REJECT ...
# this doesn't include the IPs 220.127.116.11 - 18.104.22.168
# but that makes many "cidr blocks".
# if you feel a little angry, extend the block up to 22.214.171.124.
#126.96.36.199/27 REJECT ....
# if you are very angry, just block the /24.
> /etc/postfix$ grep client-blacklist *
> main.cf:smtpd_client_restrictions = permit_mynetworks,
> check_client_access hash:/etc/postfix/client-blacklist,
> reject_rbl_client dnsbl.sorbs.net, reject_rbl_client bl.spamcop.net,
> reject_rbl_client zen.spamhaus.org,reject_unknown_reverse_client_hostname
> and I'm still getting unwanted email (from iglobe.be in this example)
> Received: from paganini.iglobe.be (diegem.iglobe.be [188.8.131.52])
> by mail.domain.tld (Postfix) with ESMTP
> for <user@...>; Wed, 5 Dec 2012 12:51:37 +0100 (CET)
> Received: from pluto.be-housing.be (unknown [192.168.137.94])
> by paganini.iglobe.be (Postfix) with ESMTP id 69C6688B77
> for <user@...>; Wed, 5 Dec 2012 12:51:39 +0100 (CET)
> Received: from 184.108.40.206 (localhost [127.0.0.1])
> by pluto.be-housing.be (Postfix) with SMTP id 01744158023
> for <user@...>; Wed, 5 Dec 2012 12:51:36 +0100 (CET)
> Any suggestions on what is going on my configuration?