Re: postmulti fatal error with 3.0.0

Andreas: > Am 2/18/2015 um 18:39 schrieb Viktor Dukhovni: > > With 3.0.0 Linux distributions should start using the upstream > > default. This does mean that users should remove explicit legacy > > default settings of daemon_directory from their main.cf files. > > Distribution package upgrades will

Re: postmulti fatal error with 3.0.0

Am 18.02.2015 um 19:59 schrieb Andreas: Am 2/18/2015 um 18:39 schrieb Viktor Dukhovni: With 3.0.0 Linux distributions should start using the upstream default. This does mean that users should remove explicit legacy default settings of daemon_directory from their main.cf files. Distribution pac

Re: postmulti fatal error with 3.0.0

Am 2/18/2015 um 18:39 schrieb Viktor Dukhovni: > With 3.0.0 Linux distributions should start using the upstream > default. This does mean that users should remove explicit legacy > default settings of daemon_directory from their main.cf files. > Distribution package upgrades will need to update or

Re: postmulti fatal error with 3.0.0

Viktor Dukhovni: > The upstream Postfix release defaults to > > daemon_directory = /usr/libexec/postfix > > on all but one system type (GNU0 Debian whatever that is), > and even that one should probably be changed to /usr/libexec. Postfix should have its own libexec subdirectory. Unlike comm

Re: Dovecot on a separate server as LDA

Thanks to everyone for your answers, I will try! Отправлено от Blue Mail На 21:49, 18.02.2015, в 21:49, Robert Schetterer написал:п>Am 18.02.2015 um 18:26 schrieb Орхан Ибад-оглы Гасымов: >> Good day! >> >> I need an advice about a simple (I guess) thing. >> When Postfix and Dovecot are runn

Re: Dovecot on a separate server as LDA

Am 18.02.2015 um 18:26 schrieb Орхан Ибад-оглы Гасымов: > Good day! > > I need an advice about a simple (I guess) thing. > When Postfix and Dovecot are running on the same machine, > then to specify Dovecot as LDA, I use this command in "main.cf > ": > > mailbox_command = /usr/loc

Re: 2.11.4: Error in post-install

On Wed, 18 Feb 2015, Wietse Venema wrote: That means we will need command output from the modified post-install script to find out what is going on. Wietse, As soon as I can. Rich

Re: postmulti fatal error with 3.0.0

On Wed, Feb 18, 2015 at 11:16:19AM +0100, Andreas wrote: > > This is something the distribution maintainers will have to figure > > out. If you are a distribution maintainer, please DO NOT apply > > the above patch unless it is first adopted upstream. > > Since, as you said, some distributions la

Re: 2.11.4: Error in post-install

Rich Shepard: > On Wed, 18 Feb 2015, Wietse Venema wrote: > > > Or y[o]u can send us the postfix-files file that Postfix 2.11.4 > > wants to install. > > $config_directory:d:root:-:755:u > Thanks. This is identical to the file as distributed from postfix.org. That means we will need command

Re: Dovecot on a separate server as LDA

Am 18.02.2015 um 18:26 schrieb Орхан Ибад-оглы Гасымов: I need an advice about a simple (I guess) thing. When Postfix and Dovecot are running on the same machine, then to specify Dovecot as LDA, I use this command in "main.cf ": mailbox_command = /usr/local/libexec/dovecot/dovec

Re: Dovecot on a separate server as LDA

? - ???: > Good day! > > I need an advice about a simple (I guess) thing. > When Postfix and Dovecot are running on the same machine, > then to specify Dovecot as LDA, I use this command in "main.cf": > > mailbox_command = /usr/local/libexec/dovecot/dovecot-lda -f "$SENDER" -a > "

Dovecot on a separate server as LDA

Good day! I need an advice about a simple (I guess) thing. When Postfix and Dovecot are running on the same machine, then to specify Dovecot as LDA, I use this command in "main.cf": mailbox_command = /usr/local/libexec/dovecot/dovecot-lda -f "$SENDER" -a "$RECIPIENT" But if Dovecot is running on

Re: 2.11.4: Error in post-install

On Wed, 18 Feb 2015, Wietse Venema wrote: Or y9u can send us the postfix-files file that Postfix 2.11.4 wants to install. $config_directory:d:root:-:755:u $data_directory:d:$mail_owner:-:700:uc $daemon_directory:d:root:-:755:u $queue_directory:d:root:-:755:uc $sample_directory:d:root:-:755:o $

Re: 2.11.4: Error in post-install

