Re: limit and monitor too many sasl login from same user

2013-10-04 Thread nik600
i know, but if you have thousands of users you can't trust too much them. I know also that smtps,pop3s,imaps must be used but you can't change a production system. it's a long migration, and during this migration you need tools to stop spammers and broken accounts. then, when the world will be per

Re: limit and monitor too many sasl login from same user

2013-10-04 Thread Stan Hoeppner
On 10/4/2013 2:29 AM, nik600 wrote: > Virus, botnet and user's bad policies about password allows many 3rd party > entities to stole passwords, in the last month i've experienced a grows of > hacked users, and in some case many spam messages are sent from my servers > before i can block the user. >

Re: real postfix mail server (isp)

2013-10-04 Thread Viktor Dukhovni
On Fri, Oct 04, 2013 at 10:11:53PM +0200, Pol Hallen wrote: > After configurated postfix like isp mail server, do I need other things to > do a real mail server (from other ISP)? > > So, every real isp in the world can send to me same email? 42. If the above answer is not sufficiently specific,

real postfix mail server (isp)

2013-10-04 Thread Pol Hallen
Howdy :-) After configurated postfix like isp mail server, do I need other things to do a real mail server (from other ISP)? So, every real isp in the world can send to me same email? Thanks Pol

Re: postfix hardening - what can we do?

2013-10-04 Thread Viktor Dukhovni
On Fri, Oct 04, 2013 at 11:21:34AM -0400, micah wrote: > > By default the server picks the client's most preferred cipher that > > is also available on the server. You can set "tls_preempt_cipherlist > > = yes" to have the server use its most preferred cipher supported > > by the client. This co

Re: postfix hardening - what can we do?

2013-10-04 Thread micah
Viktor Dukhovni writes: >> but...the way this works: the server gets offered a list of ciphersuites >> from the client, and then the server picks a ciphersuite, so without >> knowing how the server picks its ciphersuites from the client, these >> results are not clear. > > By default the server p

Re: limit and monitor too many sasl login from same user

2013-10-04 Thread Wietse Venema
nik600: > Virus, botnet and user's bad policies about password allows many 3rd party > entities to stole passwords, in the last month i've experienced a grows of > hacked users, and in some case many spam messages are sent from my servers > before i can block the user. > > I've tried many combinat

Re: postfix hardening - what can we do?

2013-10-04 Thread li...@rhsoft.net
Am 04.10.2013 13:43, schrieb LuKreme: > On 03 Oct 2013, at 12:48 , micah wrote: >> Providing a TLS-wrapped, from the beginning, port is better than offering >> STARTTLS. > > No, it really isn’t. > > I’m not clear on what problem you ae trying to solve. You seem to want “mo > security” without

Re: postfix hardening - what can we do?

2013-10-04 Thread LuKreme
On 03 Oct 2013, at 12:48 , micah wrote: > Providing a TLS-wrapped, from the beginning, port is better than offering > STARTTLS. No, it really isn’t. I’m not clear on what problem you ae trying to solve. You seem to want “mo security” without any evidence that the current security is insufficie

Re: limit and monitor too many sasl login from same user

2013-10-04 Thread Jaco Lesch
Nik Maybe try a policy server, CBPolicyd works well and support SASL quotas. Have a look at http://www.policyd.org. Regards On 04/10/2013 09:29, nik600 wrote: Virus, botnet and user's bad policies about password allows many 3rd party entities to stole passwords, in the last month i've experi

limit and monitor too many sasl login from same user

2013-10-04 Thread nik600
Virus, botnet and user's bad policies about password allows many 3rd party entities to stole passwords, in the last month i've experienced a grows of hacked users, and in some case many spam messages are sent from my servers before i can block the user. I've tried many combination smtpd_client_me