On 2023-01-07, Andrew C Aitchison via Exim-users wrote:
> On Sat, 7 Jan 2023, Julian Bradfield via Exim-users wrote:
...
>> But the question was, why is this panic-worthy? I thought the paniclog
>> was supposed to indicate that exim is seriously broken, not just
>> encountering some malformed
On Sat, 7 Jan 2023, Julian Bradfield via Exim-users wrote:
On 2023-01-06, Jeremy Harris via Exim-users wrote:
You could perhaps configure to not attempt to sign such messages
by using a suitable expansion for dkim_domain. If you can't
use something like $sender_address then
On 2023-01-06, Jeremy Harris via Exim-users wrote:
> You could perhaps configure to not attempt to sign such messages
> by using a suitable expansion for dkim_domain. If you can't
> use something like $sender_address then $max_received_line_length
> might work.
Or I could just reject them on
On 06/01/2023 08:12, Julian Bradfield via Exim-users wrote:
From time to time I get this. I know what the message means, and why
it happens, but why does this message go into the paniclog and disturb
me, when I don't care at all about it and can't see why I should?
You could perhaps configure
>From time to time I get this. I know what the message means, and why
it happens, but why does this message go into the paniclog and disturb
me, when I don't care at all about it and can't see why I should?
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details
Jeremy Harris via Exim-users wrote:
> On 12/12/2022 09:21, Victor Sudakov via Exim-users wrote:
> > acl_check_dkim:
> > accept add_header = :at_start:${authresults {$primary_hostname}}
>
> It's generally better to use ${authresults } in the data ACL, so that it
> can pick up other
Slavko via Exim-users wrote:
[dd]
>
> You can try to send messages to two recipients (target hosts)
> at once, then get message file from both and compare them to
> find difference.
This is actually how I started the thread, by sending one message to
two recipients at once, on FreeBSD and on
Dňa 12. decembra 2022 9:21:11 UTC používateľ Victor Sudakov via Exim-users
napísal:
>I'm using a single /etc/exim4/exim4.conf file as I have a FreeBSD
>background and am used to a single exim config. In fact, I hate the
>split stuff very much.
It must do not matter until you switch from one to
On 12/12/2022 09:21, Victor Sudakov via Exim-users wrote:
acl_check_dkim:
accept add_header = :at_start:${authresults {$primary_hostname}}
It's generally better to use ${authresults } in the data ACL, so that it
can pick up other results even when the message wasn't DKIM-signed.
Also,
Andrew C Aitchison via Exim-users wrote:
>
> > Slavko via Exim-users wrote:
> >> Dňa 9. 12. o 8:49 Victor Sudakov via Exim-users napísal(a):
> >>> Slavko via Exim-users wrote:
> Dňa 9. 12. o 5:15 Victor Sudakov via Exim-users napísal(a):
>
> > I've just sent two messages to you with
On Sun, 11 Dec 2022, Victor Sudakov via Exim-users wrote:
Slavko via Exim-users wrote:
Dňa 9. 12. o 8:49 Victor Sudakov via Exim-users napísal(a):
Slavko via Exim-users wrote:
Dňa 9. 12. o 5:15 Victor Sudakov via Exim-users napísal(a):
I've just sent two messages to you with Message-IDs
Slavko via Exim-users wrote:
> Dňa 9. 12. o 8:49 Victor Sudakov via Exim-users napísal(a):
> > Slavko via Exim-users wrote:
> >> Dňa 9. 12. o 5:15 Victor Sudakov via Exim-users napísal(a):
> >>
> >> > I've just sent two messages to you with Message-IDs
> >> > and
> >> >
> >>
> >> I got both
Dňa 9. 12. o 8:49 Victor Sudakov via Exim-users napísal(a):
Slavko via Exim-users wrote:
Dňa 9. 12. o 5:15 Victor Sudakov via Exim-users napísal(a):
> I've just sent two messages to you with Message-IDs
and
I got both and both has DKIM=pass in both, the exim (4.94.2) and rspamd
What OS
Slavko via Exim-users wrote:
> Dňa 9. 12. o 5:15 Victor Sudakov via Exim-users napísal(a):
>
> > I've just sent two messages to you with Message-IDs
> > and
> >
>
> I got both and both has DKIM=pass in both, the exim (4.94.2) and rspamd
What OS is exim running on?
--
Victor Sudakov
Dňa 9. 12. o 5:15 Victor Sudakov via Exim-users napísal(a):
I've just sent two messages to you with Message-IDs
and
I got both and both has DKIM=pass in both, the exim (4.94.2) and rspamd
(3.4) -- some headers (wrapped by me):
The small message:
Authentication-Results:
Bill Cole via Exim-users wrote:
> On 2022-12-05 at 11:00:21 UTC-0500 (Mon, 5 Dec 2022 16:00:21 +)
> Jeremy Harris via Exim-users
> is rumored to have said:
>
> > On 05/12/2022 15:38, Bill Cole via Exim-users wrote:
> >> If you use relaxed instead of relaxed/relaxed, the unspecified body
>
Slavko via Exim-users wrote:
> Dňa 5. decembra 2022 5:46:07 UTC používateľ Victor Sudakov via Exim-users
> napísal:
>
> >Can you give me an address to send a test mail to on one of your
> >Debian receivers? And we will look at what it says about the body.
>
> Be free to send test mesage to me,
Bill Cole via Exim-users wrote:
> On 2022-12-05 at 00:46:07 UTC-0500 (Mon, 5 Dec 2022 05:46:07 +)
> Victor Sudakov via Exim-users
> is rumored to have said:
>
> > Jeremy Harris via Exim-users wrote:
> [...]
> >>
> >> I guess there's also the dkim canonicalisation. Mine was
> >>
Dňa 5. decembra 2022 5:46:07 UTC používateľ Victor Sudakov via Exim-users
napísal:
>Can you give me an address to send a test mail to on one of your
>Debian receivers? And we will look at what it says about the body.
Be free to send test mesage to me, if your IP is not on RBLs. Try
small and
On 2022-12-05 at 11:00:21 UTC-0500 (Mon, 5 Dec 2022 16:00:21 +)
Jeremy Harris via Exim-users
is rumored to have said:
On 05/12/2022 15:38, Bill Cole via Exim-users wrote:
If you use relaxed instead of relaxed/relaxed, the unspecified body
canonicalization is "simple" which is never what
On 05/12/2022 15:38, Bill Cole via Exim-users wrote:
If you use relaxed instead of relaxed/relaxed, the unspecified body canonicalization is
"simple" which is never what anyone should use.
It shouldn't be. The docs say:
"the current implementation only supports signing with
the same
On 2022-12-05 at 00:46:07 UTC-0500 (Mon, 5 Dec 2022 05:46:07 +)
Victor Sudakov via Exim-users
is rumored to have said:
Jeremy Harris via Exim-users wrote:
[...]
I guess there's also the dkim canonicalisation. Mine was
relaxed/relaxed. Yours?
dkim_canon = relaxed
There's your
203
dkim_private_key = /usr/local/etc/exim/dkim/library.tomsk.ru-private.pem
dkim_canon = relaxed
dkim_sign_headers = Date:From:To:Subject:Message-Id:In-Reply-To
I think it's using some exim default algorithm.
As the docs say, the default for dkim_hash is sha256.
What should I
Victor Sudakov via Exim-users wrote:
>
> I should also note that the test mails were 7bit ascii messages, I've
> produced them with `echo "test test" | mail -s "test test" vas@XX
> vas@YY` on the sender host.
Interestingly, I've installed the DKIM verifier plugin on Thunderbird
(it
Jeremy Harris via Exim-users wrote:
> On 04/12/2022 11:33, Michael Haardt via Exim-users wrote:
> > Is it possible that the failing system does not accept 8bitmime?
> > Reencoding the message would break DKIM.
>
> Only if there's a non-exim gateway on the path we've
> not been told about.
iffering implies, I think, that the signature algorithm isn't
> involved. I was using sha256; what's yours?
Hmm, how do I figure out? Below is the complete sender configuration,
without hiding anything:
remote_smtp:
driver = smtp
message_size_limit = ${if > {$max_received_linelength}{998} {1}{0}}
On 04/12/2022 06:33, Victor Sudakov via Exim-users wrote:
I have sent 10 short messages from the library.tomsk.ru host:
echo "test test" | mail -s "test test" vas@XX vas@YY
and its 10 times dkim=pass on FreeBSD and 10 times dkim=fail on Debian
so I guess it's consistent.
However,
On 04/12/2022 11:33, Michael Haardt via Exim-users wrote:
Is it possible that the failing system does not accept 8bitmime?
Reencoding the message would break DKIM.
Only if there's a non-exim gateway on the path we've
not been told about. Exim doesn't recode.
--
Cheers,
Jeremy
--
## List
Victor Sudakov via Exim-users wrote:
> However, I've noticed that when I send a larger mail, like
>
> uuencode /usr/bin/vi vi | mail -s "test test" vas@XX vas@YY
>
> then 10 of the 10 mails on Debian have dkim=pass. So the message size
> or encoding is envolved somehow? What gives?
Is
Jeremy Harris via Exim-users wrote:
> On 02/12/2022 16:54, Victor Sudakov via Exim-users wrote:
> > I have an exim 4.95 installation sending DKIM-signed mails to two
> > other exim servers. On one of the receiving servers (FreeBSD,exim-4.95_5),
> > I see that the DKIM check is successful:
> >
> >
On 02/12/2022 16:54, Victor Sudakov via Exim-users wrote:
I have an exim 4.95 installation sending DKIM-signed mails to two
other exim servers. On one of the receiving servers (FreeBSD,exim-4.95_5),
I see that the DKIM check is successful:
Authentication-Results: XX;
iprev=pass
Dear Colleagues,
I have an exim 4.95 installation sending DKIM-signed mails to two
other exim servers. On one of the receiving servers (FreeBSD,exim-4.95_5),
I see that the DKIM check is successful:
Authentication-Results: XX;
iprev=pass (www.library.tomsk.ru)
On 23/07/2022 07:21, ozzloy via Exim-users wrote:
is there a good tutorial for the exim configuration file language?
http://exim.org/exim-html-current/doc/html/spec_html/
--
Cheers,
Jeremy
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at
thanks!
with your help, and a lot of reading, i've updated my config to prefix = in
front of all List* headers
https://git.sr.ht/~ozzloy/exim-configuration/tree/master/item/30_exim4-config_remote_smtp#L47
i sent myself emails and did not see "List*" as part of the DKIM
signature's headers!
is
Or is it "Mailing lists break DKIM?" ;-)
On 29/06/2022 10:37, Jeremy Harris via Exim-users wrote:
DKIM breaks mailinglists.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list -
On 2022-06-26 ozzloy via Exim-users wrote:
> i'm having trouble with dkim on mail sent to a mailing list that gets
> forwarded.
[...]
> if i send an email to linux-ker...@vger.kernel.org that email gets
> forwarded and fails spf and dkim.
>
DKIM breaks mailinglists.
--
Cheers,
Jeremy
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
i'm having trouble with dkim on mail sent to a mailing list that gets
forwarded.
i've posted a description here
https://git.sr.ht/~ozzloy/exim-configuration/tree/master/item/readme.org
if i send an email from an account on my exim server to my gmail, it passes
spf, dkim, dmarc.
On 09/01/2022 23:25, Slawomir Dworaczek via Exim-users wrote:
not this way, -BEGIN RSA PRIVATE KEY- there was never a space my
typing error
In that case, you're probably not using the file you think you are.
--
Cheers,
Jeremy
--
## List details at
On 09/01/2022 23:04, Slawomir Dworaczek via Exim-users wrote:
signing_init: privkey PEM-block import: error:0909006C:PEM routines:get_name:no
start line
DKIM: signing failed: PRIVKEY
Start privkey key line is
-BEGIN RSA PRIVATE KEY -
My sample file has
-BEGIN RSA PRIVATE
Helo
not this way, -BEGIN RSA PRIVATE KEY- there was never a space my
typing error
regards
Slawek
- Original Message -
From: "Slawomir Dworaczek via Exim-users"
To: "'Mailing List'"
Sent: Monday, January 10, 2022 12:04 AM
Subject: [exim] DKIM problem
delete space between Y and -should be:-BEGIN RSA PRIVATE KEY-
Originalmeddelande Från: Slawomir Dworaczek via Exim-users
Datum: 2022-01-10 00:08 (GMT+01:00) Till: 'Mailing
List' Ämne: [exim] DKIM problem HeloWhats Wrong
?signing_init: privkey PEM-block import
Helo
Whats Wrong ?
signing_init: privkey PEM-block import: error:0909006C:PEM
routines:get_name:no start line
DKIM: signing failed: PRIVKEY
Start privkey key line is
-BEGIN RSA PRIVATE KEY -
name private key is domainame.eu
regards
Slawek
--
## List details at
Dňa 14. októbra 2021 22:22:34 UTC používateľ Andy Bennett via Exim-users
napísal:
>Is there any reason why the default settings are not optimal?
>
>...and how to choose between relaxed and strict modes?
I mean not optimal for me, of course.
By derault "the header names listed in RFC4871 will
Dňa 14. októbra 2021 22:22:34 UTC používateľ Andy Bennett via
Exim-users napísal:
>Is there any reason why the default settings are not optimal?
>
>...and how to choose between relaxed and strict modes?
I mean not optimal for me, of course.
By derault "the header names listed in RFC4871 will be
Hi,
I remember how hard was good resources/tutorial about setting DKIM with
exim, a will provide you my observations and settings (which can be
good or not).
Thanks for this Slavko! It's exactly what I was looking for (and more),
especially the remarks about how it interacts with DMARC.
I
Hi,
Dňa Thu, 14 Oct 2021 14:34:19 +0100 Andy Bennett via Exim-users
napísal:
> I have been trying to find good resources for how DKIM is commonly
> deployed on The Internet: all the DKIM RFCs and early guides seem to
> shift almost all of the policy decisions to the implementors and
>
Hi,
I have been (finally!) looking at setting up DKIM on my outgoing exim
relay.
It is set up to handle several domains for incoming and outgoing mail.
I have been trying to find good resources for how DKIM is commonly deployed
on The Internet: all the DKIM RFCs and early guides seem to
Am 05.10.21 um 00:46 schrieb Jeremy Harris via Exim-users:
On 04/10/2021 16:35, Cyborg via Exim-users wrote:
Fedora 33 4.92.2-1
oh that's embarrassing for me // .. ofcourse it's 4.94.2-1 F33 latest
are you sure that isn't a log message generated by your
config? If not, can you get a
On 04/10/2021 16:35, Cyborg via Exim-users wrote:
Fedora 33 4.92.2-1
Assuming that's based on the project exim-4.92.2 release,
it's 2 years old. There are some 30 commits mentioning
DKIM between 4.92 and 4.95. However, I don't find either
"rejected DKIM" or "with invalid" in the current
Am 04.10.21 um 16:32 schrieb Jeremy Harris via Exim-users:
On 04/10/2021 15:10, Cyborg via Exim-users wrote:
while investigating a DKIM problem, this messages was found:
Distro? Version?
Fedora 33 4.92.2-1
best regards,
Marius
--
## List details at
On 04/10/2021 15:10, Cyborg via Exim-users wrote:
while investigating a DKIM problem, this messages was found:
Distro? Version?
--
Cheers,
Jeremy
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with
Hi,
while investigating a DKIM problem, this messages was found:
2021-10-04 14:38:43 1mXNEx-0057RV-3Q H=sender.de [sender-ip]
X=TLS1.3:TLS_AES_256_GCM_SHA384:256 CV=no rejected DKIM 1084 LAST: Mail
from sender-domain.de with invalid
a) invalid what???
I think a complete message would be
Evgeniy Berdnikov via Exim-users writes:
> The built-in value could be changed with dkim_sign_headers, but
> this patch gives much more reasonable default, IMHO.
I'm now running with this local config instead:
DKIM_SIGN_HEADERS =
On Thu, Aug 12, 2021 at 10:55:37AM +0200, Simon Josefsson via Exim-users wrote:
> Hi! I think I have ran into this problem:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939808
>
> My outgoing e-mails (like this one) is DKIM signed by Exim, and the
> signature covers (on sending, the
On 12/08/2021 13:19, Jeremy Harris via Exim-users wrote:
Don't waste your time. DKIM breaks on mailinglists, as
a general rule.
Not necessarily. If the list adds List-* headers, but does not change
the subject nor the body, and the DKIM signature does not include
headers that are
Don't waste your time. DKIM breaks on mailinglists, as
a general rule.
--
Cheers,
Jeremy
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
Hi! I think I have ran into this problem:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939808
My outgoing e-mails (like this one) is DKIM signed by Exim, and the
signature covers (on sending, the non-existing) List-Id header, which a
mailing list software inserts, breaking the DKIM
On 28 Apr 2021, at 9:22, SysAdmin EM via Exim-users wrote:
Could you tell me how to solve the problem? or what documentation to
read?
You need to fix whatever is generating the mail so that it stops sending
mail with such long lines. The most reliable way to do that is simply to
make it use
Could you tell me how to solve the problem? or what documentation to read?
Regards,
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
On 28/04/2021 13:29, SysAdmin EM via Exim-users wrote:
Hi everyone, sometimes in exim logs I see this message: DKIM: signing
failed: LONG_LINE
There was a line of more than 16kB in the input message.
--
Cheers,
Jeremy
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
o such
file or directory H=172.17.80.2 [172.17.80.2]: send() to 172.17.80.2
[172.17.80.2] failed:
I investigated this error but found little information.
### Configuration DKIM in exim
# DKIM
DKIM_DOMAIN = ${domain:$authenticated_id}
DKIM_FILE = /opt/exim/dkim/${domain:$authenticated_id}
DKIM_
On 21 Apr 2021, at 15:37, Wayne via Exim-users wrote:
Does this include lines in the body of the messages or just the
headers?
Both. See RFC5322 Section 2.1.1. MTAs can safely fix over-long header
lines by folding them, but to fix a body with over-long lines, they'd
need to either modify
On 21 Apr 2021, at 17:39, Wayne via Exim-users wrote:
Then I assume the body is being signed implicitly no matter what
headers
are selected?
Yes. A DKIM signature technically signs a selected set of headers and of
a hash of the body, both in a canonicalized form. Without the body hash,
it
On 4/22/21 5:39 AM, Wayne via Exim-users wrote:
> On Thu, Apr 22, 2021 at 05:11:30AM +0800, Gedalya via Exim-users wrote:
>> On 4/22/21 4:39 AM, Wayne via Exim-users wrote:
>>> I'm still confused as it seems like EXIM should be signing based on just
>>> headers content and not message body content
On Thu, Apr 22, 2021 at 05:11:30AM +0800, Gedalya via Exim-users wrote:
> On 4/22/21 4:39 AM, Wayne via Exim-users wrote:
> > I'm still confused as it seems like EXIM should be signing based on just
> > headers content and not message body content
>
> What makes you say that? DKIM normally signs
On 4/22/21 4:39 AM, Wayne via Exim-users wrote:
> I'm still confused as it seems like EXIM should be signing based on just
> headers content and not message body content
What makes you say that? DKIM normally signs the header and the body.
--
## List details at
On Thu, Apr 22, 2021 at 04:00:45AM +0800, Gedalya via Exim-users wrote:
> On 4/22/21 3:37 AM, Wayne via Exim-users wrote:
> > On Wed, Apr 21, 2021 at 08:21:02PM +0100, Jeremy Harris via Exim-users
> > wrote:
> >> On 21/04/2021 19:59, Wayne via Exim-users wrote:
> >>> 2021-04-21 14:34:48
On 21/04/2021 20:37, Wayne via Exim-users wrote:
Does this include lines in the body of the messages or just the headers?
Both. Body lines have to be processed for canonicalization before
adding into the hash value that becomes part of the signature.
The DKIM standard does not limit the
On 4/22/21 3:37 AM, Wayne via Exim-users wrote:
> On Wed, Apr 21, 2021 at 08:21:02PM +0100, Jeremy Harris via Exim-users wrote:
>> On 21/04/2021 19:59, Wayne via Exim-users wrote:
>>> 2021-04-21 14:34:48 1lZDwB-0003pb-TY DKIM: validation error: LONG_LINE
>>> 2021-04-21 14:34:48 1lZDwB-0003pb-TY
On Wed, Apr 21, 2021 at 08:21:02PM +0100, Jeremy Harris via Exim-users wrote:
> On 21/04/2021 19:59, Wayne via Exim-users wrote:
> > 2021-04-21 14:34:48 1lZDwB-0003pb-TY DKIM: validation error: LONG_LINE
> > 2021-04-21 14:34:48 1lZDwB-0003pb-TY DKIM: Error during validation,
> > disabling
On 21/04/2021 19:59, Wayne via Exim-users wrote:
2021-04-21 14:34:48 1lZDwB-0003pb-TY DKIM: validation error: LONG_LINE
2021-04-21 14:34:48 1lZDwB-0003pb-TY DKIM: Error during validation, disabling
signature verification: LONG_LINE
2021-04-21 14:34:48 1lZDwB-0003pb-TY <= XX@XXX
Greetings,
A certain device within our organization is relaying email via our EXIM
systems but EXIM is unable to sign the message. The vast majority of our
other messages are signed without issues.
Here is the corresponding error from the log.
2021-04-21 14:34:48 1lZDwB-0003pb-TY DKIM:
Gregory Edigarov via Exim-users (Mo 04 Jan 2021 08:49:34
CET):
> Hello, everybody.
>
> Recently I've found exim fails to check some DKIM records properly, so
> some domains need to be allowed no matter what.
> Tried to add something like this in DKIM acl:
Exim fails or the signatures are
Hello, everybody.
Recently I've found exim fails to check some DKIM records properly, so
some domains need to be allowed no matter what.
Tried to add something like this in DKIM acl:
accept domains = brokendkimdomains
this passed config file verification ok, but later shows errors in log
file
On 2020-11-18 10:25, James Strother wrote:
> I'm getting errors when I try to send outgoing emails that I don't
> have permission to access the dkim private key. If I set the key to be
> world-readable, then everything works perfectly. Setting the file to
> be world-readable is okay temporarily
On 18/11/2020 15:25, James Strother via Exim-users wrote:
Can you suggest
owners/permissions for the key?
Mine are root:exim 640
--
Cheers,
Jeremy
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with
My apologies if this question has been asked before, but I've been
searching and unable to come up with an answer.
I'm getting errors when I try to send outgoing emails that I don't have
permission to access the dkim private key. If I set the key to be
world-readable, then everything works
Mandi! Jeremy Harris via Exim-users
In chel di` si favelave...
> Run the exim that results in the transport be run,
> with debug turned on.
> If this test message is smtp-fed, that'll be the daemon.
> If commandline, it's the one you start.
> Grab stderr to file, for later perusal.
> Feed in
On 12/07/2020 22:51, Marco Gaiarin via Exim-users wrote:
>>> How can i debug trasport?! ;-)
Run the exim that forks to become the transport with
debug enabled (either via ACL action or commandline option).
>>> Ahem... some examples or some direct link in documentation? O;-)
>> The
Mandi! Jeremy Harris via Exim-users
In chel di` si favelave...
>> How can i debug trasport?! ;-)
>>> Run the exim that forks to become the transport with
>>> debug enabled (either via ACL action or commandline option).
>> Ahem... some examples or some direct link in documentation? O;-)
>
On 09/07/2020 22:48, Marco Gaiarin via Exim-users wrote:
> How can i debug trasport?! ;-)
>> Run the exim that forks to become the transport with
>> debug enabled (either via ACL action or commandline option).
>
> Ahem... some examples or some direct link in documentation? O;-)
The Exim
Mandi! Jeremy Harris via Exim-users
In chel di` si favelave...
How can i debug trasport?! ;-)
> Run the exim that forks to become the transport with
> debug enabled (either via ACL action or commandline option).
Ahem... some examples or some direct link in documentation? O;-)
Thanks.
On 08/07/2020 08:34, Marco Gaiarin via Exim-users wrote:
>>> How can i debug trasport?! ;-)
Run the exim that forks to become the transport with
debug enabled (either via ACL action or commandline option).
--
Cheers,
Jeremy
--
## List details at
Mandi! Mike Tubby via Exim-users
In chel di` si favelave...
>> I'm used, in exim on debian stretch (4.89-2+deb9u7) add something like:
>>
>> DKIM_CANON = relaxed
>> DKIM_SELECTOR = 2020
>> DKIM_DOMAIN = ${lc:${domain:$h_from:}}
>> DKIM_PRIVATE_KEY = ${if
>>
On 07/07/2020 13:58, Mike Tubby via Exim-users wrote:
> set (dkim_selector, dkim_dkim_canon, dkim_private_key, dkim_hash) =
> ${lookup mysql {SELECT selector,canon,private_key, hash FROM dkim WHERE
> domain='${quote_mysql:${dkim_domain}}' AND active=1}{$value}{false}}
That would be a whole
On 07/07/2020 00:23, Jeremy Harris via Exim-users wrote:
On 07/07/2020 00:01, Mike Tubby via Exim-users wrote:
remote_smtp:
driver = smtp
dkim_domain = ${lc:${domain:$h_from:}}
dkim_selector = ${lookup mysql{SELECT selector FROM dkim WHERE
On 07/07/2020 00:01, Mike Tubby via Exim-users wrote:
> remote_smtp:
> driver = smtp
> dkim_domain = ${lc:${domain:$h_from:}}
> dkim_selector = ${lookup mysql{SELECT selector FROM dkim WHERE
> domain='${quote_mysql:${dkim_domain}}' AND active=1}{$value}{false}}
>
On 02/07/2020 23:11, Marco Gaiarin via Exim-users wrote:
I'm used, in exim on debian stretch (4.89-2+deb9u7) add something like:
DKIM_CANON = relaxed
DKIM_SELECTOR = 2020
DKIM_DOMAIN = ${lc:${domain:$h_from:}}
DKIM_PRIVATE_KEY = ${if
Mandi! Jeremy Harris via Exim-users
In chel di` si favelave...
> Can you get a debug output for an attempted delivery?
Suffices something like an:
root@mail:~# exim -d -bhc 127.0.0.1
Mmm... no, seems that in this monde there's no delivery, so no debug in
trasport.
How can i
On 04/07/2020 05:55, Andreas Metzler via Exim-users wrote:
> On 2020-07-03 Jeremy Harris via Exim-users wrote:
>> On 02/07/2020 23:11, Marco Gaiarin via Exim-users wrote:
> [...]
>>> I've done the same on buster (exim 4.92-8+deb10u4)
> [...]
>
>> You didn't mention what, if any errors were
On 2020-07-03 Jeremy Harris via Exim-users wrote:
> On 02/07/2020 23:11, Marco Gaiarin via Exim-users wrote:
[...]
> > I've done the same on buster (exim 4.92-8+deb10u4)
[...]
> You didn't mention what, if any errors were logged.
> I'm guessing you're trying to use a tainted string as a
Mandi! Jeremy Harris via Exim-users
In chel di` si favelave...
> You didn't mention what, if any errors were logged.
No.
> I'm guessing you're trying to use a tainted string as a filename.
> If so, the usual rules apply: you must now verify the string in
> a way that Exim understands, so as
On 02/07/2020 23:11, Marco Gaiarin via Exim-users wrote:
>
> I'm used, in exim on debian stretch (4.89-2+deb9u7) add something like:
>
> DKIM_CANON = relaxed
> DKIM_SELECTOR = 2020
> DKIM_DOMAIN = ${lc:${domain:$h_from:}}
> DKIM_PRIVATE_KEY = ${if
>
Mandi! Andreas Metzler via Exim-users
In chel di` si favelave...
> are these macros actually set correctly? Check with
> /usr/sbin/exim4 -bP transport remote_smtp | grep dkim
seems yes...
root@mail:~# exim4 -bP transport remote_smtp | grep dkim
dkim_canon = relaxed
dkim_domain =
On 2020-07-03 Marco Gaiarin via Exim-users wrote:
> I'm used, in exim on debian stretch (4.89-2+deb9u7) add something like:
> DKIM_CANON = relaxed
> DKIM_SELECTOR = 2020
> DKIM_DOMAIN = ${lc:${domain:$h_from:}}
> DKIM_PRIVATE_KEY = ${if
>
I'm used, in exim on debian stretch (4.89-2+deb9u7) add something like:
DKIM_CANON = relaxed
DKIM_SELECTOR = 2020
DKIM_DOMAIN = ${lc:${domain:$h_from:}}
DKIM_PRIVATE_KEY = ${if
Thanks to pointers from this list, I now have ed25519 keys working as
expected.
My platform is opensuse 15.1.
Solution was to build exim-4.93 from source with GnuTLS.
My ISP's DNS tool is happy with the smaller ed25519 key.
Pity most MTAs (even gmail) don't recognise ed25519 yet, but the day
On 2020-03-05 at 09:02 +, Graham McAlister via Exim-users wrote:
> Suspect my distro build uses openssl instead of gnutls and my version
> of openssl is 1.1.0 but ed25519 support is in 1.1.1
>
> So, either I build exim to use gnutls, or I upgrade openssl to 1.1.1
>
> That's my plan, and will
Thanks for your reply.
I am using Exim version is 4.88, the standard package in the OpenSuse
15.1 distro
openssl version is 1.1.0
Perhaps here lies my issue? AFAIK ed25519 is in openssl 1.1.1
exim -bP macros | grep ED25519
returns nothing
So I assume my binary doesn't support it? I'm
1 - 100 of 482 matches
Mail list logo
