Re: transport table ignored

On Mon, Aug 29, 2016 at 4:53 PM, Noel Jones wrote: > On 8/29/2016 12:17 PM, Jared Brokaw wrote: > > > > > > > I don't want any recipient address checking or validation or > > > > In that case you should not be using Postfix. > > > > > > I meant I do not necessarily need/want recipient val

Re: Trouble relaying email from Dovecot through postfix to another mail server after putting in client restrictions

On 8/29/2016 11:34 AM, Scott W. Sander wrote: > Here is the exact error message that is received by the mail client: We prefer postfix log messages rather than messages from a mail client that may have been altered. > > --- > > Server error: '554 5.7.1 [10.10.10

Re: transport table ignored

On 8/29/2016 12:17 PM, Jared Brokaw wrote: > > > > I don't want any recipient address checking or validation or > > In that case you should not be using Postfix. > > > I meant I do not necessarily need/want recipient validation on the > relay, just on the final destination for the time

Re: Postfix stable release 3.1.2 and legacy release 3.0.6

Quanah Gibson-Mount: > --On Monday, August 29, 2016 10:40 AM -0400 Wietse Venema > wrote: > > > [An on-line version of this announcement will be available at > > http://www.postfix.org/announcements/postfix-3.1.2.html] > > Are there any plans to add the 20160730-postscreen patch to future 2.11.

Re: transport table ignored

On Mon, Aug 29, 2016 at 7:39 AM, Wietse Venema wrote: > JB: > > I keep getting: "Recipient address rejected: User unknown in > table>" where depends on my configuration and I have > > tried many. > > You need to read http://www.postfix.org/ADDRESS_CLASS_README.html > which explains exactly what

Trouble relaying email from Dovecot through postfix to another mail server after putting in client restrictions

I set up a internal postfix + dovecot server running on Ubuntu 14.04.5 a few months ago. I used the guide at the following link in order to get it set up: http://www.binarytides.com/install-postfix-dovecot-debian/ Just last week, I noticed that the server was accepting mail from basically anythi

Re: collate.pl

On Mon, Aug 29, 2016 at 09:36:44AM -0400, Wietse Venema wrote: > Robert Dahlem: > > Because it does no harm to anything existing I propose that attached > > patch gets into the distribution. > > It works with multi-instance names. What is the result for the stock > master.cf file, which has entri

Re: Postfix stable release 3.1.2 and legacy release 3.0.6

--On Monday, August 29, 2016 10:40 AM -0400 Wietse Venema wrote: [An on-line version of this announcement will be available at http://www.postfix.org/announcements/postfix-3.1.2.html] Are there any plans to add the 20160730-postscreen patch to future 2.11.x and 3.x releases? Thanks, Quana

Re: collate.pl

Hi, On 29.08.2016 16:41, Robert Dahlem wrote: > There is a potential problem with multiple instances: $syslog_name > defaults to $multi_instance_name. You need to pay attention to change > this in /etc/postfix-sec/master.cf too. > > Unfortunately, /dev/rob0's proposol to use > "syslog_name=$sysl

Re: collate.pl

/dev/rob0: > On Mon, Aug 29, 2016 at 09:36:44AM -0400, Wietse Venema wrote: > > Robert Dahlem: > > > Because it does no harm to anything existing I propose that > > > attached patch gets into the distribution. > > > > It works with multi-instance names. What is the result for the > > stock maste

Re: collate.pl

Hi, On 29.08.2016 15:36, Wietse Venema wrote: >> Because it does no harm to anything existing I propose that attached >> patch gets into the distribution. > It works with multi-instance names. What is the result for the stock > master.cf file, which has entries as shown below? > > submissio

Re: collate.pl

On Mon, Aug 29, 2016 at 09:36:44AM -0400, Wietse Venema wrote: > Robert Dahlem: > > Because it does no harm to anything existing I propose that > > attached patch gets into the distribution. > > It works with multi-instance names. What is the result for the > stock master.cf file, which has entr

Postfix stable release 3.1.2 and legacy release 3.0.6

[An on-line version of this announcement will be available at http://www.postfix.org/announcements/postfix-3.1.2.html] Postfix stable release 3.1.2 is available, as well as legacy release 3.0.6. Fixed with Postfix 3.1.2: * Changes to make Postfix build with OpenSSL 1.1.0. Fixed with Postfix 3

Re: transport table ignored

JB: > I keep getting: "Recipient address rejected: User unknown in table>" where depends on my configuration and I have > tried many. You need to read http://www.postfix.org/ADDRESS_CLASS_README.html which explains exactly what causes that error message. > I don't want any recipient address ch

Re: collate.pl

Robert Dahlem: > Because it does no harm to anything existing I propose that attached > patch gets into the distribution. It works with multi-instance names. What is the result for the stock master.cf file, which has entries as shown below? submission inet n - n - -

Re: collate.pl

Hi, On 23.08.2016 18:44, Viktor Dukhovni wrote: > A more general approach may be to replace "_slow" with "/slow" and > ignore any additional / delimited components between the instance > name and the program name. That would require you to set a syslog_name > along the lines of postfix-sec/slow

transport table ignored

Hello to all you postfix gurus. I'm running into a nasty problem (at least for me.) I would be grateful for any help with this. I have a setup with postfix that receives mail for a number of virtual domains, runs it through spam checks, and reinjects it back into post fix for final delivery. O