From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Can't push to 'next'
Date: Thu, 19 Sep 2024 14:38:02 +0200 [thread overview]
Message-ID: <96752e4d-230c-4a6f-9b02-1c783c6ae708@ipfire.org> (raw)
In-Reply-To: <1F547922-3F9E-43AA-BE76-B56C462CA1F4@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1469 bytes --]
Hi,
On 18.09.2024 14:48, Michael Tremer wrote:
> What do you mean by pushing? This looks like an email…
Of course - I meant e-mail.
> It looks like Postfix is unhappy with what your computer calls itself :) We have not made any changes to the mail system in a long time.
Me too.
This is what I - suddenly - get:
***SNIP***
root(a)Devel64-1: /git/ipfire-2.x # git send-email --annotate -1
/tmp/PWYGZ63w4H/0001-squid-Update-to-6.11.patch
Password for 'smtp://mfischer(a)submissions.ipfire.org:465':
5.5.2 <Devel64-1..>: Helo command rejected: Invalid name. Refer to
https://wiki.ipfire.org/postmaster for further information.
***SNAP***
Hostname is the same as always...:
***SNIP***
root(a)Devel64-1: /git/ipfire-2.x # cat /etc/hostname
Devel64-1
***SNAP***
Any idea what's the culprit or what I could do? Use *another* hostname
(after several years...)?
Best
Matthias
>
> -Michael
>
>> On 17 Sep 2024, at 19:46, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>
>> Hi,
>>
>> trying to push the latest 'squid' today - but it leaves me with:
>>
>>
>> ***SNIP***
>> ...
>> Password for 'smtp://mfischer(a)submissions.ipfire.org:465': [Correct
>> Password entered...]
>>
>> 5.5.2 <Devel64-1..>: Helo command rejected: Invalid name. Refer to
>> https://wiki.ipfire.org/postmaster for further information.
>> ...
>> ***SNAP***
>>
>> Can anyone confirm?
>>
>> Best
>> Matthias
>>
>
prev parent reply other threads:[~2024-09-19 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 18:46 Matthias Fischer
2024-09-18 12:48 ` Michael Tremer
2024-09-19 12:38 ` Matthias Fischer [this message]
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=96752e4d-230c-4a6f-9b02-1c783c6ae708@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