Send inn-workers mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."
Today's Topics:
1. Re: INN and docker default hostnames (Richard Kettlewell)
2. Re: INN and docker default hostnames (Russ Allbery)
3. Re: [#6D2-CD8-83E2A] INN and docker default hostnames
(Russ Allbery)
4. Re: [#6D2-CD8-83E2A] INN and docker default hostnames
(Grant Taylor)
5. Re: INN and docker default hostnames (Richard Kettlewell)
6. Re: INN and docker default hostnames (Russ Allbery)
----------------------------------------------------------------------
Message: 1
Date: Sat, 4 Apr 2020 18:30:44 +0100
From: Richard Kettlewell <[email protected]>
To: [email protected]
Subject: Re: INN and docker default hostnames
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
On 04/04/2020 18:07, Grant Taylor wrote:
> I seriously question if the failure is in INN itself or the Debian
> package manager.
>
> I bet that innconfval is working exactly like it should and that
> something is not liking what innconfval is returning.
I see nothing in the man page for innconfval that says it critiques
aspects of the local environment even when asked for unrelated
configuration parameters, so I suspect you would lose your bet, unless
of course you are aware of some other specification for the program.
> I'm not convinced that this is a bug in INN.? In fact, I think this is a
> bug in the installer / script that it's using.
OK, how should the postinst find pathdb, ovmethod, etc, then, in your
opinion?
> I suspect it's something outside of INN that's not liking what it's seeing.
Suspect? There is no mystery about the causes of the behavior observed.
The question is what should be done about it.
>> My suggestion is that INN should believe getaddrinfo(), i.e. remove
>> the strchr() check for '.'.
>
> Names without a period in them are unqualified (in the DNS world).
>
> INN "SHOULD" (in the RFC sense of the word) have a FQDN to work with.
> Much like email servers SHOULD have an FQDN.
Why?
What it actually needs is a valid hostname for the environment it's
running in. And it's got one, it just doesn't like it.
INN is the odd one out here: so far my personal experience is that mail
servers, web servers, database servers and middleware for specialized
hardware all work fine...
ttfn/rjk
------------------------------
Message: 2
Date: Sat, 04 Apr 2020 10:41:17 -0700
From: Russ Allbery <[email protected]>
To: [email protected]
Subject: Re: INN and docker default hostnames
Message-ID: <[email protected]>
Content-Type: text/plain
Richard Kettlewell <[email protected]> writes:
> However, INN hates it, and refuses to even install:
INN refuses to run with a single component hostname because the chances
are low that it's globally unique, and historically INN considers it
unsafe to run without an FQDN to put in the Path. This is an old, old
check, predating containers and Docker and all of that world.
I do think it's at least mildly dubious to run INN without an FQDN to put
into the Path header. It's kind of obnoxious for innconfval to fail
(that's because there's only one inn.conf parser and it behaves the same
way for everything).
The quick fix would probably be to find a way to preseed the domain name
so that the package installation succeeds (which may not be supported by
the Debian packaging currently). I'm a little dubious about relaxing this
check in general, since putting unqualified hostnames in the Path header
and using them for loop checking sounds likely to cause weird problems.
--
Russ Allbery ([email protected]) <https://www.eyrie.org/~eagle/>
Please send questions to the list rather than mailing me directly.
<https://www.eyrie.org/~eagle/faqs/questions.html> explains why.
------------------------------
Message: 3
Date: Sat, 04 Apr 2020 10:45:01 -0700
From: Russ Allbery <[email protected]>
To: [email protected], [email protected]
Subject: Re: [#6D2-CD8-83E2A] INN and docker default hostnames
Message-ID: <[email protected]>
Content-Type: text/plain
Richard Kettlewell <[email protected]> writes:
> I think someone has subscribed some organization's support address to
> inn-workers?
I've unsubscribed [email protected] from the list, which I think was
the problem address. (Please feel free to resubscribe from an address
that doesn't send out confirmation messages like this.)
--
Russ Allbery ([email protected]) <https://www.eyrie.org/~eagle/>
Please send questions to the list rather than mailing me directly.
<https://www.eyrie.org/~eagle/faqs/questions.html> explains why.
------------------------------
Message: 4
Date: Sat, 4 Apr 2020 12:04:17 -0600
From: Grant Taylor <[email protected]>
To: [email protected]
Subject: Re: [#6D2-CD8-83E2A] INN and docker default hostnames
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
On 4/4/20 11:45 AM, Russ Allbery wrote:
> I've unsubscribed [email protected] from the list, which I think
> was the problem address.
Thank you Russ.
--
Grant. . . .
unix || die
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4013 bytes
Desc: S/MIME Cryptographic Signature
URL:
<https://lists.isc.org/pipermail/inn-workers/attachments/20200404/f5050260/attachment-0001.bin>
------------------------------
Message: 5
Date: Sat, 4 Apr 2020 19:35:53 +0100
From: Richard Kettlewell <[email protected]>
To: [email protected]
Subject: Re: INN and docker default hostnames
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
On 04/04/2020 18:41, Russ Allbery wrote:
> Richard Kettlewell <[email protected]> writes:
>
>> However, INN hates it, and refuses to even install:
>
> INN refuses to run with a single component hostname because the chances
> are low that it's globally unique, and historically INN considers it
> unsafe to run without an FQDN to put in the Path. This is an old, old
> check, predating containers and Docker and all of that world.
Of course it isn't actually going to run with a dotless pathhost; it
will be properly configured subsequent to installation.
> I do think it's at least mildly dubious to run INN without an FQDN to put
> into the Path header. It's kind of obnoxious for innconfval to fail
> (that's because there's only one inn.conf parser and it behaves the same
> way for everything).
Yes.
> The quick fix would probably be to find a way to preseed the domain name
> so that the package installation succeeds (which may not be supported by
> the Debian packaging currently). I'm a little dubious about relaxing this
> check in general, since putting unqualified hostnames in the Path header
> and using them for loop checking sounds likely to cause weird problems.
I see where you're coming from, but dotless pathhost isn't actually the
goal here. It's not even going to exchange any articles during the
'docker build' step, that only happens much later.
If Debian had a way to preseed INN configuration then I'd use it, but it
doesn't, so here we are...
ttfn/rjk
------------------------------
Message: 6
Date: Sat, 04 Apr 2020 11:42:23 -0700
From: Russ Allbery <[email protected]>
To: [email protected]
Subject: Re: INN and docker default hostnames
Message-ID: <[email protected]>
Content-Type: text/plain
Richard Kettlewell <[email protected]> writes:
> If Debian had a way to preseed INN configuration then I'd use it, but it
> doesn't, so here we are...
Thinking about this some more, I'm pretty sure you could drop a
configuration file in /etc/news/inn.conf before installing inn2 and that
would fix the problem. Any FQDN would be fine, even something ending in
example.com.
--
Russ Allbery ([email protected]) <https://www.eyrie.org/~eagle/>
Please send questions to the list rather than mailing me directly.
<https://www.eyrie.org/~eagle/faqs/questions.html> explains why.
------------------------------
Subject: Digest Footer
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
------------------------------
End of inn-workers Digest, Vol 118, Issue 2
*******************************************
