On Mon, Jan 03, 2022 at 10:06:02PM -0500, Ken Wright
wrote:
> On Mon, 2022-01-03 at 20:50 -0500, Viktor Dukhovni wrote:
> > On Mon, Jan 03, 2022 at 08:02:20PM -0500, Ken Wright wrote:
> >
> > > $ sudo chmod g+s /usr/sbin/postdrop
> > > $ ls -la /usr/sbin/postdrop
> > > -r-xr-sr-x 1 postfix post
Ken Wright:
> On Tue, 2022-01-04 at 07:30 -0500, Wietse Venema wrote:
> > Ken Wright:
> > > Okay, I ran sudo postfix set-permissions.? It ran with no trouble
> > > whatsoever; no errors, warnings, nothing.? Still getting the exact
> > > same messages in mail.log.
> >
> > Then your file system is m
On Tue, 2022-01-04 at 07:30 -0500, Wietse Venema wrote:
> Ken Wright:
> > Okay, I ran sudo postfix set-permissions. It ran with no trouble
> > whatsoever; no errors, warnings, nothing. Still getting the exact
> > same messages in mail.log.
>
> Then your file system is mounted with 'nosuid' optio
Am 04.01.2022 um 16:25 schrieb Wietse Venema:
Alex JOST:
Am 04.01.2022 um 02:02 schrieb Ken Wright:
$ sudo chmod g+s /usr/sbin/postdrop
$ ls -la /usr/sbin/postdrop
-r-xr-sr-x 1 postfix postdrop 22808 Sep 7 02:58 /usr/sbin/postdrop
Wietse, is this what's expected?
AFAICT you are lacking writ
Alex JOST:
> Am 04.01.2022 um 02:02 schrieb Ken Wright:
> > $ sudo chmod g+s /usr/sbin/postdrop
> > $ ls -la /usr/sbin/postdrop
> > -r-xr-sr-x 1 postfix postdrop 22808 Sep 7 02:58 /usr/sbin/postdrop
> >
> > Wietse, is this what's expected?
>
> AFAICT you are lacking write permission for the user
Am 04.01.2022 um 02:02 schrieb Ken Wright:
$ sudo chmod g+s /usr/sbin/postdrop
$ ls -la /usr/sbin/postdrop
-r-xr-sr-x 1 postfix postdrop 22808 Sep 7 02:58 /usr/sbin/postdrop
Wietse, is this what's expected?
AFAICT you are lacking write permission for the user.
--
Alex JOST
Ken Wright:
> On Mon, 2022-01-03 at 20:50 -0500, Viktor Dukhovni wrote:
> > On Mon, Jan 03, 2022 at 08:02:20PM -0500, Ken Wright wrote:
> >
> > > $ sudo chmod g+s /usr/sbin/postdrop
> > > $ ls -la /usr/sbin/postdrop
> > > -r-xr-sr-x 1 postfix postdrop 22808 Sep? 7 02:58 /usr/sbin/postdrop
> > >
>
On Tue, 2022-01-04 at 15:32 +1100, raf wrote:
> On Mon, Jan 03, 2022 at 07:22:24PM -0500, Ken Wright
> wrote:
>
> > On Tue, 2022-01-04 at 08:32 +1100, raf wrote:
> > > Actually, if you are still getting
> > > "/usr/lib/postfix/sbin/0: No such file or directory"
> > > messages (with new timestamps
On Mon, Jan 03, 2022 at 08:02:20PM -0500, Ken Wright
wrote:
> On Mon, 2022-01-03 at 19:45 -0500, Wietse Venema wrote:
> > Ken Wright:
> > > On Tue, 2022-01-04 at 08:32 +1100, raf wrote:
> > > > Actually, if you are still getting
> > > > "/usr/lib/postfix/sbin/0: No such file or directory"
> > >
On Mon, Jan 03, 2022 at 07:22:24PM -0500, Ken Wright
wrote:
> On Tue, 2022-01-04 at 08:32 +1100, raf wrote:
> > Actually, if you are still getting
> > "/usr/lib/postfix/sbin/0: No such file or directory"
> > messages (with new timestamps), that must mean that you
> > didn't reload postfix after
On Mon, 2022-01-03 at 20:50 -0500, Viktor Dukhovni wrote:
> On Mon, Jan 03, 2022 at 08:02:20PM -0500, Ken Wright wrote:
>
> > $ sudo chmod g+s /usr/sbin/postdrop
> > $ ls -la /usr/sbin/postdrop
> > -r-xr-sr-x 1 postfix postdrop 22808 Sep 7 02:58 /usr/sbin/postdrop
> >
> > Wietse, is this what's
On Mon, Jan 03, 2022 at 08:02:20PM -0500, Ken Wright wrote:
> $ sudo chmod g+s /usr/sbin/postdrop
> $ ls -la /usr/sbin/postdrop
> -r-xr-sr-x 1 postfix postdrop 22808 Sep 7 02:58 /usr/sbin/postdrop
>
> Wietse, is this what's expected?
The expected permissions are recorded in the "postfix-files"
On 1/3/22 20:02, Ken Wright wrote:
$ sudo chmod g+s /usr/sbin/postdrop
$ ls -la /usr/sbin/postdrop
-r-xr-sr-x 1 postfix postdrop 22808 Sep 7 02:58 /usr/sbin/postdrop
Wietse, is this what's expected?
That looks exactly correct to me.
--
Phil Stracchino
Babylon Communications
ph...@ca
On Mon, 2022-01-03 at 19:45 -0500, Wietse Venema wrote:
> Ken Wright:
> > On Tue, 2022-01-04 at 08:32 +1100, raf wrote:
> > > Actually, if you are still getting
> > > "/usr/lib/postfix/sbin/0: No such file or directory"
> > > messages (with new timestamps), that must mean that you
> > > didn't relo
Ken Wright:
> On Tue, 2022-01-04 at 08:32 +1100, raf wrote:
> > Actually, if you are still getting
> > "/usr/lib/postfix/sbin/0: No such file or directory"
> > messages (with new timestamps), that must mean that you
> > didn't reload postfix after fixing master.cf. You need
> > to do that. Reload P
On Tue, 2022-01-04 at 08:32 +1100, raf wrote:
> Actually, if you are still getting
> "/usr/lib/postfix/sbin/0: No such file or directory"
> messages (with new timestamps), that must mean that you
> didn't reload postfix after fixing master.cf. You need
> to do that. Reload Postfix and see if those
On Mon, Jan 03, 2022 at 03:14:32PM +1100, raf wrote:
> On Sun, Jan 02, 2022 at 11:03:08PM -0500, Ken Wright
> wrote:
>
> > On Mon, 2022-01-03 at 14:50 +1100, raf wrote:
> > > On Sun, Jan 02, 2022 at 09:32:53PM -0500, Ken Wright
> > > wrote:
> > >
> > > > Just checked my mail logs. Do any of
Ken Wright:
> On Sun, 2022-01-02 at 21:59 -0500, Wietse Venema wrote:
> > Ken Wright:
> > > On Sun, 2022-01-02 at 19:40 -0500, Wietse Venema wrote:
> > > > Sorry, I mis-typed 'postqueue'.
> > > >
> > > > Try this instead.
> > > >
> > > > Here is what happens on my system.
> > > >
> > > > As root
On Sun, Jan 02, 2022 at 11:03:08PM -0500, Ken Wright
wrote:
> On Mon, 2022-01-03 at 14:50 +1100, raf wrote:
> > On Sun, Jan 02, 2022 at 09:32:53PM -0500, Ken Wright
> > wrote:
> >
> > > Just checked my mail logs. Do any of these help anyone?
> > >
> > > kwright:~$ tail /var/log/mail.log
> >
On Mon, 2022-01-03 at 14:50 +1100, raf wrote:
> On Sun, Jan 02, 2022 at 09:32:53PM -0500, Ken Wright
> wrote:
>
> > Just checked my mail logs. Do any of these help anyone?
> >
> > kwright:~$ tail /var/log/mail.log
> > [...]
> > kwright:~$ tail /var/log/mail.err
> > Jan 2 21:15:34 grace master[
On Sun, Jan 02, 2022 at 09:32:53PM -0500, Ken Wright
wrote:
> Just checked my mail logs. Do any of these help anyone?
>
> kwright:~$ tail /var/log/mail.log
> [...]
> kwright:~$ tail /var/log/mail.err
> Jan 2 21:15:34 grace master[79805]: fatal: master_spawn: exec
> /usr/lib/postfix/sbin/0: No
On Sun, 2022-01-02 at 21:59 -0500, Wietse Venema wrote:
> Ken Wright:
> > On Sun, 2022-01-02 at 19:40 -0500, Wietse Venema wrote:
> > > Sorry, I mis-typed 'postqueue'.
> > >
> > > Try this instead.
> > >
> > > Here is what happens on my system.
> > >
> > > As root:
> > >
> > > # chmod g-s /usr/
Ken Wright:
> Just checked my mail logs. Do any of these help anyone?
>
> kwright:~$ tail /var/log/mail.log
> Jan 2 21:23:31 grace postfix/postdrop[58322]: warning:
> mail_queue_enter: create file maildrop/914822.58322: Permission denied
Yes, that is because I made a mistake in my first comman
Ken Wright:
> On Sun, 2022-01-02 at 19:40 -0500, Wietse Venema wrote:
> > Sorry, I mis-typed 'postqueue'.
> >
> > Try this instead.
> >
> > Here is what happens on my system.
> >
> > As root:
> >
> > # chmod g-s /usr/sbin/postqueue
> > # ls -l /usr/sbin/postqueue
> > -rwxr-xr-x 1 root postdrop
postfix/postqueue[80723]: fatal: Queue report
unavailable - mail system is down
Jan 2 21:23:04 grace master[81109]: fatal: master_spawn: exec
/usr/lib/postfix/sbin/0: No such file or directory
Jan 2 21:24:05 grace master[81158]: fatal: master_spawn: exec
/usr/lib/postfix/sbin/0: No such file or
On Mon, 2022-01-03 at 13:02 +1100, raf wrote:
> Note: The errors above are due to copying and pasting
> the command prompt ("wzv$") and the strace output (i.e.
> connect...) along with the commands themselves. Your
> shell was trying to execute those things as though they
> were shell commands, but
On Sun, Jan 02, 2022 at 08:10:06PM -0500, Ken Wright
wrote:
> On Sun, 2022-01-02 at 19:40 -0500, Wietse Venema wrote:
> > Sorry, I mis-typed 'postqueue'.
> >
> > Try this instead.
> >
> > Here is what happens on my system.
> >
> > As root:
> >
> > # chmod g-s /usr/sbin/postqueue
> > # ls -l
On Sun, 2022-01-02 at 19:40 -0500, Wietse Venema wrote:
> Sorry, I mis-typed 'postqueue'.
>
> Try this instead.
>
> Here is what happens on my system.
>
> As root:
>
> # chmod g-s /usr/sbin/postqueue
> # ls -l /usr/sbin/postqueue
> -rwxr-xr-x 1 root postdrop 60072 Dec 23 18:08 /usr/sbin/postque
Sorry, I mis-typed 'postqueue'.
Try this instead.
Here is what happens on my system.
As root:
# chmod g-s /usr/sbin/postqueue
# ls -l /usr/sbin/postqueue
-rwxr-xr-x 1 root postdrop 60072 Dec 23 18:08 /usr/sbin/postqueue
# chmod 777 /var/spool/postfix/public
# ls -ld /var/spool/postfix/public /
On Sun, 2022-01-02 at 18:37 -0500, Wietse Venema wrote:
> Here is what happens on m system.
>
> As root:
>
> # chmod g-s /usr/sbin/postdrop
> # ls -l /usr/sbin/postdrop
> -rwxr-xr-x 1 root postdrop 44472 Dec 23 18:08 /usr/sbin/postdrop
For some reason, there is no write permission on postdrop, f
John Fawcett:
> On 03/01/2022 00:37, Wietse Venema wrote:
> > Here is what happens on m system.
> > As root:
> >
> > # chmod g-s /usr/sbin/postdrop
> > # ls -l /usr/sbin/postdrop
> > -rwxr-xr-x 1 root postdrop 44472 Dec 23 18:08 /usr/sbin/postdrop
> > # chmod 777 /var/spool/postfix/public
> > # ls
On 03/01/2022 00:37, Wietse Venema wrote:
Here is what happens on m system.
As root:
# chmod g-s /usr/sbin/postdrop
# ls -l /usr/sbin/postdrop
-rwxr-xr-x 1 root postdrop 44472 Dec 23 18:08 /usr/sbin/postdrop
# chmod 777 /var/spool/postfix/public
# ls -ld /var/spool/postfix/public /var/spool/post
On 03/01/2022 00:06, Ken Wright wrote:
On Sun, 2022-01-02 at 17:30 -0500, Wietse Venema wrote:
Ken Wright:
On Sun, 2022-01-02 at 16:01 -0500, Wietse Venema wrote:
Does it also fail when run as root? In that case,
??? # strace -e connect postqueue -p |&grep showq
Otherwise, some temporary hac
Ken Wright:
> On Sun, 2022-01-02 at 17:30 -0500, Wietse Venema wrote:
> > Ken Wright:
> > > On Sun, 2022-01-02 at 16:01 -0500, Wietse Venema wrote:
> > > > Does it also fail when run as root? In that case,
> > > >
> > > > ??? # strace -e connect postqueue -p |&grep showq
> > > >
> > > > Otherwise
On Sun, 2022-01-02 at 17:30 -0500, Wietse Venema wrote:
> Ken Wright:
> > On Sun, 2022-01-02 at 16:01 -0500, Wietse Venema wrote:
> > > Does it also fail when run as root? In that case,
> > >
> > > ??? # strace -e connect postqueue -p |&grep showq
> > >
> > > Otherwise, some temporary hack is nee
Kenneth Irving:
>
> On Sun, 2 Jan 2022, Ken Wright wrote:
>
> > On Sun, 2022-01-02 at 16:01 -0500, Wietse Venema wrote:
> >> Does it also fail when run as root? In that case,
> >>
> >> ??? # strace -e connect postqueue -p |&grep showq
> >>
> >> Otherwise, some temporary hack is needed.
> >>
> >>
Ken Wright:
> On Sun, 2022-01-02 at 16:01 -0500, Wietse Venema wrote:
> > Does it also fail when run as root? In that case,
> >
> > ??? # strace -e connect postqueue -p |&grep showq
> >
> > Otherwise, some temporary hack is needed.
> >
> > As root, disdable file permissions:
> >
> > # chmod 777
On Sun, 2 Jan 2022, Ken Wright wrote:
On Sun, 2022-01-02 at 16:01 -0500, Wietse Venema wrote:
Does it also fail when run as root? In that case,
# strace -e connect postqueue -p |&grep showq
Otherwise, some temporary hack is needed.
As root, disdable file permissions:
# chmod 777 /var/s
On Sun, 2022-01-02 at 16:01 -0500, Wietse Venema wrote:
> Does it also fail when run as root? In that case,
>
> # strace -e connect postqueue -p |&grep showq
>
> Otherwise, some temporary hack is needed.
>
> As root, disdable file permissions:
>
> # chmod 777 /var/spool/postfix/public
> # c
Ken Wright:
> On Sun, 2022-01-02 at 11:16 -0500, Wietse Venema wrote:
> > Ken Wright:
> > > On Sat, 2022-01-01 at 18:50 -0500, Wietse Venema wrote:
> > > > Ken Wright:
> > > > >
> > > > > I did a quick Google search, and ran sudo apparmor_status.
> > > > > There don't appear to be any postfix-rela
On Sun, 2022-01-02 at 11:16 -0500, Wietse Venema wrote:
> Ken Wright:
> > On Sat, 2022-01-01 at 18:50 -0500, Wietse Venema wrote:
> > > Ken Wright:
> > > >
> > > > I did a quick Google search, and ran sudo apparmor_status.
> > > > There don't appear to be any postfix-related programs listed.
> > >
On 1/2/22 17:16, Wietse Venema wrote:
Ken Wright:
On Sat, 2022-01-01 at 18:50 -0500, Wietse Venema wrote:
Ken Wright:
I did a quick Google search, and ran sudo apparmor_status. There
don't appear to be any postfix-related programs listed.
Then that leaves the cron related profiles.
None o
Ken Wright:
> On Sat, 2022-01-01 at 18:50 -0500, Wietse Venema wrote:
> > Ken Wright:
> > >
> > > I did a quick Google search, and ran sudo apparmor_status. There
> > > don't appear to be any postfix-related programs listed.
> >
> > Then that leaves the cron related profiles.
>
> None of those e
On Sat, 2022-01-01 at 18:50 -0500, Wietse Venema wrote:
> Ken Wright:
> >
> > I did a quick Google search, and ran sudo apparmor_status. There
> > don't appear to be any postfix-related programs listed.
>
> Then that leaves the cron related profiles.
None of those either.
; > > errors,
> > > > ? but when AppArmor returns a different error code such as EPERM,
> > > > ? postqueue will just say "mail system is down" (it does not try
> > > > ? to evaluate every possible error code).
> > >
> > > AppAr
mor returns a different error code such as EPERM,
> > > postqueue will just say "mail system is down" (it does not try
> > > to evaluate every possible error code).
> >
> > AppArmor 2.13.3 is installed, but I'm not familiar with it. How
> >
Ken Wright:
> > Is the postqueue command subject to AppArmor reduced privileges?
> > The postqueue command will log EACES (Permission denied) errors,
> > but when AppArmor returns a different error code such as EPERM,
> > postqueue will just say "mail sys
ave an ellipsis in the
fifth column; does that mean "doesn't matter"?
> Is the postqueue command subject to AppArmor reduced privileges?
> The postqueue command will log EACES (Permission denied) errors,
> but when AppArmor returns a different error code such as EPERM
Ken Wright:
> What a way to start the new year!
>
> I got the following message in /var/log/mail.err this morning:
>
> Jan 1 01:34:03 grace postfix/postqueue[1684046]: fatal: Queue report
> unavailable - mail system is down
postqueue will log this when it is unable to con
What a way to start the new year!
I got the following message in /var/log/mail.err this morning:
Jan 1 01:34:03 grace postfix/postqueue[1684046]: fatal: Queue report
unavailable - mail system is down
Naturally, I checked, and both Postfix and Dovecot are running. Can
anyone translate this for
50 matches
Mail list logo