Tomasz Pala via Postfix-users:
> > Again, what about the logging from NON-DAEMON Postfix processes
> > such as sendmail, postdrop, postqueue, and so on?
>
> They belong to their calling service. Therefore if I run sendmail from
> the shell, it belongs to my user's slice. If postdrop is run from
>
On 2024-12-16 01:16, Wietse Venema via Postfix-users wrote:
>>
>> All the processes of a service share single CGroup, so there's no ambiguity.
>
> You read half my question and stopped mid-way. Please extend
> your attention san.
Actually I've answered it all, but might elaborate.
> Again, what
Tomasz Pala via Postfix-users:
> On 2024-12-15 23:28, Wietse Venema via Postfix-users wrote:
> >>
> >> System-wide "defaults to 1 messages in 30s" and "is applied per-
> >> service", so this can be easily resolved by providing postfix.service
> >> with:
> >>
> >> LogRateLimitIntervalSec=0
> >
On 2024-12-16 00:23, Tomasz Pala via Postfix-users wrote:
>
> All the processes of a service share single CGroup, so there's no ambiguity.
Catched in several seconds intervals:
host-server ~# machinectl shell mail-server
mail-server ~# systemd-cgls -u postfix
Unit postfix.service (/system.slice/
On 2024-12-15 23:28, Wietse Venema via Postfix-users wrote:
>>
>> System-wide "defaults to 1 messages in 30s" and "is applied per-
>> service", so this can be easily resolved by providing postfix.service
>> with:
>>
>> LogRateLimitIntervalSec=0
>
> How would it know that a message sent with th
Tomasz Pala via Postfix-users:
> On 2024-12-15 09:44, Viktor Dukhovni via Postfix-users wrote:
> >
> > With systemd logging, logs are by default lossy (rate-limits too tight
> > and many users don't notice until it is too late). Also logging is
>
> System-wide "defaults to 1 messages in 30s"
Michael Tokarev via Postfix-users:
> 09.12.2024 17:17, Wietse Venema via Postfix-users wrote:
> ...
> > Setting up the necessary helper files under /var/spool/postfix
> > (nsswitch.conf, TLS, resolv.conf, services) remains platform-specific.
>
> I was under impression postfix does not need nsswitc
On 2024-12-15 21:57, Gerald Galster via Postfix-users wrote:
>
> By default journald keeps about 4 GB of logs, which will only retain a
> few hours on a busy server. One might try to overcome that by setting
[...]
> when you discover some needed log data is not available anymore ...
>
> Storing l
>> With systemd logging, logs are by default lossy (rate-limits too tight
>> and many users don't notice until it is too late). Also logging is
>
> System-wide "defaults to 1 messages in 30s" and "is applied per-
> service", so this can be easily resolved by providing postfix.service
> with
09.12.2024 17:17, Wietse Venema via Postfix-users wrote:
...
Setting up the necessary helper files under /var/spool/postfix
(nsswitch.conf, TLS, resolv.conf, services) remains platform-specific.
I was under impression postfix does not need nsswitch.conf in the chroot.
But I was wrong.
smtp_hos
14.12.2024 17:32, Wietse Venema via Postfix-users wrote:
..
Suggesting that these programs are running continuously is not fair.
Instead, they sleep. If the file system activity bothers you then
somene could add a few stat() calls and skip directories that have
no recently modified time stamp.
Hello Wietse,
Thanks for the explanation and your patience, that explains a lot for
me. It really is a bit confusing with the different date and time
formats, depending on the system locales and the different RFCs. I'm not
that familiar with the subject after all. But that must still come for
Andreas Kuhlen via Postfix-users:
> Postfix uses the RFC 5322 date/time format, you say. On the subject of
> RFC 5322 date/time format, I can find the following in the ?date? man page:
>
> ?-R, --rfc-email
> ? output date and time in RFC 5322 format.? Example: Mon,
> 14 Aug 2006 02
Postfix uses the RFC 5322 date/time format, you say. On the subject of
RFC 5322 date/time format, I can find the following in the ‘date’ man page:
-R, --rfc-email
output date and time in RFC 5322 format. Example: Mon,
14 Aug 2006 02:34:56 -0600
And when I enter the command ‘da
On 2024-12-15 13:43, Wietse Venema via Postfix-users wrote:
>
> Oh, it is wonderful for laptops. On a busy server, it is known to
> discard events and to use more resources. No-one carea about the
> resources, with 16-core CPUs and SSDs.
In case anyone's interested - since v245 there are long awa
15.12.2024 14:33, Viktor Dukhovni via Postfix-users wrote:
On Sun, Dec 15, 2024 at 11:34:54AM +0100, Tomasz Pala via Postfix-users wrote:
System-wide "defaults to 1 messages in 30s" and "is applied per-
service", so this can be easily resolved by providing postfix.service
with:
LogRateLimi
On 2024-12-15 12:33, Viktor Dukhovni via Postfix-users wrote:
>
>> LogRateLimitIntervalSec=0
>
> Nice in theory, but neither Wietse nor I distribute systemd service
> definition files,
Why is that? Service units are best provided upstream.
In case of postfix, having magnitude of options, harden
Andreas Kuhlen via Postfix-users:
> Hello,
>
> currently, some dates appear in American format. As can be seen at the
> end of the line below:
>
> 2024-12-15T09:48:57.200203+01:00 mail postfix/anvil[919910]: statistics:
> max cache size 1 at Dec 15 09:45:36
Postfix uses the RFC 5322 date-time
Michael Tokarev via Postfix-users:
> 15.12.2024 03:07, Wietse Venema via Postfix-users wrote:
> > Michael Tokarev via Postfix-users:
> ...
> >> Today systemd plays major role in linux, and linux plays major role in the
> >> IT world. And while some its ideas are questionable or may look weird,
>
On Sun, Dec 15, 2024 at 11:34:54AM +0100, Tomasz Pala via Postfix-users wrote:
> System-wide "defaults to 1 messages in 30s" and "is applied per-
> service", so this can be easily resolved by providing postfix.service
> with:
>
> LogRateLimitIntervalSec=0
Nice in theory, but neither Wietse n
On 15/12/24 23:34, Tomasz Pala via Postfix-users wrote:
On 2024-12-15 09:44, Viktor Dukhovni via Postfix-users wrote:
With systemd logging, logs are by default lossy (rate-limits too tight
and many users don't notice until it is too late). Also logging is
System-wide "defaults to 1 messa
On 2024-12-15 09:44, Viktor Dukhovni via Postfix-users wrote:
>
> With systemd logging, logs are by default lossy (rate-limits too tight
> and many users don't notice until it is too late). Also logging is
System-wide "defaults to 1 messages in 30s" and "is applied per-
service", so this can
On 15/12/24 20:06, Andreas Kuhlen via Postfix-users wrote:
Hello,
currently, some dates appear in American format. As can be seen at the
end of the line below:
2024-12-15T09:48:57.200203+01:00 mail postfix/anvil[919910]: statistics:
max cache size 1 at Dec 15 09:45:36
Is it possible to cha
Hello,
currently, some dates appear in American format. As can be seen at the
end of the line below:
2024-12-15T09:48:57.200203+01:00 mail postfix/anvil[919910]: statistics:
max cache size 1 at Dec 15 09:45:36
Is it possible to change this so that it is displayed as ‘day month time’?
Is thi
On Sun, Dec 15, 2024 at 11:16:16AM +0300, Michael Tokarev via Postfix-users
wrote:
> What was so unreliable in there?
On Sun, Dec 15, 2024 at 09:29:48AM +0100, Tomasz Pala via Postfix-users wrote:
> On 2024-12-15 01:07, Wietse Venema via Postfix-users wrote:
> Would you mind elaborating this a
On 2024-12-15 01:07, Wietse Venema via Postfix-users wrote:
>
> It also sucks raw eggs at doing this, to the point that I was
> motivated to add a postlogd service to make Postfix logging reliable
> again.
Would you mind elaborating this a bit? There are configurable
rate-limiters I am aware of,
15.12.2024 03:07, Wietse Venema via Postfix-users wrote:
Michael Tokarev via Postfix-users:
...
Today systemd plays major role in linux, and linux plays major role in the
IT world. And while some its ideas are questionable or may look weird, some
are interesting. And logging is one of them: i
27 matches
Mail list logo
