Re: Restricting port 25 with cidr table

2012-01-31 Thread Nikolaos Milas
On 26/1/2012 1:09 πμ, Charles Marcus wrote: However, we could formulate gwservers.cidr as (for example): > > xxx.xxx.xxx.xxx OK > xxx.xxx.xxx.xxx OK > 127.0.0.1 OK > :::::: OK > :::::OK > ::1

Re: Restricting port 25 with cidr table

2012-01-25 Thread Charles Marcus
On 1/21/2012 3:58 AM, Nikolaos Milas wrote: > However, we could formulate gwservers.cidr as (for example): > > xxx.xxx.xxx.xxx OK > xxx.xxx.xxx.xxx OK > 127.0.0.1 OK > :::::: OK > :::::OK > ::1

Re: Restricting port 25 with cidr table

2012-01-25 Thread Charles Marcus
On 1/20/2012 3:54 PM, Wietse Venema wrote: > On 20/1/2012 3:24 ??, Nikolaos Milas wrote: >> By the way, I fail to see any difference between the two methods. It >> seems to me the same to use: >>smtpd_client_restrictions = check_client_access >> cidr:/etc/postfix/gwservers.cidr >>where gw

Re: Restricting port 25 with cidr table

2012-01-21 Thread Nikolaos Milas
On 20/1/2012 10:54 μμ, Wietse Venema wrote: > seems to me the same to use: > smtpd_client_restrictions = check_client_access > cidr:/etc/postfix/gwservers.cidr > where gwservers.cidr is: > xxx.xxx.xxx.xxx OK > xxx.xxx.xxx.xxx OK > 0.0.0.0/0 reject unauthori

Re: Restricting port 25 with cidr table

2012-01-20 Thread Wietse Venema
Nikolaos Milas: [ Charset UTF-8 unsupported, converting... ] > On 20/1/2012 3:24 ??, Nikolaos Milas wrote: > > >> # reject all clients not matching anything above, and be damn sure > >> # to comment out the last reject under recipient_restrictions > >> # > >> 0.0.0.0/0 reject unauthorized

Re: Restricting port 25 with cidr table

2012-01-20 Thread Nikolaos Milas
On 20/1/2012 3:24 μμ, Nikolaos Milas wrote: # reject all clients not matching anything above, and be damn sure # to comment out the last reject under recipient_restrictions # 0.0.0.0/0 reject unauthorized client, please use our MX You mean to remove "reject" from *smtpd_client_restric

Re: Restricting port 25 with cidr table

2012-01-20 Thread Reindl Harald
Am 20.01.2012 11:55, schrieb Charles Marcus: >> why are you not only opening from the allowed addresses in >> the packet-filter (iptables)? so you have no log-entries >> from spammers all over the world and any protection should >> generally happen as wide as possible before the service > > I a

Re: Restricting port 25 with cidr table

2012-01-20 Thread Nikolaos Milas
On 20/1/2012 12:55 μμ, Charles Marcus wrote: # reject all clients not matching anything above, and be damn sure # to comment out the last reject under recipient_restrictions # 0.0.0.0/0 reject unauthorized client, please use our MX You mean to remove "reject" from *smtpd_client_restri

Re: Restricting port 25 with cidr table

2012-01-20 Thread Charles Marcus
On 2012-01-20 3:31 AM, Reindl Harald wrote: Am 20.01.2012 09:18, schrieb Nikolaos Milas: As our internal (main) mail server only accepts mail from two mail gateways and users submit their mail through submission port (587), I am planning to explicitly allow accepting mail on port 25 ONLY by our

Re: Restricting port 25 with cidr table

2012-01-20 Thread Reindl Harald
Am 20.01.2012 09:18, schrieb Nikolaos Milas: > Hello, > > As our internal (main) mail server only accepts mail from two mail gateways > and users submit their mail through > submission port (587), I am planning to explicitly allow accepting mail on > port 25 ONLY by our mail gateway servers >