Mailing List Archive

[Bug 2669] dc_relay_nets
https://bugs.exim.org/show_bug.cgi?id=2669

--- Comment #1 from Jeremy Harris <jgh146exb@wizmail.org> ---
Here in the Exim project we don't necessarily know how the Debian config uses
that list. Either raise this as a Debian bug, or provide debug output showing
the failing use of the list.

--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[Bug 2669] dc_relay_nets [ In reply to ]
https://bugs.exim.org/show_bug.cgi?id=2669

--- Comment #2 from Andreas Metzler <eximusers@bebt.de> ---
(In reply to Jeremy Harris from comment #1)
> Here in the Exim project we don't necessarily know how the Debian config uses
> that list. Either raise this as a Debian bug, or provide debug output
> showing
> the failing use of the list.

It ends up verbatim in a macro which is used to fill a hostlist (hostlist
relay_from_hosts = MAIN_RELAY_NETS) which in turn is used in the rcpt acl in a
host statement.

There is probably a line length limit for either/both macros or/and host lists.

--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[Bug 2669] dc_relay_nets [ In reply to ]
https://bugs.exim.org/show_bug.cgi?id=2669

Heiko Schlittermann <hs@schlittermann.de> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |hs@schlittermann.de

--- Comment #3 from Heiko Schlittermann <hs@schlittermann.de> ---
I can reproduce it using a minimal config:
```
hostlist relay_nets = 192.168.93.0/24 : ... : 10.42.1.134
acl_smtp_rcpt = accept hosts = +relay_nets
```

and `swaks -f '<>' -t x@y -q rcpt --pipe 'exim -C /tmp/test.conf -bh
10.42.1.134'`

For the very last address (.134) I got 550. For the last but one (.133) 250.
Removing the spaces from the address list doesn't change the result.

--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[Bug 2669] dc_relay_nets [ In reply to ]
https://bugs.exim.org/show_bug.cgi?id=2669

--- Comment #4 from Heiko Schlittermann <hs@schlittermann.de> ---
But... removing the "??" from the list seems to help. And the last but one
entry was found because it is twice in the list and the first occurrence is
*before* the ??.

So, I think, the "list parser" stops working on the items that are suffixed
with the two question marks. And yes, it could tell you about the issue.

--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[Bug 2669] dc_relay_nets [ In reply to ]
https://bugs.exim.org/show_bug.cgi?id=2669

Heiko Schlittermann <hs@schlittermann.de> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID

--- Comment #5 from Heiko Schlittermann <hs@schlittermann.de> ---
Ah, totally normal behavior, a hostlist *may* contain hostnames, and
10.234.141.12?? is considered a host *name*. So Exim tries to do a PTR lookup
for the IP address in question, this fails and stop reading the hostlist (there
are options how to handle these host-not-found errors).

>>> sender host name required, to match against 10.234.141.12??
>>> looking up host name for 10.42.1.134
>>> IP address lookup using gethostbyaddr()
>>> IP address lookup failed: h_errno=1
LOG: no host name found for IP address 10.42.1.134

--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[Bug 2669] dc_relay_nets [ In reply to ]
https://bugs.exim.org/show_bug.cgi?id=2669

--- Comment #6 from Jeremy Harris <jgh146exb@wizmail.org> ---
I'm not seeing a "??" in the original list.

--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[Bug 2669] dc_relay_nets [ In reply to ]
https://bugs.exim.org/show_bug.cgi?id=2669

Heiko Schlittermann <hs@schlittermann.de> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |---

--- Comment #7 from Heiko Schlittermann <hs@schlittermann.de> ---
You're right. But mutt shows something like this:

192.168.90.180 : 192.168.90.181 : 192.168.90.183 : 192.168.90.191 :
192.168.90.193 : 192.168.90.195 : 10.235.0.21??: 10.235.0.22 : 10.235.0.24??:
10.235.0.25 : 10.235.0.26 : 10.235.0.27??: 10.235.0.28 : 10.235.0.29 :
10.235.0.37 : 10.233.0.65 : 10.233.1.41 : 10.233.6.193 : 10.233.8.220 :

And I used cut-and-paste from mutt to construct a sample config. Then I need a
bit more investigation here.

--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[Bug 2669] dc_relay_nets [ In reply to ]
https://bugs.exim.org/show_bug.cgi?id=2669

--- Comment #8 from Heiko Schlittermann <hs@schlittermann.de> ---
cat -A using the mail gives me:
...
192.168.90.193 : 192.168.90.195 : 10.235.0.21M-BM- : 10.235.0.22 :
10.235.0.24M-BM- :$
10.235.0.25 : 10.235.0.26 : 10.235.0.27M-BM- : 10.235.0.28 : 10.235.0.29 :$
10.235.0.37 : 10.233.0.65 : 10.233.1.41 : 10.233.6.193 : 10.233.8.220 :$
10.234.3.47 : 10.234.3.48 : 10.41.21.29 : 10.41.21.40 : 10.42.4.20 :$
...

So there are clearly some special characters, while in other places they are
not there. @OURVY: please can you attach your config as an attachment to this
bug?

And xxd from the initial mail (around the same line as presented above)

00001bb0: 3233 352e 302e 3237 c2a0 3a20 3130 2e32 235.0.27..: 10.2
~~~~ ~~

--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[Bug 2669] dc_relay_nets [ In reply to ]
https://bugs.exim.org/show_bug.cgi?id=2669

--- Comment #9 from Heiko Schlittermann <hs@schlittermann.de> ---
http://www.fileformat.info/info/unicode/char/00a0/index.htm

I'm tempted to close this bug :)

--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[Bug 2669] dc_relay_nets [ In reply to ]
https://bugs.exim.org/show_bug.cgi?id=2669

--- Comment #10 from Heiko Schlittermann <hs@schlittermann.de> ---
Created attachment 1349
--> https://bugs.exim.org/attachment.cgi?id=1349&action=edit
short bash script to reproduce the issue (contains UTF8 nbsp)

The attached script reproduces the behaviour. Watch out for the line
`>>> sender host name required, to match against 192.168.0.2`
which indicates, that 192.168.0.2 is considered as a host*name*, not an IP
address.

(Hint: the 192.168.0.2 is suffixed with a nonbrakeable UTF-8 space:
192.168.0.2<nbsp>:<space>192.168.0.3)

--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[Bug 2669] dc_relay_nets [ In reply to ]
https://bugs.exim.org/show_bug.cgi?id=2669

Heiko Schlittermann <hs@schlittermann.de> changed:

What |Removed |Added
----------------------------------------------------------------------------
Severity|bug |wishlist

--- Comment #11 from Heiko Schlittermann <hs@schlittermann.de> ---
Changed the importance to "wishlist": Warn in face of "unexpected" UTF-8
characters in the config and/or other files Exim reads. But first clarify what
is "unexpected".

- non-breakable-space?
- other? (with respect to UTF-8 in hostnames, local parts, ...)
- BOM at start of the config file (done
inaf542dcfa62fc2341e8253f10c5c778b887444b9)

--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[Bug 2669] dc_relay_nets [ In reply to ]
https://bugs.exim.org/show_bug.cgi?id=2669

--- Comment #12 from Jeremy Harris <jgh146exb@wizmail.org> ---
UTF-8 is acceptable, even required, in domain lists, because an original UTF-8
domain from an SMTP transaction is maintained in that form. I'm not sure about
hostnames though; anything we get from DNS should be A-label form, and
hostlists
used for checking received connections would be comparing against that.
Hostlists
used by routers/transports for destinations could, I think, potentially use
U-label form. It'd be interesting to hunt for any standards defining
disallowed
UTF-8 chars in DNS. Nbsp sounds like one, but who knows? And does it vary for
different RR types?

--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[Bug 2669] dc_relay_nets [ In reply to ]
https://bugs.exim.org/show_bug.cgi?id=2669

--- Comment #13 from OUVRY <eouvry@sqli.com> ---
I have edited the list dc_relay_nets with notpad++ and I have found some
"space" that where quoted differently ; by changing them with real space
character its running now.

Thank you for your search and it's a good idea to have a check on characters ;
do you always need the config file that was in error ?

--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[Bug 2669] dc_relay_nets [ In reply to ]
https://bugs.exim.org/show_bug.cgi?id=2669

--- Comment #14 from Heiko Schlittermann <hs@schlittermann.de> ---
Getting the configuration makes support a lot easier. The current issue shows
that the more verbatim the configuration is, the better the chance to spot the
issue is.

But, you're invited to first reduce the configuration to the minimum that
exposes the odd behavior (as I did for my investigations), and to avoid leaking
sensitive information.

--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##