On Sat, 2021-07-03 at 00:30 -0600, @lbutlr wrote:
>
> MX backups are a legacy of 30-40 years ago when it was very common to
> have machines that only periodically connected to the Internet. There
> are many reasons they are a bad idea in a modern context, and having a
> third party be a alternate
Wietse Venema:
> Jaroslav Skarvada:
> > Reproducer:
> >
> > # useradd -c " " myuser # or more whitespaces
> > # su - myuser
> > $ echo | mail -s TEST root@localhost
> > # journalctl -u postfix | tail
> > Jun 30 13:31:13 vm-postfix8 postfix/pickup[4476]: 91309115983C:
> > uid=1000 from=
> > Jun 30
Jaroslav Skarvada:
> Reproducer:
>
> # useradd -c " " myuser # or more whitespaces
> # su - myuser
> $ echo | mail -s TEST root@localhost
> # journalctl -u postfix | tail
> Jun 30 13:31:13 vm-postfix8 postfix/pickup[4476]: 91309115983C:
> uid=1000 from=
> Jun 30 13:31:13 vm-postfix8 postfix/picku
On Mon, 28 Jun 2021, Kevin N. wrote:
Super. Thank you for all the info :)
Cheers,
Kevin
By the way, I like the way Google merges the headers into one, like:
Authentication-Results: mx.google.com;
dkim=pass header.i=@example.net header.s=example header.b=lXmpAXoJ;
spf=pass (google.c
Reproducer:
# useradd -c " " myuser # or more whitespaces
# su - myuser
$ echo | mail -s TEST root@localhost
# journalctl -u postfix | tail
Jun 30 13:31:13 vm-postfix8 postfix/pickup[4476]: 91309115983C:
uid=1000 from=
Jun 30 13:31:13 vm-postfix8 postfix/pickup[4476]: warning:
maildrop/D19752025C
On Jul 3, 2021, at 00:53, Dominic Raferd wrote:
>
> On 03/07/2021 07:48, @lbutlr wrote:
>> When going to https://www.postfix.org I get, after an invalid certificate
>> error,...
> The correct address is http://www.postfix.org (no https...)
Then it really should not be responding to https or r