On Wed, Feb 18, 2015 at 11:18:10AM -0500, Wietse Venema wrote: > > diff --git a/conf/post-install b/conf/post-install > > index 7e79c92..35279d0 100644 > > --- a/conf/post-install > > +++ b/conf/post-install > > @@ -501,6 +501,7 @@ test -n "$create" && { > > # Flag obsolete objects. XXX So

Re: 2.11.4: Error in post-install

Viktor Dukhovni: > On Wed, Feb 18, 2015 at 07:32:38AM -0800, Rich Shepard wrote: > > On Wed, 18 Feb 2015, Wietse Venema wrote: > > > > >This suggests that you have a space in a pathname of some Postfix > > >configuration pathname parameters such as queue_directory, > > >command_directory, sendmail

Re: 2.11.4: Error in post-install

On Wed, 18 Feb 2015, Viktor Dukhovni wrote: This does not matter, the problem might come from somewhere else. You need to figure out why that particular path on line "504" is causing the problem. We can't do that for you. To do that, you need to edit the post-install shell script to log the obs

Re: 2.11.4: Error in post-install

On Wed, Feb 18, 2015 at 07:32:38AM -0800, Rich Shepard wrote: > On Wed, 18 Feb 2015, Wietse Venema wrote: > > >This suggests that you have a space in a pathname of some Postfix > >configuration pathname parameters such as queue_directory, > >command_directory, sendmail_path, and so on. > > Wietse

Re: 2.11.4: Error in post-install

On Wed, 18 Feb 2015, Wietse Venema wrote: This suggests that you have a space in a pathname of some Postfix configuration pathname parameters such as queue_directory, command_directory, sendmail_path, and so on. Wietse, Here are all directory paths from main.cf; I deleted all other lines:

Re: 2.11.4: Error in post-install

On Wed, Feb 18, 2015 at 07:23:50AM -0800, Rich Shepard wrote: > >Oops, I was looking at line 504 in the 3.0.0 source. Indeed in the above > >line 504, $path should be in quotes, though it if it needs quoting, > >appending it to "obsolete" still won't work right. > > Viktor, > > Only the first

Re: 2.11.4: Error in post-install

On Wed, 18 Feb 2015, Viktor Dukhovni wrote: Oops, I was looking at line 504 in the 3.0.0 source. Indeed in the above line 504, $path should be in quotes, though it if it needs quoting, appending it to "obsolete" still won't work right. Viktor, Only the first, unquoted $path needs the quote

Re: 2.11.4: Error in post-install

On Wed, 18 Feb 2015, Wietse Venema wrote: Just to be sure we are talking about the same thing, are you referring to the same line 504 that I have here: 501 # Flag obsolete objects. XXX Solaris 2..9 does not have "test -e". 502 if [ -n "$obsolete_flag" ] 503 then 504 test -r $path -a

Re: 2.11.4: Error in post-install

Wietse Venema: > Rich Shepard: > >When upgrading to -2.11.4 (on Slackware-14.1), a message is displayed > > that > > line 504 in /usr/libexec/postfix/post-install has too many arguments. Adding > > double quotes to $path fixes this problem. > > Maintainers sometimes make "improvements" and th

Re: 2.11.4: Error in post-install

On Wed, Feb 18, 2015 at 09:43:19AM -0500, Wietse Venema wrote: > Rich Shepard: > >When upgrading to -2.11.4 (on Slackware-14.1), a message is displayed > > that > > line 504 in /usr/libexec/postfix/post-install has too many arguments. Adding > > double quotes to $path fixes this problem. > >

RE: destination throttling state sharing

Marco, > Is there a way to share this kind of information between Postfix instances? > I would really if you could share your personal experience on how to deal in > general with a scenario like this. I've been using policyd for this, with a single MySQL backend. You can create a policy to matc

Re: 2.11.4: Error in post-install

Rich Shepard: >When upgrading to -2.11.4 (on Slackware-14.1), a message is displayed that > line 504 in /usr/libexec/postfix/post-install has too many arguments. Adding > double quotes to $path fixes this problem. Maintainers sometimes make "improvements" and that can change line numbers. Just

Re: Transitioning from cyrus-SASL to dovecot-SASL

On Wed, 18 Feb 2015, Viktor Dukhovni wrote: Sounds like nonsense to me. You can operate a port 587 submission service on a machine which routes outbound mail via a smarthost. Viktor, For my situation that's not worth my time and effort. You'll have to somehow deal with tracking the machin

Re: Transitioning from cyrus-SASL to dovecot-SASL [RESOLVED]

On Tue, 17 Feb 2015, Wietse Venema wrote: Dovecot has no client support. Server only. Wietse, Thank you. I'll stay with cyrus then. Much appreciated, Rich

Re: destination throttling state sharing

Hi Wietse, On Wed, Feb 18, 2015 at 1:23 PM, Wietse Venema wrote: > Marco Pizzoli: > > > Is there a way to share this kind of information between Postfix > instances? > > This is not implemented. Postfix by design can recover from a crash > in any program except the master daemon. I don't know h

Re: postmulti fatal error with 3.0.0

Andreas: > Since, as you said, some distributions lack /usr/libexec, wouldn't > it be a better idea to leave it up to the package/distribution > maintainers to separate shared objects from shared executables? That is not how Postfix works. With Postfix, things are forbidden unless explicitly permi

Re: destination throttling state sharing

Marco Pizzoli: > Hi all, > I have a battery of postfix servers used for sending bulk emails to the > Internet. > All of them are seen from the outside as they were one: > - same hostname > - same public IP address > > Considered that I have implemented the sending throttling for specific > destina

Re: postmulti fatal error with 3.0.0

Dear Viktor, sorry, i got your mail quite delayed... i can confirm this patch working, thank you! > IIRC the main reason for the conflict detection in question is to > avoid use of the shared directories also as per-instance directories. Which is a very good idea and prevents many configuration e

Re: using conditional other smtp

Am 18.02.2015 um 09:26 schrieb Gianluca Gargiulo: my postfix directly send email, but in some conditions based on *@domain-part* i'd like relay the email to another smtp server that require credentials based on sender. Can i configure postfix for this scenario? http://www.postfix.org/transport

using conditional other smtp

Hi, my postfix directly send email, but in some conditions based on @domain-part i'd like relay the email to another smtp server that require credentials based on sender. Can i configure postfix for this scenario? Thanks Ediconsul Informatica S.r.l. System Administrator Gianluc

destination throttling state sharing

Hi all, I have a battery of postfix servers used for sending bulk emails to the Internet. All of them are seen from the outside as they were one: - same hostname - same public IP address Considered that I have implemented the sending throttling for specific destinations in order to avoid "status=d