- Message from Damian -
Date: Thu, 17 Jun 2021 12:22:28 +0200
From: Damian
Subject: Re: Mail not being sent to file
To: postfix-users@postfix.org
That's interesting... 8.4 saw the upgrade to Postfix 3.5.8 (from
3.3.1 I believe)
http://rpmfind.net/linux/centos/8.3.2011
On Thu, Jun 17, 2021 at 12:22:28PM +0200, Damian wrote:
> >That's interesting... 8.4 saw the upgrade to Postfix 3.5.8 (from
> >3.3.1 I believe)
> http://rpmfind.net/linux/centos/8.3.2011/BaseOS/x86_64/os/Packages/postfix-3.3.1-12.el8.x86_64.rpm
> already had PrivateTmp.
Thanks. Honestly I don't
That's interesting... 8.4 saw the upgrade to Postfix 3.5.8 (from 3.3.1
I believe)
http://rpmfind.net/linux/centos/8.3.2011/BaseOS/x86_64/os/Packages/postfix-3.3.1-12.el8.x86_64.rpm
already had PrivateTmp.
It broke because as Bastian pointed out in CentOS 8 the Postfix
service definition (postfix.service) changed with the addition of
PrivateTmp=true. CentOS 7 did not have that so used the "standard"
/tmp. Your process WAS WORKING - just not writing to the /tmp you
were looking at, but to the
On Thu, Jun 17, 2021 at 06:43:11PM +1000, Simon Wilson wrote:
> >>>Just don't assume /tmp or /var/tmp are the same between services.
> >>>
> >>>Postfix on RHEL 8 is configured with private /tmp. To be exact:
> >>>| PrivateTmp=true
> >>>| CapabilityBoundingSet=~ CAP_NET_ADMIN CAP_SYS_ADMIN
>Just don't assume /tmp or /var/tmp are the same between services.
>
>Postfix on RHEL 8 is configured with private /tmp. To be exact:
>| PrivateTmp=true
>| CapabilityBoundingSet=~ CAP_NET_ADMIN CAP_SYS_ADMIN CAP_SYS_BOOT
>CAP_SYS_MODULE
>| ProtectSystem=true
>| PrivateDevices=true
>
>Bastian
On Thu, Jun 17, 2021 at 05:18:54PM +1000, Simon Wilson wrote:
> - Message from Bastian Blank
> -
>Date: Thu, 17 Jun 2021 07:59:10 +0200
>From: Bastian Blank
> Subject: Re: Mail not being sent to file
> To: postfix-users@postfix.org
>
>
> >
- Message from Bastian Blank
-
Date: Thu, 17 Jun 2021 07:59:10 +0200
From: Bastian Blank
Subject: Re: Mail not being sent to file
To: postfix-users@postfix.org
On Wed, Jun 16, 2021 at 05:59:16PM -0700, Jeremiah Rothschild wrote:
To triple check my sanity, I created
On Wed, Jun 16, 2021 at 10:48:27PM -0400, Viktor Dukhovni wrote:
> On Wed, Jun 16, 2021 at 05:59:16PM -0700, Jeremiah Rothschild wrote:
>
> > So anyone should be able to easily reproduce this.
> >
> > * Fresh CentOS 8.4 install
> > * Choose "Minimal" base environment
> > * Defaults for
On Wed, Jun 16, 2021 at 05:59:16PM -0700, Jeremiah Rothschild wrote:
> To triple check my sanity, I created a brand new VM and confirmed the
> behavior.
> So anyone should be able to easily reproduce this.
>
> * Fresh CentOS 8.4 install
> * Choose "Minimal" base environment
> * Defaults for
On Thu, Jun 17, 2021 at 12:42:43PM +1000, Simon Wilson wrote:
> On RHEL 8:
>
> [root@emp87 ~]# echo "somealias: /tmp/somefile" >> /etc/aliases && newaliases
> [root@emp87 ~]# echo "test" | mail somealias@localhost
> [root@emp87 ~]# ls /tmp/somefile
> ls: cannot access '/tmp/somefile': No such
On Wed, Jun 16, 2021 at 05:59:16PM -0700, Jeremiah Rothschild wrote:
> So anyone should be able to easily reproduce this.
>
> * Fresh CentOS 8.4 install
> * Choose "Minimal" base environment
> * Defaults for everything else
You can debug further with:
- Message from Jeremiah Rothschild -
Date: Wed, 16 Jun 2021 17:59:16 -0700
From: Jeremiah Rothschild
Subject: Re: Mail not being sent to file
To: Postfix users
On Wed, Jun 16, 2021 at 04:48:09PM -0700, Jeremiah Rothschild wrote:
On Wed, Jun 16, 2021 at 07:13:18PM
On Wed, Jun 16, 2021 at 04:48:09PM -0700, Jeremiah Rothschild wrote:
> On Wed, Jun 16, 2021 at 07:13:18PM -0400, Wietse Venema wrote:
> > Is the 'lost file' problem reproducible?
>
> Yes, the time gap is a red herring. First the issue was noticed in
> production then I tested with this VM.
To
On Wed, Jun 16, 2021 at 07:13:18PM -0400, Wietse Venema wrote:
> Jeremiah Rothschild:
> > /tmp is a separate filesystem:
> > [root@c8vm ~]# grep tmp /etc/fstab
> > /dev/mapper/rootvg-tmp /tmpext4defaults1 2
> > [root@c8vm ~]# df -h /tmp
> > Filesystem
Jeremiah Rothschild wrote:
> * OS: CentOS 8.4.2105 x64 (fully updated)
I tested this on CentOS 7 and it worked okay for me. No problem. I
don't know anything about CentOS 8.
> [root@c8vm ~]# ls -l /tmp/somefile
> ls: cannot access '/tmp/somefile': No such file or directory
Is your postfix
Jeremiah Rothschild:
> /tmp is a separate filesystem:
> [root@c8vm ~]# grep tmp /etc/fstab
> /dev/mapper/rootvg-tmp /tmpext4defaults1 2
> [root@c8vm ~]# df -h /tmp
> Filesystem Size Used Avail Use% Mounted on
> /dev/mapper/rootvg-tmp 2.0G 6.1M 1.8G
On Wed, Jun 16, 2021 at 05:33:33PM -0400, Viktor Dukhovni wrote:
> On Wed, Jun 16, 2021 at 01:51:37PM -0700, Jeremiah Rothschild wrote:
>
> > I have an alias that is supposed to write to a file but it is not.
> >
> > * OS: CentOS 8.4.2105 x64 (fully updated)
> > * Kernel:
On Wed, Jun 16, 2021 at 05:23:20PM -0400, Wietse Venema wrote:
> Jeremiah Rothschild:
> > Hello,
> >
> > I have an alias that is supposed to write to a file but it is not.
> >
> > * OS: CentOS 8.4.2105 x64 (fully updated)
> > * Kernel: 4.18.0-305.3.1.el8.x86_64
> > * Postfix: 3.5.8-1.el8.x86_64
On Wed, Jun 16, 2021 at 01:51:37PM -0700, Jeremiah Rothschild wrote:
> I have an alias that is supposed to write to a file but it is not.
>
> * OS: CentOS 8.4.2105 x64 (fully updated)
> * Kernel: 4.18.0-305.3.1.el8.x86_64
> * Postfix: 3.5.8-1.el8.x86_64 (default config w/ verbose logging)
>
>
Jeremiah Rothschild:
> Hello,
>
> I have an alias that is supposed to write to a file but it is not.
>
> * OS: CentOS 8.4.2105 x64 (fully updated)
> * Kernel: 4.18.0-305.3.1.el8.x86_64
> * Postfix: 3.5.8-1.el8.x86_64 (default config w/ verbose logging)
>
> Very basic /etc/aliases:
> [root@c8vm
Hello,
I have an alias that is supposed to write to a file but it is not.
* OS: CentOS 8.4.2105 x64 (fully updated)
* Kernel: 4.18.0-305.3.1.el8.x86_64
* Postfix: 3.5.8-1.el8.x86_64 (default config w/ verbose logging)
Very basic /etc/aliases:
[root@c8vm ~]# cat /etc/aliases
somealias:
22 matches
Mail list logo
