On 2018-03-04, Brad Smith wrote:
> Trying to build Dovecot 2.2.34 on OpenBSD fails.
>
> This seems to have been introduced by this commit..
> https://github.com/dovecot/core/commit/4a9020ed888caf03fd3132a30a7818b01daa4b9d
This is libtool-related. GNU libtool prints a warning but is able to link:
The code in ssl_protocols_to_min_protocol() to convert ssl_protocols to
min/max values can't cope with strings containing "!SSLv2".
dovecot: imap-login: Fatal: Unknown ssl_protocols setting: Unrecognized
protocol 'SSLv2'
This string might be configured explicitly by the user, or if the user
hasn
On 2018-06-07, Ricardo Branco wrote:
> Solr 7 returns JSON by default but fts_solr requires XML.
>
> Would be good to have wt=xml added to the query to force it to xml all the
> time, this would prevent errors if solr has
> not had xml set as default for index.
This is already done in Dovecot 2
On 2018/11/30 10:55, Frederick Thomssen wrote:
> Hi guys
>
> Why do I get these e-mails?
You were subscribed to the dovecot mailing list but probably had it set
to 'mail delivery: disabled' (possibly you read messages via archive
and have subscribed so you can reply, but don't want to receive ema
Originally reported here -
https://marc.info/?l=openbsd-ports&m=159731598419071&w=2
OpenBSD's printf functions have a (mostly annoying but occasionally
useful) feature where they generate a syslog entry if printf %s format
is called with a null pointer.
It is tripped in lmtp/lda deliveries with 2
On 2020-09-10, Timo Sirainen wrote:
> We had a bunch of tests, but this required a large input buffer to be =
> feeded to the zstd compression code, which didn't happen all that =
> easily. I only accidentally caught it with the same test as I wrote for =
> reproducing the xz bug.
>
> Here's the l
On 2020-09-07, Scott Q. wrote:
>
> Not sure if I mentioned it but I'm on FreeBSD too. I wonder if any
> of the patches FreeBSD applies automatically is causing this. I looked
> through them but couldn't find anything obvious that might cause this
FWIW also seen with 2.3.11.3 on OpenBSD, the only
11.3;
maybe they'll go away after the sync has finished though.
(Plus the index files themselves are in solr rather than anything
Dovecot-specific, admittedly I am using a newer schema version on the new
server though, the old one was ''
and new is 2.0).
> On Thursday, 15/
I'm seeing this on some mailboxes with 2.13 on OpenBSD amd64 (recent
snapshot):
dovecot: imap(sthen)<47220>: Panic: file istream.c: line 332
(i_stream_read_memarea): assertion failed: (!stream->blocking)
Using sieve, imapsieve, replicator, zlib (zlib_save = lz4 and has
been for some time, so the
On 2021-01-25, @lbutlr wrote:
> I get a LOT of mail that is pointlessly HTMLized (including on this list)
*especially* on this list, for some reason.
On 2021-01-24, Stuart Henderson wrote:
> I'm seeing this on some mailboxes with 2.13 on OpenBSD amd64 (recent
> snapshot):
>
> dovecot: imap(sthen)<47220>: Panic: file istream.c: line
> 332 (i_stream_read_memarea): assertion failed: (!stream->blocking)
>
>
ooking at the visible bits in that mdbox file I don't think I will be
able to identify the various correspondents enough to get their
permission to provide the whole file. (The list mail is public anyway,
but from what I can make out past the lz4 there's at least some private
mail in th
On 2021-01-30, Frank Elsner wrote:
> Hi community,
>
> when doing imapsync to my dovecot server (Host2) I get the following
>
> Host2 capability before authentication: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID
> ENABLE IDLE LITERAL+ STARTTLS AUTH=PLAIN AUTH=LOGIN AUTH
> DEBUG: .../IO/Socket/SSL.pm:111
On 2021-02-08, Joan Moreau wrote:
> Well, in the function xxx_build_more of FTS plugin, the data received in
> the original PDF, not the output of pdftotext
>
> Can you clarify where do you put your log in the solr plugin , so I can
> check the situation in the xapian plugin ?
The log is partic
On 2021/02/08 21:33, Joan Moreau wrote:
> Yes , once again : output of the decoder is fine, I also put log inide the
> dovecot core to
> check whether data is properly transmitted, and result is that it is (i.e.
> dovecot core
> receives the proper output of pdftotext via the decoder
>
> Now, th
On 2021-03-14, lja@koti wrote:
> # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf
That's nowhere near the latest Dovecot.
On 2021-03-18, Marc wrote:
>
> [@ sbin]# doveadm -f table -o
> mail_location=mdbox_deleted:/home/popusers/testtest/mdbox:INDEX=/home/popindex/testtest/index
> fetch -u testtest 'guid' mailbox INBOX 2> /dev/null
> 3c967f33b8aea671f3551db1ea8e33e9
> 6fa01ccc103a7009c7b940657dbcd72c
> ba955a6d62189
On 2021-06-29, @lbutlr wrote:
> On 27 Jun 2021, at 05:38, Andreas M. Kirchwitz wrote:
>> Dovecot 2.3.15
>
> On FreeBSD 13.0 I am seeing that my installed version, 2.3.13_1 is the newest
> dovecot.
>
> I've been checking since I have some CVEs on that version, but no update yet.
>
> Any timeline
On 2021-07-09, Saarts, Erik wrote:
> We have domain A on cloud, from where mail gets forwarded to our local
> server to domain B. Forwarding is done in
> SPF-compliant way by using SRS (this part we have no control
> over).=C2=A0=C2=A0This SRS address ends up in
> Return-Path header, and sieve vac
On 2021-07-15, Sebastian wrote:
> Best solution is to offer a webmail with TOTP or SQRL or similiar secure =
> auth method.
>
> Then have that webmail adds IP or country into trusted list, so if you =
> want to access IMAP mail or SMTP mail from hotel wifi, you have to =
> simply do one single log
Continuation of https://dovecot.org/pipermail/dovecot/2021-January/121235.html
- I didn't get a reply to my last mail, so ended up deleting the various
messages (or in some cases mailboxes) and stopped running into problems for
a while, but am now seeing it again.
I get "i_stream_read_memarea: ass
On 2021/08/16 13:32, Timo Sirainen wrote:
> On 13. Aug 2021, at 19.10, Stuart Henderson wrote:
> > I get "i_stream_read_memarea: assertion failed: (!stream->blocking)" when
> > accessing some messages. Backtrace and doveconf -n below.
>
> Does the attached patch fix it?
It does - thank you.
On 2021-09-07, N wrote:
> Separate subject, but couldn't help but notice, SSL3 is being used?
> Wasn't SSL3 retired because of POODLE exploits? Can someone more
> knowledgeable confirm?
"sslv3 alert certificate unknown" does not mean that SSLv3 is used.
On 2021-09-07, Amol Kulkarni wrote:
> After I replaced my certificate with a new one yesterday, I'm seeing some
> ssl related errors. There are successful pop/imap logins using SSL also. So
> I think the certificate in itself is fine. No user has complained as yet,
> so I don't know for sure. Howe
On 2021-10-07, Felipe Gasper wrote:
>> On Oct 7, 2021, at 7:47 PM, Benny Pedersen wrote:
>>
>> https://dovecot.org/pipermail/dovecot/2013-December/094214.html
>
> SNI’s security problem is that the server name is sent unencrypted. This
> isn’t really of much concern for mail, though.
>
> Of not
On 2021-11-07, Ralph Seichter wrote:
> * Alexander Dalloz:
>
>> Don't know about Ubuntu specifics [...]
>
> Thank you for the pointers. Am I right to interpret the Dovecot docs as
> stating that SSHA384 is not supported by the official packages, and that
> my only recourse might be building from t
On 2022-01-20, Johan wrote:
> I have computers at two different locations and one computer running
> dovecot at each place. I sync my emails between these two servers using
> ssh and I haven't had any problems with this lately until I upgraded
> dovecot recently.
>
> I now get the following err
On 2022-02-05, Jacek Grabowski wrote:
> Ok but I have to know the date (approximate) when support for lucene will
> be removed completely from dovecot.
> Does anyone know when this will happen? It is scheduled in some version in
> the future maybe?
Why not assume that it could be removed at the n
On 2022-02-10, dove...@ptld.com wrote:
> It is possible for a mailing list to pass DMARC verification, but
> there doesn't seem to be a lot of motivation to put in the extra effort
> to make it work.
It is possible, but it breaks how many people expect mailing lists to work.
On 2020-02-11, ml_dove...@thorsten-reichelt.de
wrote:
> I know that there are many results if I search for "dovecot thunderbird
> very slow" on Google but none of them helped me with my problem. :(
Do you have imap compression enabled? I had some problems with that and
Thunderbird.
> I just don
On 2020-03-06, Aki Tuomi wrote:
> + Add tool for generating sysreport called dovecot-sysreport.
>=C2=A0 This generates a bundle of information usually needed for support
>=C2=A0 requests.
This goes to some lengths to remove passwords in dovecot config files, but
it includes userdb/passdb files in
On 2020-05-19, David Gessel wrote:
> I'm getting some log errors with clucene that I am having no luck tracking
> down on the interwebs.
This looks relevant:
https://www.mail-archive.com/dovecot@dovecot.org/msg66366.html
> I am considering switch to xapian (solr and java... pls noe) as the
> p
On 2020/05/19 17:04, Aki Tuomi wrote:
>
> On 19/05/2020 16:48 Stuart Henderson wrote:
>
>
> On 2020-05-19, David Gessel wrote:
>
> I'm getting some log errors with clucene that I am having no luck
> tracking down on the
> interwe
On 2020-05-26, mj wrote:
> Hi,
>
> On 25/05/2020 23:04, Voytek wrote:
>> jumping here with a question, if I use 143 with STARTTLS, and, force
>> TLS/SSL in configuration, that's equivalent from security POV, isn't
>> it? and, same for 110 STARTTLS? Or am I missing something?
> Interesting point, a
On 2020-06-15, Alexander Strasser wrote:
> I had some imap crashes (sig11) starting at the end of 2019 after
> an upgrade of dovecot.
>
> I found out, that I didn't have any problems using version v2.3.8,
> but any version v2.3.9 and higher would trigger the crashes.
>
> After investigating more d
On 2020-07-06, Rupert Gallagher wrote:
> Both Dovecot and OpenDKIM packages on OpenBSD are rejecting
> connections because of CRYPTO, and they use libressl by default.
That's best reported with information (at least version numbers of
software involved, relevant logs, and info about which server
On 2016-10-19, Timo Sirainen wrote:
> http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz
> http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz.sig
>
> There are quite a lot of changes since v2.2.25. Please try out this RC so we
> can get a good and stable v2.2.26 out.
I'm seei
On 2016-11-02, Aki Tuomi wrote:
> If the standard way works, I am happy to include the original patch I
> sent, amended so that it checks for presence of LIBRESSL_VERSION_NUMBER.
> If they keep this promise, then we should have no worries about things
> breaking up.
Diff below is what I've add
On 2017-02-19, KT Walrus wrote:
>> That's one of the reasons I don't like Let's Encrypt, with one year
>> certs it is easier to look at the certs and see what is going to expire
>> in the coming month needing a new private key.
>
> I use dehydrated (with Cloudflare DNS challenges) and as far as I
On 2017-02-18, Ben wrote:
>
>> What I did when encountering a similar issue was to take one of the messages
>> from INBOX that should have been moved elsewhere and use sieve-test on it:
>>
>> sieve-test -Tlevel=matching
>>
>> That generates a lot of output as it goes through every line of the s
On 2022-05-17, Kurt Fitzner wrote:
> I run a medium-sized virtual domain email server for about 15 domains=2E I=
> also use it myself and have 3 or 4 devices using imap=2E I am often usin=
> g a VPN to connect to my home network, which makes all my connections appea=
> r to come from one IP=2E
On 2022-05-24, Hippo Man wrote:
> * Hacker makes numerous login attempts one after the other with various
> passwords, and without disconnecting in between attempts. I've seen 10 and
> more of these repeated attempts rapidly during a single imap or pop3
> connection.
"numerous" and "rapidly" soun
On 2022-05-24, Niklas Meyer wrote:
> since we´ve tested around with the new dovecot release in the mailcow
> project we´ve came across a curious and new error with Dovecot:
>
> /auth: Panic: file userdb-blocking.c: line 124
> (userdb_blocking_iter_next): assertion failed: (ctx->conn != NULL)/
T
On 2022-07-07, @lbutlr wrote:
> I am getting a lot of these in the logs:
>
> dovecot[52816] imap: Error: Use of uninitialized value $ENV{"PATH"} in split
> at /usr/local/lib/perl5/5.36/mach/File/Spec/Unix.pm line 256.
>
> FreeBSD 13.1-RELEASE releng/13.1-n250148-fc952ac2212 GENERIC
>===>>> dovec
On 2022-09-14, Goetz Schultz wrote:
> I had the same issue on TB102. Self-Signed certificates rejected despite
> having the CA installed correctly as authority. Turns out out that that
> TB now wants extension "Subject Alt Names". Added that and all works
> now. Seems another Google pressed iss
On 2022-10-11, Bernardo Reino wrote:
> Please please stop top-posting. Makes a mess of everything!
I think everything that can be said in this thread, already has been said...
On 2022-10-24, Alessio Cecchi wrote:
>
> Director is not only used by large companies but also in small
> installations consisting of 2 servers and cannot be immediately replaced
> with Nginx as it has to manage the user/backend association for POP,
> IMAP, LMTP, Managesieve.
For the small mul
On 2023-02-01, Tim Evers wrote:
> I run a fairly large Dovecot Installation (around 100k mailboxes) on
> several servers.
>
> gzip compression is on.
>
> Every once in a while I get the dreaded "cache corruption" messages in
> the log:
>
> Error: Corrupted record in index cache file
> /[redacte
On 2023-02-02, Tim Evers wrote:
>
> Am 02.02.23 um 16:23 schrieb Aki Tuomi:
>> For bug reports, we do ask that you try to reproduce it with 2.3.20 (current
>> latest), you can get packages from https://repo.dovecot.org/ and would be
>> nice if you can provide steps to reproduce this issue.
>>
>>
On 2023-02-10, Michael Peddemors wrote:
> TOP POSTING for clarity
>
> I think this is getting off topic for the dovecot list. Vacation
> messaging is a complex topic, and for the record it does seem that the
> way they are doing vacation messages could use improvement.
>
> This should NOT be se
On 2023-04-12, dovecot--- via dovecot wrote:
>> I noticed starting today the Sender: header is no longer included on the
>> mailing list.
>> I used to use the Sender: header in sieve rules for sorting.
>> Now the list emails only come From: rando email addresses.
>> On the postfix mailing list it
On 2023-04-19, John Gateley via dovecot wrote:
> The instructions here
> https://doc.dovecot.org/configuration_manual/fts/solr/ are quite out of
> date, they reference Debian 8 and 9 (current version 11), and Solr 7.7
> (current version 9.2)
There are some posts on this list with updated confi
On 2023-06-03, John Stoffel wrote:
>> "Oliver" == Oliver Glas writes:
>
>> I am looking for a way to remove attachments, based on a condition.
>> Like attachments starting with "TimeReport" shall be removed, and
>> then the mail should be delivered, with all other attachments.
>
> This is not
On 2023-07-18, Gerald Galster wrote:
> While I understand it takes effort to maintain the replication plugin, this
> is especially problematic for small active/active high-availability
> deployments.
> I guess there are lots of servers that use replication for just 50 or 100
> mailboxes. Clouds
On 2023-08-16, Gareth Evans wrote:
>
> ... however it relies on doveadm which I don't have access to on a shared
> host.
>
> I am looking into IMAP-based "doveadm backup" (ie running doveadm elsewhere)
> but I fear this will require an admin username/password which wouldn't be
> accessible on a
On 2023-09-27, dovecot--- via dovecot wrote:
>> Quick Q: Can dovecot use wildcard TLS Certificates?
>>
>> I'm having issues with a new dovecot/postfix stack set-up and I can't get
>> mutt on the local box to connect via imap - its coming back with an SSL
>> error, and as I'm using a wildcard ce
On 2023-10-14, Philip Iezzi via dovecot wrote:
> Thanks for the clear statement. I thought, plans might have changed since
> last June, as I didn't hear anything about upcoming Dovecot 2.4.
> Can we expect to see a release in the near future? No pressure! Please just
> point me to some 2.4 roadm
On 2024-03-12, steffan--- via dovecot wrote:
> I have an old CentOS 7 server using dovecot 2.2.36 and OpenSSL 1.0.2k-fips=
> that=92s been fine for quite some time. Recently I started getting complai=
> nts related to SNI.
>
> I test with this: openssl s_client -connect mail.domain.com:993 -crlf
https://github.com/dovecot/core/commit/54a1b3574acab5f778843f7f1e04d2d26d61a852
fixed a 'doveadm pw' crash "when trying to use CRYPT scheme when crypt() doesn't
support DES" by testing to see if crypt would generate a DES password and, if
not, disabling the scheme.
I'm using Dovecot on OpenBSD wit
On 2012-04-06, Thomas von Eyben wrote:
> I am seeing a >10x as slow performance when trying to complete a
> "send/receive" from an Outlook 2010 client to Dovecot via IMAP, but
> only when the LAN is fully loaded with other traffic, EG file copying.
> It seems the problem is when outlook is trying
deliver has the following:
-- -- --
/* After buffer grows larger than this, create a temporary file to /tmp
where to read the mail. */
#define MAIL_MAX_MEMORY_BUFFER (1024*128)
...
static struct istream *create_raw_stream(int fd, time_t *mtime_r)
...
input = i_stream_create_seekable(
On 2010-03-14, Sabahattin Gucukoglu wrote:
> The question is: does anybody know how I can find and remove duplicates, =
> either while injecting mail with IMAP, or afterward? I can use tools to =
> find duplicate Message-IDs, but don't know of a way to remove duplicates =
> in mailboxes that are
On 2019-02-13, Mark Foley via dovecot wrote:
> Is it possible that no one on this list is authenticating Outlook with
> Dovecot and NTLM?
Yes, it's possible, the outdated instructions you found on the wiki
suggests it's an uncommon configiration.
No actual answers from me, but it might give you
On 2019-02-22, David Pottage via dovecot wrote:
> On 2019-02-21 22:14, Christoph Haas via dovecot wrote:
>
NO! My mail storage is mdbox. And at the moment I have no intention
to
convert it to Maildir!
>>> Could I ask why? maildir is a better storage format is almost every
>>> resp
On 2019-07-13, Reio Remma via dovecot wrote:
> Hello!
>
> I noticed these in the logs since upgrading from 2.3.6. to 2.3.7:
>
> Jul 13 11:52:10 turin dovecot: doveadm: Error:
> dsync-remote(r...@mrstuudio.ee): Error:
> Exporting mailbox INBOX failed: Mailbox attribute
> vendor/vendor.dovecot/pv
On 2019/07/16 19:46, Aki Tuomi wrote:
>
> > On 16/07/2019 18:40 Stuart Henderson via dovecot
> > wrote:
> >
> >
> > On 2019-07-13, Reio Remma via dovecot wrote:
> > > Hello!
> > >
> > > I noticed these in the logs since upgra
On 2019-07-16, Stuart Henderson via dovecot wrote:
> On 2019/07/16 19:46, Aki Tuomi wrote:
>>
>> > On 16/07/2019 18:40 Stuart Henderson via dovecot
>> > wrote:
>> >
>> >
>> > On 2019-07-13, Reio Remma via dovecot wrote:
>>
On 2019-08-09, Joseph Mays via dovecot wrote:
> I am looking at replacing our creaky old courier-imap server, which takes
> authentication and user info from an LDAP database, with dovecot imap. Any
> comments on the wisdom of this choice of action, or anything I should know
> about the setting
On 2019-11-22, Ralph Seichter via dovecot wrote:
> * Robert via dovecot:
>
>> We use a simple system for routing emails to different email users by
>> postfixing the addresses with the actual user: xxxJohn@domain;
>> yyyJohn@domain etc all will be delivered to user John.
>> (This way John can in
On 2024-05-16, Christopher Wensink via dovecot wrote:
> See here for the documentation for dovecot:
>
> https://doc.dovecot.org/admin_manual/ssl/
Wrong bit of the manual. See the sample dovecot-sql.conf.ext or
https://doc.dovecot.org/configuration_manual/authentication/sql/#id10
___
70 matches
Mail list logo
