On 09.02.22 02:13, Wayne Spivak wrote:
The vendor I have, which is having the difficulty is still
saying he gets a self-signed cert… but as I showed in my
last email after I added Intermediate to the certificate,
everything was ok.
"*A* self-signed cert" would match the root cert that your have
Hello there
We stumbled upon an user account with Solr FTS, which returned no search
results for any given search query.
Further investigation revealed an issue between indexing mails and
querying the index.
The user name contains upper and lower case characters (eg.
some.u...@domain.net).
W
Woops, this time with better formatting.
On 09.02.22 12:21, Patrik Peng wrote:
Hello there
We stumbled upon an user account with Solr FTS, which returned no
search results for any given search query.
Further investigation revealed an issue between indexing mails and
querying the index.
The u
That I have, thank you Justina
From: dovecot On Behalf Of justina colmena ~biz
Sent: Tuesday, February 8, 2022 8:57 PM
To: dovecot@dovecot.org
Subject: RE: Certificate and showing a sign-cert not there
You shouldn't need a root in the full chain, because the client already has to
have the
We did that replacement for a while, but people complained. We have ARC signing
there, unfortunately it only works if you trust it.
Aki
> On 04/02/2022 23:10 Sebastian Nielsen wrote:
>
>
> I get it too. These appear because they don't replace either MAIL FROM: or
> Mime From: with the list
On February 4, 2022 11:56:53 AM AKST, Lev Serebryakov
wrote:
> After that I've got several DMARC reports about "spam" from my domain. All
> these reports are about my mailing list post.
>
Interesting. That's exactly how DMARC is supposed to work with reporting
enabled. So you've got that se
On 2022-02-09 14:33, Aki Tuomi wrote:
We did that replacement for a while, but people complained. We have
ARC signing there, unfortunately it only works if you trust it.
ARC-Authentication-Results: i=1; talvi.dovecot.org;
dkim=pass header.d=open-xchange.com header.s=201705 header.b=kWkbHwXq;
On 2022-02-09 16:16, Benny Pedersen wrote:
On 2022-02-09 14:33, Aki Tuomi wrote:
We did that replacement for a while, but people complained. We have
ARC signing there, unfortunately it only works if you trust it.
ARC-Authentication-Results: i=1; talvi.dovecot.org;
dkim=pass header.d=open-xcha
Google, Yahoo and Microsoft, the big providers all use ARC, and have used it
for years. But Wikipedia doesn't have much nice to say about it.
--> allows a receiving service to validate an email when the email's SPF and
DKIM records are rendered invalid by an intermediate server's processing. ARC
Le 09/02/2022 à 16:55, Benny Pedersen a écrit :
hope maillist users turn there dkim signers into sign only, not verify
aswell, verify must only happen in dmarc
I am a little bit confused.
- why not verify dkim ? It seems fine for your message. I get:
Received-SPF: Pass (mailfrom) identity=m
On 2022-02-09 17:25, Julien Salort wrote:
Le 09/02/2022 à 16:55, Benny Pedersen a écrit :
hope maillist users turn there dkim signers into sign only, not verify
aswell, verify must only happen in dmarc
I am a little bit confused.
- why not verify dkim ? It seems fine for your message. I get:
On February 9, 2022 12:31:23 PM GMT+01:00, Patrik Peng
wrote:
>Woops, this time with better formatting.
>
>On 09.02.22 12:21, Patrik Peng wrote:
>>
>> Hello there
>>
>> We stumbled upon an user account with Solr FTS, which returned no
>> search results for any given search query.
>> Further i
To all, we finally succeeded in solving the problem.
I believe changing the Servercert to Servercert + Intermediate solved the issue.
Thank you all for your help.
> when dkim pass there is no breakage, but dkim fail can lead to in some setups
> to make reject, even for maillists
> that is a design fail on dkim
I disagree. DKIM is doing its job. It is a design fail on the part of most
mailing list and/or lack of user's DKIM signatures.
Look at it logical
14 matches
Mail list logo
