On Sun, 28 Jan 2018, Wietse Venema wrote:
Please tell the maintainer that it they need to run the command, not the
user.
Wietse,
I'll do this.
Thanks,
Rich
Rich Shepard:
> On Sun, 28 Jan 2018, Wietse Venema wrote:
>
> > You're not supposed to chown the files. That is part of the Postfix
> > installation/upgrade process. If you use some non-Postfix
> > installation/upgrade procedure, then that is broken.
>
> Wietse,
>
>Next upgrade I'll run the
On Sun, 28 Jan 2018, Wietse Venema wrote:
You're not supposed to chown the files. That is part of the Postfix
installation/upgrade process. If you use some non-Postfix
installation/upgrade procedure, then that is broken.
Wietse,
Next upgrade I'll run the set-permissions script.
Thanks,
Ri
On Sun, 28 Jan 2018, Viktor Dukhovni wrote:
When upgrading from an older postfix version, make sure the variables such as
html_directory and readme_directory in /etc/postfix/main.cf point to the new
location. These can also be fixed later, afterwards make sure to run:
postfix set-per
> On Jan 28, 2018, at 2:41 PM, Rich Shepard wrote:
>
> I use the SlackBuilds.org build script (as I do for all my installations
> and upgrades).
Please file a bug report for the build scripts in question. When it installs
Postfix, it should run "postfix set-permissions" and perform some equiv
Rich Shepard:
>postdrop still is a group. What I had neglected in my post-installation
> notes was to change the group to postdrop for those two scripts prior to
> running set-gid on them.
You're not supposed to chown the files. That is part of the
Postfix installation/upgrade process. If you
On Sun, 28 Jan 2018, Viktor Dukhovni wrote:
Note that "make; make upgrade" would normally take care of this, perhaps
you're doing something else (needlessly complicated)?
Viktor,
I use the SlackBuilds.org build script (as I do for all my installations
and upgrades).
Also see:
http://www
> On Jan 28, 2018, at 2:08 PM, Rich Shepard wrote:
>
> On Sun, 28 Jan 2018, Viktor Dukhovni wrote:
>
>> # postfix set-permissions upgrade-configuration
Note that "make; make upgrade" would normally take care of this, perhaps you're
doing something else (needlessly complicated)?
> I thought t
Viktor Dukhovni:
>
>
> > On Jan 28, 2018, at 10:52 AM, Wietse Venema wrote:
> >
> > This announcement concerns fixes for problems that were introduced
> > with Postfix 2.1 and later, and updates the Postfix 3.2 license.
> >
> > License update: starting with Postfix 3.2.5, Postfix 3.2 is distr
On Sun, 28 Jan 2018, Viktor Dukhovni wrote:
# postfix set-permissions upgrade-configuration
Viktor,
I thought there was a procedure for post-upgrade configuration but had
forgotten where I had seen it.
Thanks very much for the information. It now resides where I'll see it
(and use it) f
> On Jan 28, 2018, at 1:11 PM, Rich Shepard wrote:
>
> I just upgraded from 3.2.4 to 3.2.5 and ensured that /usr/sbin/postdrop
> and /usr/sbin/postqueue were set gid:
>
> -rwxr-sr-x 1 root root 13888 Jan 28 08:58 /usr/sbin/postdrop*
> -rwxr-sr-x 1 root root 18012 Jan 28 08:58 /usr/sbin/post
> On Jan 28, 2018, at 10:52 AM, Wietse Venema wrote:
>
> This announcement concerns fixes for problems that were introduced
> with Postfix 2.1 and later, and updates the Postfix 3.2 license.
>
> License update: starting with Postfix 3.2.5, Postfix 3.2 is distributed
> with a dual license: in
On Sun, 28 Jan 2018, robert.wo...@robertwolfe.org wrote:
I would first check and see if group "postdrop" exists. Then, if so, I
would recommend running a "chown root:postdrop" on these files. But, of
course, YMMV.
Robert,
postdrop still is a group. What I had neglected in my post-installati
I would first check and see if group "postdrop" exists. Then, if so, I
would recommend running a "chown root:postdrop" on these files. But, of
course, YMMV.
-Original Message-
From: owner-postfix-us...@postfix.org
[mailto:owner-postfix-us...@postfix.org] On Behalf Of Rich Shepard
Sent: S
I just upgraded from 3.2.4 to 3.2.5 and ensured that /usr/sbin/postdrop
and /usr/sbin/postqueue were set gid:
-rwxr-sr-x 1 root root 13888 Jan 28 08:58 /usr/sbin/postdrop*
-rwxr-sr-x 1 root root 18012 Jan 28 08:58 /usr/sbin/postqueue*
Yet, when I start postfix I see these messages:
Jan 28
https://github.com/stevejenkins/hardwarefreak.com-fqrdns.pcre
check_client_access hash:/etc/postfix/whitelist
check_reverse_client_hostname_access pcre:/etc/postfix/fqrdns.pcre
On Sun, January 28, 2018 7:00 am, Noel Jones wrote:
So generally, you can put it anywhere after
reject_unauth_destin
[An on-line version of this announcement will be available at
http://www.postfix.org/announcements/postfix-3.2.5.html]
This announcement concerns fixes for problems that were introduced
with Postfix 2.1 and later, and updates the Postfix 3.2 license.
License update: starting with Postfix 3.2.5,
On Sun, January 28, 2018 7:00 am, Noel Jones wrote:
>>> https://github.com/stevejenkins/hardwarefreak.com-fqrdns.pcre
>> check_client_access hash:/etc/postfix/whitelist
>> check_reverse_client_hostname_access pcre:/etc/postfix/fqrdns.pcre
> So generally, you can put it anywhere after
> reject_una
On 01/28/2018 12:04 PM, Karol Augustin wrote:
On 2018-01-28 9:25, CP wrote:
on 01/27/2018 09:30 PM, Karol Augustin wrote:
With Message-ID header and dovecot lmtp (I think lda works also) you
eliminate (a lot!!) of these duplicates so try it if you have the same
problem.
In my case I have a robo
On 2018-01-28 9:25, CP wrote:
> on 01/27/2018 09:30 PM, Karol Augustin wrote:
>
> With Message-ID header and dovecot lmtp (I think lda works also) you
> eliminate (a lot!!) of these duplicates so try it if you have the same
> problem.
> In my case I have a robot account which sends (from LAN) e
on 01/27/2018 09:30 PM, Karol Augustin wrote:
On 2018-01-27 17:24, CP wrote:
On 01/27/2018 02:05 PM, Matus UHLAR - fantomas wrote:
On 27.01.18 11:16, CP wrote:
I'm trying to eliminate a problem with duplicate emails in alias
expansion and I have seen that some (local generated and SMTP also)
21 matches
Mail list logo
