On Wed, 20 Feb 2019, SH Development wrote:
To: Joan Moreau via dovecot
Jean did take over the list for a while when developing his FTS backend,
so you can be forgiven that he actually runs this list.
2. It was also suggested to rsync the directory, but the question was
brought up, and not
mick crane wrote:
Apache2 default install has this snake oil certificate
Can make a new one for apache
I won't go over some of the excellent points in previous posts,
but I will mention SAN as a third type of certificate you can make.
LetsEncrypt supports this type of certificate.
This is
On Thu, 14 Mar 2019, John Tulp wrote:
Encryption is just really not that much of a barrier any more.
Spoken like someone who hasn't actually tried breaking any of these
algorithms. It's not like every, or event most, cryptologists who
designs these algorithms, or analyzes them for
On Sat, 9 Feb 2019, Tamas Hegedus wrote:
I have users with file system folders, which contain mbox files and dovecot
indexes, in the ~/mail directory.
If I run dsync, I have an error message and the sync can not be completed:
Can't sync mailbox FOLDER_NAME: Mailbox isn't selectable
I could
On Fri, 12 Apr 2019, mj wrote:
What we do is: use https://github.com/trick77/ipset-blacklist to block IPs
(from various existing blacklists) at the iptables level using an ipset.
"www.blocklist.de" is a nifty source. Could you suggest other publically
available blacklists?
That way, the
On Thu, 11 Apr 2019, Marc Roos wrote:
Say for instance you have some one trying to constantly access an
account
Has any of you made something creative like this:
* configure that account to allow to login with any password
* link that account to something like /dev/zero that generates
Hello I am experiencing some strange issue with the dovecot, the web
round cube works fine but when I try to connect with an iPhone over
IMAP IMAPs it tells me that the account is disabled.
May 25 14:30:32 imap-login: Info: Aborted login (no auth attempts in 0 secs):
user=<>, rip=...
...
It?s also possible that the cache files USED to grow quite large in
previous versions and that now they are much more reasonable, but the
only way to reset their size appears to be to delete them and let
dovecot rebuild them.
I seem to recall these cache files ballooned in size when I did
as stated by Aki
> passdb {
> driver = static
> args = nopassword
>}
works fine and does what I want: accept any SMTP AUTH :-)
(Brings back memories of good fun I had with patched Qpopper snare
feeding custom messages to the hacker.)
Another alternative is to use the checkpassword hook
On Wed, 10 Jul 2019, Timo Sirainen wrote:
This is unexpected. But I don't see how it's a Dovecot bug. It seems
as if your compiler doesn't do padding correctly and then crashes
because it didn't do it correctly. I guess you're compiling this as
32bit?
Yes, 32-bit.
Is size_t 32bit or
On Thu, 11 Jul 2019, Lefteris Tsintjelis wrote:
Is it possible to enable statistics and keep track of the maximum number of
connections per user and also per IP?
If you can't get what you want from the stats module, you can always
post process the logs. Filter on user/IP, then keep a rolling
Hopefully, there is some fix for issue 3 which is beyond my
skill to fix.
Issue 1) Need recent gcc version
Building Dovecot versions <=2.2.x using gcc 3.4.4 worked,
but this gcc version fails to build 2.3.x properly: symptoms
include compile failures and executable
On Sun, 25 Aug 2019, Mauricio Tavares wrote:
Per [1] I decided to see what the response (base64-reply) I am
submitting to dovecot looks like:
echo 'base64-reply' | base64 -d
raub@example.compassword
I think there's a hidden null character netween username and password which
you can see
On Fri, 6 Sep 2019, zahn wrote:
I changed our old gcc compiler from the version: gcc-4.1.2-13.fc6 to the
newer one: gcc version 8.3.0 (GCC). Then I wanted to compile: Dovecot 2.3.7 and I
get the following error with ./configure
...
checking whether fd passing works... no
configure: error: fd
On Sat, 7 Sep 2019, Remo Mattei wrote:
Thanks Michael I will check with the free cert lets encrypt to test it.
If all your certificate subjects are domains under your control,
such as when they are aliases of each other (e.g. smtp.domain.tld,
pop3.domain.tld, imap.domain.tld,
On Wed, 7 Aug 2019, Aki Tuomi wrote:
> (Maybe this config variable should be renamed "ssl_client_ca".)
... except there already is ssl_client_ca_* settings used to validate
connections from dovecot.
So there is. Maybe "ssl_usercert_ca" then. A low-priority suggestion
to avoid newbies who
On Tue, 6 Aug 2019, telsch wrote:
if i cat ssl_ca and ssl_cert into one file and only use ssl_cert it's working
with 2.3.X
ssl_ca =
In the words of Montoya, "I do not think it means what you think it
means", referring to "ssl_ca". That file is not used to to establish
the trust chain to
On Mon, 22 Jul 2019, Timo Sirainen wrote:
Ah, okay, I see. submission_max_mail_size should be defined as uoff_t
instead of size_t in struct submission_settings and struct
submission_settings.
Thanks!
This appears to be the correct diagnosis as this patch (for 2.3.7) got
rid of the segfaults
Looking further into this segfault at
settings-parser.c:setting_copy():1519
*dest_size = *src_size;
*src_size points to type size_t (typedef unsigned long), a 4-byte
aligned value consistent with a 32-bit build. This is mismatched with
declared type
(gdb) whatis
On Fri, 27 Sep 2019, Aki Tuomi wrote:
On 27/09/2019 16:08 Marc Roos via dovecot wrote:
Is it possible to mail debug just one user? Maybe via the userdb?
You could try returning mail_debug=yes from userdb.
For raw IMAP logging, you can configure
protocol imap {
...
On Tue, 9 Jul 2019, Aki Tuomi wrote:
Hopefully, there is some fix for issue 3 which is beyond my
skill to fix.
Issue 1) Need recent gcc version
Issue 2) Cannot build with --enable-hardening
Issue 3) dovecot/doveconf segfaults on startup
Just to be sure ...
You did gmake clean; ./configure
On Wed, 4 Dec 2019, Aki Tuomi wrote:
We are pleased to release v2.3.9 of Dovecot. Please find it from
locations below
I compiled this and ran into the same crash problem I reported as
Issue 3 (v2.3.6) in
https://dovecot.org/pipermail/dovecot/2019-July/116413.html
The last 2 messages
On Tue, 29 Oct 2019, Ralf Hildebrandt wrote:
But how do I search for a sequence of multiple words?
doveadm import -u restore@backup.invalid mdbox:/home/copymail/mdbox "" mailbox INBOX BODY
"Greetings of the day"
doveadm import -u restore@backup.invalid mdbox:/home/copymail/mdbox "" mailbox
On Tue, 22 Oct 2019, Plutocrat wrote:
I recently wrote a script to check disk space every week and email me
an alert if there was less than 5G.
Every week? Unless you're using a telephone modem, an out of control mail
loop or being the victim of a joe-job can consume 5Gb of space in no time.
On Thu, 28 Nov 2019, Marc Roos wrote:
When changing in a working setup sendmail.mc
From this
MAILER(smtp)dnl
MAILER(procmail)dnl
To this
FEATURE(`local_lmtp',`[IPC]',`FILE /var/run/dovecot/lmtp')dnl
MAILER(local)dnl
I am getting these errors '501 5.6.0 Data format error' and '
Unrecognized
On Mon, 23 Sep 2019, Dave McGuire wrote:
On 9/23/19 8:36 PM, Steve Litt via dovecot wrote:
Alpine appears not to be ready for prime time to act as a window into
IMAP.
Wha...? Alpine/Pine have implemented IMAP for decades; that was one
of the first IMAP implementations to see widespread
On Wed, 25 Sep 2019, Plutocrat wrote:
On 23/09/2019 4:13 PM, Bernd Petrovitsch via dovecot wrote:
It's not directly a solution within dovecot but "fail2ban" exists.
Yes, I have fail2ban, but that bans based on IP address. And most mail
password attacks these days are distributed, and
On Fri, 11 Oct 2019, @lbutlr wrote:
Oct 09 16:02:50 imap-login: Info: Aborted login (auth failed, 5 attempts in 33 secs):
user=, xx.xx.xx.xx, PLAIN, TLS
This turns out to have been caused by the MUA attempting to connect to
port 25 (despite clearly showing port 587 in the MUA settings).
Greg Earle writes:
> Obviously I've changed the account password but I would really like to
> know how they were able to create e-mails on my system when ostensibly I
> would have assumed they could only read the account's e-mails via IMAP.
The INBOX is not read-only. There's nothing really
On Tue, Apr 23, 2024 at 7:33 AM wrote:
> > I am upgrading to postfix 3.9.0. I have not used DKIM in previous postfix
> > installs, but I
>> would like to start now with the new google rules. I have done some research
>> and opendkim
>> is the most recommended, however, other research states
30 matches
Mail list logo
