Re: Delivery to accounts of the same domain on two different servers

On 6 Jun 2017, at 17:27, Daniel wrote: Checking application/pgp-signature: FAILURE Here the signature is validated correctly with Thunderbird and Mutt. Maybe the client does not have the public key (ID 14E61D37) and so was not able to validate the signature? That key (long ID

Re: Delivery to accounts of the same domain on two different servers

Hi again, Wietse. On 06/06/17 18:27, Daniel wrote: I am gradually migrating the accounts of a server (let's say mail1.domain.com) to another server (let's say mail2.domain.com). In mail2.domain.com I'm using something like this:

Re: Delivery to accounts of the same domain on two different servers

On 06/06/17 17:44, Wietse Venema wrote: > Daniel: Hi, Wietse. What an honor to receive this response from you :) > Checking application/pgp-signature: FAILURE Here the signature is validated correctly with Thunderbird and Mutt. Maybe the client does not have the public key (ID 14E61D37) and

Re: Accept all mail on separate port

On 6/6/2017 3:21 PM, Andrea wrote: > Hi all. > > Due to the demise of the Sixxs project, which I was using to bypass the > ISP’s filtering of port 25 (in/out), I would like to open a "private" port > on postfix. > It’s a non-standard port and I will be filtering the src range at firewall > level

Re: Delivery to accounts of the same domain on two different servers

Daniel: Checking application/pgp-signature: FAILURE -- Start of PGP signed section. > Hi again. > > On 06/06/17 12:11, Daniel Bareiro wrote: > > > I am gradually migrating the accounts of a server (let's say > > mail1.domain.com) to another server (let's say mail2.domain.com). > > > > In

Accept all mail on separate port

Hi all. Due to the demise of the Sixxs project, which I was using to bypass the ISP’s filtering of port 25 (in/out), I would like to open a "private" port on postfix. It’s a non-standard port and I will be filtering the src range at firewall level so I’m pretty confident there will be no abuse. I

Re: Delivery to accounts of the same domain on two different servers

Hi again. On 06/06/17 12:11, Daniel Bareiro wrote: > I am gradually migrating the accounts of a server (let's say > mail1.domain.com) to another server (let's say mail2.domain.com). > > In mail2.domain.com I'm using something like this: > >

Re: Issue with SASL authentication

Hi all! Thanks to all who were interested and answered for this issue. I appreciate it. An update below. On 25/05/17 18:08, Andreas Schamanek wrote: > Hi Daniel, > > I wish I could help. I even compared your stuff with my setup and > re-read https://wiki.debian.org/PostfixAndSASL , Now I

Delivery to accounts of the same domain on two different servers

Hi all! I am gradually migrating the accounts of a server (let's say mail1.domain.com) to another server (let's say mail2.domain.com). In mail2.domain.com I'm using something like this: virtual_alias_domains = domain.com

Re: header_checks and custom header fails to trigger

On 06/06/17 03:20, rolelael wrote: > I understand , but .. > > /^route_gcgw: BE/ WARN Test > > is triggered now. Because that's a single-line test. Your other test is failing because if the /route_gcgw/ condition is triggered, you try to compare *the line that triggered it* against a

Re: telnet hangs when I enable sasl

On 06/06/17 05:08, Wietse Venema wrote: > It says: "yum install cyrus-sasl-plain". Nowadays one would use "dnf". CentOS 7 (being several years old now) still uses yum. Peter

Feature request: MX rollup

This is a followup of the following request: http://postfix.1071664.n5.nabble.com/Sending-rate-limiting-per-destination-MTA-not-recipient-domain-td87355.html The feature I am asking for is implemented in PowerMTA with the name "MX rollup":

Re: header_checks and custom header fails to trigger

I understand , but .. /^route_gcgw: BE/ WARN Test is triggered now. And is there any way with header_checks I can accomplish my if .. end if somehow . Or is it really limited and not suitable for what I'm looking to do ? -- View this message in context:

Re: header_checks and custom header fails to trigger

On 6 June 2017 at 07:49, rolelael wrote: > Hello > > It's me again and the header_checks is driving me crazy > > Mail comming from other mail system comes into postfix were header_checks > is > enabled > > The mail system adds a header : > > route_gcgw: BE > > This

header_checks and custom header fails to trigger

Hello It's me again and the header_checks is driving me crazy Mail comming from other mail system comes into postfix were header_checks is enabled The mail system adds a header : route_gcgw: BE This header is visible when the mail is received I have a header_checks file where 'again' the if