From: Maxime Ripard <maxime@cerno.tech>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: b4 bugs / future improvements
Date: Thu, 20 Oct 2022 10:49:30 +0200 [thread overview]
Message-ID: <20221020084930.vpu552rag6gdvmvm@houat> (raw)
In-Reply-To: <20221019080140.zc42aqi7gwjpvczs@houat>
[-- Attachment #1: Type: text/plain, Size: 1517 bytes --]
On Wed, Oct 19, 2022 at 10:01:40AM +0200, Maxime Ripard wrote:
> On Tue, Oct 18, 2022 at 04:18:04PM -0400, Konstantin Ryabitsev wrote:
> > > There's a bunch of things I have noticed in the recent weeks:
> > >
> > > - It looks like 87e0e464959c breaks msmtp which doesn't recognize the
> > > -f option, and will just error out
> >
> > There's got to be something else going on, since -f is required for sendmail
> > compatibility. The msmtp manpage specifically mentions that is supports it:
> > https://manpages.ubuntu.com/manpages/trusty/man1/msmtp.1.html
> >
> > (see under "options specific to sendmail mode")
>
> It might be the auto argument that confuses it then? I'll check.
So, here's the behaviour I'm seeing:
$ printf "From: <maxime@cerno.tech>\nTo: <maxime@cerno.tech>\nSubject: Test\n\nTest Test." | msmtp -i -f auto maxime@cerno.tech
msmtp: recipient address maxime@cerno.tech not accepted by the server
msmtp: server message: 504 5.5.2 <auto>: Sender address rejected: need fully-qualified address
msmtp: could not send mail (account default from /home/max/.config/msmtp/config)
If I drop the -f auto, it works:
$ printf "From: <maxime@cerno.tech>\nTo: <maxime@cerno.tech>\nSubject: Test\n\nTest Test." | msmtp -i maxime@cerno.tech
$ echo $?
0
It seems to be related to
https://github.com/marlam/msmtp-mirror/issues/51 except I don't have
set_from_header in my config. I've tried to use allow_from_override and
force it to off, and it didn't help.
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-10-20 8:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 15:36 b4 bugs / future improvements Maxime Ripard
2022-10-18 20:18 ` Konstantin Ryabitsev
2022-10-18 20:29 ` Mark Brown
2022-10-18 20:37 ` Konstantin Ryabitsev
2022-10-19 8:04 ` Maxime Ripard
2022-10-19 19:16 ` Konstantin Ryabitsev
2022-10-20 8:41 ` Maxime Ripard
2022-10-19 2:05 ` Rob Herring
2022-10-19 8:01 ` Maxime Ripard
2022-10-19 19:21 ` Konstantin Ryabitsev
2022-10-20 8:49 ` Maxime Ripard [this message]
2022-11-09 14:14 ` Maxime Ripard
2022-11-29 17:14 ` Konstantin Ryabitsev
2022-11-29 20:52 ` Maxime Ripard
2023-05-05 7:17 ` Maxime Ripard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221020084930.vpu552rag6gdvmvm@houat \
--to=maxime@cerno.tech \
--cc=konstantin@linuxfoundation.org \
--cc=tools@linux.kernel.org \
--cc=users@linux.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.