From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Helo command rejected: Invalid name
Date: Mon, 23 Sep 2024 21:13:19 +0200 [thread overview]
Message-ID: <1be0bd8d-d774-48eb-80ad-17578a145308@ipfire.org> (raw)
In-Reply-To: <d45f35c7620ad7e0e817df6472449f08@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2779 bytes --]
Hi,
ok, two dots then... Hm.
I saw them and feared it would be something like that.
But I found a solution:
***SNIP***
git send-email --annotate --smtp-domain=devel64-2.localdomain -1
***SNAP***
This command worked - I added the "--smtp-domain=<FQDN>". ;-)
Best
Matthias
On 23.09.2024 19:01, Peter Müller wrote:
> Hello Matthias,
>
> thank you for raising this.
>
> On 2024-09-23 16:54, Michael Tremer wrote:
>> Hello Matthias,
>>
>> I let Peter know. He will get back to you.
>>
>> -Michael
>>
>>> On 23 Sep 2024, at 17:07, Matthias Fischer
>>> <matthias.fischer(a)ipfire.org> wrote:
>>>
>>> Hi,
>>>
>>> I'm giving up.
>>>
>>> No matter what name I use (Devel-2, Devel, Justaname, Nothing), from
>>> one
>>> day to another I can't send git mails anymore:
>
> This is because for whatever reason your local application chose
> to submit an invalid HELO/EHLO banner when establishing the SMTP
> connection to our mail infrastructure.
>
> The culprit is the double dot ("devel.."), which should not be
> there. This might have been caused by an update on your end, or
> your machine having set a hostname only, rather than a complete
> FQDN (and Git not coping with that properly).
>
> If it takes longer to fix this, turning off HELO validation is an
> option, though I have to admit I am not really fond of that, especially
> not since it has been in place for years, and nothing has changed
> on this end. :-)
>
> Thanks, and best regards,
> Peter Müller
>
>>>
>>> ***SNIP***
>>> root(a)Devel64-2: /git/ipfire-2.x # git send-email --annotate -1
>>> /tmp/Zp2mVJvp60/0001-squid-Update-to-6.11.patch
>>> Password for 'smtp://mfischer(a)submissions.ipfire.org:465':
>>> 5.5.2 <Devel..>: Helo command rejected: Invalid name. Refer to
>>> https://wiki.ipfire.org/postmaster for further information.
>>>
>>> root(a)Devel64-2: /git/ipfire-2.x # hostname Justaname
>>>
>>> root(a)Devel64-2: /git/ipfire-2.x # git send-email --annotate -1
>>> /tmp/XKUXVyPmdy/0001-squid-Update-to-6.11.patch
>>> Password for 'smtp://mfischer(a)submissions.ipfire.org:465':
>>> 5.5.2 <Justaname..>: Helo command rejected: Invalid name. Refer to
>>> https://wiki.ipfire.org/postmaster for further information.
>>>
>>> root(a)Devel64-2: /git/ipfire-2.x # hostname
>>> Justaname
>>>
>>> root(a)Devel64-2: /git/ipfire-2.x # hostname Nothing
>>>
>>> root(a)Devel64-2: /git/ipfire-2.x # git send-email --annotate -1
>>> /tmp/yRTXjA1gp9/0001-squid-Update-to-6.11.patch
>>> Password for 'smtp://mfischer(a)submissions.ipfire.org:465':
>>> 5.5.2 <Nothing..>: Helo command rejected: Invalid name. Refer to
>>> https://wiki.ipfire.org/postmaster for further information.
>>> ***SNAP***
>>>
>>> If the "postmaster" would have an idea, I'd be thankful...
>>>
>>> Best
>>> Matthias
>>>
next prev parent reply other threads:[~2024-09-23 19:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 16:07 Matthias Fischer
2024-09-23 16:54 ` Michael Tremer
2024-09-23 17:01 ` Peter Müller
2024-09-23 19:13 ` Matthias Fischer [this message]
2024-09-23 20:11 ` Peter Müller
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=1be0bd8d-d774-48eb-80ad-17578a145308@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox