Re: RFC: automatic backup of main.cf/master.cf before edit

2013-01-11 Thread Wietse Venema
Robert Moskowitz: > > On 01/10/2013 04:01 PM, Wietse Venema wrote: > > With the option to edit master.cf will come new opportunities > > to destroy a configuration. > > > > Below is a first design for a "backup before edit" option. If no > > command is configured, then no backup will be made. If

Learning how to quote shell commands

2013-01-11 Thread Wietse Venema
Robert Moskowitz: > cat <>master.cf || exit 1 > # > # Dovecot LDA > dovecot unix - n n - - pipe > flags=DRhu user=vmail:mail argv=/usr/libexec/dovecot/deliver -d ${recipient} > # > # Vacation mail > vacation unix - n n - - pipe > flags=Rq user=vacation argv=/var/spool/vacation/vacation.pl -f ${send

Re: Learning how to quote shell commands

2013-01-11 Thread Robert Moskowitz
On 01/11/2013 07:10 AM, Wietse Venema wrote: Robert Moskowitz: cat <>master.cf || exit 1 # # Dovecot LDA dovecot unix - n n - - pipe flags=DRhu user=vmail:mail argv=/usr/libexec/dovecot/deliver -d ${recipient} # # Vacation mail vacation unix - n n - - pipe flags=Rq user=vacation argv=/var/spool

Learning how to respecth REPLY-TO headers

2013-01-11 Thread Wietse Venema
Robert, please configure your mail reader to respect the REPLY-TO header. I have asked you this before, and I think I will ignore your email until you play by the same rules as everyone else. Wietse

Re: Learning how to respecth REPLY-TO headers

2013-01-11 Thread Robert Moskowitz
On 01/11/2013 09:07 AM, Wietse Venema wrote: Robert, please configure your mail reader to respect the REPLY-TO header. I have asked you this before, and I think I will ignore your email until you play by the same rules as everyone else. Sorry about that last transmission. Your request would b

Re: Learning how to respecth REPLY-TO headers

2013-01-11 Thread Wietse Venema
Robert Moskowitz: > > On 01/11/2013 09:07 AM, Wietse Venema wrote: > > Robert, please configure your mail reader to respect the REPLY-TO > > header. I have asked you this before, and I think I will ignore > > your email until you play by the same rules as everyone else. > > Sorry about that last

postfix permission denied outside of homedir

2013-01-11 Thread Vitaly Tskhovrebov
Hello. I have ubuntu 12.04 running postfix 2.9.1-4. I wrote a script to work with incoming emails to one of the address. Updated /etc/alias with something like email: "|/path/to/script 2> /path/to/log" I'm getting permission denied errors while it tries to open log for write. I disabled AppArmor

Re: postfix permission denied outside of homedir

2013-01-11 Thread Reindl Harald
Am 11.01.2013 17:07, schrieb Vitaly Tskhovrebov: > Hello. > > I have ubuntu 12.04 running postfix 2.9.1-4. > > I wrote a script to work with incoming emails to one of the address. Updated > /etc/alias with something like > email: "|/path/to/script 2> /path/to/log" > > I'm getting permission

Re: postfix permission denied outside of homedir

2013-01-11 Thread /dev/rob0
On Fri, Jan 11, 2013 at 11:07:47AM -0500, Vitaly Tskhovrebov wrote: > I have ubuntu 12.04 running postfix 2.9.1-4. > > I wrote a script to work with incoming emails to one of the address. > Updated /etc/alias with something like Was that "/etc/aliases"? Details do matter. Is /etc/aliases owned by

Re: postfix permission denied outside of homedir

2013-01-11 Thread Wietse Venema
Vitaly Tskhovrebov: > Excerpt from log: > Command died with status 2: > "/path/to/script 2>>/path/to/log". Command output: > sh: 1: cannot create /path/to/log: Permission denied According to the local(8) manpage: DELIVERY RIGHTS Deliveries to external files and external commands ar

postfix permission denied outside of homedir

2013-01-11 Thread Vitaly Tskhovrebov
default_privs definitely helped, thanks everyone!

Naming a master.cf attribute (RFC: postconf user interface)

2013-01-11 Thread Wietse Venema
Viktor Dukhovni: > The only part that is tricky is the "command + args" column, where > users arguably may want to add/delete "-o" flags, but in general > the various "-o" flags one may want to add are not necessarily > othogonal, and it is not always safe to add such a setting while > unware of it

