Il giorno gio 16 mag 2024 alle ore 22:55 Jeremy Harris via Exim-users
ha scritto:
> ... (I'm guessing) say to look fist in a directory called conf.d -
> and we don't see the strace doing that either.
>
> I think you're not running the mysql configuration you think you are running.
That's the sta
On 17/05/2024 10:41, Gandalf Corvotempesta via Exim-users wrote:
That's the standard workflow .. mysql tries to look for my.cnf in the
/etc, then in /etc/mysql/my.cnf (and it finds there),
then in other location (not found, as expected)
But /etc/mysql/my.cnf exists and there are some includes in
> On 16/05/2024 22:32, Ian Z via Exim-users wrote:
> > But my question is about verification, and in
> > particular about the situation where a RCPT stage ACL will have verify
> > = recipient. The filter can't be evaluated at that stage.
>
> Verification consists of running the routing process; the
On 2024-05-16 Jeremy Harris via Exim-users wrote:
> On 16/05/2024 18:03, Andreas Metzler via Exim-users wrote:
>> On 2024-05-16 Slavko via Exim-users wrote:
>> [...]
>>> Anyway, would be great, if exim can use system's crypto library,
>>> to support all system's password hash formats.
>> crypte
On 17/05/2024 17:31, Andreas Metzler via Exim-users wrote:
I think you are mistaken or misunderstood me
Yup - I didn't read the code hard enough.
Thanks for the correction!
So (for the OP) - if the libc crypt() support blowfish,
then a "crypteq" comparison provides access from Exim.
--
Cheers,
On Fri, May 17, 2024 at 10:39:19AM GMT, Chris Siebenmann via Exim-users wrote:
Again sorry to persist in my obtuseness, but ...
> > > But my question is about verification, and in particular about
> > > the situation where a RCPT stage ACL will have verify =
> > > recipient. The filter can't be e
On Fri, May 17, 2024 at 11:22:45AM GMT, Ian Z via Exim-users wrote:
> And regardless of the answer to the above, if I do add no_verify to
> the redirect router in question, Lena's solution to the problem of
> getting the forwarding address into an ACL ceases to be available.
To cut short any spec
On 17/05/2024 19:22, Ian Z via Exim-users wrote:
But what do you mean by "properly"? How does a router do verification
"improperly"?
A router depends on all the options set for it. Typically, a router
will only depend on things that are already available at ACL time
(for example, the recipient
Is there any ftp location where a pre-release or a testing version of
exim is available to fetch and try ?
--
Jim Pazarena e...@paz.bz
Haida Gwaii - British Columbia - Canada
--
## subscription configuration (requires account):
## https://lists.exim.org/mailman3/postorius/lists/exim-us
On Fri, May 17, 2024 at 07:50:53PM GMT, Jeremy Harris via Exim-users wrote:
> > But what do you mean by "properly"? How does a router do
> > verification "improperly"?
> A router depends on all the options set for it. Typically, a router
> will only depend on things that are already available at
On Fri, 17 May 2024, Jim Pazarena via Exim-users wrote:
Is there any ftp location where a pre-release or a testing version of exim is
available to fetch and try ?
Such things are only available when developers have things
that are ready to be tested.
Not strictly ftp but the Exim Git site
On 17/05/2024 19:53, Jim Pazarena via Exim-users wrote:
Is there any ftp location where a pre-release or a testing version of exim is
available to fetch and try ?
The sources are at git://git.exim.org/exim.git
You get to build it yourself; but it's available all the time.
During the run-up to
Il giorno ven 17 mag 2024 alle ore 16:37 Jeremy Harris via Exim-users
ha scritto:
> If there were, then it should go on to try those files.
> This is not an Exim problem.
This is the issue:
https://jira.mariadb.org/browse/CONC-396
--
## subscription configuration (requires account):
## https:
On 17/05/2024 20:15, Ian Z via Exim-users wrote:
It doesn't look like the address_data way of getting the forwading
address will work for full sieve / exim filters, does it?
If
- the redirect router that runs the filter has not disabled itself
for verify (cf. the no_verify option)
- the rout
> > The corollary and implication of this is that if you have routers
> > that will only work properly once the message is fully received
> > (because they require headers or ACL variables only set then), you
> > need to mark them as no_verify, and possibly write verify_only
> > versions that do ad
On Fri, May 17, 2024 at 09:05:15PM GMT, Jeremy Harris via Exim-users wrote:
> > It doesn't look like the address_data way of getting the forwading
> > address will work for full sieve / exim filters, does it?
Chris already went most of the way to answering this (in the
negative). So feel free to
Dňa 17. mája 2024 16:31:08 UTC používateľ Andreas Metzler via Exim-users
napísal:
>ametzler@argenau:~$ /usr/sbin/exim -be "\${if crypteq {blah}{\N$(mkpasswd
>--method=bcrypt blah)\N}{yes}{no}}"
>yes
Eh, yes, that works. When i test that with -be i did mistake with escaping
of $ in hash...
IM
On Fri, May 17, 2024 at 08:40:49PM GMT, Slavko via Exim-users wrote:
> IMO would be great to mention it directly in {crypt} description,
> that it will use any hash format supported by system...
I find that part of the documentation already confusing enough :-(
I'd be perfectly happy if exim *on
18 matches
Mail list logo
