Re: www.postfix.org site appears to be down.
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 redirecting it, no? Especially with the browsers starting to default to checking https and and others supporting extensions to check https first. I’ll check when I get back to the computer.
regression: cleanup crashes if fullname contains only whitespace(s)
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/D19752025C83: error writing 91309115983C: queue file write
error
Jun 30 13:31:13 vm-postfix8 postfix/master[4475]: warning: process
/usr/libexec/postfix/cleanup pid 4797 killed by signal 11
Attached workaround patch.
It seems postfix-3.6.1 is also affected. The postfix-2 wasn't
affected, that's why I flagged it as a regression.
Original downstream bug report including the debug analysis:
https://bugzilla.redhat.com/show_bug.cgi?id=1977732
Debug analysis and reproducer provided by Renaud Métrich
thanks & regards
Jaroslav
diff --git a/src/cleanup/cleanup_message.c b/src/cleanup/cleanup_message.c
index 391c711..be5ce42 100644
--- a/src/cleanup/cleanup_message.c
+++ b/src/cleanup/cleanup_message.c
@@ -773,6 +773,8 @@ static void cleanup_header_done_callback(void *context)
/* Normalize whitespace. */
token = tok822_scan_limit(state->fullname, &dummy_token,
var_token_limit);
+ if (!token)
+token = tok822_alloc(TOK822_QSTRING, state->fullname);
} else {
token = tok822_alloc(TOK822_QSTRING, state->fullname);
}
Re: "Authentication-Results" header order
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.com: domain of u...@example.net designates X.X.X.X as permitted sender) smtp.mailfrom=u...@example.net; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=example.net -me
Re: regression: cleanup crashes if fullname contains only whitespace(s)
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/pickup[4476]: warning: > maildrop/D19752025C83: error writing 91309115983C: queue file write > error > Jun 30 13:31:13 vm-postfix8 postfix/master[4475]: warning: process > /usr/libexec/postfix/cleanup pid 4797 killed by signal 11 > > Attached workaround patch. > > It seems postfix-3.6.1 is also affected. The postfix-2 wasn't > affected, that's why I flagged it as a regression. > > Original downstream bug report including the debug analysis: > https://bugzilla.redhat.com/show_bug.cgi?id=1977732 > > Debug analysis and reproducer provided by Renaud M?trich And thank you for passing this on. Wietse
Re: regression: cleanup crashes if fullname contains only whitespace(s)
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 13:31:13 vm-postfix8 postfix/pickup[4476]: warning: > > maildrop/D19752025C83: error writing 91309115983C: queue file write > > error > > Jun 30 13:31:13 vm-postfix8 postfix/master[4475]: warning: process > > /usr/libexec/postfix/cleanup pid 4797 killed by signal 11 > > > > Attached workaround patch. > > > > It seems postfix-3.6.1 is also affected. The postfix-2 wasn't > > affected, that's why I flagged it as a regression. > > > > Original downstream bug report including the debug analysis: > > https://bugzilla.redhat.com/show_bug.cgi?id=1977732 > > > > Debug analysis and reproducer provided by Renaud M?trich > > > > And thank you for passing this on. This was introduced with Postfix 3.3.0, when "header_from_format=standard" became the default. Workaround: "header_from_format=obsolete". Wietse
Re: Search for free MX Backup Service
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 path for your mail is a particularly bad > idea. While I agree that MX backups are a pita, it's important to note that something very common these days are routing issues. I have a SMTP server in NYC area that (new to me) can't deliver email to people who use Level3/CenturyLink due to some things outside of my control. I'm 100% sure the reverse situation exists somewhere even though I may not know about it today. So my resolution to others' corporate greed and neck beard routing laziness is more than 1 MX. -Jim P.
