Re: OpenSMTPD ignores the system time zone in mail header and logfile

2022-12-12 Thread Thomas L.
On Mon, 12 Dec 2022 20:49:06 +0100 (CET) "Nils" wrote: > O.k., thanks. But has tzset() also effect on the forked processes, i. > e. is the timezone data then also available for the forked processes? afaik the processes are created via fork+exec to rerandomize the address space layout. so all

Re: OpenSMTPD ignores the system time zone in mail header and logfile

2022-12-10 Thread Thomas L.
On Sat, 10 Dec 2022 19:03:23 +0100 (CET) "Nils" wrote: > And why does this problem occur in Linux, but *not* in OpenBSD? > log_init calls tzset(3), which reads the timezone data early. not sure why this does not work on Linux.

Re: Cipher list

2021-12-07 Thread Thomas L.
> Where do you find the definition of cipher settings: all, insecure, > default, etc? The "man tls_config_set_ciphers" mentions them but > doesn't define them. Neither does "man openssl". > > "TLSv1.2:ECDHE-RSA-AES256-SHA384:256" looks reasonably modern, why is > it not part of "ciphers secure"?

Re: Catchall user

2020-04-05 Thread Thomas L.
On Thu, 2 Apr 2020 15:57:17 +0800 Stephan Chedlivili wrote: > Is there a way to achieve that? And more generally, is that a good > idea? You could have a list with valid receivers and redirect the rest to your user X with a catchall rule. Something like this (untested, partial): table aliases

log spam

2017-11-09 Thread Thomas L.
Hello everyone, I recently got lots of log messages of the form Nov 10 00:24:07 puffy smtpd[8419]: smtp-out: Enabling route [] <-> some.redacted.ip.address (some.redacted.ip.address) Nov 10 00:24:11 puffy smtpd[8419]: ada98c6f333577d7 mta event=connecting