Re: Unmeant update from 2.2.10 to 2.5.1

6 msg	DSN relay host
1 msg	Restrict sender and from to one domain on outbo...
10 msg	Outbound postfix routing issue
25 msg	Problem with Black List
3 msg	Looking at new mail server layout
26 msg	why every minute: 'reload configuration /etc/po...
2 msg	myhostname parameter
17 msg	RBL problems with smarthost on private address ...
34 msg	Backscatting filter?
3 msg	how to setup postfix in 'deliver-only' mode?
7 msg	Slow queue configuration
17 msg	Some Windows SMTP Server have problems with STA...
5 msg	For each check_ns or each check_mx, the value i...
4 msg	postfix and spf
2 msg	Password Validation in postfix
4 msg	catching some spam with warn_if_reject and reje...
9 msg	RFC: Check mail quota at a mail relay (backscat...
31 msg	GPS vs GLD (greylisting)

Unmeant update from 2.2.10 to 2.5.1
\ Jens Mueller (5 May 2008)
. \ mouss (5 May 2008)
. \ (Wietse Venema) (5 May 2008)

27 msg	mailq lockups

Subject:	Re: Unmeant update from 2.2.10 to 2.5.1
Group:	Postfix-users
From:	(Wietse Venema)
Date:	5 May 2008

Jens Mueller:
> May_ 5 17:41:28 vinola1 postfix/pipe[1739]: fatal: user= command-line
> attribute specifies mail system postdrop group id 112

As documented, you MUST NOT use the postfix user and group IDs
for non-postfix commands.

Specifically, in master.cf, you MUST NOT specify a "user=xxx"
attribute that has the group ID of the postdrop group.

Wietse