On 2019-02-26 22:26, Ian Zimmerman wrote:
> In fact it seems that iplsearch lookups are somewhat special when used
> in lists. And that is what interests me in this situation, because I
> want corkipset lookup to share the same specialness. I think the dot
> translation is an awful hack, and
I am still confused by this paragraph in section 10.12:
When an IPv6 address is converted to a string, dots are normally used
instead of colons, so that keys in lsearch files need not contain colons
(which terminate lsearch keys). This was implemented some time before
the ability to quote
On 26/02/2019 18:23, Ian Zimmerman via Exim-dev wrote:
> So at least this is a documentation bug.
Notes added; 52af443324 and c77d3d85fe.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim
details at http://www.exim.org/ ##
On 2019-02-26 17:28, Jeremy Harris wrote:
> > devuan-205f!35 exim$ cat strange-iplist
> > "::::::0102:0203" : data
> > ":::102:203" : also_data
> > 1.2.3.4 : more_data
>
>
> > devuan-205f!38 exim$ ./src/build-Linux-aarch64/exim -C
> > /home/itz/exim/exim.conf
On 26/02/2019 16:17, Ian Zimmerman via Exim-dev wrote:
> On 2019-02-26 11:21, Jeremy Harris wrote:
>
>>> And bingo, it seems to not work as documented:
>
> devuan-205f!35 exim$ cat strange-iplist
> "::::::0102:0203" : data
> ":::102:203" : also_data
> 1.2.3.4 :
On 2019-02-26 11:21, Jeremy Harris wrote:
> > And bingo, it seems to not work as documented:
devuan-205f!35 exim$ cat strange-iplist
"::::::0102:0203" : data
":::102:203" : also_data
1.2.3.4 : more_data
devuan-205f!38 exim$ ./src/build-Linux-aarch64/exim -C
On 26/02/2019 02:19, Ian Zimmerman via Exim-dev wrote:
> And bingo, it seems to not work as documented:
Which bit are you saying doesn't match docs?
So far, I see you giving a dot-group-hex ipv6 to an iplsearch
lookup, which is wrong per docs:
"key for an iplsearch lookup must be an IP address".
On 2019-02-25 18:19, Ian Zimmerman wrote:
> I thought I would start by looking what iplsearch does, because it is
> the closest lookup to what I'm dreaming about, semantically at least.
> And bingo, it seems to not work as documented:
>
> devuan-205f!33 exim$ ls `pwd`/strange-iplist
>
On 2019-02-24 19:51, Jeremy Harris wrote:
> On 24/02/2019 19:17, Jeremy Harris via Exim-dev wrote:
> > I don't know if a lookup done via the list-syntax
> > "hosts = corkipset:/filename"
> > will be different. Probably it will, sigh.
>
> Dots, and always seven.
>
> I tested by adding
>
>
On 24/02/2019 19:17, Jeremy Harris via Exim-dev wrote:
> I don't know if a lookup done via the list-syntax
> "hosts = corkipset:/filename"
> will be different. Probably it will, sigh.
Dots, and always seven.
I tested by adding
"pipeline_advertised_hosts =
On 24/02/2019 18:52, Jeremy Harris via Exim-dev wrote:
> On 24/02/2019 18:11, Ian Zimmerman via Exim-dev wrote:
>>> I'd expect conversion to unabbreviated form to have been done too.
>>
>> Do you mean I can expect an IPv6 address (mapped or not) to have exactly
>> 7 separators, whatever these
On 24/02/2019 18:11, Ian Zimmerman via Exim-dev wrote:
>> I'd expect conversion to unabbreviated form to have been done too.
>
> Do you mean I can expect an IPv6 address (mapped or not) to have exactly
> 7 separators, whatever these might be? If yes, there is no ambiguity.
That is my hope. But
On 2019-02-24 15:01, Jeremy Harris wrote:
> On 24/02/2019 07:47, Ian Zimmerman via Exim-dev wrote:
> >
> > How are the IPv4-mapped IPv6 addresses written in Exim?
> >
> > The straight translation to dots instead of colons would be ambiguous,
> > wouldn't it? Say, ...1.2.3.4 could mean
On 24/02/2019 07:47, Ian Zimmerman via Exim-dev wrote:
> On 2019-02-10 23:03, Jeremy Harris wrote:
>
>> If you can reliably detect the ipv6-ness, yes, that sounds like the
>> minimally intrusive way.
>
> How are the IPv4-mapped IPv6 addresses written in Exim?
>
> The straight translation to
On 2019-02-10 23:03, Jeremy Harris wrote:
> If you can reliably detect the ipv6-ness, yes, that sounds like the
> minimally intrusive way.
How are the IPv4-mapped IPv6 addresses written in Exim?
The straight translation to dots instead of colons would be ambiguous,
wouldn't it? Say,
On 10/02/2019 22:42, Ian Zimmerman via Exim-dev wrote:
> Turns out the underlying library wants IPv6 addresses colon separated;
> but in contexts where a host address is being tested for list
> membership, exim passes it to the lookup as dot-separated. This is of
> course documented in the Spec,
Turns out the underlying library wants IPv6 addresses colon separated;
but in contexts where a host address is being tested for list
membership, exim passes it to the lookup as dot-separated. This is of
course documented in the Spec, section 10.12.
Since IP addresses are the only things worth
On 04/02/2019 15:53, Ian Zimmerman via Exim-dev wrote:
> Is there a document about the preferred project style?
I've done a quick writeup here:
https://github.com/Exim/exim/wiki/Exim-coding-style
--
Cheers,
Jeremy
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim
On 2019-02-04 14:38, admin--- wrote:
> https://bugs.exim.org/show_bug.cgi?id=2369
>
> --- Comment #1 from Jeremy Harris ---
> My preferred dev platform, currently f28, does not - and building
> libcork fails, on an initial attempt.
How does it fail for you? It works for me.
$ autoreconf -i
On 2019-02-04 14:38, admin--- wrote:
> https://bugs.exim.org/show_bug.cgi?id=2369
>
> --- Comment #1 from Jeremy Harris ---
I much prefer email communication to bugzilla (perhaps not a surprise),
so replying here. I hope that's OK; if we reach any conclusions, I'll
summarize in the bug log.
20 matches
Mail list logo
