Random addition to this thread, in case it helps ... recently had
a client reporting certificate problems after Letsencrypt changed
their root certificate late last year. Long story short: it boiled
down to the fact he was using an ancient version of Outlook which
You shouldn't need a root in the full chain, because the client already has to
have the root cert, but you do need all the links in the chain up to the root.
On February 8, 2022 4:13:06 PM AKST, Wayne Spivak wrote:
>Justina,
>
>
>
>The vendor I have, which is having the difficulty is still
Justina,
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.
So ServerCert, Intermediate, Root in same file should solve this?
Wayne
From:
Dear list,
I built a dovecot package for openindiana (which is a Solaris
derivative) from latest version 2.3.18. Everything compiles and builds
fine without any issue. Even subsequent installation and startup of main
dovecot process works as expected. But execution of
In general:
Lots of mail servers out in the wild do not require TLS or even bother to
verifying TLS certificates when connecting to a remote server on port 25.
However, desktop and mobile email *clients* tend to be much stricter about
verifying server certificates when connecting via SSL or
Hi Christian,
Thanks for answering. I think you found my issue.
I now get:
[root@mcq wbs]# openssl s_client -connect mcq.sbanetweb.com:993 -servername
mcq.sbanetweb.com
CONNECTED(0003)
depth=2 C = US, O = "Entrust, Inc.", OU = See www.entrust.net/legal-terms,
OU = "(c) 2009 Entrust, Inc. -
On 8. Feb 2022, at 12.27, itan...@univ-brest.fr wrote:
service auth-worker {
client_limit = 1
idle_kill = 0
process_limit = 600
process_min_avail = 0
service_count = 1
vsz_limit = 18446744073709551615 B
}
What dovecot version is this? with 2.3.17 or later you should
On 2022-02-08 15:53, Wayne Spivak wrote:
Hi -
I am running Postfix 3.6.4 with Dovecot 2.3.17.1 (476cd46418).
I have a multi-signed cert from Entrust.
The cert works fine on port 25.
Certificates on port 25 verify ok for me.
However, on Port 587 I get an error: c
Certificates on port
Folks:
I'm migrating to Dovecot to provide IMAP services for my personal network.
I have more than a couple of decades of mail in multiple (1000+) mbox
mail files, but I don't care to expose all of those to IMAP.
Is there any way to filter out what mail folders Dovecot will LIST and
provide
One extra thing, this to be 200% perfect, was the ability to send a
message to the sender telling that the message got queue due to the end
user's mailbox being full.
would it be possible? this may be postfix related but if anyone can
help.
Thanks,
On 2022-02-08 14:22, Jorge Bastos wrote:
Hi -
I am running Postfix 3.6.4 with Dovecot 2.3.17.1 (476cd46418).
I have a multi-signed cert from Entrust.
The cert works fine on port 25.
However, on Port 587 I get an error: c
[root@mcq wbs]# openssl s_client -connect mcq.sbanetweb.com:993 -servername
mcq.sbanetweb.com
On 08.02.22 15:37, Sami Ketola wrote:
Maybe you should check the extdata plugin for pigeonhole:
https://doc.dovecot.org/configuration_manual/sieve/plugins/extdata/
I had seen that. But after reading that page it appeared to my rather as
a lookup for static data, e.g. the vacation message
> On 8. Feb 2022, at 3.59, Hadmut Danisch wrote:
>
> I found that dovecot's sieve has some database connections, e.g. LDAP or
>
> https://doc.dovecot.org/configuration_manual/sieve/dict/
>
> but rather to receive the whole sieve script for a given recipient as the
> owner of the mailbox.
>
Hi Lucas,
Oh, it's so damn simple!
Thank you!!
Thank you all others aswell, i've read all info sent, thanks!!
Jorge
On 2022-02-07 22:57, Lucas Rolff wrote:
An option is to use
https://doc.dovecot.org/settings/core/#core_setting-quota_full_tempfail
- you can configure it e.g.
protocol
>> I want postfix not to discard the message imediatly when a mailbox is
>> full, i mean when postfix tries to deliver it to dovecot lmtp.
> if you set "quota_full_tempfail" to "yes" in dovecots lda.conf, it
> should answer with a temporary failure-code 422 instead of permanent
> 522. (at least
> On 8. Feb 2022, at 12.27, itan...@univ-brest.fr wrote:
>
> service auth-worker {
> client_limit = 1
> idle_kill = 0
> process_limit = 600
> process_min_avail = 0
> service_count = 1
> vsz_limit = 18446744073709551615 B
> }
What dovecot version is this? with 2.3.17 or later
Is it possible with sieve to :
1. get sender of an email
2. lookup if this sender is present in an mailbox
3. if the sender is known, change the subject of the email.
if the sender is not known, do nothing.
4. put/leave message in inbox.
or maybe use dictionary (not really familiar with
Hello,
thank you for your advices and sorry to not have detailed infra
ismael> I'm currently benchmarking new hardware aimed to serve around
ismael> 70k users For now, our IMAP server have 13k users.
This doesn't help us help you. Is this a new rasperry Pi 4? Is it a
Dual CPU AMD Rzyzen
__
I'm using this dedicated address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.
El 8/2/22 a les 10:02, dc...@dvl.werbittewas.de ha escrit:
Am 07.02.22 um 23:41
Am 07.02.22 um 23:41 schrieb Jorge Bastos:
> I want postfix not to discard the message imediatly when a mailbox is
> full, i mean when postfix tries to deliver it to dovecot lmtp.
> Is it possible to change the behavior to something like what postfix
> does when he tries to deliver a message
> On 08/02/2022 09:09 Narcis Garcia wrote:
>
>
> +1
>
>
>
> Narcis Garcia
>
> __
> I'm using this dedicated address because personal addresses aren't
> masked enough at this mail public archive. Public archive administrator
> should fix this against automated addresses
21 matches
Mail list logo
