Re: Mitigating DROWN

2016-03-09 Thread Marc Patermann
Am 03.03.2016 um 19:29 Uhr schrieb Viktor Dukhovni: Postfix 2.6 and later, with the recommended settings is sufficient, but it is recommended that you also deploy OpenSSL 1.0.1s or 1.0.2g, or your O/S vendor's "equivalent" update. It is sadly common to selectively backport fixes without changing

Re: Mitigating DROWN

2016-03-03 Thread Marc Patermann
Viktor, Am 01.03.2016 um 18:16 Uhr schrieb Viktor Dukhovni: Some of the servers that expose TLS to cross-protocol DROWN attacks via SSLv2 are MTAs running Postfix. If you're using an older Postfix release (released prior to July 20 2015), or you've explicitly configured TLS settings that may ha

Re: result_attribute on ldap query

2009-02-09 Thread Marc Patermann
Hi, Manuel Mely schrieb: query_filter = (&(&(objectClass=VirtualMailAccount)(mail=%s))(permitFrom=inet)(accountActive=TRUE)(delete=FALSE)) result_attribute = final version = 3 "final" is the name of a postfix class, and i have the same attribute for all my users, Do you mean, all values of

Re: Replacing Message-Id for SASL authenticated senders

2009-02-09 Thread Marc Patermann
Hi, Bastian Blank schrieb: On Sun, Feb 08, 2009 at 03:38:22AM -0500, Sahil Tandon wrote: This works as I'd expect, but will it break anything else? Yes. It will break the complete mail handling of the client. _Never_ ever touch a message id. Not all users are dumb. ;) Sender: I'm mi

Re: Relay when user is unknown

2008-09-25 Thread Marc Patermann
Hi! Blaise Hurtlin schrieb: I'm migrating my mail system from an old, buggy, Groupwise system to Postfix. The migration will take several month as I can't migrate all users at the same time. I want the following behaviour: all migrated users use the Postfix to send mails. On Postfix, if the u