catchall for one domain versus virtual domains

2013-01-11 Thread mosha
Hi, I'm operating a very small mail server and am having trouble getting 2 apparantly antagonistic behaviours to work. The server is responsible for domainA.org and domain1...domain5.org. I want all mail to domainA to be sent to a catchall address/local user and I also want domain1-5 to act as

Re: Naming a master.cf attribute (RFC: postconf user interface)

2013-01-11 Thread Viktor Dukhovni
On Fri, Jan 11, 2013 at 03:47:41PM -0500, Wietse Venema wrote: > If the concerns with '=' and '.' in service names can be overcome, > then the mouss syntax would simplify the user interface to query > or update a master.cf attribute. Neither is actually a problem provided we use "strrchr" to find

Re: catchall for one domain versus virtual domains

2013-01-11 Thread Noel Jones
On 1/11/2013 3:48 PM, mo...@arcor.de wrote: > Hi, > > I'm operating a very small mail server and am having trouble getting 2 > apparantly antagonistic behaviours to work. > > The server is responsible for domainA.org and domain1...domain5.org. > > I want all mail to domainA to be sent to a catc

Re: Re: catchall for one domain versus virtual domains

2013-01-11 Thread mosha
> On 1/11/2013 3:48 PM, mo...@arcor.de wrote: > > Hi, > > > > I'm operating a very small mail server and am having trouble getting 2 > apparantly antagonistic behaviours to work. > > > > The server is responsible for domainA.org and domain1...domain5.org. > > > > I want all mail to domainA to be

Re: catchall for one domain versus virtual domains

2013-01-11 Thread Noel Jones
On 1/11/2013 5:07 PM, mo...@arcor.de wrote: >> >> Use a fully-qualified domain for the result, such as >> @domainA catch...@localhost.domaina.org > > this was working fine so no change needed, changed it anyway for good measure. > >> p...@domain3.org u...@localhost.domaina.org > > changed thi

Re: catchall for one domain versus virtual domains

2013-01-11 Thread Reindl Harald
Am 12.01.2013 00:07, schrieb mo...@arcor.de: >> Please note that catchall addresses are evil and strongly discouraged. > > Whys that? Im the only recipient of all mail directed at domainA.org (so no > "spying") and as such can use websiteisignedupw...@domaina.org so I can > always tell which s

Re: Re: catchall for one domain versus virtual domains

2013-01-11 Thread mosha
> On 1/11/2013 5:07 PM, mo...@arcor.de wrote: > > >> > >> Use a fully-qualified domain for the result, such as > >> @domainA catch...@localhost.domaina.org > > > > this was working fine so no change needed, changed it anyway for good > measure. > > > >> p...@domain3.org u...@localhost.dom

Re: Naming a master.cf attribute (RFC: postconf user interface)

2013-01-11 Thread Wietse Venema
Viktor Dukhovni: > On Fri, Jan 11, 2013 at 03:47:41PM -0500, Wietse Venema wrote: > > > If the concerns with '=' and '.' in service names can be overcome, > > then the mouss syntax would simplify the user interface to query > > or update a master.cf attribute. > > Neither is actually a problem pr

Re: catchall for one domain versus virtual domains

2013-01-11 Thread Reindl Harald
Am 12.01.2013 01:50, schrieb mo...@arcor.de: > From another reply from a different person: >> hopefully you NEVER bounce because an internal error > I don't see the difference between catchall and not-catchall for this. if > postfix accepts a mail which then bounces with dovecot for... say quota

Re: catchall for one domain versus virtual domains

2013-01-11 Thread Reindl Harald
Am 12.01.2013 01:50, schrieb mo...@arcor.de: > found the section about chroot, remembered I had that turned on for some > parts > turned them all of for testing. :x, postfix reload > went for coffee (mainly saying this because there was a 5 minute break here) > came back tried again (as before

Re: Learning how to respecth REPLY-TO headers

2013-01-11 Thread Richard Damon
On 1/11/13 9:51 AM, Wietse Venema wrote: > Robert Moskowitz: >> On 01/11/2013 09:07 AM, Wietse Venema wrote: >>> Robert, please configure your mail reader to respect the REPLY-TO >>> header. I have asked you this before, and I think I will ignore >>> your email until you play by the same rules as e