Re: header_checks to reject domain

On 3/6/2013 7:22 PM, LuKreme wrote: > /dev/rob0 opined on Wednesday 06-Mar-2013@17:26:02 >> On Wed, Mar 06, 2013 at 11:52:35AM -0700, LuKreme wrote: >>> The bad word begins with u and then is followed by n, s, u, b, an >>> archaic word meaning a person who is employed in writing, and then >>> a f

Re: header_checks to reject domain

/dev/rob0 opined on Wednesday 06-Mar-2013@17:26:02 > On Wed, Mar 06, 2013 at 11:52:35AM -0700, LuKreme wrote: >> The bad word begins with u and then is followed by n, s, u, b, an >> archaic word meaning a person who is employed in writing, and then >> a final d. >> >> u, n, s, u, b, >> scribe >

Re: header_checks to reject domain

On Wed, Mar 06, 2013 at 11:52:35AM -0700, LuKreme wrote: > The bad word begins with u and then is followed by n, s, u, b, an > archaic word meaning a person who is employed in writing, and then > a final d. > > u, n, s, u, b, > scribe > d Cute. :) > I [bad word] from a mailing list but the co

Re: Temporary lookup failure with relay_recipient_maps

On Wed, Mar 06, 2013 at 06:13:05PM +, lst_ho...@kwsoft.de wrote: > Zitat von Wietse Venema : > > >Postfix reports that the LDAP client library could not connect to > >any of the LDAP servers. Don't shoot the messenger. > > > > Wietse > > Would the "domain" parameter in the LDAP config pr

Re: Temporary lookup failure with relay_recipient_maps

Zitat von Wietse Venema : Alvaro Marin: For a moment, one ActiveDirectory server for some domains was down, so I've seen in logs: warning: dict_ldap_connect: Unable to bind to server ldap://IP1 ldap://IP2 as cn=x,ou=x,dc=x,dc=x: -1 (Can't contact LDAP server) ... Is anyway to configure Post

header_checks to reject domain

I tired to post this, but evidently having the word beginning with u and ending with d in the first line of the messages might be a problem, so I am trying to post again with that word NOT in the first line. Or the first paragraph. Nope. That did not work. Evidently the word is not allowed to ap

Re: Building el6 RPMs for v2.10

On 27/2/2013 10:38 μμ, Birta Levente wrote: I use it on 2 small servers in production. No problem here. Thank you, Following your experience, I built 2.10.0 RPMs based on S. J. Mudd's SRPMs (http://ftp.wl0.org/official/2.9/SRPMS/) for CentOS 6.3 x86_64 and I upgraded (until now) two serve

Re: Temporary lookup failure with relay_recipient_maps

Alvaro Marin: > For a moment, one ActiveDirectory server for some domains was down, so > I've seen in logs: > > warning: dict_ldap_connect: Unable to bind to server ldap://IP1 > ldap://IP2 as cn=x,ou=x,dc=x,dc=x: -1 (Can't contact LDAP server) ... > Is anyway to configure Postfix to avoid this s

Re: Temporary lookup failure with relay_recipient_maps

Am 06.03.2013 17:17, schrieb Alvaro Marin: > Hello, > > I've several Postfix servers configured to relay email for users/domains. > We've different LDAP servers to query and a cdb file; something like this: > > relay_recipient_maps = ldap:/etc/postfix/ldap_users.cf, > ldap:/etc/postfix/actived

Temporary lookup failure with relay_recipient_maps

Hello, I've several Postfix servers configured to relay email for users/domains. We've different LDAP servers to query and a cdb file; something like this: relay_recipient_maps = ldap:/etc/postfix/ldap_users.cf, ldap:/etc/postfix/activedirectory.cf, ldap:/etc/postfix/activedirectory2.cf, cdb:/

Re: ldap_table and insignificant spaces

Viktor Dukhovni: > On Tue, Mar 05, 2013 at 11:16:18PM -0500, Wietse Venema wrote: > > > Viktor Dukhovni: > > > Arguably, all lookup keys in tables should be in "external" (RFC-5322) > > > form. The suggested doubling of internal spaces is far less important > > > in practice that avoiding the loss

Re: Postfix 2.10 / haproxy 1.5-dev17 / proxy protocol

Laurent CARON: > When using the SSMTP port *and* send-proxy it fails. ... > Did I miss something obvious ? Yes. Unlike (port 25) smtp and (port 587) submission, the obsolete and deprecated ssmtp service has no plain-text phase before the TLS handshake. This means that an obsolete and deprecated s

Re: smtpd_relay_restrictions in 2.10.0

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 3/6/2013 4:19 AM, Reindl Harald wrote: > > > Am 06.03.2013 11:08, schrieb Nikolaos Milas: > >> I had a postfix 2.9.4 and upgraded to 2.10.0 (on CentOS 6.3 >> x86_64), building an RPM using Simon J. Mudd's SRPM (for >> v2.9.x). During installation

Postfix 2.10 / haproxy 1.5-dev17 / proxy protocol

Hi, I'm currently upgrading from postfix 2.9 to 2.10 with haproxy 1.5-dev17 So far, everythink works fine with: :/etc/haproxy/haproxy.cfg: frontend ft_smtps bind :465 mode tcp default_backend bk_smtps frontend ft_submission bind :587 mode tcp default_backend bk_submissi

Re: smtpd_relay_restrictions in 2.10.0

Am 06.03.2013 11:08, schrieb Nikolaos Milas: > I had a postfix 2.9.4 and upgraded to 2.10.0 (on CentOS 6.3 x86_64), building > an RPM using Simon J. Mudd's SRPM > (for v2.9.x). During installation, I got: > >warning: /etc/postfix/main.cf created as /etc/postfix/main.cf.rpmnew >warning:

smtpd_relay_restrictions in 2.10.0

Hello, I had a postfix 2.9.4 and upgraded to 2.10.0 (on CentOS 6.3 x86_64), building an RPM using Simon J. Mudd's SRPM (for v2.9.x). During installation, I got: warning: /etc/postfix/main.cf created as /etc/postfix/main.cf.rpmnew warning: /etc/postfix/master.cf created as /etc/postfix/m

Re: ldap_table and insignificant spaces

On Wed, Mar 06, 2013 at 03:51:28AM +, Viktor Dukhovni wrote: > On Fri, Mar 01, 2013 at 03:19:42PM +0100, Bastian Blank wrote: > > - The ldap server sanitices the query to (mail=t...@example.com) as > > mandated by RFC 4717, 4.2.3; it removes the insignificant space. > I see the "insignificant