Re: Configure: "Can't build with MySQL support: libmysqlclient not found"
On Tue, Mar 12, 2024 at 4:20 AM James L. Brown via dovecot wrote: Hi all. I’m getting errors when trying to configure make for version 2.3.21 on macOS 14.3.1 Sonoma. It ends with: checking for mysql_config... mysql_config checking for mysql_init in -lmysqlclient... no configure: error: Can't build with MySQL support: libmysqlclient not found I’m using: env PKG_CONFIG_PATH=/opt/homebrew/lib/pkgconfig pkg-config --libs libsodium CPPFLAGS=-I/opt/homebrew/Cellar/openssl@3/3.2.1/include LDFLAGS=-L/ opt/ homebrew/opt/openssl@3/lib ./configure --with-ssl=openssl --with- mysql --with- sodium Looking at config.log I see: configure:28222: checking for mysql_config configure:28238: found /opt/homebrew/bin/mysql_config configure:28250: result: mysql_config configure:28285: checking for mysql_init in -lmysqlclient configure:28310: gcc -o conftest -std=gnu99 -g -O2 -fstack-protector- strong - U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wall -W -Wmissing-prototypes - Wmissing- declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad- function-cast - Wno-duplicate-decl-specifier -Wstrict-aliasing=2 -I/opt/homebrew/ Cellar/ openssl@3/3.2.1/include -I/opt/homebrew/Cellar/openssl@3/3.2.1/ include -L/opt/ homebrew/opt/openssl@3/lib conftest.c -lmysqlclient -L/opt/ homebrew/Cellar/ mysql/8.3.0_1/lib -lmysqlclient -lz -lzstd -lssl -lcrypto -lresolv -lz -lm >&5 ld: warning: ignoring duplicate libraries: '-lmysqlclient', '-lz' ld: library 'zstd' not found clang: error: linker command failed with exit code 1 (use -v to see invocation) configure:28310: $? =1 Odd that it is using the old version mysql. Would someone be able to help me get it to find libmysqlclient? In /opt/homebrew/Cellar/mysql/8.0.32/lib/ I have: libmysqlclient.21.dylib libmysqlclient.a libmysqlclient.dylib Thanks, James. Maybe https://github.com/PyMySQL/mysqlclient/issues/496#issuecomment-1614688099 -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart- questions.html] ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: Bug/Warning not sure which
On Sun, Mar 3, 2024 at 1:46 AM Richard Shetron wrote: Hello, My sysadmin and I spent a couple hours trying to figure out a POP3 problem that has worked for about 20 or so years. We run our own dns for sgeinc.com. I've always used mail.sgeinc.com as my incoming and outgoing server. At various times mail has been an alias for another machine. It's currently on the same address as sge.sgeinc.com. On the update forced on us on 2/22/24 or 2/23/24 it stopped working. It still works as an outgoing server but incoming POP3 it stopped working. It started working when I changed my incoming server to sge.sgeinc.com. You might want to look into it or not. We chased the initial problem to, we think, ssh-keygen in /usr/local/bin/ which was Not found but is there. Why would dovecot need ssh-keygen? What for? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart- questions.html] ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: Recommended changes for delivery from Exim
On Fri, Feb 2, 2024 at 6:24 PM Benoît PELISSIER via dovecot
wrote:
Hi,
it's not working do this.
i tried ans doesnt work.
i use workaround from Kirill Miazine
---
$ cat /local/bin/dovecot-lda-wrapper
#!/bin/sh
exec /usr/local/libexec/dovecot/dovecot-lda \
-d "${LOCAL_PART}@${DOMAIN}" \
-a "${LOCAL_PART}${LOCAL_PART_SUFFIX}@${DOMAIN}" \
-r "${LOCAL_PART}${LOCAL_PART_SUFFIX}@${DOMAIN}" \
-f "${SENDER}"
Here's how it is called from Exim:
dovecot_pipe:
driver = pipe
command = /local/bin/dovecot-lda-wrapper
# command = /usr/local/libexec/dovecot/dovecot-lda \
# -d $local_part@$domain \
# -a $local_part$local_part_suffix@$domain \
# -r $local_part$local_part_suffix@$domain \
# -r $local_part$local_part_suffix@$domain \
# -f $return_path
---
Benoît
It's 2024! You've awakened a thread from 2022 without explanations :)
What is it that you're trying to achieve?
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
In an Internet failure case, the #1 suspect is a constant: DNS.
"Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
[How to ask smart questions: http://www.catb.org/~esr/faqs/smart-
questions.html]
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
Re: Help - Permissions issue with new mail
On Wed, May 3, 2023 at 9:02 PM dovecot--- via dovecot wrote: > > On 05-03-2023 1:52 pm, michele.clark--- via dovecot wrote: > > Hi all. > > > > We have an install of Dovecot running with Postfix and Roundcube using > virtual mail to allow us to connect to our AD domain which got messed up > after a power issue. > > > > I can log into our Roundcube and see all my old emails, however new > emails keep getting stuck in the CUR files with permissions of -rw--- > > > > If I chmod the email it will deliver to the inbox in Roundcube. > > > > Can anyone advise on how I can adjust this so all new emails will come > thru with the correct permissions? - Thanks in advance > In a Maildir type of storage, new mail would get delivered to Maildir/new. After having been accessed, it would then move to Maidir/cur/ No MTA delivers to the cur/ directory unless you have configured your Postfix to do that. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html] ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: Blacklistd
On Thu, Apr 20, 2023 at 9:08 AM Doug Hardie wrote: > Are there any plans to interface to blacklistd? > > -- Doug > Hi Doug, Since blacklistd uses PF, you can already use fail2ban or sshguard <https://www.sshguard.net/> to achieve the same thing you are after. Given that blacklistd is just an intermediary like fail2ban, is there a real need for dovecot interfacing with it? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html] ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: Mailing list update
On Tue, Apr 18, 2023 at 4:01 PM Aki Tuomi via dovecot wrote: > > > On 17/04/2023 17:44 EEST Peter Wienemann > wrote: > > > > > > Dear Aki, > > > > On 12.04.23 13:31, Aki Tuomi via dovecot wrote: > > > We finally managed to move from mailman2 to mailman3, and mail > archives are now at https://dovecot.org/mailman3/archives and they can be > now searched, too. > > > > thanks for this. > > > > > Please let us know if you have face any issues with the mailing list > and we'll look into it. > > Is there a way to keep old links to archived messages (such as > > https://dovecot.org/pipermail/dovecot/-/.html) > > intact? > > > > Best regards, > > > > Peter > > ___ > > dovecot mailing list -- dovecot@dovecot.org > > To unsubscribe send an email to dovecot-le...@dovecot.org > > I restored the old archives. > You mean you imported the old archives into Mailman3?? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html] ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: Mailing list update
On Thu, Apr 13, 2023 at 3:14 PM Aki Tuomi wrote: > > > On 13/04/2023 15:02 EEST Odhiambo Washington wrote: > > > > > > > > > > > > > > On Wed, Apr 12, 2023 at 4:11 PM Aki Tuomi > wrote: > > > > > > > On 12/04/2023 15:47 EEST Odhiambo Washington > wrote: > > > > > > > > > > > > > > > > > > > > > > > > On Wed, Apr 12, 2023 at 3:24 PM Johannes Rohr > wrote: > > > > > > > > > > > > > > > Am 12.04.23 um 14:14 schrieb Johannes Rohr: > > > > > > > > > > > > > > > > > > > > > > > Am 12.04.23 um 13:58 schrieb Odhiambo Washington: > > > > > > > > > > > > > On Wed, Apr 12, 2023 at 2:31 PM Aki Tuomi via dovecot < > dovecot@dovecot.org> wrote: > > > > > > > > > > > > > > > > > > > > > > > We finally managed to move from mailman2 to mailman3, and > mail archives are now at https://dovecot.org/mailman3/archives and they > can be now searched, too. > > > > > > > > > > > > > > > > Please let us know if you have face any issues with the > mailing list and we'll look into it. > > > > > > > > > > > > > > [...] > > > > > > > > > > > > > > > > > > > > > > > > > > > What is the new signup method, given that signup is closed on > this new MM3 instance? > > > > > > > > > > > > > I guess you can still subscribe via email. But why is account > registration closed? I too manage a mailman3 instance. I cannot see any > reason why you would want to disable account registration. A newly > registered account does not automatically get new privileges, so this > doesn't increase security. At the same time, it strips the user of the > possibility to manage their account. > > > > > BTW, I am under the impression that archiving isn't set up > properly. The newest mail in the archive ( > https://dovecot.org/mailman3/archives/list/dovecot@dovecot.org/) is of > April 11. As in Mailman3, the mailing list manager (postorius) and the > archiver (hyperkitty) are separate, it also took a bit of trial and error > for me to ensure, that new mails are being archived. I don't remember what > was the cause in my case. But I think the mailman-web log files revealed it > to me. > > > > While it's already getting OT, the archiving is done via > mailman-web settings and cron. > > > > And maybe they better opt for the much faster Xapian indexer ( > https://github.com/notanumber/xapian-haystack/tree/master). > > > > > > > > -- > > > > > > We have, in fact, opted for the Xapian indexer, given that the Whoosh > indexer is not usable in practice. > > > > > > I forgot to reopen the registration, I'll open it. > > > > > > Aki > > > > Will you consider implementing social account signups? > > > > > > I'll take a look at it. > > Aki > Great! If you manage to incorporate Twitter amongst them, please consider sharing the trick to achieving it offlist :) I know you have the capacity. It did beat me on my lists. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html] ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: Mailing list update
On Wed, Apr 12, 2023 at 4:11 PM Aki Tuomi wrote: > > > On 12/04/2023 15:47 EEST Odhiambo Washington wrote: > > > > > > > > > > > > On Wed, Apr 12, 2023 at 3:24 PM Johannes Rohr wrote: > > > > > > > > > Am 12.04.23 um 14:14 schrieb Johannes Rohr: > > > > > > > > > > > > > > > Am 12.04.23 um 13:58 schrieb Odhiambo Washington: > > > > > > > > > On Wed, Apr 12, 2023 at 2:31 PM Aki Tuomi via dovecot < > dovecot@dovecot.org> wrote: > > > > > > > > > > > > > > > > > We finally managed to move from mailman2 to mailman3, and mail > archives are now at https://dovecot.org/mailman3/archives and they can be > now searched, too. > > > > > > > > > > > > Please let us know if you have face any issues with the mailing > list and we'll look into it. > > > > > > > > > > [...] > > > > > > > > > > > > > > > > > > > What is the new signup method, given that signup is closed on this > new MM3 instance? > > > > > > > > > I guess you can still subscribe via email. But why is account > registration closed? I too manage a mailman3 instance. I cannot see any > reason why you would want to disable account registration. A newly > registered account does not automatically get new privileges, so this > doesn't increase security. At the same time, it strips the user of the > possibility to manage their account. > > > BTW, I am under the impression that archiving isn't set up properly. > The newest mail in the archive ( > https://dovecot.org/mailman3/archives/list/dovecot@dovecot.org/) is of > April 11. As in Mailman3, the mailing list manager (postorius) and the > archiver (hyperkitty) are separate, it also took a bit of trial and error > for me to ensure, that new mails are being archived. I don't remember what > was the cause in my case. But I think the mailman-web log files revealed it > to me. > > While it's already getting OT, the archiving is done via mailman-web > settings and cron. > > And maybe they better opt for the much faster Xapian indexer ( > https://github.com/notanumber/xapian-haystack/tree/master). > > > > -- > > We have, in fact, opted for the Xapian indexer, given that the Whoosh > indexer is not usable in practice. > > I forgot to reopen the registration, I'll open it. > > Aki > Will you consider implementing social account signups? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html] ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: Mailing list update
On Wed, Apr 12, 2023 at 3:24 PM Johannes Rohr wrote: > > Am 12.04.23 um 14:14 schrieb Johannes Rohr: > > > Am 12.04.23 um 13:58 schrieb Odhiambo Washington: > > On Wed, Apr 12, 2023 at 2:31 PM Aki Tuomi via dovecot > wrote: > >> >> We finally managed to move from mailman2 to mailman3, and mail archives >> are now at https://dovecot.org/mailman3/archives and they can be now >> searched, too. >> >> Please let us know if you have face any issues with the mailing list and >> we'll look into it. >> > [...] > > > What is the new signup method, given that signup is closed on this new MM3 > instance? > > I guess you can still subscribe via email. But why is account registration > closed? I too manage a mailman3 instance. I cannot see any reason why you > would want to disable account registration. A newly registered account does > not automatically get new privileges, so this doesn't increase security. At > the same time, it strips the user of the possibility to manage their > account. > > BTW, I am under the impression that archiving isn't set up properly. The > newest mail in the archive > <https://dovecot.org/mailman3/archives/list/dovecot@dovecot.org/> is of > April 11. As in Mailman3, the mailing list manager (postorius) and the > archiver (hyperkitty) are separate, it also took a bit of trial and error > for me to ensure, that new mails are being archived. I don't remember what > was the cause in my case. But I think the mailman-web log files revealed it > to me. > While it's already getting OT, the archiving is done via mailman-web settings and cron. And maybe they better opt for the much faster Xapian indexer <https://github.com/notanumber/xapian-haystack/tree/master>. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html] ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: Mailing list update
On Wed, Apr 12, 2023 at 2:31 PM Aki Tuomi via dovecot wrote: > Hi all! > > We finally managed to move from mailman2 to mailman3, and mail archives > are now at https://dovecot.org/mailman3/archives and they can be now > searched, too. > > Please let us know if you have face any issues with the mailing list and > we'll look into it. > > Regards, > Aki Tuomi > Open-Xchange oy > What is the new signup method, given that signup is closed on this new MM3 instance? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html] ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: Postfix : root and system user authentication
On Wed, Mar 15, 2023 at 1:46 AM Aymeric Agon-Rambosson < aymeric.a...@yandex.com> wrote: > > Hello everyone, > > From what I understand of the documentation, it is impossible to > log in to the dovecot server as root, or as any user not in the > interval between first_valid_uid and last_valid_uid. > https://doc.dovecot.org/configuration_manual/authentication/master_users/ -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
Re: Error: Mailbox INBOX: file_dotlock_create in directory /var/mail failed: Permission denied
On Mon, Jan 16, 2023 at 1:34 PM manmatha wrote: > Hi All, > > We are running Round cube on top of dovecot and postfix as our email echo > system. Main problem we are facing is that, roundcube loads really slow for > big inboxes (~5000 emails). I found that, while it loads, imap process goes > high in terms of CPU utilization(~90%). I asked it in some roundcube > support group, They believe that it is related to dovecot not roundcube. > Can you shed any light on this issue. Thanks in advance. > > Here is $dovecot -n$ output > > xyz@roundcube-internal-server-1: > /etc/dovecot$ > dovecot -n > # 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.5.16 (09c29328) > # OS: Linux 5.15.0-1024-kvm x86_64 Ubuntu 22.04.1 LTS > # Hostname: roundcube-internal-server-1 > auth_mechanisms = plain login > disable_plaintext_auth = no > listen = * > lock_method = dotlock > mail_always_cache_fields = date.received > mail_cache_min_mail_count = 5000 > mail_location = mbox:~/mail:INBOX=/var/mail/%u:INDEX=/var/indexes/ > isical.ac.in/%n > Yes. Please migrate from mbox to Maildir++ and you will not suffer from those lock issues. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
Re: Dovecot and TLSv1 on ubuntu 22.04
On Thu, Nov 24, 2022 at 1:34 PM Six002 wrote: > Hello, > I have ubuntu 22.04, dovecot 2.3.16 and old email client (Outlook 2013) > and their dont support TLSv1_2. > In dovecot 10-ssl.conf i put: ssl_min_protocol = TLSv1, > in openssl.cnf i have: > openssl_conf = default_conf > [ default_conf ] > ssl_conf = ssl_section > [ssl_section] > system_default = ssl_default_sectq > [ssl_default_sect] > MinProtocol = TLSv1 > CipherString = DEFAULT:@SECLEVEL=1 > > but when i check openssl s_client -connect localhost:993 -tls1_1 > have output: > > CONNECTED(0003) > 803BD26AC67F:error:0A000126:SSL routines:ssl3_read_n:unexpected eof > while reading:../ssl/record/rec_layer_s3.c:308: > --- > no peer certificate available > --- > No client certificate CA names sent > --- > SSL handshake has read 0 bytes and written 111 bytes > Verification: OK > --- > New, (NONE), Cipher is (NONE) > Secure Renegotiation IS NOT supported > Compression: NONE > Expansion: NONE > No ALPN negotiated > SSL-Session: > Protocol : TLSv1.1 > Cipher: > Session-ID: > Session-ID-ctx: > Master-Key: > PSK identity: None > PSK identity hint: None > SRP username: None > Start Time: 1668602712 > Timeout : 7200 (sec) > Verify return code: 0 (ok) > Extended master secret: no > --- > > version tls1_2 and 1_3 works fine. > What I doing wrong? > Thanks for help. > > Not to answer your question about TLS, but about Outlook. Your version of Outlook is outdated and seeing as you use Outlook with Dovecot, there is nothing special that you need Outlook for. Why not just switch to something like Thunderbird for a MuA? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
Re: Office 365 SSL issue
On Sat, Oct 22, 2022 at 11:31 AM Ervin Hegedüs wrote: > Hi there, > > I have a bit old Dovecot instance (Ubuntu 14.04 - there is no > chance to upgrade it), with these versions of packages: > > * Dovecot: 2.2.9 > * OpenSSL: 1.0.1f > > Few days ago a client noticed me, that he can't reach his mails > through his Office 365. He uses POP3S. > > I tried to set up a same client for this Dovecot server, but when > I configured the POP3 protocoll, after the settings check Office > says: > > Your server does not support the connection encryption type you > have specified. Try changing the encryption method. Contact your > mail server ... > > While the client was trying, I see these lines in the log: > > Oct 21 16:12:18 mail dovecot: pop3-login: Debug: SSL: where=0x10, ret=1: > before/accept initialization [192.168.8.133] > Oct 21 16:12:18 mail dovecot: pop3-login: Debug: SSL: where=0x2001, ret=1: > before/accept initialization [192.168.8.133] > Oct 21 16:12:18 mail dovecot: pop3-login: Debug: SSL: where=0x2001, ret=1: > SSLv3 read client hello A [192.168.8.133] > Oct 21 16:12:18 mail dovecot: pop3-login: Debug: SSL: where=0x2001, ret=1: > SSLv3 write server hello A [192.168.8.133] > Oct 21 16:12:18 mail dovecot: pop3-login: Debug: SSL: where=0x2001, ret=1: > SSLv3 write certificate A [192.168.8.133] > Oct 21 16:12:18 mail dovecot: pop3-login: Debug: SSL: where=0x2001, ret=1: > SSLv3 write key exchange A [192.168.8.133] > Oct 21 16:12:18 mail dovecot: pop3-login: Debug: SSL: where=0x2001, ret=1: > SSLv3 write server done A [192.168.8.133] > Oct 21 16:12:18 mail dovecot: pop3-login: Debug: SSL: where=0x2001, ret=1: > SSLv3 flush data [192.168.8.133] > Oct 21 16:12:18 mail dovecot: pop3-login: Debug: SSL: where=0x2002, > ret=-1: SSLv3 read client certificate A [192.168.8.133] > Oct 21 16:12:18 mail dovecot: pop3-login: Debug: SSL: where=0x2002, > ret=-1: SSLv3 read client certificate A [192.168.8.133] > Oct 21 16:12:18 mail dovecot: pop3-login: Warning: SSL failed: > where=0x2002: SSLv3 read client certificate A [192.168.8.133] > Oct 21 16:12:18 mail dovecot: pop3-login: Disconnected (no auth attempts > in 0 secs): user=<>, rip=192.168.8.133, lip=192.168.8.21, TLS handshaking: > Disconnected, session=<9sWMB4zr+ADAqAiF> > > Which is weird, because I disabled SSLv3. Here is the (relevant) > config: > > ssl_cert = ssl_key = ssl_dh_parameters_length = 2048 > ssl_protocols = !SSLv2 !SSLv3 > ssl_cipher_list = > ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA > verbose_ssl = yes > > When I check the supported encryption type with nmap, I get this: > > $ nmap --script ssl-enum-ciphers -p 995 192.168.8.21 > Starting Nmap 7.80 ( https://nmap.org ) at 2022-10-22 10:20 CEST > Nmap scan report for 192.168.8.21 > Host is up (0.021s latency). > > PORTSTATE SERVICE > 995/tcp open pop3s > | ssl-enum-ciphers: > | TLSv1.0: > | ciphers: > | TLS_DHE_RSA_WITH_AES_128_CBC_SHA (dh 2048) - A > | ... > | TLSv1.1: > | ciphers: > | TLS_DHE_RSA_WITH_AES_128_CBC_SHA (dh 2048) - A > | ... > | TLSv1.2: > | ciphers: > | TLS_DHE_RSA_WITH_AES_128_CBC_SHA (dh 2048) - A > | ,,, > |_ least strength: C > > When I check the traffic with tcpdump, I see that client > uses TLSv1.2: > > https://www.dropbox.com/s/k8wqzg5xzki5p23/pop3_traffic.png > > Only the one client who reported the problem, and my test client > can't reach the server - other (about) 400 users can (but I don't > know with what kind of types of clients - most use Thunderbird). > > > What can I do? How can I fix this problem? As I wrote, this > problem has came few days ago suddenly... > If the client is running Windows 11 and recently updated to 22H2, then you may be interested in the below: https://support.microsoft.com/en-us/topic/october-17-2022-kb5020387-os-build-22000-1100-out-of-band-5e723873-2769-4e3d-8882-5cb044455a92 -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
Re: Dovecot mail-crypt webmail can't read encrypted messages
On Thu, Oct 13, 2022 at 5:40 PM Serveria Support wrote: > Hi, > > Unfortunately, after running autogen.sh and ./configure the file is > still not there. I understand that this is not a Dovecot issue, but > perhaps someone can help me with this? 1. mkdir ~reinob/Sources 2. cd ~reinob/Sources 3. wget https://dovecot.org/releases/2.3/dovecot-2.3.19.1.tar.gz 4. tar -xzvf dovecot-2.3.19.1.tar.gz 5. cd dovecot-2.3.19.1 # make the changes to the file you want to patch 6. ./configure --help # select your options 7. ./configure --opt1 --opt2 --opt3, etc 8. make install -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
Re: Dovecot mail-crypt webmail can't read encrypted messages
@Tulp - the attacker has to 0wn your server first. In which case they will have found a password to SSH in - regardless of dovecot being there or not. You will be dealing with a bigger problem than dovecot. On Tue, Oct 11, 2022 at 5:39 PM John Tulp wrote: > I find this conversation "interesting". > > Serveria, i think some can't see the attack scenario where the > attacker's goal is simply to get email passwords, and nothing else. it > would make sense for their strategy to do nothing else "bad" on the > server to attract attention to their intrusion. In that case, all they > would do is send back the treasure trove of passwords to their home > server(s), and sit there, remaining possibly for years, hiding, > exploiting the fact that dovecot, with no code modification, will allow > them to grab email passwords. If a dovecot server has thousands of > email accounts, that represents thousands of other devices they could > target, which is worth much more to the attacker than a single dovecot > server. > > Oh well, food for thought. > > > On Tue, 2022-10-11 at 15:11 +0300, Serveria Support wrote: > > Yes, I realize that. But I can't think of a reason this password is > > necessary in the logs. It's kind of a backdoor and has to be removed > > from code. Why make intruder's life easier? > > > > On 2022-10-11 13:39, Arjen de Korte wrote: > > > Citeren Serveria Support : > > > > > >> Yes, there is a tiny problem letting the attacker change this value > > >> back to yes and instantly get access to users' passwords in plain > > >> text. Apart from that - no problems at all. :) > > > > > > If an attacker is able to modify your Dovecot configuration, you have > > > bigger problems than leaking your users' password. Much bigger... > > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
Re: Dovecot mail-crypt webmail can't read encrypted messages
If you don't store cleartext passwords in your backend, how will an intruder get them?? On Tue, Oct 11, 2022 at 3:45 PM Serveria Support wrote: > Yes, I realize that. But I can't think of a reason this password is > necessary in the logs. It's kind of a backdoor and has to be removed > from code. Why make intruder's life easier? > > On 2022-10-11 13:39, Arjen de Korte wrote: > > Citeren Serveria Support : > > > >> Yes, there is a tiny problem letting the attacker change this value > >> back to yes and instantly get access to users' passwords in plain > >> text. Apart from that - no problems at all. :) > > > > If an attacker is able to modify your Dovecot configuration, you have > > bigger problems than leaking your users' password. Much bigger... > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
Re: One-off backup
On Tue, Oct 11, 2022 at 11:26 AM Cristiano Deana wrote: > Il 10/10/2022 16:57, Ian Evans ha scritto: > > > is shutting down postfix and running > > tar czf mailstorage.tgz /path/to/mail okay? > > remember -p to preserve permissions. > I have never imagined that tar requires a -p to preserve permissions. Are you talking about cp? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
Re: dovecot error
On Fri, Dec 10, 2021 at 10:04 PM Rajesh M <24x7ser...@24x7server.net> wrote:
> hello all
>
> we were seeing an error as such in dovecot.log for the first time
>
> we use sogo for active sync
>
> dovecot: master: Warning: service(dict): process_limit (100) reached,
> client connections are being dropped
>
You could check why you are spawning so many dict processes. Maybe there is
a bottleneck around MySQL?
In the meantime you could increase the process limit - from 10-master.conf:
service dict {
service_count = 1
process_limit = 500
}
once we restarted sogo service this issue got resolved
>
Check what sogo is doing.
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", egrep -v '^$|^.*#' :-)
Re: Errors after freebsd upgrade
On Sat, Oct 30, 2021 at 7:10 PM Hanns Mattes wrote:
> Hi,
>
> after upgrading Freebsd from ports dovecot is throwing the following error
>
> Oct 30 18:04:15 freebsd dovecot[59232]:
> doveadm(x...@example.com)<84061>: Fatal: master:
> service(doveadm): child 84061 killed with signal 6 (core not dumped -
> https://dovecot.org/bugreport.html#coredumps - set service doveadm {
> drop_priv_before_exec=yes })
>
> I (surely) may have missed something while upgrading (I've learned a lot
> about backup/snapshot-strategies with zfs, but to late to apply).
>
> How can I debug the erro?
>
> Regards Hanns
>
The "service doveadm { drop_priv_before_exec=yes }" bit should go into
/usr/local/etc/dovecot/conf.d/10-master.conf.
Append the bit I have quoted into that file and then restart dovecot.
What command is it that you are running with doveadm?
The also run the following commands (as root):
sysctl -w kern.sugid_coredump=1
sysctl -w kern.corefile=/var/coredumps/%U.%N.core
mkdir /var/coredumps
chown -R 1777 /var/coredumps
The next time you get that fatal error, you'll probably find a file in
/var/coredumps/
You can then obtain a backtrace from it:
gdb /usr/local/bin/doveadm /var/coredumps/FILENAME
bt full
Present the output, together with that from 'doveconf -n'.
HTH
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", egrep -v '^$|^.*#' :-)
Re: Long Term Archival
Between the MTA and the IMAP4 who should be responsible for archiving? I think if you need to keep copies of e-mails, it's better done at the MTA level. Deliver one copy to the recipient and another copy to the archive. IMHO. On Fri, 29 Jan 2021 at 17:12, Rupert Gallagher wrote: > Hello, I would like to know what is your strategy for legally compliant > long term archival of e-mails (up to 10 years). Thank you > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: [EXT] Re: Reminder Re: Dovecot Gmail OAuth2.0 Setting Question
You broke this thread. In the original thread, I remember seeing Aki gave
you the configuration which he believed might work.
The next thing I thought was for you to go to
https://developers.google.com/identity/sign-in/web/devconsole-project and
get an access token.
PS: I have never configured this kind of thing so I was only following the
thread to try and understand what it entails.
On Fri, 29 Jan 2021 at 04:00, 福田泰葵 wrote:
> Google is responding to me as Unauthorized.
> So I need to send my credentials such as access token in the request
> parameter for authentication in google’s Get User API request.
> But I don’t know how to configure dovecot to achieve that.
> Could you please help me with this?
>
> Best regards,
>
> -
> 〒163-6017 東京都新宿区西新宿6-8-1 住友不動産新宿オークタワー
> 株式会社 ジャストシステム 技術企画室 情報システムグループ 福田泰葵
> e-mail: taiki.fuk...@justsystems.com
> 内線: 5158
> TEL: 03-5324-7900
> mobile: 080-6198-7328
>
> -----
>
>
> 2021年1月29日(金) 3:30 Odhiambo Washington :
>
>> Your clue is in the log:
>>
>> 1611654464.207331 "message": "Request is missing required authentication
>> credential. Expected OAuth 2 access token, login cookie or other valid
>> authentication credential. See
>> https://developers.google.com/identity/sign-in/web/devconsole-project.;,
>> 1611654464.207331 "status": "UNAUTHENTICATED" 1611654464.207331 }
>>
>>
>>
>> On Thu, 28 Jan 2021 at 09:25, 福田泰葵 wrote:
>>
>>> Dear Mr. Tuomi
>>>
>>> Do you have any idea how to solve this problem?
>>>
>>> Best regards,
>>>
>>> -
>>> 〒163-6017 東京都新宿区西新宿6-8-1 住友不動産新宿オークタワー
>>> 株式会社 ジャストシステム 技術企画室 情報システムグループ 福田泰葵
>>> e-mail: taiki.fuk...@justsystems.com
>>> 内線: 5158
>>> TEL: 03-5324-7900
>>> mobile: 080-6198-7328
>>>
>>> -
>>>
>>>
>>> 2021年1月26日(火) 18:51 福田泰葵 :
>>>
>>>> Dear Mr. Tuomi
>>>>
>>>> Thank you for the instruction.
>>>> I was able to output rawlogs.
>>>> The following is the result.
>>>>
>>>> 20210126-184744.1.1.in：
>>>>
>>>> 1611654464.207331 HTTP/1.1 401 Unauthorized
>>>> 1611654464.207331 Cache-Control: no-cache, no-store, max-age=0,
>>>> must-revalidate
>>>> 1611654464.207331 Pragma: no-cache
>>>> 1611654464.207331 Expires: Mon, 01 Jan 1990 00:00:00 GMT
>>>> 1611654464.207331 Date: Tue, 26 Jan 2021 09:47:44 GMT
>>>> 1611654464.207331 Vary: X-Origin
>>>> 1611654464.207331 Vary: Referer
>>>> 1611654464.207331 Content-Type: application/json; charset=UTF-8
>>>> 1611654464.207331 Server: ESF
>>>> 1611654464.207331 X-XSS-Protection: 0
>>>> 1611654464.207331 X-Frame-Options: SAMEORIGIN
>>>> 1611654464.207331 X-Content-Type-Options: nosniff
>>>> 1611654464.207331 Alt-Svc: h3-29=":443"; ma=2592000,h3-T051=":443";
>>>> ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443";
>>>> ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43"
>>>> 1611654464.207331 Accept-Ranges: none
>>>> 1611654464.207331 Vary: Origin,Accept-Encoding
>>>> 1611654464.207331 Transfer-Encoding: chunked
>>>> 1611654464.207331
>>>> 1611654464.207331 130
>>>> 1611654464.207331 {
>>>> 1611654464.207331 "error": {
>>>> 1611654464.207331 "code": 401,
>>>> 1611654464.207331 "message": "Request is missing required
>>>> authentication credential. Expected OAuth 2 access token, login cookie or
>>>> other valid authentication credential. See
>>>> https://developers.google.com/identity/sign-in/web/devconsole-project.;,
>>>> 1611654464.207331 "status": "UNAUTHENTICATED"
>>>> 1611654464.207331 }
>>>> 1611654464.207331 }
>>>> 1611654464.207331
>>>> 1611654464.207737 0
>>>> 1611654464.207737
>>>&
Re: [EXT] Re: Reminder Re: Dovecot Gmail OAuth2.0 Setting Question
gt; > 内線: 5158 >>> > > > > > TEL: 03-5324-7900 >>> > > > > > mobile: 080-6198-7328 >>> > > > > > -- >>> > > > > > >>> > > > > > >>> > > > > > 2021年1月25日(月) 17:24 福田泰葵 : >>> > > > > > > Yes. In my last email, I sent you the log of the result of >>> running with oauth debug logging enabled. >>> > > > > > > >>> > > > > > > /etc/dovecot/conf.d/10-logging.conf： >>> > > > > > > >>> > > > > > > ``` >>> > > > > > > ``` >>> > > > > > > >>> > > > > > > >>> > > > > > > >>> > > > > > > >>> - >>> > > > > > > 〒163-6017 東京都新宿区西新宿6-8-1 住友不動産新宿オークタワー >>> > > > > > > 株式会社 ジャストシステム 技術企画室 情報システムグループ 福田泰葵 >>> > > > > > > e-mail: taiki.fuk...@justsystems.com >>> > > > > > > 内線: 5158 >>> > > > > > > TEL: 03-5324-7900 >>> > > > > > > mobile: 080-6198-7328 >>> > > > > > > >>> - >>> > > > > > > >>> > > > > > > >>> > > > > > > >>> > > > > > > 2021年1月25日(月) 17:16 Aki Tuomi : >>> > > > > > > > >>> > > > > > > > > On 25/01/2021 10:12 福田泰葵 >>> wrote: >>> > > > > > > > > >>> > > > > > > > > >>> > > > > > > > > Dear Mr. Tuomi >>> > > > > > > > > Google is responding to me as Unauthorized. >>> > > > > > > > > So I need to send my credentials such as access token >>> in the request parameter for authentication in google’s Get User API >>> request. >>> > > > > > > > > But I don’t know how to configure dovecot to achieve >>> that. >>> > > > > > > > > Could you please help me with this? >>> > > > > > > > > Best regards, >>> > > > > > > > > >>> > > > > > > > > -- >>> > > > > > > > > 〒163-6017 東京都新宿区西新宿6-8-1 住友不動産新宿オークタワー >>> > > > > > > > > 株式会社 ジャストシステム 技術企画室 情報システムグループ 福田泰葵 >>> > > > > > > > > e-mail: taiki.fuk...@justsystems.com >>> > > > > > > > > 内線: 5158 >>> > > > > > > > > TEL: 03-5324-7900 >>> > > > > > > > > >>> > > > > > > > > mobile: 080-6198-7328 >>> > > > > > > > >>> > > > > > > > >>> > > > > > > > Did you try the debugging things I mentioned? Your logs >>> do not indicate that you did. >>> > > > > > > > >>> > > > > > > > So, >>> > > > > > > > >>> > > > > > > > - Try turning on rawlogs for the oauth2 requests and see >>> what google is sending you? >>> > > > > > > > - You can also try log_debug=category=oauth2 (2.3.13) to >>> get more debug logs from oauth2. >>> > > > > > > > >>> > > > > > > > Aki >>> > > > > > > > >>> > > > > >>> > > >>> >> -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: Dovecot and mutt
On Wed, 20 Jan 2021 at 15:59, @lbutlr wrote: > On 20 Jan 2021, at 04:33, Piotr Auksztulewicz wrote: > > On Wed, Jan 20, 2021 at 04:27:11AM -0700, @lbutlr wrote: > >> set imap_pass = "lasH-hds[er$asd" # Not a real password > > > > Use single quotes around the password. Double quotes make $asd to be > > interpreted as shell variable and replaced with (most likely) empty > > string, so you get a shortened passwort in effect. > > This worked, thank you. > > Also… gr. Who though expansion inside a password string was a clever > idea and can I introduce them to a clue bat? :p > > > PS. Also a mutt lover :-) > > With the amount of HTML mail out there I really don't understand how > people are able to use it anymore. Now, if I could get a 'stip html down to > plain text' side function to work… > > Someone using mutt in 2021 must be a hater of all forms of GUI :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: mbox to pst advice
On Sun, 17 Jan 2021 at 22:42, Benny Pedersen wrote: > On 2021-01-17 18:43, Odhiambo Washington wrote: > > > Personally, I would not bother looking for a script or even asking > > anyone if they knew how to convert > > mbox2pst. > > there is always alternatives :-) > > aid4mail > Yes :-) Spend some bucks! -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: mbox to pst advice
On Sun, 17 Jan 2021 at 20:27, Marc Roos wrote: > > > > > > Anyone an idea how to convert mbox ot pst on linux? > > > > > > > > > > > > Just run let Outlook fetch the mail and it will automatically create a > > PST. > > > > There is no need for wasting CPU cycles and time converting :-) > > Scripting this on linux would be much faster for me than doing it manually > with outlook. > I disagree. Outlook will take shorter than you take to write and run a script. In fact, if you gave me the login credential to the server, I'd fetch all the mail with Outlook in a short time and upload for you the PST back into the server :-) Personally, I would not bother looking for a script or even asking anyone if they knew how to convert mbox2pst. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: mbox to pst advice
On Sun, 17 Jan 2021 at 15:41, Marc Roos wrote: > > > Anyone an idea how to convert mbox ot pst on linux? > > > Just run let Outlook fetch the mail and it will automatically create a PST. There is no need for wasting CPU cycles and time converting :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: doveadm backup only working once?
gt;>>> sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes
> >>>>
> >>>
> location=mbox:~/mail/mailboxes:INBOX=/var/mail/synctest:DIRNAME=mBoX-MeSsAgEs:INDEX=~/mail/index:CONTROL=~/mail/control
> >>>> doveadm(synctest): Debug: fs: root=/home/synctest/mail/mailboxes,
> >>>> index=/home/synctest/mail/index, indexpvt=,
> >>>> control=/home/synctest/mail/control, inbox=/var/mail/synctest, alt=
> >>>> doveadm(synctest): Debug: brain M: Namespace has location
> >>>>
> >>>
> mbox:~/mail/mailboxes:INBOX=/var/mail/synctest:DIRNAME=mBoX-MeSsAgEs:INDEX=~/mail/index:CONTROL=~/mail/control
> >>>> doveadm(synctest): Debug: Namespace :
> >>>> /home/synctest/mail/mailboxes/INBOX doesn't exist yet, using default
> >>>> permissions
> >>>> doveadm(synctest): Debug: Namespace : Using permissions from
> >>>> /home/synctest/mail/mailboxes: mode=0700 gid=default
> >>>> dsync-local(synctest): Debug: brain M: Local
> >>>> mailbox tree: INBOX guid=f8ecea204a65f05fea46b4581695
> >>>> uid_validity=1609590090 uid_next=9 subs=no last_change=0 last_subs=0
> >>>> dsync-local(synctest): Debug: brain M: Remote
> >>>> mailbox tree: INBOX guid=f8ecea204a65f05fea46b4581695
> >>>> uid_validity=1609590090 uid_next=9 subs=no last_change=0 last_subs=0
> >>>> dsync-local(synctest): Debug: brain M:
> >>> Mailbox
> >>>> INBOX: local=f8ecea204a65f05fea46b4581695/0/1,
> >>>> remote=f8ecea204a65f05fea46b4581695/0/1: Mailboxes are equal
> >>>> dsync-local(synctest): Debug: Namespace :
> >>>> /home/synctest/mail/mailboxes/INBOX doesn't exist yet, using default
> >>>> permissions
> >>>> dsync-local(synctest): Debug: Namespace :
> >>>> Using permissions from /home/synctest/mail/mailboxes: mode=0700
> >>>> gid=default
> >>>> dsync-local(synctest): Debug: brain M: Import
> >>>> INBOX: Import change type=expunge GUID= UID=1 hdr_hash=
> >>>> result=Expunged mail has no GUID, can't verify it
> >>>> dsync-local(synctest): Debug: brain M: Import
> >>>> INBOX: Import change type=expunge GUID= UID=2 hdr_hash=
> >>>> result=Expunged mail has no GUID, can't verify it
> >>>> dsync-local(synctest): Debug: brain M: Import
> >>>> INBOX: Import change type=expunge GUID= UID=3 hdr_hash=
> >>>> result=Expunged mail has no GUID, can't verify it
> >>>> dsync-local(synctest): Debug: brain M: Import
> >>>> INBOX: Import change type=expunge GUID= UID=4 hdr_hash=
> >>>> result=Expunged mail has no GUID, can't verify it
> >>>> dsync-local(synctest): Debug: brain M: Import
> >>>> INBOX: Import change type=expunge GUID= UID=5 hdr_hash=
> >>>> result=Expunged mail has no GUID, can't verify it
> >>>> dsync-local(synctest): Debug: brain M: Import
> >>>> INBOX: Import change type=expunge GUID= UID=6 hdr_hash=
> >>>> result=Expunged mail has no GUID, can't verify it
> >>>> dsync-local(synctest): Warning: Deleting
> >>>> mailbox 'INBOX': UID=7 already exists locally for a different mail:
> >>>> Headers hashes don't match (9fc2f2229a1a2a8d5f12304cb5287f97 vs
> >>>> b62e0281b4f375a45040c552b55ab31a)
> >>>> dsync-local(synctest): Debug: brain M: Import
> >>>> INBOX: Import change type=save GUID=8bce3bc615e7f2a1dfad970a3cd36bdb
> >>>> UID=7 hdr_hash=9fc2f2229a1a2a8d5f12304cb5287f97 result=Headers hashes
> >>>> don't match (9fc2f2229a1a2a8d5f12304cb5287f97 vs
> >>>> b62e0281b4f375a45040c552b55ab31a)
> >>>> dsync-local(synctest): Debug: brain M: Import
> >>>> INBOX: Saved UIDs:
> >>>> dsync-local(synctest): Debug: doveadm-sieve:
> >>>> Iterating Sieve mailbox attributes
> >>>> dsync-local(synctest): Debug: sieve:
> >>>> Pigeonhole version 0.5.4 () initializing
> >>>> dsync-local(synctest): Debug: sieve: include:
> >>>> sieve_global is not set; it is currently not possible to include
> >>>> `:global' scripts.
> >>>> dsync-local(synctest): Debug: sieve: file
> >>>> storage: Using active Sieve script path:
> >>> /home/synctest/.dovecot.sieve
> >>>> dsync-local(synctest): Debug: sieve: file
> >>>> storage: Using script storage path: /home/synctest/sieve
> >>>> dsync-local(synctest): Debug: sieve: file
> >>>> storage: Using permissions from /home/synctest/sieve: mode=0700
> >>> gid=-1
> >>>> dsync-local(synctest): Debug: sieve: file
> >>>> storage: Relative path to sieve storage in active link: sieve/
> >>>> dsync-local(synctest): Debug: sieve: file
> >>>> storage: sync: Synchronization active
> >>>> dsync-local(synctest): Error: Couldn't delete
> >>>> mailbox INBOX: Permission denied
> >>>>
> >>>> root@server2:/home/synctest/mail# dovecot -n
> >>>> # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf
> >>>> # Pigeonhole version 0.5.4 ()
> >>>> # OS: Linux 4.19.0-12-amd64 x86_64 Debian 10.6
> >>>> # Hostname: server2.fritz.box
> >>>> auth_username_format = %Ln
> >>>> doveadm_password = # hidden, use -P to show it
> >>>> lda_mailbox_autocreate = yes
> >>>> login_trusted_networks = 192.168.3.0/24
> >>>> mail_location =
> >>>>
> >>>
> mbox:~/mail/mailboxes:INBOX=/var/mail/%u:DIRNAME=mBoX-MeSsAgEs:INDEX=~/mail/index:CONTROL=~/mail/control
> >>>> mail_privileged_group = mail
> >>>> managesieve_notify_capability = mailto
> >>>> managesieve_sieve_capability = fileinto reject envelope
> >>>> encoded-character vacation subaddress comparator-i;ascii-numeric
> >>>> relational regex imap4flags copy include variables body enotify
> >>>> environment mailbox date index ihave duplicate mime foreverypart
> >>>> extracttext
> >>>> namespace inbox {
> >>>>inbox = yes
> >>>>location =
> >>>>mailbox Drafts {
> >>>> special_use = \Drafts
> >>>>}
> >>>>mailbox Junk {
> >>>> special_use = \Junk
> >>>>}
> >>>>mailbox Sent {
> >>>> special_use = \Sent
> >>>>}
> >>>>mailbox "Sent Messages" {
> >>>> special_use = \Sent
> >>>>}
> >>>>mailbox Trash {
> >>>> special_use = \Trash
> >>>>}
> >>>>prefix =
> >>>> }
> >>>> passdb {
> >>>>driver = pam
> >>>> }
> >>>> plugin {
> >>>>sieve = ~/.dovecot.sieve
> >>>>sieve_default = /var/lib/dovecot/sieve/default.sieve
> >>>>sieve_dir = ~/sieve
> >>>> }
> >>>> postmaster_address = postmaster@"domain"
> >>>> protocols = imap pop3 lmtp
> >>>> service doveadm {
> >>>>inet_listener {
> >>>> port = 12345
> >>>>}
> >>>> }
> >>>> service managesieve-login {
> >>>>inet_listener sieve {
> >>>> port = 4190
> >>>>}
> >>>> }
> >>>> ssl_cert = >>>> ssl_dh = # hidden, use -P to show it
> >>>> ssl_key = # hidden, use -P to show it
> >>>> userdb {
> >>>>driver = passwd
> >>>> }
> >>>> protocol lmtp {
> >>>>mail_plugins = " sieve"
> >>>> }
> >>>> protocol lda {
> >>>>mail_plugins = " sieve"
> >>>> }
> >>>>
> >> --
> >> Christian Kivalo
>
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", grep ^[^#] :-)
Re: import_environment = $import_environment DEBUG=1 where should this be logged?
Hi Marc,
The same document says this:
rawlog binary
It works by checking if dovecot.rawlog/ directory exists in the logged in
user's home directory, and writing the traffic to mmdd-HHMMSS-pid.in
and .out files. Each connection gets their own in/out files. *Rawlog will
simply skip users who don't have the dovecot.rawlog/ directory and the
performance impact for those users is minimal.*
On Wed, 30 Dec 2020 at 20:10, Marc Roos wrote:
>
> You know by any chance how to limit this only for one user?
>
>
>
> -Original Message-
> From: Odhiambo Washington [mailto:odhia...@gmail.com]
> Sent: 30 December 2020 18:00
> To: dovecot
> Subject: Re: import_environment = $import_environment DEBUG=1 where
> should this be logged?
>
>
> Hi Marc,
>
> If you read the link keenly - Debugging/Rawlog - Dovecot Wiki
> <https://wiki.dovecot.org/Debugging/Rawlog> - you will realize that you
> need to do some stuff.
> I have done them and they produced the results.
>
> Edit /path/to/dovecot/conf.d/10-master.conf and add the following:
>
> Under this block:
>
> add executable = imap postlogin to the block that has service imap {
>
> ...
> }
>
> Then create another block in the same file as follows:
>
> service postlogin {
> executable = script-login -d rawlog
> unix_listener postlogin {
> }
> }
>
> Identify the user for whom you want the rawlogs:
>
> doveadm user -u techni...@mydomain.name
> userdb: techni...@mydomain.name
> user : techni...@mydomain.name
> home : /var/spool/virtual/mydomain.name/technical
> uid : 26
> gid : 26
>
> Now do the following:
> cd /var/spool/virtual/mydomain.name/technical
> mkdir dovecot.rawlog
> chown -R 26:26 dovecot.rawlog
>
> systemctl restart dovecot (or however you do it in CentOS)
>
> Now login to imap as the user .. perform some operations.
>
> Now look inside
> /var/spool/virtual/mydomain.name/technical/dovecot.rawlog/
>
> PS: Adapt as necessary. I tested this on FreeBSD with dovecot- 2.3.11.3
>
> Ignore the /tmp/rawlog/%u portion of the HOWTO. I did it too, but there
> was nothing in /tmp/rawlog/ even though I created the directory and did
> chmod 1777 /tmp/rawlog.
>
> Adios.
>
>
>
>
> On Wed, 30 Dec 2020 at 19:30, Marc Roos
> wrote:
>
>
>
>
> You can also set DEBUG environment to have rawlog log an info
> message
> why it's not doing anything:
> import_environment = $import_environment DEBUG=1
>
> Where should this message appear, I also don't have this one.
>
> [1]
> https://wiki2.dovecot.org/Debugging/Rawlog
>
>
>
>
> --
>
> Best regards,
> Odhiambo WASHINGTON,
> Nairobi,KE
> +254 7 3200 0004/+254 7 2274 3223
> "Oh, the cruft.", grep ^[^#] :-)
>
>
>
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", grep ^[^#] :-)
Re: import_environment = $import_environment DEBUG=1 where should this be logged?
Hi Marc,
If you read the link keenly - Debugging/Rawlog - Dovecot Wiki
<https://wiki.dovecot.org/Debugging/Rawlog> - you will realize that you
need to do some stuff.
I have done them and they produced the results.
Edit /path/to/dovecot/conf.d/10-master.conf and add the following:
Under this block:
add executable = imap postlogin to the block that has
service imap {
...
}
Then create another block in the same file as follows:
service postlogin {
executable = script-login -d rawlog
unix_listener postlogin {
}
}
Identify the user for whom you want the rawlogs:
doveadm user -u techni...@mydomain.name
userdb: techni...@mydomain.name
user : techni...@mydomain.name
home : /var/spool/virtual/mydomain.name/technical
uid : 26
gid : 26
Now do the following:
cd /var/spool/virtual/mydomain.name/technical
mkdir dovecot.rawlog
chown -R 26:26 dovecot.rawlog
systemctl restart dovecot (or however you do it in CentOS)
Now login to imap as the user .. perform some operations.
Now look inside /var/spool/virtual/mydomain.name/technical/dovecot.rawlog/
PS: Adapt as necessary. I tested this on FreeBSD with dovecot- 2.3.11.3
Ignore the /tmp/rawlog/%u portion of the HOWTO. I did it too, but there was
nothing in /tmp/rawlog/ even though I created the directory and did chmod
1777 /tmp/rawlog.
Adios.
On Wed, 30 Dec 2020 at 19:30, Marc Roos wrote:
>
>
> You can also set DEBUG environment to have rawlog log an info message
> why it's not doing anything:
> import_environment = $import_environment DEBUG=1
>
> Where should this message appear, I also don't have this one.
>
> [1]
> https://wiki2.dovecot.org/Debugging/Rawlog
>
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", grep ^[^#] :-)
Re: Outlook with Dovecot
On Sun, 13 Dec 2020 at 18:22, Elise wrote: > Op 12-12-20 om 17:20 schreef Elise: > > > dovecot-2.3.11.3_1 > > Providing the correct email address and password. > > I think the origin of this issue is caused by Outlook itself. > Setting up a new account in Outlook, one has to provide an email address > instead of a user name. With using BSD usermanager, adding a user named > 'i...@mydomain.com' is converted automatically to user 'ilse'. > > I am not expecting that Microsoft will solve this issue on short term > though. Will stick with Thunderbird (as I already planned) but how nice > it would be to make Outlook my backup mail client with > IMAP/Dovecot/Postfix... > > Best, E. > Elise, your problem is simple. And yes, I am a *BSD diehard for donkey years. You want to setup a system that handles virtual users. The BSD usermanager creates system accounts (/etc/passwd) and those cannot be made to be user@domain by default, although Dovecot authenticating system users and concatenating the domain is possible. So what you need to focus on is whether you want to authenticate system users or virtual users. Read Postfix docs about this. For Dovecot, it is easy. Just look at the passdb and userdb configs and Dovecot will do whatever you decide from the above choices. It can actually do both - and many! I have a system where dovecot authenticates system accounts and vurtual accounts (MySQL and SambaAD) . I am an Exim user though. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: Dovecot+Samba AD - authentication failure - SOLVED
On Tue, 24 Nov 2020 at 14:51, Aki Tuomi wrote:
>
> > On 24/11/2020 13:20 Odhiambo Washington wrote:
> >
> >
> >
> >
> >
> > On Sun, 22 Nov 2020 at 15:08, Odhiambo Washington
> wrote:
> > > Hi,
> > >
> > > I have setup samba4 as AD and hoping to have dovecot authenticate
> users against it. I am facing challenges though and I am unable to figure
> it out.
> > > I could do with a third eye to help me spot what is wrong.
> > >
> > >
> > >
> > > root@adc0:/etc# doveadm auth test -x service=imap
> odhiambo@newideatest.local
> > > Password:
> > > passdb: odhiambo@newideatest.local auth failed
> > > extra fields:
> > >
> > > info.log:
> > >
> > > Nov 22 14:31:08 auth: Info: > >
> > >
> > > Here is my doveconf -n:
> > >
> > > https://paste.ubuntu.com/p/SPmrxZxHPx/
> > >
> > > My dovecot-ldap.cont.ext:
> > >
> > > uris = ldap://localhost/
> > > dn = "dovecot@newideatest.local"
> > > dnpass = ""
> > > sasl_bind = no
> > > tls = no
> > > ldap_version = 3
> > > deref = never
> > > scope = subtree
> > > base = cn=Users,dc=NEWIDEATEST,dc=LOCAL
> > > auth_bind = yes
> > > user_filter =
> (&(objectClass=user)(!(userAccountControl:1.2.840.113556.1.4.803:=2))(|(mail=%u)(sAMAccountName=%u)(otherMailbox=%u)))
> > > user_attrs =
> sAMAccountName=user,userPassword=password,=mail=maildir:/home/%n/Maildir/
> > > pass_filter =
> (&(objectClass=user)(!(userAccountControl:1.2.840.113556.1.4.803:=2))(sAMAccountName=%u))
> > > pass_attrs = sAMAccountName=user,userPassword=password
> > >
> > > The use exists in the database:
> > >
> >
> >
> > For the record, this is what I finally came up with that worked -
> dovecot-ldap.conf.ext:
> >
> >
> > # BEGIN
> > uris = ldap://localhost/
> > dn = "dovecot@newideatest.local"
> > dnpass = "verystupid"
> > sasl_bind = no
> > tls = no
> > ldap_version = 3
> > deref = never
> > scope = subtree
> > base = cn=Users,dc=NEWIDEATEST,dc=LOCAL
> > auth_bind = yes
>
> You probably would want to set this to 'no', it causes dovecot to rebind
> after authentication. This is not required when you can return password
from LDAP, it is only required when you have to do first a lookup and then
> authenticate as the user to verify password.
>
Hello Aki,
Thanks for looking at this.
In my case, when I change to "auth_bind = no", then this happens:
root@adc0:/etc/dovecot# telnet 0 143
Trying 0.0.0.0...
Connected to 0.
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+
STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot (Ubuntu) ready.
1 login odhiambo@newideatest.local XXX
1 NO [AUTHENTICATIONFAILED] Authentication failed.
1 logout
Auth succeeds though when I have it set to "yes".
My conf.d/auth-ldap.conf.ext contains:
passdb {
driver = ldap
args = /etc/dovecot/dovecot-ldap.conf.ext
}
userdb {
driver = static
args = uid=Debian-exim gid=Debian-exim home=/var/spool/virtual/%Ld/%Ln
}
How can I return the password from LDAP?
I'd be happy to know what I need to do so that I can use your suggestion.
This LDAP stuff is still quite some "greek" to me.
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", grep ^[^#] :-)
Re: Dovecot+Samba AD - authentication failure - SOLVED
On Sun, 22 Nov 2020 at 15:08, Odhiambo Washington wrote: > Hi, > > I have setup samba4 as AD and hoping to have dovecot authenticate users > against it. I am facing challenges though and I am unable to figure it out. > I could do with a third eye to help me spot what is wrong. > > > root@adc0:/etc# doveadm auth test -x service=imap > odhiambo@newideatest.local > Password: > passdb: odhiambo@newideatest.local auth failed > extra fields: > temp > Warning: auth-client: conn unix:/var/run/dovecot/auth-client: Auth > connection closed with 1 pending requests (max 0 secs, pid=10537, EOF) > Fatal: Couldn't connect to auth socket > > A test against IMAP gives the following debug information: > Nov 22 14:31:01 auth: Debug: Loading modules from directory: > /usr/lib/dovecot/modules/auth > Nov 22 14:31:01 auth: Debug: Module loaded: > /usr/lib/dovecot/modules/auth/lib20_auth_var_expand_crypt.so > Nov 22 14:31:01 auth: Debug: Module loaded: > /usr/lib/dovecot/modules/auth/libdriver_mysql.so > Nov 22 14:31:01 auth: Debug: Loading modules from directory: > /usr/lib/dovecot/modules/auth > Nov 22 14:31:01 auth: Debug: Module loaded: > /usr/lib/dovecot/modules/auth/libauthdb_ldap.so > Nov 22 14:31:01 auth: Debug: Read auth token secret from > /var/run/dovecot/auth-token-secret.dat > Nov 22 14:31:01 auth: Debug: auth client connected (pid=10979) > Nov 22 14:31:08 auth: Debug: client in: AUTH1 PLAIN > service=imapsecured session=uPLvabC0RIh/AAABlip=127.0.0.1 > rip=127.0.0.1 lport=143 rport=34884 resp= > Nov 22 14:31:08 auth: Debug: > ldap(odhiambo@newideatest.local,127.0.0.1,): > Performing passdb lookup > Nov 22 14:31:08 auth: Debug: > ldap(odhiambo@newideatest.local,127.0.0.1,): > bind search: base=cn=Users,dc=NEWIDEATEST,dc=LOCAL > filter=(&(objectClass=user)(!(userAccountControl:1.2.840.113556.1.4.803:=2))(sAMAccountName=odhiambo@newideatest.local > )) > Nov 22 14:31:08 auth: Debug: > ldap(odhiambo@newideatest.local,127.0.0.1,): > no fields returned by the server *< * > Nov 22 14:31:08 auth: Debug: > ldap(odhiambo@newideatest.local,127.0.0.1,): > Finished passdb lookup > Nov 22 14:31:08 auth: Debug: > auth(odhiambo@newideatest.local,127.0.0.1,): > Auth request finished > Nov 22 14:31:10 auth: Debug: client passdb out: FAIL1 > user=odhiambo@newideatest.local > > info.log: > > Nov 22 14:31:08 auth: Info: ldap(odhiambo@newideatest.local > ,127.0.0.1,):* unknown user* (given password: XXX) > Nov 22 14:31:15 imap-login: Info: Aborted login (auth failed, 1 attempts > in 7 secs): user=, method=PLAIN, > rip=127.0.0.1, lip=127.0.0.1, secured, session= > > > Here is my doveconf -n: > > https://paste.ubuntu.com/p/SPmrxZxHPx/ > > My dovecot-ldap.cont.ext: > > uris = ldap://localhost/ > dn = "dovecot@newideatest.local" > dnpass = "" > sasl_bind= no > tls = no > ldap_version = 3 > deref= never > scope= subtree > base = cn=Users,dc=NEWIDEATEST,dc=LOCAL > auth_bind= yes > user_filter = > (&(objectClass=user)(!(userAccountControl:1.2.840.113556.1.4.803:=2))(|(mail=%u)(sAMAccountName=%u)(otherMailbox=%u))) > user_attrs = > sAMAccountName=user,userPassword=password,=mail=maildir:/home/%n/Maildir/ > pass_filter = > (&(objectClass=user)(!(userAccountControl:1.2.840.113556.1.4.803:=2))(sAMAccountName=%u)) > pass_attrs = sAMAccountName=user,userPassword=password > > The use exists in the database: > > *root@adc0:/var/log/dovecot# samba-tool user show odhiambo* > ldb_wrap open of secrets.ldb > dn: CN=Odhiambo Washington,CN=Users,DC=newideatest,DC=local > objectClass: top > objectClass: person > objectClass: organizationalPerson > objectClass: user > cn: Odhiambo Washington > sn: Washington > givenName: Odhiambo > instanceType: 4 > whenCreated: 20201120101420.0Z > displayName: Odhiambo Washington > uSNCreated: 4086 > name: Odhiambo Washington > objectGUID: e6969596-8b28-41af-b5d8-cea63cc97f98 > badPwdCount: 0 > codePage: 0 > countryCode: 0 > badPasswordTime: 0 > lastLogoff: 0 > lastLogon: 0 > primaryGroupID: 513 > objectSid: S-1-5-21-701866827-3355127779-3787685610-1106 > accountExpires: 9223372036854775807 > logonCount: 0 > sAMAccountName: odhiambo > sAMAccountType: 805306368 > userPrincipalName: odhiambo@newideatest.local > objectCategory: > CN=Person,CN=Schema,CN=Configuration,DC=newideatest,DC=local > mail: odhiambo@newideatest.local > loginShell: /bin/bash > userAccountControl: 512 > pwdLastSet: 132505181852397220 > whenChanged: 20201122112945.0Z > uSNChanged: 4104 > di
Dovecot+Samba AD - authentication failure
Hi, I have setup samba4 as AD and hoping to have dovecot authenticate users against it. I am facing challenges though and I am unable to figure it out. I could do with a third eye to help me spot what is wrong. root@adc0:/etc# doveadm auth test -x service=imap odhiambo@newideatest.local Password: passdb: odhiambo@newideatest.local auth failed extra fields: temp Warning: auth-client: conn unix:/var/run/dovecot/auth-client: Auth connection closed with 1 pending requests (max 0 secs, pid=10537, EOF) Fatal: Couldn't connect to auth socket A test against IMAP gives the following debug information: Nov 22 14:31:01 auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Nov 22 14:31:01 auth: Debug: Module loaded: /usr/lib/dovecot/modules/auth/lib20_auth_var_expand_crypt.so Nov 22 14:31:01 auth: Debug: Module loaded: /usr/lib/dovecot/modules/auth/libdriver_mysql.so Nov 22 14:31:01 auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Nov 22 14:31:01 auth: Debug: Module loaded: /usr/lib/dovecot/modules/auth/libauthdb_ldap.so Nov 22 14:31:01 auth: Debug: Read auth token secret from /var/run/dovecot/auth-token-secret.dat Nov 22 14:31:01 auth: Debug: auth client connected (pid=10979) Nov 22 14:31:08 auth: Debug: client in: AUTH1 PLAIN service=imapsecured session=uPLvabC0RIh/AAABlip=127.0.0.1 rip=127.0.0.1 lport=143 rport=34884 resp= Nov 22 14:31:08 auth: Debug: ldap(odhiambo@newideatest.local,127.0.0.1,): Performing passdb lookup Nov 22 14:31:08 auth: Debug: ldap(odhiambo@newideatest.local,127.0.0.1,): bind search: base=cn=Users,dc=NEWIDEATEST,dc=LOCAL filter=(&(objectClass=user)(!(userAccountControl:1.2.840.113556.1.4.803:=2))(sAMAccountName=odhiambo@newideatest.local )) Nov 22 14:31:08 auth: Debug: ldap(odhiambo@newideatest.local,127.0.0.1,): no fields returned by the server *< * Nov 22 14:31:08 auth: Debug: ldap(odhiambo@newideatest.local,127.0.0.1,): Finished passdb lookup Nov 22 14:31:08 auth: Debug: auth(odhiambo@newideatest.local,127.0.0.1,): Auth request finished Nov 22 14:31:10 auth: Debug: client passdb out: FAIL1 user=odhiambo@newideatest.local info.log: Nov 22 14:31:08 auth: Info: ldap(odhiambo@newideatest.local ,127.0.0.1,):* unknown user* (given password: XXX) Nov 22 14:31:15 imap-login: Info: Aborted login (auth failed, 1 attempts in 7 secs): user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured, session= Here is my doveconf -n: https://paste.ubuntu.com/p/SPmrxZxHPx/ My dovecot-ldap.cont.ext: uris = ldap://localhost/ dn = "dovecot@newideatest.local" dnpass = "" sasl_bind= no tls = no ldap_version = 3 deref= never scope= subtree base = cn=Users,dc=NEWIDEATEST,dc=LOCAL auth_bind= yes user_filter = (&(objectClass=user)(!(userAccountControl:1.2.840.113556.1.4.803:=2))(|(mail=%u)(sAMAccountName=%u)(otherMailbox=%u))) user_attrs = sAMAccountName=user,userPassword=password,=mail=maildir:/home/%n/Maildir/ pass_filter = (&(objectClass=user)(!(userAccountControl:1.2.840.113556.1.4.803:=2))(sAMAccountName=%u)) pass_attrs = sAMAccountName=user,userPassword=password The use exists in the database: *root@adc0:/var/log/dovecot# samba-tool user show odhiambo* ldb_wrap open of secrets.ldb dn: CN=Odhiambo Washington,CN=Users,DC=newideatest,DC=local objectClass: top objectClass: person objectClass: organizationalPerson objectClass: user cn: Odhiambo Washington sn: Washington givenName: Odhiambo instanceType: 4 whenCreated: 20201120101420.0Z displayName: Odhiambo Washington uSNCreated: 4086 name: Odhiambo Washington objectGUID: e6969596-8b28-41af-b5d8-cea63cc97f98 badPwdCount: 0 codePage: 0 countryCode: 0 badPasswordTime: 0 lastLogoff: 0 lastLogon: 0 primaryGroupID: 513 objectSid: S-1-5-21-701866827-3355127779-3787685610-1106 accountExpires: 9223372036854775807 logonCount: 0 sAMAccountName: odhiambo sAMAccountType: 805306368 userPrincipalName: odhiambo@newideatest.local objectCategory: CN=Person,CN=Schema,CN=Configuration,DC=newideatest,DC=local mail: odhiambo@newideatest.local loginShell: /bin/bash userAccountControl: 512 pwdLastSet: 132505181852397220 whenChanged: 20201122112945.0Z uSNChanged: 4104 distinguishedName: CN=Odhiambo Washington,CN=Users,DC=newideatest,DC=local -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: Sieve filter script EXECUTION FAILED
On Fri, 30 Oct 2020 at 20:12, @lbutlr wrote:
> So, I have the sieve working up to the point that it calls the script, and
> the script is called (I get different errors if the script is not there,
> for example).
>
> filter action
> execute program `darkmode.sh'
> [[EXECUTION ABORTED]]
>
> There's no other error logged (for example, when I had
> sieve_filter_bin_dir miss-set, I would get:
>
> sieve: action filter: failed to execute program `darkmode.sh':
> vnd.dovecot.filter extension is unconfigured
>
> In /var/log/messages, but I fixed that.
>
> I assume there is something wrong with what I am doing in the script, bit
> that is something I am not finding any examples on that are proving useful.
>
> The script file is simply:
>
> Darkmode.sh:
> #!/bin/sh
> echo $1 | sed -e '||* {color:white !important;
> background-color: black !important; } |'
>
echo $1 | sed -e 's||* {color:white !important;
background-color: black !important; } |g'
??
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", grep ^[^#] :-)
Re: Filtering mails with sieve filters - SOLVED
I doubt there is a way to do that when using the SOGo web UI.
On Fri, 30 Oct 2020 at 15:57, Tom Talpey wrote:
> You might consider adding "stop;" after the fileinto, otherwise
> a second match might process the message again, moving it
> elsewhere, etc.
>
> Tom.
>
> On 10/30/2020 5:47 AM, Odhiambo Washington wrote:
> >
> > Answering to myself,
> >
> > The issue was as a result of a config parameter for SOGo:
> >
> > Changed
> > NGImap4ConnectionStringSeparator = "/";
> >
> > to
> >
> > NGImap4ConnectionStringSeparator = ".";
> >
> > and the problem is solved.
> >
> >
> > On Fri, 30 Oct 2020 at 11:43, Odhiambo Washington > <mailto:odhia...@gmail.com>> wrote:
> >
> > Hello good people,
> >
> > I have dovecot- 2.3.7.2 (Ubuntu Ubuntu 20.04.1 LTS) running fine.
> > However, I have a hitch with mail filtering.
> >
> > Using SOGo as the webmail UI, I created a filter rule which resulted
> > into the rule below:
> >
> > require ["fileinto"];
> > if allof (address :contains "from" "odhiambo") {
> > fileinto "INBOX/Odhiambo";
> > }
> >
> > However, the test mail I sent did not end up the folder expected.
> >
> > lda.log contains this info:
> > Oct 30 07:39:07 lda(wash@mydomain)<2415266>:
> > Info: sieve:
> > msgid= o8unvr152x...@mail.gmail.com
> > <mailto:o8unvr152x...@mail.gmail.com>>: stored mail into mailbox
> 'INBOX'
> > Oct 30 07:39:07 lda(wash@mydomain)<2415266>:
> > Info: sieve: Execution of script
> > /var/spool/virtual/mydomain/wash/.dovecot.sieve failed, but implicit
> > keep was successful (user logfile
> > /var/spool/virtual/mydomain/wash/.dovecot.sieve.log may reveal
> > additional details)
> >
> > And the .dovecot.sieve.log contains:
> > sieve: info: started log at Oct 30 07:39:07.
> > error:
> > msgid= o8unvr152x...@mail.gmail.com
> > <mailto:o8unvr152x...@mail.gmail.com>>: failed to store into mailbox
> > 'INBOX/Odhiambo': *Invalid mailbox name: Name must not have '/'
> > characters.*
> > *
> > *
> > What might be the problem here??
> >
> >
> > dovecot -n output is below:
> >
> > # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf
> > # Pigeonhole version 0.5.7.2 ()
> > # OS: Linux 5.4.0-29-generic x86_64 Ubuntu 20.04.1 LTS ext4
> > # Hostname: jp.mydomain
> > auth_mechanisms = plain login
> > auth_socket_path = /var/run/dovecot/auth-userdb
> > debug_log_path = /var/log/dovecot/debug.log
> > default_login_user = dovecot
> > default_vsz_limit = 2 G
> > disable_plaintext_auth = no
> > first_valid_uid = 110
> > hostname = gw.mydomain
> > info_log_path = /var/log/dovecot/info.log
> > log_path = /var/log/dovecot/error.log
> > mail_gid = Debian-exim
> > mail_location =
> maildir:/var/spool/virtual/%d/%n/Maildir:INDEX=/var/spool/virtual/indexes/%d/%1n/%n
> > mail_plugins = fts
> > mail_privileged_group = mail
> > mail_server_admin = postmaster@mydomain
> > mail_uid = Debian-exim
> > managesieve_notify_capability = mailto
> > managesieve_sieve_capability = fileinto reject envelope
> encoded-character vacation subaddress comparator-i;ascii-numeric relational
> regex imap4flags copy include variables body enotify environment mailbox
> date index ihave duplicate mime foreverypart extracttext imapsieve
> vnd.dovecot.imapsieve
> > namespace inbox {
> >inbox = yes
> >location =
> >mailbox Drafts {
> > special_use = \Drafts
> >}
> >mailbox Junk {
> > special_use = \Junk
> >}
> >mailbox Sent {
> > special_use = \Sent
> >}
> >mailbox "Sent Messages" {
> > special_use = \Sent
> >}
> >mailbox Trash {
> > special_use = \Trash
> >}
> >prefix =
> > }
> > passdb {
> >args = /etc/dovecot/dovecot-sql.conf.ext
> >driver = sql
> > }
> > plugin {
> >fts_autoindex = yes
> >fts_autoindex_exclude = \Junk
> >fts_autoindex_exclude2 = \Trash
> >fts_autoindex_exclude3 = \Drafts
>
Re: Filtering mails with sieve filters - SOLVED
Answering to myself,
The issue was as a result of a config parameter for SOGo:
Changed
NGImap4ConnectionStringSeparator = "/";
to
NGImap4ConnectionStringSeparator = ".";
and the problem is solved.
On Fri, 30 Oct 2020 at 11:43, Odhiambo Washington
wrote:
> Hello good people,
>
> I have dovecot- 2.3.7.2 (Ubuntu Ubuntu 20.04.1 LTS) running fine.
> However, I have a hitch with mail filtering.
>
> Using SOGo as the webmail UI, I created a filter rule which resulted into
> the rule below:
>
> require ["fileinto"];
> if allof (address :contains "from" "odhiambo") {
> fileinto "INBOX/Odhiambo";
> }
>
> However, the test mail I sent did not end up the folder expected.
>
> lda.log contains this info:
> Oct 30 07:39:07 lda(wash@mydomain)<2415266>:
> Info: sieve: msgid= o8unvr152x...@mail.gmail.com>: stored mail into mailbox 'INBOX'
> Oct 30 07:39:07 lda(wash@mydomain)<2415266>:
> Info: sieve: Execution of script
> /var/spool/virtual/mydomain/wash/.dovecot.sieve failed, but implicit keep
> was successful (user logfile
> /var/spool/virtual/mydomain/wash/.dovecot.sieve.log may reveal additional
> details)
>
> And the .dovecot.sieve.log contains:
> sieve: info: started log at Oct 30 07:39:07.
> error: msgid= o8unvr152x...@mail.gmail.com>: failed to store into mailbox
> 'INBOX/Odhiambo': *Invalid mailbox name: Name must not have '/'
> characters.*
>
> What might be the problem here??
>
>
> dovecot -n output is below:
>
> # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf
> # Pigeonhole version 0.5.7.2 ()
> # OS: Linux 5.4.0-29-generic x86_64 Ubuntu 20.04.1 LTS ext4
> # Hostname: jp.mydomain
> auth_mechanisms = plain login
> auth_socket_path = /var/run/dovecot/auth-userdb
> debug_log_path = /var/log/dovecot/debug.log
> default_login_user = dovecot
> default_vsz_limit = 2 G
> disable_plaintext_auth = no
> first_valid_uid = 110
> hostname = gw.mydomain
> info_log_path = /var/log/dovecot/info.log
> log_path = /var/log/dovecot/error.log
> mail_gid = Debian-exim
> mail_location =
> maildir:/var/spool/virtual/%d/%n/Maildir:INDEX=/var/spool/virtual/indexes/%d/%1n/%n
> mail_plugins = fts
> mail_privileged_group = mail
> mail_server_admin = postmaster@mydomain
> mail_uid = Debian-exim
> managesieve_notify_capability = mailto
> managesieve_sieve_capability = fileinto reject envelope encoded-character
> vacation subaddress comparator-i;ascii-numeric relational regex imap4flags
> copy include variables body enotify environment mailbox date index ihave
> duplicate mime foreverypart extracttext imapsieve vnd.dovecot.imapsieve
> namespace inbox {
> inbox = yes
> location =
> mailbox Drafts {
> special_use = \Drafts
> }
> mailbox Junk {
> special_use = \Junk
> }
> mailbox Sent {
> special_use = \Sent
> }
> mailbox "Sent Messages" {
> special_use = \Sent
> }
> mailbox Trash {
> special_use = \Trash
> }
> prefix =
> }
> passdb {
> args = /etc/dovecot/dovecot-sql.conf.ext
> driver = sql
> }
> plugin {
> fts_autoindex = yes
> fts_autoindex_exclude = \Junk
> fts_autoindex_exclude2 = \Trash
> fts_autoindex_exclude3 = \Drafts
> fts_autoindex_exclude4 = \Spam
> fts_enforced = yes
> imapsieve_mailbox1_before = file:/usr/lib/dovecot/sieve/report-spam.sieve
> imapsieve_mailbox1_causes = COPY
> imapsieve_mailbox1_name = Spam
> imapsieve_mailbox2_before = file:/usr/lib/dovecot/sieve/report-ham.sieve
> imapsieve_mailbox2_causes = COPY
> imapsieve_mailbox2_from = Spam
> imapsieve_mailbox2_name = *
> plugin = fts managesieve sieve
> sieve = file:~/sieve;active=~/.dovecot.sieve
> sieve_execute_bin_dir = /usr/lib/dovecot/sieve-execute
> sieve_filter_bin_dir = /usr/lib/dovecot/sieve-filter
> sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment
> sieve_pipe_bin_dir = /usr/lib/dovecot/sieve
> sieve_plugins = sieve_imapsieve sieve_extprograms
> }
> postmaster_address = postmaster@mydomain
> protocols = imap lmtp sieve
> service auth {
> unix_listener auth-client {
> mode = 0600
> user = Debian-exim
> }
> unix_listener auth-userdb {
> group = Debian-exim
> user = Debian-exim
> }
> }
> service stats {
> unix_listener stats-reader {
> user = Debian-exim
> }
> unix_listener stats-writer {
> user = Debian-exim
> }
> }
> service submission-login {
> inet_listener submission {
> port = 2587
> }
> }
> ssl_cert = ssl_client_ca_dir = /etc/ssl/certs
> ssl_dh = # hidden, use -P to show it
> ssl_key = # hidden, use -
Filtering mails with sieve filters
Hello good people,
I have dovecot- 2.3.7.2 (Ubuntu Ubuntu 20.04.1 LTS) running fine.
However, I have a hitch with mail filtering.
Using SOGo as the webmail UI, I created a filter rule which resulted into
the rule below:
require ["fileinto"];
if allof (address :contains "from" "odhiambo") {
fileinto "INBOX/Odhiambo";
}
However, the test mail I sent did not end up the folder expected.
lda.log contains this info:
Oct 30 07:39:07 lda(wash@mydomain)<2415266>: Info:
sieve: msgid=: stored mail into mailbox 'INBOX'
Oct 30 07:39:07 lda(wash@mydomain)<2415266>: Info:
sieve: Execution of script /var/spool/virtual/mydomain/wash/.dovecot.sieve
failed, but implicit keep was successful (user logfile
/var/spool/virtual/mydomain/wash/.dovecot.sieve.log may reveal additional
details)
And the .dovecot.sieve.log contains:
sieve: info: started log at Oct 30 07:39:07.
error: msgid=: failed to store into mailbox
'INBOX/Odhiambo': *Invalid mailbox name: Name must not have '/' characters.*
What might be the problem here??
dovecot -n output is below:
# 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.7.2 ()
# OS: Linux 5.4.0-29-generic x86_64 Ubuntu 20.04.1 LTS ext4
# Hostname: jp.mydomain
auth_mechanisms = plain login
auth_socket_path = /var/run/dovecot/auth-userdb
debug_log_path = /var/log/dovecot/debug.log
default_login_user = dovecot
default_vsz_limit = 2 G
disable_plaintext_auth = no
first_valid_uid = 110
hostname = gw.mydomain
info_log_path = /var/log/dovecot/info.log
log_path = /var/log/dovecot/error.log
mail_gid = Debian-exim
mail_location =
maildir:/var/spool/virtual/%d/%n/Maildir:INDEX=/var/spool/virtual/indexes/%d/%1n/%n
mail_plugins = fts
mail_privileged_group = mail
mail_server_admin = postmaster@mydomain
mail_uid = Debian-exim
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope
encoded-character vacation subaddress comparator-i;ascii-numeric
relational regex imap4flags copy include variables body enotify
environment mailbox date index ihave duplicate mime foreverypart
extracttext imapsieve vnd.dovecot.imapsieve
namespace inbox {
inbox = yes
location =
mailbox Drafts {
special_use = \Drafts
}
mailbox Junk {
special_use = \Junk
}
mailbox Sent {
special_use = \Sent
}
mailbox "Sent Messages" {
special_use = \Sent
}
mailbox Trash {
special_use = \Trash
}
prefix =
}
passdb {
args = /etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
plugin {
fts_autoindex = yes
fts_autoindex_exclude = \Junk
fts_autoindex_exclude2 = \Trash
fts_autoindex_exclude3 = \Drafts
fts_autoindex_exclude4 = \Spam
fts_enforced = yes
imapsieve_mailbox1_before = file:/usr/lib/dovecot/sieve/report-spam.sieve
imapsieve_mailbox1_causes = COPY
imapsieve_mailbox1_name = Spam
imapsieve_mailbox2_before = file:/usr/lib/dovecot/sieve/report-ham.sieve
imapsieve_mailbox2_causes = COPY
imapsieve_mailbox2_from = Spam
imapsieve_mailbox2_name = *
plugin = fts managesieve sieve
sieve = file:~/sieve;active=~/.dovecot.sieve
sieve_execute_bin_dir = /usr/lib/dovecot/sieve-execute
sieve_filter_bin_dir = /usr/lib/dovecot/sieve-filter
sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment
sieve_pipe_bin_dir = /usr/lib/dovecot/sieve
sieve_plugins = sieve_imapsieve sieve_extprograms
}
postmaster_address = postmaster@mydomain
protocols = imap lmtp sieve
service auth {
unix_listener auth-client {
mode = 0600
user = Debian-exim
}
unix_listener auth-userdb {
group = Debian-exim
user = Debian-exim
}
}
service stats {
unix_listener stats-reader {
user = Debian-exim
}
unix_listener stats-writer {
user = Debian-exim
}
}
service submission-login {
inet_listener submission {
port = 2587
}
}
ssl_cert =
Re: Unable to access mail via Outlook
On Mon, 19 Oct 2020 at 09:54, Aki Tuomi wrote: > > > On 19/10/2020 09:48 Odhiambo Washington wrote: > > > > > > > > > > > > On Mon, 19 Oct 2020 at 09:27, Aki Tuomi > wrote: > > > > > > > On 19/10/2020 09:16 Odhiambo Washington wrote: > > > > > > > > > > > > Bump! > > > > > > > > > > > > On Fri, 16 Oct 2020 at 13:26, Odhiambo Washington < > odhia...@gmail.com> wrote: > > > > > > > > > > > > > > > > > > > > On Fri, 16 Oct 2020 at 13:15, Aki Tuomi < > aki.tu...@open-xchange.com> wrote: > > > > > > > > > > > > > On 16/10/2020 13:11 Odhiambo Washington > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, 16 Oct 2020 at 08:19, Aki Tuomi < > aki.tu...@open-xchange.com> wrote: > > > > > > > > > On 15/10/2020 18:14 Odhiambo Washington < > odhia...@gmail.com> wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > Here is what I see on the error.log: > > > > > > > > > > > > > > > > > > Oct 15 17:37:58 > > > imap(techni...@mydomain.name)<62260><9ucgmLax7s3F6FH2>: > Error: Mailbox INBOX: Cache /var/spool/virtual/ > mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache > ( > http://mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache) > ( > http://mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache) > ( > http://mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache) > ( > http://mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache): > Deleting corrupted cache record uid=798: > > > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > Odhiambo WASHINGTON, > > > > > > > > > Nairobi,KE > > > > > > > > > +254 7 3200 0004/+254 7 2274 3223 > > > > > > > > > "Oh, the cruft.",grep ^[^#] :-) > > > > > > > > > > > > > > > > There is a bug in compression in 2.3.11.3, see > https://dovecot.org/pipermail/dovecot/2020-September/119907.html > > > > > > > > > > > > > > > > Aki > > > > > > > > > > > > > > I don't use any compression mechanisms in my setup. > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > Best regards, > > > > > > > Odhiambo WASHINGTON, > > > > > > > Nairobi,KE > > > > > > > +254 7 3200 0004/+254 7 2274 3223 > > > > > > > "Oh, the cruft.",grep ^[^#] :-) > > > > > > > > > > > > Try rm /var/spool/virtual/ > mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache > ( > http://mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache) > ( > http://mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache) > > > > > > > > > > > > > Aki > > > > > > > > > > I have done that. Sent a test mail. Outlook (using IMAP) does not > sync the mailbox. It does not even receive the test mail. > > > > > root@gw:/ # telnet 0 110 > > > > > Trying 0.0.0.0... > > > > > Connected to 0. > > > > > Escape character is '^]'. > > > > > +OK Dovecot ready. > > > > > user techni...@mydomain.name > > > > > +OK > > > > > pass XXX > > > > > +OK Logged in. > > > > > stat > > > > > +OK 330 23948401 > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > Best regards, > > > > > Odhiambo WASHINGTON, > > > > > Nairobi,KE > > > > > > Hi! > > > > > > Are you sure the mail is delivered to right place? Can you see this > mail using
Re: Unable to access mail via Outlook
On Mon, 19 Oct 2020 at 09:27, Aki Tuomi wrote: > > > On 19/10/2020 09:16 Odhiambo Washington wrote: > > > > > > Bump! > > > > > > On Fri, 16 Oct 2020 at 13:26, Odhiambo Washington > wrote: > > > > > > > > > > > > On Fri, 16 Oct 2020 at 13:15, Aki Tuomi > wrote: > > > > > > > > > On 16/10/2020 13:11 Odhiambo Washington > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, 16 Oct 2020 at 08:19, Aki Tuomi < > aki.tu...@open-xchange.com> wrote: > > > > > > > On 15/10/2020 18:14 Odhiambo Washington > wrote: > > > > > > > > > > > > > > > > > > > > > Here is what I see on the error.log: > > > > > > > > > > > > > > Oct 15 17:37:58 > > > > imap(techni...@mydomain.name)<62260><9ucgmLax7s3F6FH2>: > Error: Mailbox INBOX: Cache /var/spool/virtual/ > mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache > ( > http://mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache) > ( > http://mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache) > ( > http://mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache): > Deleting corrupted cache record uid=798: > > > > > > > > > > > > > > Best regards, > > > > > > > Odhiambo WASHINGTON, > > > > > > > Nairobi,KE > > > > > > > +254 7 3200 0004/+254 7 2274 3223 > > > > > > > "Oh, the cruft.",grep ^[^#] :-) > > > > > > > > > > > > There is a bug in compression in 2.3.11.3, see > https://dovecot.org/pipermail/dovecot/2020-September/119907.html > > > > > > > > > > > > Aki > > > > > > > > > > I don't use any compression mechanisms in my setup. > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > Best regards, > > > > > Odhiambo WASHINGTON, > > > > > Nairobi,KE > > > > > +254 7 3200 0004/+254 7 2274 3223 > > > > > "Oh, the cruft.",grep ^[^#] :-) > > > > > > > > Try rm /var/spool/virtual/ > mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache > ( > http://mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache) > > > > > > > > > Aki > > > > > > I have done that. Sent a test mail. Outlook (using IMAP) does not sync > the mailbox. It does not even receive the test mail. > > > root@gw:/ # telnet 0 110 > > > Trying 0.0.0.0... > > > Connected to 0. > > > Escape character is '^]'. > > > +OK Dovecot ready. > > > user techni...@mydomain.name > > > +OK > > > pass XXX > > > +OK Logged in. > > > stat > > > +OK 330 23948401 > > > > > > > > > > > > -- > > > > > > Best regards, > > > Odhiambo WASHINGTON, > > > Nairobi,KE > > Hi! > > Are you sure the mail is delivered to right place? Can you see this mail > using `doveadm fetch -u odhiambo text mailbox INBOX "*"`? > > Aki > Yes. I use SOGo as the IMAP client (webmail) and see all the emails - all folders. However, Outlook doesn't. mail_location = mdbox:~/mdbox That doveadm command is able to fetch an e-mail, but just one mail. My error log is filled with lines like this: Oct 17 11:08:22 imap(sal...@mydomain.name)<34837>: Error: Mailbox Trash: Cache /var/spool/virtual/ mydomain.name/sales1/mdbox/mailboxes/Trash/dbox-Mails/dovecot.index.cache: Deleting corrupted cache record uid=8: UID 8:Broken virtual size in mailbox Trash: read(/var/spool/virtual/mydomain.name/sales1/mdbox/storage/m.657): FETCH BODY[] got too little data: 107289 vs 1338249 Oct 17 11:38:40 imap(sal...@mydomain.name)<63260>: Error: Mailbox INBOX: Cache /var/spool/virtual/ mydomain.name/sales1/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: Deleting corrupted cache record uid=956: UID 956: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.name/sales1/mdbox/storage/m.602): FETCH BODY[] got too little data: 203354 vs 774706 Oct 17 11:38:40 imap(sa...@mydomain.name)<62764>: Error: Mailbox Trash: Cache /var/spool/virtual/ mydomain.name/sales/mdbox/mailboxes/Trash/dbox-Ma
Re: Unable to access mail via Outlook
Bump! On Fri, 16 Oct 2020 at 13:26, Odhiambo Washington wrote: > > > On Fri, 16 Oct 2020 at 13:15, Aki Tuomi > wrote: > >> >> > On 16/10/2020 13:11 Odhiambo Washington wrote: >> > >> > >> > >> > >> > >> > On Fri, 16 Oct 2020 at 08:19, Aki Tuomi >> wrote: >> > > > On 15/10/2020 18:14 Odhiambo Washington wrote: >> > > > >> > > > >> > > > Here is what I see on the error.log: >> > > > >> > > > Oct 15 17:37:58 >> > > imap(techni...@mydomain.name)<62260><9ucgmLax7s3F6FH2>: >> Error: Mailbox INBOX: Cache /var/spool/virtual/ >> mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache >> ( >> http://mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache) >> ( >> http://mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache): >> Deleting corrupted cache record uid=798: >> > > > >> > > > Best regards, >> > > > Odhiambo WASHINGTON, >> > > > Nairobi,KE >> > > > +254 7 3200 0004/+254 7 2274 3223 >> > > > "Oh, the cruft.",grep ^[^#] :-) >> > > >> > > There is a bug in compression in 2.3.11.3, see >> https://dovecot.org/pipermail/dovecot/2020-September/119907.html >> > > >> > > Aki >> > >> > I don't use any compression mechanisms in my setup. >> > >> > >> > >> > -- >> > >> > Best regards, >> > Odhiambo WASHINGTON, >> > Nairobi,KE >> > +254 7 3200 0004/+254 7 2274 3223 >> > "Oh, the cruft.",grep ^[^#] :-) >> >> Try rm /var/spool/virtual/ >> mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache >> >> Aki >> > > I have done that. Sent a test mail. Outlook (using IMAP) does not sync the > mailbox. It does not even receive the test mail. > root@gw:/ # telnet 0 110 > Trying 0.0.0.0... > Connected to 0. > Escape character is '^]'. > +OK Dovecot ready. > user techni...@mydomain.name > +OK > pass XXX > +OK Logged in. > stat > +OK 330 23948401 > > > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", grep ^[^#] :-) > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: Unable to access mail via Outlook
On Fri, 16 Oct 2020 at 13:15, Aki Tuomi wrote: > > > On 16/10/2020 13:11 Odhiambo Washington wrote: > > > > > > > > > > > > On Fri, 16 Oct 2020 at 08:19, Aki Tuomi > wrote: > > > > On 15/10/2020 18:14 Odhiambo Washington wrote: > > > > > > > > > > > > Here is what I see on the error.log: > > > > > > > > Oct 15 17:37:58 imap(techni...@mydomain.name)<62260><9ucgmLax7s3F6FH2>: > Error: Mailbox INBOX: Cache /var/spool/virtual/ > mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache > ( > http://mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache) > ( > http://mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache): > Deleting corrupted cache record uid=798: > > > > > > > > Best regards, > > > > Odhiambo WASHINGTON, > > > > Nairobi,KE > > > > +254 7 3200 0004/+254 7 2274 3223 > > > > "Oh, the cruft.",grep ^[^#] :-) > > > > > > There is a bug in compression in 2.3.11.3, see > https://dovecot.org/pipermail/dovecot/2020-September/119907.html > > > > > > Aki > > > > I don't use any compression mechanisms in my setup. > > > > > > > > -- > > > > Best regards, > > Odhiambo WASHINGTON, > > Nairobi,KE > > +254 7 3200 0004/+254 7 2274 3223 > > "Oh, the cruft.",grep ^[^#] :-) > > Try rm /var/spool/virtual/ > mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache > > Aki > I have done that. Sent a test mail. Outlook (using IMAP) does not sync the mailbox. It does not even receive the test mail. root@gw:/ # telnet 0 110 Trying 0.0.0.0... Connected to 0. Escape character is '^]'. +OK Dovecot ready. user techni...@mydomain.name +OK pass XXX +OK Logged in. stat +OK 330 23948401 -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: Unable to access mail via Outlook
On Fri, 16 Oct 2020 at 08:19, Aki Tuomi wrote: > > On 15/10/2020 18:14 Odhiambo Washington wrote: > > > > > > Here is what I see on the error.log: > > > > Oct 15 17:37:58 imap(techni...@mydomain.name)<62260><9ucgmLax7s3F6FH2>: > Error: Mailbox INBOX: Cache /var/spool/virtual/ > mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache > ( > http://mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache): > Deleting corrupted cache record uid=798: > > > > Best regards, > > Odhiambo WASHINGTON, > > Nairobi,KE > > +254 7 3200 0004/+254 7 2274 3223 > > "Oh, the cruft.",grep ^[^#] :-) > > There is a bug in compression in 2.3.11.3, see > https://dovecot.org/pipermail/dovecot/2020-September/119907.html > > Aki > I don't use any compression mechanisms in my setup. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: Unable to access mail via Outlook
Here is what I see on the error.log: Oct 15 17:37:58 imap(techni...@mydomain.name)<62260><9ucgmLax7s3F6FH2>: Error: Mailbox INBOX: Cache /var/spool/virtual/ mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: Deleting corrupted cache record uid=798: UID 798: Broken physical size in mailbox INBOX: read(/var/spool/virtual/ mydomain.name/technical/mdbox/storage/m.3) failed: Cached message size larger than expected (174159 > 42234, box=INBOX, UID=798) Oct 15 17:37:58 imap(techni...@mydomain.name)<62260><9ucgmLax7s3F6FH2>: Error: Mailbox INBOX: UID=798: read(/var/spool/virtual/ mydomain.name/technical/mdbox/storage/m.3) failed: Cached message size larger than expected (174159 > 42234, b ox=INBOX, UID=798) (FETCH BODY[]) Oct 15 17:38:08 imap(techni...@mydomain.name)<80433>: Error: Mailbox INBOX: Cache /var/spool/virtual/ mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: Deleting corrupted cache record uid=798: UID 798: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.name/technical/mdbox/storage/m.3): FETCH BODY[] got too little data: 42930 vs 176568 Oct 15 17:38:15 imap(techni...@mydomain.name)<80488>: Error: Mailbox INBOX: Cache /var/spool/virtual/ mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: Deleting corrupted cache record uid=798: UID 798: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.name/technical/mdbox/storage/m.3): FETCH BODY[] got too little data: 42930 vs 176568 Oct 15 17:38:36 imap(techni...@mydomain.name)<81313>: Error: Mailbox INBOX: Cache /var/spool/virtual/ mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: Deleting corrupted cache record uid=798: UID 798: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.name/technical/mdbox/storage/m.3): FETCH BODY[] got too little data: 42930 vs 176568 Oct 15 17:39:00 imap(techni...@mydomain.name)<82161>: Error: Mailbox INBOX: Cache /var/spool/virtual/ mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: Deleting corrupted cache record uid=798: UID 798: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.name/technical/mdbox/storage/m.3): FETCH BODY[] got too little data: 42930 vs 176568 Outlook shows no error at all. Just doesn't display mails. I am not using SSL. On Thu, 15 Oct 2020 at 18:09, Goetz Schultz wrote: > Hi, > > can you see the server-side logs if there is any error? > What error does Outlook give you? Is the connection via SSL or plain? > > Thanks and regards > >Goetz R. Schultz > > On 15/10/2020 15:40, Odhiambo Washington wrote: > > On Tue, 13 Oct 2020 at 14:00, Jerry wrote: > > > >> On Tue, 13 Oct 2020 09:48:16 +0300, Odhiambo Washington stated: > >>> Hola, > >>> > >>> Dovecot- 2.3.11.3 with mdbox. > >>> > >>> I have a situation where I can access (view) the e-mails when I use a > >>> web-based IMAP client, but NOT M$ Outlook (configured for IMAP). > >>> Is there an easy way to solve this? > >>> When I send an e-mail to the mailbox address, I can see it on the > >>> webmail, but not on Outlook. > >> > >> What version of MS Outlook are you using? > >> > >> -- > >> Jerry > >> > > > > > > Hi Jerry, > > > > I am using Outlook from Office 2019. > > > > Thanks > > > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: Unable to access mail via Outlook
On Tue, 13 Oct 2020 at 14:00, Jerry wrote: > On Tue, 13 Oct 2020 09:48:16 +0300, Odhiambo Washington stated: > >Hola, > > > >Dovecot- 2.3.11.3 with mdbox. > > > >I have a situation where I can access (view) the e-mails when I use a > >web-based IMAP client, but NOT M$ Outlook (configured for IMAP). > >Is there an easy way to solve this? > >When I send an e-mail to the mailbox address, I can see it on the > >webmail, but not on Outlook. > > What version of MS Outlook are you using? > > -- > Jerry > Hi Jerry, I am using Outlook from Office 2019. Thanks -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Unable to access mail via Outlook
Hola, Dovecot- 2.3.11.3 with mdbox. I have a situation where I can access (view) the e-mails when I use a web-based IMAP client, but NOT M$ Outlook (configured for IMAP). Is there an easy way to solve this? When I send an e-mail to the mailbox address, I can see it on the webmail, but not on Outlook. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: Importing Mail
Hi Rudolf, Thank you for the quick response. Let me try that. On Thu, 24 Sep 2020 at 17:00, wrote: > Hey, > > for an import between two servers i would use imapsync. With doveadm flag ( > https://wiki.dovecot.org/Tools/Doveadm/Flags) you can mark the mails as > unseen but be careful here, you can simple overwrite all other flags here > too, maybe an other way is better here. > > > > With doveadm backup / doveadm sync you can convert the mails between the > formats like this way: > > > > dsync backup -u "" maildir:~/maildir-NEW > > > > after converting the mails you can rename the mdbox folder to mdbox-OLD or > something (backup) and rename the maildir-NEW folder to maildir > > > > Yours sincerely > > Pascal Rudolf > > > > > > > > > > *Von:* dovecot *Im Auftrag von *Odhiambo > Washington > *Gesendet:* Donnerstag, 24. September 2020 15:25 > *An:* Dovecot Mailing List > *Betreff:* Importing Mail > > > > Hi good people, > > > > I have an old server that holds old mail (mdbox) and a new server that > also uses mdbox. > > I'd like to import the old mail from the old server into the live/new > server. The imported mail should not be treated as new mail for the > existing mail accounts. > > > > What is the best way to achieve this? > > > > Lastly, is there a way to convert mdbox to Maildir? > > > > > -- > > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", grep ^[^#] :-) > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Importing Mail
Hi good people, I have an old server that holds old mail (mdbox) and a new server that also uses mdbox. I'd like to import the old mail from the old server into the live/new server. The imported mail should not be treated as new mail for the existing mail accounts. What is the best way to achieve this? Lastly, is there a way to convert mdbox to Maildir? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: Moving Spam to Junk Folder
What did the bounce contain? On Thu, 3 Sep 2020 at 21:33, bobby wrote: > I am following this tutorial: > https://www.linuxbabe.com/redhat/spamassassin-centos-rhel-block-email-spam > . > I followed the steps in "Move Spam into the Junk Folder". When I send an > email from a blacklisted e-mail address, I get a bounce e-mail from my > e-mail server. Here is what is in my spamass-milter file: > EXTRA_FLAGS="-m -r 8 -R NO_SPAM -i 127.0.0.1 -g sa-milt -- > --max-size=512" > I would prefer it to go into my Junk folder. How can I make this happen? > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Dovecot auth crashing??
Dovecot-2.3.9 I am seeing a lot of the following on my logs: Dec 13 09:16:25 auth: Warning: Timeout leak: 0x105fb00 (auth-request-handler.c:584) Dec 13 09:16:25 auth: Warning: Timeout leak: 0x105fb00 (auth-request-handler.c:584) Dec 13 09:16:25 auth: Warning: Timeout leak: 0x105fb00 (auth-request-handler.c:584) Dec 13 09:16:25 auth: Warning: Event 0x827d6e20 leaked (parent=0x827d4220): auth-request.c:878 Dec 13 09:16:25 auth: Warning: Event 0x827d6420 leaked (parent=0x827d4820): auth-request.c:878 Dec 13 09:16:25 auth: Warning: Event 0x82780c20 leaked (parent=0x827d6220): auth-request.c:878 Dec 13 09:16:25 auth: Warning: Event 0x827d6c20 leaked (parent=0x827d4220): auth-request.c:115 Dec 13 09:16:25 auth: Warning: Event 0x827d4220 leaked (parent=0x827d6a20): auth-request.c:114 Dec 13 09:16:25 auth: Warning: Event 0x827d6a20 leaked (parent=0x0): auth-client-connection.c:338 Dec 13 09:16:25 auth: Warning: Event 0x827d4c20 leaked (parent=0x827d4820): auth-request.c:115 Dec 13 09:16:25 auth: Warning: Event 0x827d4820 leaked (parent=0x827fe620): auth-request.c:114 Dec 13 09:16:25 auth: Warning: Event 0x827fe620 leaked (parent=0x0): auth-client-connection.c:338 Dec 13 09:16:25 auth: Warning: Event 0x827ff420 leaked (parent=0x827d6220): auth-request.c:115 Dec 13 09:16:25 auth: Warning: Event 0x827d6220 leaked (parent=0x82780e20): auth-request.c:114 Dec 13 09:16:25 auth: Warning: Event 0x82780e20 leaked (parent=0x0): auth-client-connection.c:338 Dec 13 11:27:29 master: Warning: Killed with signal 15 (by pid=9326 uid=0 code=kill) Dec 13 11:27:37 master: Warning: Killed with signal 15 (by pid=16518 uid=0 code=kill) Dec 13 11:27:38 auth: Error: net_connect_unix(auth-worker) failed: No such file or directory Dec 13 11:27:39 auth: Error: net_connect_unix(auth-worker) failed: No such file or directory Dec 13 11:27:59 auth: Error: net_connect_unix(/var/run/dovecot//stats-writer) failed: No such file or directory Dec 13 11:27:59 auth: Warning: Timeout leak: 0x105fb00 (auth-request-handler.c:584) Dec 13 11:27:59 auth: Warning: Timeout leak: 0x105fb00 (auth-request-handler.c:584) Dec 13 11:27:59 auth: Warning: Event 0x82781a20 leaked (parent=0x827d4620): auth-request.c:878 Dec 13 11:27:59 auth: Warning: Event 0x827d4220 leaked (parent=0x827d4820): auth-request.c:878 Dec 13 11:27:59 auth: Warning: Event 0x82780e20 leaked (parent=0x827d4620): auth-request.c:115 Dec 13 11:27:59 auth: Warning: Event 0x827d4620 leaked (parent=0x827d0820): auth-request.c:114 Dec 13 11:27:59 auth: Warning: Event 0x827d0820 leaked (parent=0x0): auth-client-connection.c:338 Dec 13 11:27:59 auth: Warning: Event 0x82781220 leaked (parent=0x827d4820): auth-request.c:115 Dec 13 11:27:59 auth: Warning: Event 0x827d4820 leaked (parent=0x827d0c20): auth-request.c:114 Dec 13 11:27:59 auth: Warning: Event 0x827d0c20 leaked (parent=0x0): auth-client-connection.c:338 Dec 13 11:28:07 auth: Warning: Timeout leak: 0x105fb00 (auth-request-handler.c:584) Dec 13 11:28:07 auth: Warning: Event 0x82780c20 leaked (parent=0x82781c20): auth-request.c:878 Dec 13 11:28:07 auth: Warning: Event 0x82781e20 leaked (parent=0x82781c20): auth-request.c:115 Dec 13 11:28:07 auth: Warning: Event 0x82781c20 leaked (parent=0x82781a20): auth-request.c:114 Dec 13 11:28:07 auth: Warning: Event 0x82781a20 leaked (parent=0x0): auth-client-connection.c:338 -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Problem syncing mail with IMAP
spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:31:36 imap(techni...@mydomain.co.ke)<61899>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 29: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.1): FETCH BODY[] got too little data: 131524 vs 772408 Jun 18 11:31:37 imap(sa...@mydomain.co.ke)<61897>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:31:37 imap(techni...@mydomain.co.ke)<61916>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/Deleted Items/dbox-Mails/dovecot.index.cache: UID 2: Broken virtual size in mailbox Deleted Items: read(/var/spool/virtual/mydomain.co.ke/technical/mdbox/storage/m.460): FETCH BODY[] got too little data: 10123 vs 197577 Jun 18 11:31:37 imap(techni...@mydomain.co.ke)<61919>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/Sent Items/dbox-Mails/dovecot.index.cache: UID 2: Broken virtual size in mailbox Sent Items: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.2): FETCH BODY[] got too little data: 3620 vs 817692 Jun 18 11:31:40 imap(sa...@mydomain.co.ke)<61924>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/Sent Items/dbox-Mails/dovecot.index.cache: UID 1: Broken virtual size in mailbox Sent Items: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.24): FETCH BODY[] got too little data: 5202 vs 1196884 Jun 18 11:31:44 imap(sa...@mydomain.co.ke)<61937>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/Sent/dbox-Mails/dovecot.index.cache: UID 9: Broken virtual size in mailbox Sent: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.255): FETCH BODY[] got too little data: 46155 vs 1156185 Jun 18 11:31:46 imap(sa...@mydomain.co.ke)<61962>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/Trash/dbox-Mails/dovecot.index.cache: UID 8: Broken virtual size in mailbox Trash: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.657): FETCH BODY[] got too little data: 107289 vs 1338249 Jun 18 11:32:07 imap(sa...@mydomain.co.ke)<62063>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: mdbox to Maildir
On Tue, 18 Jun 2019 at 01:35, Ralph Seichter via dovecot < dovecot@dovecot.org> wrote: > * Odhiambo Washington via dovecot: > > > Is it possible? How do I do it for ALL mailboxes? > > This has been asked (and answered) recently; see the Dovecot Wiki. > > -Ralph > Could you kindly point me to the exact article in the wiki, please? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Problem syncing e-mails with Outlook
e: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:31:36 imap(sa...@mydomain.co.ke)<61905>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:31:36 imap(techni...@mydomain.co.ke)<61899>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 29: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.1): FETCH BODY[] got too little data: 131524 vs 772408 Jun 18 11:31:37 imap(sa...@mydomain.co.ke)<61897>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:31:37 imap(techni...@mydomain.co.ke)<61916>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/Deleted Items/dbox-Mails/dovecot.index.cache: UID 2: Broken virtual size in mailbox Deleted Items: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.460): FETCH BODY[] got too little data: 10123 vs 197577 Jun 18 11:31:37 imap(techni...@mydomain.co.ke)<61919>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/Sent Items/dbox-Mails/dovecot.index.cache: UID 2: Broken virtual size in mailbox Sent Items: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.2): FETCH BODY[] got too little data: 3620 vs 817692 Jun 18 11:31:40 imap(sa...@mydomain.co.ke)<61924>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/Sent Items/dbox-Mails/dovecot.index.cache: UID 1: Broken virtual size in mailbox Sent Items: read(/var/spool/virtual/mydomain.co.ke/sales/mdbox/storage/m.24): FETCH BODY[] got too little data: 5202 vs 1196884 Jun 18 11:31:44 imap(sa...@mydomain.co.ke)<61937>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/Sent/dbox-Mails/dovecot.index.cache: UID 9: Broken virtual size in mailbox Sent: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.255): FETCH BODY[] got too little data: 46155 vs 1156185 Jun 18 11:31:46 imap(sa...@mydomain.co.ke)<61962>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/Trash/dbox-Mails/dovecot.index.cache: UID 8: Broken virtual size in mailbox Trash: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.657): FETCH BODY[] got too little data: 107289 vs 1338249 Jun 18 11:32:07 imap(sa...@mydomain.co.ke)<62063>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
mdbox to Maildir
I'd like a way to convert all my mailboxes from mdbox to Maildir. Is it possible? How do I do it for ALL mailboxes? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: Deleted dovecot.index.*
On Mon, 17 Jun 2019 at 21:03, Aki Tuomi wrote: > > > On 17 June 2019 20:55 Odhiambo Washington wrote: > > > > > > > > > > > > On Mon, 17 Jun 2019 at 20:45, Aki Tuomi via dovecot > wrote: > > > > > > > On 17 June 2019 18:59 Odhiambo Washington via dovecot < > dovecot@dovecot.org> wrote: > > > > > > > > > > > > I'm using mdbox. > > > > > > > > What's the consequence of deleting dovecot.index.* from all folders? > > > > > > > > All mail gets lost or I can rebuild the indexes and get the mails? > > > > > > > > > > > > > > You will lose flags, such as \Seen. But mails should come out intact. > > > > > > Aki > > > > > > > Thank you for this fast (and comforting) response. > > > > All the previous mails disappeared after I deleted the files. What do I > need to do to get them back?? > > > > > > > > -- > > > > Best regards, > > Odhiambo WASHINGTON, > > Nairobi,KE > > +254 7 3200 0004/+254 7 2274 3223 > > "Oh, the cruft.",grep ^[^#] :-) > > doveadm force-resync -u victim "*" > Is there a way to mark all mails older that today as "Read" in all folders? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: Deleted dovecot.index.*
On Mon, 17 Jun 2019 at 21:03, Aki Tuomi wrote: > > > On 17 June 2019 20:55 Odhiambo Washington wrote: > > > > > > > > > > > > On Mon, 17 Jun 2019 at 20:45, Aki Tuomi via dovecot > wrote: > > > > > > > On 17 June 2019 18:59 Odhiambo Washington via dovecot < > dovecot@dovecot.org> wrote: > > > > > > > > > > > > I'm using mdbox. > > > > > > > > What's the consequence of deleting dovecot.index.* from all folders? > > > > > > > > All mail gets lost or I can rebuild the indexes and get the mails? > > > > > > > > > > > > > > You will lose flags, such as \Seen. But mails should come out intact. > > > > > > Aki > > > > > > > Thank you for this fast (and comforting) response. > > > > All the previous mails disappeared after I deleted the files. What do I > need to do to get them back?? > > > > > > > > -- > > > > Best regards, > > Odhiambo WASHINGTON, > > Nairobi,KE > > +254 7 3200 0004/+254 7 2274 3223 > > "Oh, the cruft.",grep ^[^#] :-) > > doveadm force-resync -u victim "*" > > Aki > Thank you very very much. Now off to read again about dbox storage. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: Deleted dovecot.index.*
On Mon, 17 Jun 2019 at 20:45, Aki Tuomi via dovecot wrote: > > > On 17 June 2019 18:59 Odhiambo Washington via dovecot < > dovecot@dovecot.org> wrote: > > > > > > I'm using mdbox. > > > > What's the consequence of deleting dovecot.index.* from all folders? > > > > All mail gets lost or I can rebuild the indexes and get the mails? > > > > > > You will lose flags, such as \Seen. But mails should come out intact. > > Aki > Thank you for this fast (and comforting) response. All the previous mails disappeared after I deleted the files. What do I need to do to get them back?? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Deleted dovecot.index.*
I'm using mdbox. What's the consequence of deleting dovecot.index.* from all folders? All mail gets lost or I can rebuild the indexes and get the mails?
Re: Dovecot 2.3 error, FreeBSD 12 in a jail
On Sat, 15 Jun 2019 at 07:12, David Mehler via dovecot wrote: > Hello, > > I'm trying to get Dovecot going on my system. It's a FreeBSD > 12.0-RELEASE system and it's running dovecot 2.3 via ports in a jail. > I'm getting the same error message(s) as in this bug report, which has > been marked as closed: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225078 > > Dovecot is not starting at all in this jail when starting with service > dovecot start. A service dovecot status also reveals the error message > about /var/run/dovecot/dovecot.conf file, but a doveconf -n does not > reveal any configuration file issues. I did put a symlink in > /var/run/dovecot to /usr/local/etc/dovecot/dovecot.conf, this did not > correct the issue. > > Any suggestions welcome. > Thanks. > Dave. > Hi David, Your problem must be something to do with your jails on FreeBSD, IMHO. The FreeBSD port maintainer (Larry Rosenman) is here. Perhaps he'll be willing to help troubleshoot the jail issue. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: Mail account brute force / harassment
All your approaches are not well thought out. The best solutions are always the simplest ones. KISS principle dictates so. On Thu, 11 Apr 2019 at 15:01, Marc Roos wrote: > > How long have we been using the current strategy? Do we have less or > more abuse clouds operating? > > "Let the others bother with their own problems." is a bit narrow minded > view. If every one on this mailing list would have this attitude, there > would be no single answer to your question. > > > -----Original Message- > From: Odhiambo Washington [mailto:odhia...@gmail.com] > Sent: donderdag 11 april 2019 12:54 > To: Marc Roos > Cc: dovecot > Subject: Re: Mail account brute force / harassment > > Marc, > > There is a strategy loosely referred to as "choose your battles well" > :-) > If you can, hack the server and dump the 500GB - you'll be using > resources transferring the 500GB as the other server receives it. Two > servers wasting resources because you think you are punishing an > offender! > > > On Thu, 11 Apr 2019 at 13:43, wrote: > > > Please do not assume anything other than what is written, it is a > hypothetical situation > > > A. With the fail2ban solution >- you 'solve' that the current ip is not able to access you >- it will continue bothering other servers and admins >- you get the next abuse host to give a try. > > B. With 500GB dump > - the owner of the attacking server (probably hacked) will notice > it > will be forced to take action. > > > If abuse clouds are smart (most are) they would notice that > attacking my > servers, will result in the loss of abuse nodes, hence they will > not > bother me anymore. > > If every one would apply strategy B, the abuse problem would get > less. > Don't you agree?? > > > > > > > -Original Message- > From: Odhiambo Washington > Sent: donderdag 11 april 2019 12:28 > To: Marc Roos > Cc: dovecot > Subject: Re: Mail account brute force / harassment > > > > On Thu, 11 Apr 2019 at 13:24, Marc Roos via dovecot > 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 > infinite > amount of messages > (maybe send an archive of virusses?) > * transferring TB's of data to this harassing client. > > I think it would be interesting to be able to do such a > thing. > > > > > Instead of being evil, just use fail2ban to address this problem > :-) > > -- > > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", grep ^[^#] :-) > > > > > > > -- > > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", grep ^[^#] :-) > > > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: Mail account brute force / harassment
Marc, There is a strategy loosely referred to as "choose your battles well" :-) Let the others bother with their own problems. If you can, hack the server and dump the 500GB - you'll be using resources transferring the 500GB as the other server receives it. Two servers wasting resources because you think you are punishing an offender! On Thu, 11 Apr 2019 at 13:43, Marc Roos wrote: > Please do not assume anything other than what is written, it is a > hypothetical situation > > > A. With the fail2ban solution >- you 'solve' that the current ip is not able to access you >- it will continue bothering other servers and admins >- you get the next abuse host to give a try. > > B. With 500GB dump > - the owner of the attacking server (probably hacked) will notice it > will be forced to take action. > > > If abuse clouds are smart (most are) they would notice that attacking my > servers, will result in the loss of abuse nodes, hence they will not > bother me anymore. > > If every one would apply strategy B, the abuse problem would get less. > Don't you agree?? > > > > > > > -Original Message- > From: Odhiambo Washington > Sent: donderdag 11 april 2019 12:28 > To: Marc Roos > Cc: dovecot > Subject: Re: Mail account brute force / harassment > > > > On Thu, 11 Apr 2019 at 13:24, Marc Roos via dovecot > 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 > infinite > amount of messages > (maybe send an archive of virusses?) > * transferring TB's of data to this harassing client. > > I think it would be interesting to be able to do such a thing. > > > > > Instead of being evil, just use fail2ban to address this problem :-) > > -- > > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", grep ^[^#] :-) > > > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: Mail account brute force / harassment
On Thu, 11 Apr 2019 at 13:24, Marc Roos via dovecot 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 infinite > amount of messages > (maybe send an archive of virusses?) > * transferring TB's of data to this harassing client. > > I think it would be interesting to be able to do such a thing. > > Instead of being evil, just use fail2ban to address this problem :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: /var/run/dovecot/stats-writer) failed: Permission denied
On Wed, 10 Apr 2019 at 19:44, @lbutlr via dovecot
wrote:
> On 10 Apr 2019, at 09:06, @lbutlr via dovecot wrote:
> > Should I add
> >
> > service stats {
> > unix_listener stats-writer {
> > user = dovecot
> > }
> > unix_listener stats-reader {
> > user = dovecot
> > }
> > }
> >
> > to my dovecot.conf file?
>
> I did this and it appears to have fixed the issue.
>
> Also, the failed message strongly implies that the email was not
> delivered, since it happens on the delivery log line and there is not
> indication in the log that delivery succeeded. However, the message is
> delivered. It might be worth changing the message or still logging the
> actual message delivery?
>
>
I use dovecot-lda for deliveries and would see entries in both Exim (MTA)
and Dovecot log files.
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", grep ^[^#] :-)
Re: /var/run/dovecot/stats-writer) failed: Permission denied
On Wed, 10 Apr 2019 at 18:06, @lbutlr via dovecot
wrote:
>
>
> > On 10 Apr 2019, at 08:57, Odhiambo Washington via dovecot <
> dovecot@dovecot.org> wrote:
> >
> >
> >
> > On Wed, 10 Apr 2019 at 17:50, @lbutlr via dovecot
> wrote:
> > On 10 Apr 2019, at 08:36, @lbutlr via dovecot
> wrote:
> > > net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission
> den))
> >
> > One other detail:
> >
> > /var/run/dovecot/stats-writer:
> > 0 srw-rw 1 root dovecot 0 Apr 10 08:47 stats-writer
> >
> >
> > Edit your 10-master.conf and make sure that the user specified in the
> details below matches the dovecot user:
> >
> >
> > service stats {
> > unix_listener stats-writer {
> > user = mailnull
> > }
> > unix_listener stats-reader {
> > user = mailnull
> > }
>
> Sorry, i am confused. There is no similar clock in 10-master.conf
>
> In fact,. the string "stats" does not appear in that file at all. The
> commented line
>
> #default_internal_user = dovecot
>
> is in that file, and that is the dovecot user (as seen in the permissions
> above).
>
> Should I add
>
> service stats {
> unix_listener stats-writer {
> user = dovecot
> }
> unix_listener stats-reader {
> user = dovecot
> }
> }
>
> to my dovecot.conf file?
>
>
Add the two blocks to 10-master.conf, before the last "}"
My dovecot runs as user mailnull. YMMV.
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", grep ^[^#] :-)
Re: /var/run/dovecot/stats-writer) failed: Permission denied
On Wed, 10 Apr 2019 at 17:50, @lbutlr via dovecot
wrote:
> On 10 Apr 2019, at 08:36, @lbutlr via dovecot wrote:
> > net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission den))
>
> One other detail:
>
> /var/run/dovecot/stats-writer:
> 0 srw-rw 1 root dovecot 0 Apr 10 08:47 stats-writer
>
>
Edit your 10-master.conf and make sure that the user specified in the
details below matches the dovecot user:
service stats {
unix_listener stats-writer {
user = mailnull
}
unix_listener stats-reader {
user = mailnull
}
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", grep ^[^#] :-)
Re: where shall I enforce sieve and quota plugins
MDA== LDA On Wed, 3 Apr 2019 at 06:20, luckydog xf via dovecot wrote: > Hello, guys, > >I'm going to using sieve and quota plugins, but I'm not sure where > shall I enforce against properly? > >I see somebody uses them against 20-imap.conf, 15-lda.conf, or > 20-lmtp.conf > >I use LMTP as MDA, so where is the correct location to call these > plugins and why? > > Thanks, > > > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
IMAP coredumps for one user
tmp1 = "body"
tmp2 = "maureen.x...@.co.ke"
t2 =
s2 = 0x817892e0 "maureen.x...@.co.ke"
i =
#10 0x81ec24fb in XQuerySet::add (this=0x7fffe3e0,
type=, s=) at
./fts-backend-xapian-functions.cpp:182
sp = { = {}, ptr_ = 0x81eb8591
"body", length_ = 4, static npos = 2147483647}
t = { = { = { = {}, _vptr$UObject = 0x822c3bc0 }, }, fUnion = {fStackFields =
{fLengthAndFlags = 130,
fBuffer = u}, fFields =
{fLengthAndFlags = 130, fLength = 6553711, fCapacity = 121, fArray =
0x7fffe270 u}}}
s2 =
sp2 =
#11 0x81ec0667 in fts_backend_xapian_lookup (_backend=, box=, args=0x81e35110, flags=,
result=0x7fffe550) at fts-backend-xapian.cpp:470
a =
backend =
tp = {tv_sec = 1553584401, tv_usec = 717885}
is_and =
hdr =
i =
r =
n =
uid =
dt =
qs =
#12 0x81ea5bf4 in fts_backend_lookup () from
/usr/local/lib/dovecot/lib20_fts_plugin.so
No symbol table info available.
#13 0x81eaa782 in ?? () from
/usr/local/lib/dovecot/lib20_fts_plugin.so
No symbol table info available.
#14 0x81eaa5d0 in fts_search_lookup () from
/usr/local/lib/dovecot/lib20_fts_plugin.so
No symbol table info available.
#15 0x81eace94 in ?? () from
/usr/local/lib/dovecot/lib20_fts_plugin.so
No symbol table info available.
#16 0x0104fa47 in imap_search_start ()
No symbol table info available.
#17 0x01040441 in cmd_search ()
No symbol table info available.
#18 0x010486bd in command_exec ()
No symbol table info available.
#19 0x0104730a in ?? ()
No symbol table info available.
#20 0x01045ed7 in client_handle_input ()
No symbol table info available.
#21 0x010446c8 in client_input ()
No symbol table info available.
#22 0x8133ebbf in io_loop_call_io () from
/usr/local/lib/dovecot/libdovecot.so.0
No symbol table info available.
#23 0x813411ed in io_loop_handler_run_internal () from
/usr/local/lib/dovecot/libdovecot.so.0
No symbol table info available.
#24 0x8133f22e in io_loop_handler_run () from
/usr/local/lib/dovecot/libdovecot.so.0
No symbol table info available.
--Type for more, q to quit, c to continue without paging--
#25 0x8133ef98 in io_loop_run () from
/usr/local/lib/dovecot/libdovecot.so.0
No symbol table info available.
#26 0x812b2e08 in master_service_run () from
/usr/local/lib/dovecot/libdovecot.so.0
No symbol table info available.
#27 0x010558a7 in main ()
No symbol table info available.
(gdb)
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", grep ^[^#] :-)
Panic
Dovecot-2.3.5, FreeBSD-12 (amd64),
I will wait to see coredumps after setting up things to allow it.
Mar 24 20:56:08 imap(john@crownkenya.com)<82746>:
Panic: file mempool-system.c: line 137 (pool_system_realloc): assertion
failed: (old_size == (size_t)-1 || mem == NULL || old_size <=
malloc_usable_size(mem))
Mar 24 20:56:08 imap(john@crownkenya.com)<82746>:
Fatal: master: service(imap): child 82746 killed with signal 6 (core not
dumped - https://dovecot.org/bugreport.html#coredumps - set service imap {
drop_priv_before_
exec=yes })
Mar 24 20:56:08 imap(john@crownkenya.com)<81688>:
Panic: file mempool-system.c: line 137 (pool_system_realloc): assertion
failed: (old_size == (size_t)-1 || mem == NULL || old_size <=
malloc_usable_size(mem))
Mar 24 20:56:08 imap(john@crownkenya.com)<81688>:
Fatal: master: service(imap): child 81688 killed with signal 6 (core not
dumped - https://dovecot.org/bugreport.html#coredumps - set service imap {
drop_priv_before_
exec=yes })
Mar 24 20:56:08 imap(john@crownkenya.com)<82020>:
Panic: file mempool-system.c: line 137 (pool_system_realloc): assertion
failed: (old_size == (size_t)-1 || mem == NULL || old_size <=
malloc_usable_size(mem))
Mar 24 20:56:08 imap(john@crownkenya.com)<82020>:
Fatal: master: service(imap): child 82020 killed with signal 6 (core not
dumped - https://dovecot.org/bugreport.html#coredumps - set service imap {
drop_priv_before_
exec=yes })
Mar 24 20:56:08 imap(john@crownkenya.com)<83452>:
Panic: file mempool-system.c: line 137 (pool_system_realloc): assertion
failed: (old_size == (size_t)-1 || mem == NULL || old_size <=
malloc_usable_size(mem))
Mar 24 20:56:08 imap(john@crownkenya.com)<83452>:
Fatal: master: service(imap): child 83452 killed with signal 6 (core not
dumped - https://dovecot.org/bugreport.html#coredumps - set service imap {
drop_priv_before_
exec=yes })
Mar 24 20:56:08 imap(john@crownkenya.com)<84305><9vV0zdqEzueaTXHr>:
Panic: file mempool-system.c: line 137 (pool_system_realloc): assertion
failed: (old_size == (size_t)-1 || mem == NULL || old_size <=
malloc_usable_size(mem))
Mar 24 20:56:08 imap(john@crownkenya.com)<84305><9vV0zdqEzueaTXHr>:
Fatal: master: service(imap): child 84305 killed with signal 6 (core not
dumped - https://dovecot.org/bugreport.html#coredumps - set service imap {
drop_priv_before_
exec=yes })
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", grep ^[^#] :-)
Re: sieve vacation to an alias group
On Wed, 13 Mar 2019 at 11:16, Monis Monther via dovecot wrote: > Hi, > > Is there a solution for this? Not necessarily with vacation , even with > another tool. It feels like this should be a normal use case, but no one > has a solution to it. Any help would be appreciated. > > Thanks > Monis > Look for the solution within your MTA. Really, what you are looking for has nothing to do with vacation. It's just an autoresponder which you would do natively within you MTA or use procmail. The perfect tool though is Request Tracker, which I suggested a few days ago. Well, I suggested RT just because I am kinda familiar with it. There are others. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: sieve vacation to an alias group
I think you should run a true ticketing system like RT (
https://bestpractical.com/request-tracker)
On Sun, Mar 10, 2019, 13:40 Monis Monther via dovecot
wrote:
> Hi Yassine,
>
> Thanks for the effort, unfortunately, we cannot turn it into an actual
> mailbox, this is a long story that I don't want to include here. but it
> would not be a valid option in our environment. Any other ideas
>
> Is it possible to do it with vacation? Is there another auto responder or
> plugin that can achieve this? How do ticketing systems handle this?
>
> Thanks
> Monis
>
> On Sun, Mar 10, 2019 at 11:13 AM Yassine Chaouche via dovecot <
> dovecot@dovecot.org> wrote:
>
>>
>> On 3/10/19 9:07 AM, Yassine Chaouche via dovecot wrote:
>>
>> On 3/9/19 12:41 PM, Monis Monther via dovecot wrote:
>>
>> Hi,
>>
>> We have an alias group named x...@example.com, this alias group has 3
>> actual users a...@example.com, b...@example.com and c...@example.com
>>
>> We set vacation rule on the generic sieve rule, the problem is that 3
>> responses are sent to the original sender. (obviously because the rule is
>> being executed with each user in the alias group)
>>
>> Is it possible to set auto response only once, we tried the ( :days 1)
>> option but still all 3 respond back.
>>
>> How can such a setup be achieved. (Single auto response to an alias group)
>>
>> CentOS 7.5
>> dovecot-pigeonhole-2.3.4.1-1.x86_64
>> dovecot-2.3.4.1-1.x86_64
>> postfix 2.10-1
>>
>>
>> --
>> Best Regards
>> Monis
>>
>> Hello Monis,
>>
>> As a workaround, you can turn x...@example.com into an actual mailbox and
>> give a...@example.com, b...@example.com and c...@example.com read-only shared
>> folder access.
>>
>> Yassine.
>>
>>
>> As a request for comments and improvements, here's a my script to share
>> folders via acl files and symlinks (dovecot must be configured accordingly)
>> :
>>
>> root@messagerie[10.10.10.19] /usr/local/scripts/mail # cat
>> sharemailbox.single
>> #!/bin/bash
>>
>> function create_link {
>> l_src=$1
>> l_dst=$2
>> l_maildir=$3
>> t_maildir=$(echo "$3" | tr . ․)
>> t_dst="$l_dst"/.shared."$t_maildir"
>> echo pointing "$t_dst" to "$l_src"
>> echo ln -s "$l_src/" "$t_dst"
>> ln -s "$l_src/" "$t_dst"
>>
>> }
>>
>>
>> function verifier_email {
>> l_email=$1
>> if ! searchmailbox.strict.sql $l_email > /dev/null
>> then
>> echo "l'utilisateur $l_email n'a pas pu être trouvé dans la base
>> de données." >&2
>> return 1
>> fi
>> return 0
>> }
>>
>> function set_acl {
>> l_maildir=$1
>> l_email=$2
>> echo "giving $l_email access to $l_maildir"
>> if [ ! -d $l_maildir ]
>> then
>> #.Sent isn't there yet.
>> return
>> fi
>> acl_file="$l_maildir/dovecot-acl"
>> echo "echo user=$l_email lr >> $acl_file"
>> echo user="$l_email" lr >> "$acl_file"
>> chown vmail:vmail "$acl_file"
>> }
>>
>>
>> if [ "$#" -lt 2 ]
>> then
>> echo "usage : $0 part...@domain.com us...@domain.com us...@domain.com
>> ... "
>> exit 1
>> fi
>>
>> email="$1"
>> inbox="${email%@*}"
>> domain="${email#*@}"
>> src="/var/vmail/$domain/$inbox"
>> if ! verifier_email "$email"
>> then
>> echo "exit at 1"
>> exit 1
>> fi
>>
>>
>> shift
>> for share_email in $@
>> do
>> if ! verifier_email $share_email
>> then
>> continue
>> fi
>> share_inbox="${share_email%@*}"
>> share_domain="${share_email#*@}"
>> share_maildir=/var/vmail/"$share_domain"/"$share_inbox"
>> #echo grep "$share_email" "$src"/dovecot-acl
>> if grep "$share_email" "$src"/dovecot-acl > /dev/null 2>&1
>> then
>> # then is executed when exit status is 0
>> # exist status is 0 when there is a match
>> echo "$share_email" has already access to "$email"
>> else
>> set_acl $src $share_email
>> create_link $src $share_maildir $inbox
>> fi
>> done
>> root@messagerie[10.10.10.19] /usr/local/scripts/mail #
>>
>>
>
> --
> Best Regards
> Monis
>
Re: sieve vacation to an alias group
On Sat, 9 Mar 2019 at 14:41, Monis Monther via dovecot wrote: > Hi, > > We have an alias group named x...@example.com, this alias group has 3 > actual users a...@example.com, b...@example.com and c...@example.com > > We set vacation rule on the generic sieve rule, the problem is that 3 > responses are sent to the original sender. (obviously because the rule is > being executed with each user in the alias group) > > Is it possible to set auto response only once, we tried the ( :days 1) > option but still all 3 respond back. > > How can such a setup be achieved. (Single auto response to an alias group) > > CentOS 7.5 > dovecot-pigeonhole-2.3.4.1-1.x86_64 > dovecot-2.3.4.1-1.x86_64 > postfix 2.10-1 > > > -- > Best Regards > Monis > If the whole "group" (alias) isn't on vacation, then why are you doing this? Let a,b or c activate their rules individually. K.I.S.S principle. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: migrating/cloning 2.2 > 2.3?
On Sun, 3 Mar 2019 at 08:29, Voytek Eymont via dovecot wrote: > > > 11:30:12 auth-worker(32307): Warning: sqlpool(mysql): Query failed, > > retrying: Unknown column 'mailbox.enableimaptls' in 'where clause' > > Mar 03 11:30:12 auth-worker(32307): Error: > > sql(voy...@sbt.net.au,110.175.246.167,): User query > > failed: Unknown column 'mailbox.enableimaptls' in 'where clause' > > I've found a page with SQL table mods that seems to have fixed some of my > issues, after modifying SQL, I can log in > > Mar 03 16:23:34 master: Info: Dovecot v2.3.4.1 (3c0b8769e) starting up for > pop3, > imap, sieve (core dumps disabled) > Mar 03 16:23:56 config: Warning: please set ssl_dh= Mar 03 16:23:56 config: Warning: You can generate it with: dd > if=/var/lib/doveco > t/ssl-parameters.dat bs=1 skip=88 | openssl dhparam -inform der > > /etc/dovecot/d > h.pem > Mar 03 16:23:57 imap-login: Info: Login: user=, > method=PLAIN, > rip=110.175.246.167, lip=103.106.168.106, mpid=2757, TLS, > session=<283B2CmDccdu > r/an> > > I'll do the dh.pem next > > //these are SQL mods I've done > > ALTER TABLE mailbox ADD COLUMN enableimaptls TINYINT(1) NOT NULL DEFAULT 1; > ALTER TABLE mailbox ADD INDEX (enableimaptls); > ALTER TABLE mailbox ADD COLUMN enablepop3tls TINYINT(1) NOT NULL DEFAULT 1; > ALTER TABLE mailbox ADD INDEX (enablepop3tls); > ALTER TABLE mailbox ADD COLUMN enablesievetls TINYINT(1) NOT NULL DEFAULT > 1; > ALTER TABLE mailbox ADD INDEX (enablesievetls);// > > -- > Voytek > > What you did is quite practical. All you have to do is: 1. Make sure the static files named in the configs are moved to the destination server 2. All account names used in Dovecot config are adjusted or created in the destination server and the permissions/access levels are right 3. Dump mysql database and import the dump in the destination server I have done the same before, and just made sure that I went through all the files in /etc/dovecot/ with a toothcomb. I've missed one or two things depending on the level of distraction/concentration (which is normal), but it always ends up working, especially if the migration is about the same domain names. That is how it's supposed to work with virtual users I suppose. Regarding your MySQL issues, you'll notice that we all have different MySQL schemas out here, Unless the one you refer to is the standard one for CentOS, every man to their own when it comes to virtual users :) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: Assistance with doveadm backup...
On Thu, 21 Feb 2019 at 07:11, SH Development via dovecot < dovecot@dovecot.org> wrote: > I am having trouble locating examples of how to use doveadm backup. All > the examples I see are for sync. I simply want to create a backup to a > network volume of the email server's vmail folders. The goal here is to > have a reasonably current backup should the main drive on the email server > go south. > > We currently authenticate our users from a mysql database. User’s > mailboxes are stored as domainname/username/Maildir > > I assume what I will wind up on the network volume is a duplicate > directory structure as the vmail folder on the email server? > > Can someone help get me started here? > > Jeff In my previous life as a SysAdmin, I solved this kind of problem easily using the MTA. Exim is my MTA of choice and has a facility to do concurrent delivery to two storage locations using shadow_transport. I am guessing your MTA is Postfix (or maybe Sendmail). Try and see if they have such a capability or switch to Exim. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: Migrate mail data from Dovecot to Dovecot
On Tue, 19 Feb 2019 at 11:39, Aki Tuomi wrote: > > > On 19 February 2019 10:38 Odhiambo Washington via dovecot < > dovecot@dovecot.org> wrote: > > > > > > I have built a new server (FreeBSD-12) running dovecot-2.3.4. > > My old server (FreeBSD-9.3) is running dovecot-2.3.4 as well. > > The configurations are 1:1 identical. > > The are about 250 users on this server, all virtual. They are mostly > POP3 users, but they do "leave a copy of message on the server" > > for set various number of days. > > > > Now, to migrate the mail data, can I simply rsync the mail directories > between the old and the new server? Would that create a pitfall?? > > > > What is the recommended method? > > > > -- > > > > Best regards, > > Odhiambo WASHINGTON, > > Nairobi,KE > > +254 7 3200 0004/+254 7 2274 3223 > > "Oh, the cruft.",grep ^[^#] :-) > > If you are using maildir, rsync should work. > > Thank you. rsync it is. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Migrate mail data from Dovecot to Dovecot
I have built a new server (FreeBSD-12) running dovecot-2.3.4. My old server (FreeBSD-9.3) is running dovecot-2.3.4 as well. The configurations are 1:1 identical. The are about 250 users on this server, all virtual. They are mostly POP3 users, but they do "leave a copy of message on the server" for set various number of days. Now, to migrate the mail data, can I simply rsync the mail directories between the old and the new server? Would that create a pitfall?? What is the recommended method? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Migrate Mail Data from Dovecot to Dovecot
I have built a new server (FreeBSD-12) running dovecot-2.3.4. My old server (FreeBSD-9.3) is running dovecot-2.3.4 as well. The configurations are 1:1 identical. The are about 250 users on this server, all virtual. They are mostly POP3 users, but they do "leave a copy of message on the server" for set various number of days. Now, to migrate the mail data, can I simply rsync the mail directories between the old and the new server? Would that create a pitfall?? What is the recommended method? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: Using SHA256/512 for SQL based password
On Sun, 17 Feb 2019 at 11:34, Marc Weustink via dovecot
wrote:
> Jean-Daniel Dupas via dovecot wrote:
> >
> >
> >> Le 13 févr. 2019 à 14:54, Robert Moskowitz via dovecot
> >> mailto:dovecot@dovecot.org>> a écrit :
> >>
> >>
> >>
> >> On 2/13/19 8:30 AM, Aki Tuomi wrote:
> >>> On 13.2.2019 15.18, Robert Moskowitz via dovecot wrote:
> >>>>
> >>>> On 2/13/19 1:23 AM, Matthias Fechner via dovecot wrote:
> >>>>>
> >>>>> Am 13. Februar 2019 00:34:15 schrieb Robert Moskowitz
> >>>>> mailto:r...@htt-consult.com>>:
> >>>>>
> >>>>>> On 2/12/19 6:03 PM, Matthias Fechner via dovecot wrote:
> >>>>>>> Am 12.02.2019 um 17:05 schrieb Robert Moskowitz via dovecot:
> >>>>>>>> I have trying to find how to set the dovecot-sql.conf for using
> >>>>>>>> SHA256/512. I am going to start clean with the stronger format,
> not
> >>>>>>>> migrate from the old MD5. It seems all I need is:
> >>>>>>> you maybe would like to have a look to the hashing algo ARGON2I
> >>>>>>> which is
> >>>>>>> currently recommended for new developments and deployments.
> >>>>>> Recommended by whom?
> >>>>>>
> >>>>>> Can you provide a link?
> >>>>> Sure, please see here:
> >>>>> https://www.owasp.org/index.php/Password_Storage_Cheat_Sheet
> >>>>>
> >>>>>>
> >>>>>> And if I was adventurous about hashes, I would be looking more at
> >>>>>> Keccak.
> >>>>>>
> >>>>>>
> >>>>>> Check out my Internet Draft:
> >>>>>>
> >>>>>>
> >>>>>> draft-moskowitz-small-crypto-00.txt
> >>>>> Thanks for the tip, will have a look for into it.
> >>>> Keccak is a general hashing function. It was the first? of the
> >>>> hashing 'sponge' functions, that many have followed. It is the basis
> >>>> of SHA3 (at Keccak's greatest strength).
> >>>>
> >>>> Argon2 seems to be special-built for password hashing. Thing is it is
> >>>> not supported on my CentOS7 system:
> >>>>
> >>>> # doveadm pw -l
> >>>> MD5 MD5-CRYPT SHA SHA1 SHA256 SHA512 SMD5 SSHA SSHA256 SSHA512 PLAIN
> >>>> CLEAR CLEARTEXT PLAIN-TRUNC CRAM-MD5 SCRAM-SHA-1 HMAC-MD5 DIGEST-MD5
> >>>> PLAIN-MD4 PLAIN-MD5 LDAP-MD5 LANMAN NTLM OTP SKEY RPA PBKDF2 CRYPT
> >>>> SHA256-CRYPT SHA512-CRYPT
> >>>>
> >>>> Of course SHA3 is not listed either...
> >>>>
> >>>>
> >>> ARGON2 support is added in dovecot v2.3. It also needs to be enabled
> >>> when compiling dovecot, so varying from packagers it might or not be
> >>> available. The CRYPT ones are available if crypt(3) supports them. In
> >>> dovecot v2.3 we have added bcrypt support regardless of crypt(3)
> support.
> >>
> >> CentOS7 is on dovecot 2.2.36:
> >>
> >> # doveadm pw -s ARGON2-CRYPT -p secret
> >> Fatal: Unknown scheme: ARGON2-CRYPT
> >> # doveadm pw -s ARGON2 -p secret
> >> Fatal: Unknown scheme: ARGON2
> >>
> >> I tend to stay with the distro's rpms and not take on building and
> >> maintaining myself.
> >
> > And for the record, the hash names are ARGON2I and ARGON2ID (see doveadm
> > pw -l )
> >
> > With dovecot from the dovecot.org <http://dovecot.org> repo:
> >
> > # doveadm pw -s ARGON2I -p secret
> >
> {ARGON2I}$argon2i$v=19$m=32768,t=4,p=1$bt96TSr3nVrho2SRhnNP0A$h7LYiqkw/4s6d1d+0Xpe+VUE3aISPnkYq/R7QqPRntk
>
> Also from dovecot.org <http://dovecot.org> repo:
>
> doveadm pw -s ARGON2I -p secret
> Fatal: Unknown scheme: ARGON2I
>
>
>
> Marc
>
It works for me over here:
[wash@waridi ~]#/opt/dovecot2.3/bin/doveadm pw -s ARGON2I -p secret
{ARGON2I}$argon2i$v=19$m=32768,t=4,p=1$9pggnQBea9F3h3O31HoJEA$0zZZgwEuMRVZ3Mc/v6ckpalzVRVCr+GLBWnb8OrgsxU
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", grep ^[^#] :-)
Re: Release notify (2.2.36.1 and 2.3.4.1)
Bueno. I don't even remember well. Wasn't that issue about mysql-8.0.12 to 8.0.13?? On Tue, 5 Feb 2019 at 23:46, Larry Rosenman wrote: > 2.3.4 had the same compile issues > > > On Tue, Feb 5, 2019 at 2:44 PM Odhiambo Washington > wrote: > >> Noted. >> >> I will wait for dovecot-2.3.4.2 tarball then. >> >> In all the servers I listed (+2 more), I never use the mail/dovecot port. >> >> I rely on mail/dovecot port on my own prototype (FreeBSD 12) which I have >> built in preparation for the upgrade of all the servers I currently have >> (except the 11.2). >> So for now, they have to run with 2.3.4, because of that reason - I am >> not using the port. And yes, I know about DESTDIR :-) >> >> >> On Tue, 5 Feb 2019 at 23:35, Larry Rosenman wrote: >> >>> the patches are already in git master. I've pulled them into the >>> mail/dovecot port. >>> >>> The dovecot guys/gals will release it eventually, but the port works >>> TODAY. >>> >>> >>> On Tue, Feb 5, 2019 at 2:33 PM Odhiambo Washington >>> wrote: >>> >>>> I have always been able to compile manually, even from RCs so I believe >>>> I should be able to compile from the tarball as well. >>>> Something is broken, >>>> >>>> On Tue, 5 Feb 2019 at 23:29, Larry Rosenman wrote: >>>> >>>>> pull the patches from the port. >>>>> >>>>> >>>>> On Tue, Feb 5, 2019 at 2:28 PM Odhiambo Washington via dovecot < >>>>> dovecot@dovecot.org> wrote: >>>>> >>>>>> Oh, so manual compile should NOT work and it's okay or am I missing >>>>>> something? >>>>>> >>>>>> On Tue, 5 Feb 2019 at 23:26, The Doctor >>>>>> wrote: >>>>>> >>>>>>> On Tue, Feb 05, 2019 at 11:18:45PM +0300, Odhiambo Washington via >>>>>>> dovecot wrote: >>>>>>> > On Tue, 5 Feb 2019 at 20:32, Aki Tuomi via dovecot < >>>>>>> dovecot@dovecot.org> >>>>>>> > wrote: >>>>>>> > >>>>>>> > > Due to DMARC issues some people have failed to receive the >>>>>>> latest security >>>>>>> > > information, so here it is repeated for both releases: >>>>>>> > > >>>>>>> > > 2.3.4.1 >>>>>>> > > >>>>>>> > > https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz >>>>>>> > > https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz.sig >>>>>>> > > <https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz.sig> >>>>>>> > > Binary packages in https://repo.dovecot.org/ >>>>>>> > > >>>>>>> > > * CVE-2019-3814: If imap/pop3/managesieve/submission client >>>>>>> has >>>>>>> > > trusted certificate with missing username field >>>>>>> > > (ssl_cert_username_field), under some configurations >>>>>>> Dovecot >>>>>>> > > mistakenly trusts the username provided via authentication >>>>>>> instead >>>>>>> > > of failing. >>>>>>> > > * ssl_cert_username_field setting was ignored with external >>>>>>> SMTP AUTH, >>>>>>> > > because none of the MTAs (Postfix, Exim) currently send the >>>>>>> > > cert_username field. This may have allowed users with >>>>>>> trusted >>>>>>> > > certificate to specify any username in the authentication. >>>>>>> This bug >>>>>>> > > didn't affect Dovecot's Submission service. >>>>>>> > > >>>>>>> > >>>>>>> > FreeBSD-11.2 (amd64): >>>>>>> > >>>>>>> > gmake[2]: Entering directory >>>>>>> > '/usr/home/wash/Tools/Dovecot/2.3/dovecot-2.3.4.1/src/lib-master' >>>>>>> > gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib >>>>>>> -I../../src/lib-dns >>>>>>> > -I../../src/lib-test -I../../src/lib-settings >>>>>>> -I../../src/lib-ssl-iostream >>&g
Re: Release notify (2.2.36.1 and 2.3.4.1)
Noted. I will wait for dovecot-2.3.4.2 tarball then. In all the servers I listed (+2 more), I never use the mail/dovecot port. I rely on mail/dovecot port on my own prototype (FreeBSD 12) which I have built in preparation for the upgrade of all the servers I currently have (except the 11.2). So for now, they have to run with 2.3.4, because of that reason - I am not using the port. And yes, I know about DESTDIR :-) On Tue, 5 Feb 2019 at 23:35, Larry Rosenman wrote: > the patches are already in git master. I've pulled them into the > mail/dovecot port. > > The dovecot guys/gals will release it eventually, but the port works TODAY. > > > On Tue, Feb 5, 2019 at 2:33 PM Odhiambo Washington > wrote: > >> I have always been able to compile manually, even from RCs so I believe I >> should be able to compile from the tarball as well. >> Something is broken, >> >> On Tue, 5 Feb 2019 at 23:29, Larry Rosenman wrote: >> >>> pull the patches from the port. >>> >>> >>> On Tue, Feb 5, 2019 at 2:28 PM Odhiambo Washington via dovecot < >>> dovecot@dovecot.org> wrote: >>> >>>> Oh, so manual compile should NOT work and it's okay or am I missing >>>> something? >>>> >>>> On Tue, 5 Feb 2019 at 23:26, The Doctor >>>> wrote: >>>> >>>>> On Tue, Feb 05, 2019 at 11:18:45PM +0300, Odhiambo Washington via >>>>> dovecot wrote: >>>>> > On Tue, 5 Feb 2019 at 20:32, Aki Tuomi via dovecot < >>>>> dovecot@dovecot.org> >>>>> > wrote: >>>>> > >>>>> > > Due to DMARC issues some people have failed to receive the latest >>>>> security >>>>> > > information, so here it is repeated for both releases: >>>>> > > >>>>> > > 2.3.4.1 >>>>> > > >>>>> > > https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz >>>>> > > https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz.sig >>>>> > > <https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz.sig> >>>>> > > Binary packages in https://repo.dovecot.org/ >>>>> > > >>>>> > > * CVE-2019-3814: If imap/pop3/managesieve/submission client has >>>>> > > trusted certificate with missing username field >>>>> > > (ssl_cert_username_field), under some configurations Dovecot >>>>> > > mistakenly trusts the username provided via authentication >>>>> instead >>>>> > > of failing. >>>>> > > * ssl_cert_username_field setting was ignored with external >>>>> SMTP AUTH, >>>>> > > because none of the MTAs (Postfix, Exim) currently send the >>>>> > > cert_username field. This may have allowed users with trusted >>>>> > > certificate to specify any username in the authentication. >>>>> This bug >>>>> > > didn't affect Dovecot's Submission service. >>>>> > > >>>>> > >>>>> > FreeBSD-11.2 (amd64): >>>>> > >>>>> > gmake[2]: Entering directory >>>>> > '/usr/home/wash/Tools/Dovecot/2.3/dovecot-2.3.4.1/src/lib-master' >>>>> > gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-dns >>>>> > -I../../src/lib-test -I../../src/lib-settings >>>>> -I../../src/lib-ssl-iostream >>>>> > -DPKG_RUNDIR=\""/opt/dovecot2.3/var/run/dovecot"\" >>>>> > -DPKG_STATEDIR=\""/opt/dovecot2.3/var/lib/dovecot"\" >>>>> > -DSYSCONFDIR=\""/opt/dovecot2.3/etc/dovecot"\" >>>>> > -DBINDIR=\""/opt/dovecot2.3/bin"\" -std=gnu99 -g -O2 >>>>> > -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wall >>>>> -W >>>>> > -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith >>>>> > -Wchar-subscripts -Wformat=2 -Wbad-function-cast >>>>> -fno-builtin-strftime >>>>> > -Wstrict-aliasing=2 -I/usr/local/include -MT test-event-stats.o >>>>> -MD -MP >>>>> > -MF .deps/test-event-stats.Tpo -c -o test-event-stats.o >>>>> test-event-stats.c >>>>> > test-event-stats.c: In function 'kill_stats_child': >>>>> > test-event-
Re: Release notify (2.2.36.1 and 2.3.4.1)
I have always been able to compile manually, even from RCs so I believe I should be able to compile from the tarball as well. Something is broken, On Tue, 5 Feb 2019 at 23:29, Larry Rosenman wrote: > pull the patches from the port. > > > On Tue, Feb 5, 2019 at 2:28 PM Odhiambo Washington via dovecot < > dovecot@dovecot.org> wrote: > >> Oh, so manual compile should NOT work and it's okay or am I missing >> something? >> >> On Tue, 5 Feb 2019 at 23:26, The Doctor wrote: >> >>> On Tue, Feb 05, 2019 at 11:18:45PM +0300, Odhiambo Washington via >>> dovecot wrote: >>> > On Tue, 5 Feb 2019 at 20:32, Aki Tuomi via dovecot < >>> dovecot@dovecot.org> >>> > wrote: >>> > >>> > > Due to DMARC issues some people have failed to receive the latest >>> security >>> > > information, so here it is repeated for both releases: >>> > > >>> > > 2.3.4.1 >>> > > >>> > > https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz >>> > > https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz.sig >>> > > <https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz.sig> >>> > > Binary packages in https://repo.dovecot.org/ >>> > > >>> > > * CVE-2019-3814: If imap/pop3/managesieve/submission client has >>> > > trusted certificate with missing username field >>> > > (ssl_cert_username_field), under some configurations Dovecot >>> > > mistakenly trusts the username provided via authentication >>> instead >>> > > of failing. >>> > > * ssl_cert_username_field setting was ignored with external SMTP >>> AUTH, >>> > > because none of the MTAs (Postfix, Exim) currently send the >>> > > cert_username field. This may have allowed users with trusted >>> > > certificate to specify any username in the authentication. >>> This bug >>> > > didn't affect Dovecot's Submission service. >>> > > >>> > >>> > FreeBSD-11.2 (amd64): >>> > >>> > gmake[2]: Entering directory >>> > '/usr/home/wash/Tools/Dovecot/2.3/dovecot-2.3.4.1/src/lib-master' >>> > gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-dns >>> > -I../../src/lib-test -I../../src/lib-settings >>> -I../../src/lib-ssl-iostream >>> > -DPKG_RUNDIR=\""/opt/dovecot2.3/var/run/dovecot"\" >>> > -DPKG_STATEDIR=\""/opt/dovecot2.3/var/lib/dovecot"\" >>> > -DSYSCONFDIR=\""/opt/dovecot2.3/etc/dovecot"\" >>> > -DBINDIR=\""/opt/dovecot2.3/bin"\" -std=gnu99 -g -O2 >>> > -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wall -W >>> > -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith >>> > -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime >>> > -Wstrict-aliasing=2 -I/usr/local/include -MT test-event-stats.o -MD >>> -MP >>> > -MF .deps/test-event-stats.Tpo -c -o test-event-stats.o >>> test-event-stats.c >>> > test-event-stats.c: In function 'kill_stats_child': >>> > test-event-stats.c:101:2: warning: implicit declaration of function >>> 'kill' >>> > [-Wimplicit-function-declaration] >>> > (void)kill(stats_pid, SIGKILL); >>> > ^ >>> > test-event-stats.c:101:24: error: 'SIGKILL' undeclared (first use in >>> this >>> > function) >>> > (void)kill(stats_pid, SIGKILL); >>> > ^ >>> > test-event-stats.c:101:24: note: each undeclared identifier is reported >>> > only once for each function it appears in >>> > gmake[2]: *** [Makefile:638: test-event-stats.o] Error 1 >>> > gmake[2]: Leaving directory >>> > '/usr/home/wash/Tools/Dovecot/2.3/dovecot-2.3.4.1/src/lib-master' >>> > gmake[1]: *** [Makefile:565: install-recursive] Error 1 >>> > gmake[1]: Leaving directory >>> > '/usr/home/wash/Tools/Dovecot/2.3/dovecot-2.3.4.1/src' >>> > gmake: *** [Makefile:683: install-recursive] Error 1 >>> > >>> > >>> >>> >>> Ports wokred for me. >>> >>> > >>> > >>> > FreeBSD-9.3: >>> > >>> > gmake[3]: Entering directory >>> > '/usr/home/wash/Tools/Dovecot/2.3/dovecot-2.3.4.1
Re: Release notify (2.2.36.1 and 2.3.4.1)
Oh, so manual compile should NOT work and it's okay or am I missing something? On Tue, 5 Feb 2019 at 23:26, The Doctor wrote: > On Tue, Feb 05, 2019 at 11:18:45PM +0300, Odhiambo Washington via dovecot > wrote: > > On Tue, 5 Feb 2019 at 20:32, Aki Tuomi via dovecot > > wrote: > > > > > Due to DMARC issues some people have failed to receive the latest > security > > > information, so here it is repeated for both releases: > > > > > > 2.3.4.1 > > > > > > https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz > > > https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz.sig > > > <https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz.sig> > > > Binary packages in https://repo.dovecot.org/ > > > > > > * CVE-2019-3814: If imap/pop3/managesieve/submission client has > > > trusted certificate with missing username field > > > (ssl_cert_username_field), under some configurations Dovecot > > > mistakenly trusts the username provided via authentication > instead > > > of failing. > > > * ssl_cert_username_field setting was ignored with external SMTP > AUTH, > > > because none of the MTAs (Postfix, Exim) currently send the > > > cert_username field. This may have allowed users with trusted > > > certificate to specify any username in the authentication. This > bug > > > didn't affect Dovecot's Submission service. > > > > > > > FreeBSD-11.2 (amd64): > > > > gmake[2]: Entering directory > > '/usr/home/wash/Tools/Dovecot/2.3/dovecot-2.3.4.1/src/lib-master' > > gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-dns > > -I../../src/lib-test -I../../src/lib-settings > -I../../src/lib-ssl-iostream > > -DPKG_RUNDIR=\""/opt/dovecot2.3/var/run/dovecot"\" > > -DPKG_STATEDIR=\""/opt/dovecot2.3/var/lib/dovecot"\" > > -DSYSCONFDIR=\""/opt/dovecot2.3/etc/dovecot"\" > > -DBINDIR=\""/opt/dovecot2.3/bin"\" -std=gnu99 -g -O2 > > -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wall -W > > -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith > > -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime > > -Wstrict-aliasing=2 -I/usr/local/include -MT test-event-stats.o -MD -MP > > -MF .deps/test-event-stats.Tpo -c -o test-event-stats.o > test-event-stats.c > > test-event-stats.c: In function 'kill_stats_child': > > test-event-stats.c:101:2: warning: implicit declaration of function > 'kill' > > [-Wimplicit-function-declaration] > > (void)kill(stats_pid, SIGKILL); > > ^ > > test-event-stats.c:101:24: error: 'SIGKILL' undeclared (first use in this > > function) > > (void)kill(stats_pid, SIGKILL); > > ^ > > test-event-stats.c:101:24: note: each undeclared identifier is reported > > only once for each function it appears in > > gmake[2]: *** [Makefile:638: test-event-stats.o] Error 1 > > gmake[2]: Leaving directory > > '/usr/home/wash/Tools/Dovecot/2.3/dovecot-2.3.4.1/src/lib-master' > > gmake[1]: *** [Makefile:565: install-recursive] Error 1 > > gmake[1]: Leaving directory > > '/usr/home/wash/Tools/Dovecot/2.3/dovecot-2.3.4.1/src' > > gmake: *** [Makefile:683: install-recursive] Error 1 > > > > > > > Ports wokred for me. > > > > > > > FreeBSD-9.3: > > > > gmake[3]: Entering directory > > '/usr/home/wash/Tools/Dovecot/2.3/dovecot-2.3.4.1/src/lib-master' > > gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-dns > > -I../../src/lib-test -I../../src/lib-settings > -I../../src/lib-ssl-iostream > > -DPKG_RUNDIR=\""/opt/dovecot2.3/var/run/dovecot"\" > > -DPKG_STATEDIR=\""/opt/dovecot2.3/var/lib/dovecot"\" > > -DSYSCONFDIR=\""/opt/dovecot2.3/etc/dovecot"\" > > -DBINDIR=\""/opt/dovecot2.3/bin"\" -std=gnu99 -g -O2 -fstack-protector > > -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wall -W -Wmissing-prototypes > > -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 > > -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 > > -I/usr/local/include -MT test-event-stats.o -MD -MP -MF > > .deps/test-event-stats.Tpo -c -o test-event-stats.o test-event-stats.c > > test-event-stats.c: In function 'kill_stats_child': > > test-event-stats.c:101: warning: implicit declaration of function 'kill' > > test-event-stats.c:101: error: 'SIGKILL' un
Re: Release notify (2.2.36.1 and 2.3.4.1)
stats.c:484: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'uint64_t' test-event-stats.c:484: warning: format '%lu' expects type 'long unsigned int', but argument 6 has type 'uint64_t' test-event-stats.c: In function 'test_merge_events_skip_parents': test-event-stats.c:526: warning: format '%lu' expects type 'long unsigned int', but argument 2 has type 'uint64_t' test-event-stats.c:526: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'uint64_t' test-event-stats.c:526: warning: format '%lu' expects type 'long unsigned int', but argument 6 has type 'uint64_t' Makefile:638: recipe for target 'test-event-stats.o' failed gmake[3]: *** [test-event-stats.o] Error 1 gmake[3]: Leaving directory '/usr/home/wash/Tools/Dovecot/2.3/dovecot-2.3.4.1/src/lib-master' Makefile:565: recipe for target 'all-recursive' failed gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory '/usr/home/wash/Tools/Dovecot/2.3/dovecot-2.3.4.1/src' Makefile:683: recipe for target 'all-recursive' failed gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory '/usr/home/wash/Tools/Dovecot/2.3/dovecot-2.3.4.1' Makefile:527: recipe for target 'all' failed gmake: *** [all] Error 2 [wash@gw ~/Tools/Dovecot/2.3/dovecot-2.3.4.1]$ FreeBSD-8.4: Making all in lib-master source='test-event-stats.c' object='test-event-stats.o' libtool=no DEPDIR=.deps depmode=none /bin/bash ../../depcomp gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-dns -I../../src/lib-test -I../../src/lib-settings -I../../src/lib-ssl-iostream -DPKG_RUNDIR=\""/opt/dovecot2.3/var/run/dovecot"\" -DPKG_STATEDIR=\""/opt/dovecot2.3/var/lib/dovecot"\" -DSYSCONFDIR=\""/opt/dovecot2.3/etc/dovecot"\" -DBINDIR=\""/opt/dovecot2.3/bin"\"-std=gnu99 -g -O2 -fstack-protector -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I/usr/local/include -c -o test-event-stats.o test-event-stats.c test-event-stats.c: In function 'kill_stats_child': test-event-stats.c:101: warning: implicit declaration of function 'kill' test-event-stats.c:101: error: 'SIGKILL' undeclared (first use in this function) test-event-stats.c:101: error: (Each undeclared identifier is reported only once test-event-stats.c:101: error: for each function it appears in.) test-event-stats.c: In function 'test_no_merging2': test-event-stats.c:361: warning: format '%lu' expects type 'long unsigned int', but argument 2 has type 'uint64_t' test-event-stats.c: In function 'test_no_merging3': test-event-stats.c:387: warning: format '%lu' expects type 'long unsigned int', but argument 2 has type 'uint64_t' test-event-stats.c:387: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'uint64_t' test-event-stats.c:387: warning: format '%lu' expects type 'long unsigned int', but argument 6 has type 'uint64_t' test-event-stats.c: In function 'test_merge_events2': test-event-stats.c:452: warning: format '%lu' expects type 'long unsigned int', but argument 2 has type 'uint64_t' test-event-stats.c: In function 'test_skip_parents': test-event-stats.c:484: warning: format '%lu' expects type 'long unsigned int', but argument 2 has type 'uint64_t' test-event-stats.c:484: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'uint64_t' test-event-stats.c:484: warning: format '%lu' expects type 'long unsigned int', but argument 6 has type 'uint64_t' test-event-stats.c: In function 'test_merge_events_skip_parents': test-event-stats.c:526: warning: format '%lu' expects type 'long unsigned int', but argument 2 has type 'uint64_t' test-event-stats.c:526: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'uint64_t' test-event-stats.c:526: warning: format '%lu' expects type 'long unsigned int', but argument 6 has type 'uint64_t' *** Error code 1 Stop. make: stopped in /usr/home/wash/Tools/Dovecot/2.3/dovecot-2.3.4.1/src/lib-master *** Error code 1 Stop. make: stopped in /usr/home/wash/Tools/Dovecot/2.3/dovecot-2.3.4.1/src *** Error code 1 Stop. make: stopped in /home/wash/Tools/Dovecot/2.3/dovecot-2.3.4.1 Makefile:527: recipe for target 'all' failed gmake: *** [all] Error 1 (23:18:46 <~/Tools/Dovecot/2.3/dovecot-2.3.4.1>) 0 $ -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: Changing the imaps port #
On Tue, 22 Jan 2019 at 06:17, Patrick Mahan wrote:
> Dovecot 2.3.4, FreeBSD 11.2
>
> Due to comcast buisness ISP intercepting imaps I need to have my clients
> connect to non-standard port (). Previously I had been using stunnel
> to receive the imaps connection and forward it to the imap port over
> 127.0.0.1. But I would like to retire stunnel and have my imap clients
> connect remotely.
>
> I have configured the imap-login service -
>
> service imap-login {
> inet_listener imap {
> address = 127.0.0.1, ::1
> port = 143
> }
> inet_listener imaps {
> port =
> }
> process_min_avail = 3
> service_count = 0
> vsz_limit = 1 G
> }
>
> But I am not seeing any listeners on port -
>
> root@ns(1001)# netstat -an | grep
>
> Using sockstat on FreeBSD:
>
> root@ns(1002)# sockstat | grep dovecot | grep tcp
> root dovecot 34800 15 tcp4 *:4190
>*:*
> root dovecot 34800 37 tcp4 127.0.0.1:143
> *:*
> root dovecot 34800 38 tcp6 ::1:143
> *:*
>
> I have mail_debug = yes, but I don't see any failures. What is the best
> way to debug why I am not seeing this port number?
>
> Thanks,
>
> Patrick
>
>
I would leave dovecot config untouched and use a firewall (PF) to translate
port to whatever dovecot listens to.
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", grep ^[^#] :-)
Re: 2.3.4 doesnt compile on FreeBSD 11.2 using clang
And it works now. I have managed to successfully compile dovecot-2.3.4 against mysql-8.0.13. On Sun, 20 Jan 2019 at 21:22, Larry Rosenman wrote: > the above(below?) cited patch is already in the 2.3.4 port for FreeBSD. > As I stated earlier, I'm the FreeBSD port maintainer. > > On Sun, Jan 20, 2019 at 11:48 AM Stephan Bosch > wrote: > >> >> >> Op 29/12/2018 om 10:25 schreef Aki Tuomi: >> > Hi! >> > >> > Can you give >> > >> > https://github.com/dovecot/core/compare/1004822%5E..de42b54a.patch >> > >> > a try? It's in master branch. >> >> This fix is scheduled for 2.3.5. >> >> Regards, >> >> Stephan. >> >> > On 29 December 2018 at 02:51 Chris wrote: >> > >> > >> > extract below, this has already been reported a while back but still >> > no new patch, so this email is to serve as a reminder, if someone >> > manually fixes it for the ports tree, I dont consider that a fix, >> > ideally we need this fixed in the source code, as not everyone will >> > install it from ports. >> > >> > Chris >> > >> > "clang40 -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib >> > -I../../src/lib-dns -I../../src/lib-test -I../../src/lib-settings >> > -I../../src/lib-ssl-iostream -DPKG_RUNDIR=\""/var/run/dovecot"\" >> > -DPKG_STATEDIR=\""/var/lib/dovecot"\" -DSYSCONFDIR=\""/etc/dovecot"\" >> > -DBINDIR=\""/usr/bin"\" -I/usr/local/include -std=gnu99 >> > -fdiagnostics-color -Wl,-rpath=/usr/local/llvm40/lib -O2 -pipe >> > -march=native -fno-strict-aliasing -fstack-protector-strong >> > -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wall -W -Wmissing-prototypes >> > -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 >> > -Wbad-function-cast -Wno-duplicate-decl-specifier -Wstrict-aliasing=2 >> > -I/usr/local/include -MT test-event-stats.o -MD -MP -MF >> > .deps/test-event-stats.Tpo -c -o test-event-stats.o test-event-stats.c >> > clang-4.0: warning: -Wl,-rpath=/usr/local/llvm40/lib: 'linker' input >> > unused [-Wunused-command-line-argument] >> > test-event-stats.c:101:8: warning: implicit declaration of function >> > 'kill' is invalid in C99 [-Wimplicit-function-declaration] >> > (void)kill(stats_pid, SIGKILL); >> >^ >> > test-event-stats.c:101:24: error: use of undeclared identifier 'SIGKILL' >> > (void)kill(stats_pid, SIGKILL); >> >^ >> > 1 warning and 1 error generated. >> > gmake[2]: *** [Makefile:656: test-event-stats.o] Error 1 >> > gmake[2]: Leaving directory >> > '/usr/local/directadmin/custombuild/dovecot-2.3.4/src/lib-master' >> > gmake[1]: *** [Makefile:565: install-recursive] Error 1 >> > gmake[1]: Leaving directory >> > '/usr/local/directadmin/custombuild/dovecot-2.3.4/src' >> > gmake: *** [Makefile:683: install-recursive] Error 1" >> >> > > -- > Larry Rosenman http://www.lerctr.org/~ler > Phone: +1 214-642-9640 (c) E-Mail: larry...@gmail.com > US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: MySQL 8.0: Supported?
On Tue, 15 Jan 2019 at 04:57, Larry Rosenman wrote: > I got a complaint from a FreeBSD user that they couldn't compile dovecot > against MySQL 8.0. > > Is MySQL 8.0 support with 2.3.4? > > they receive: > checking for mysql_init in -lmysqlclient... no > configure: error: Can't build with MySQL support: libmysqlclient not > found ===> Script "configure" failed unexpectedly. > Please report the problem to l...@freebsd.org [maintainer] and attach the > "/wrkdirs/usr/ports/mail/dovecot/work/dovecot-2.3.4/config.log" > including the output of the failure of your make command. Also, it > might be a good idea to provide an overview of all packages installed > on your system (e.g. a /usr/local/sbin/pkg-static info -g -Ea). > *** Error code 1 > > thanks! > I recently installed FreeBSD-12 and installed MySQL-8.0 and build dovecot-2.3.4 against it. Well, I tried to do ldd /usr/local/sbin/dovecot to see what it's build against, but it shows different output than what I see when I do the same against my Exim. Maybe it's a gcc vs clang issue, but root@gw:/usr/home/wash # uname -msrsv FreeBSD 12.0-RELEASE FreeBSD 12.0-RELEASE r341666 GENERIC amd64 root@gw:/usr/home/wash # mysql --version mysql Ver 8.0.12 for FreeBSD12.0 on amd64 (Source distribution) root@gw:/usr/home/wash # strings /usr/local/sbin/dovecot | grep SQL SQL drivers: mysql postgresql sqlite In the output you've given, let's just say the issue is that there is no libmysqlclient.so.21 in the standard INCLUDE path.. I have just extracted dovecot-2.3.4 into a directory and did: ./configure --with-mysql=yes The output is: ---8< checking for mysql_config... mysql_config checking for mysql_init in -lmysqlclient... yes checking mysql.h usability... yes checking mysql.h presence... yes checking for mysql.h... yes checking for mysql_ssl_set in -lmysqlclient... yes --8<-- Install prefix . : /usr/local File offsets ... : 64bit I/O polling : kqueue I/O notifys : kqueue SSL : yes (OpenSSL) GSSAPI . : no passdbs : static passwd passwd-file pam checkpassword sql CFLAGS . : -std=gnu99 -g -O2 -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wno-duplicate-decl-specifier -Wstrict-aliasing=2 : -shadow -bsdauth -sia -ldap -vpopmail userdbs : static prefetch passwd passwd-file checkpassword sql : -ldap -vpopmail *SQL drivers : mysql* : -pgsql -sqlite -cassandra Full text search : squat : -lucene -solr root@gw:/usr/local/SRC/dovecot-2.3.4 # So, yes, it's supported! -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: [FTS Xapian] Beta release
Testing a compile on FreeBSD. gmake[2]: Entering directory '/usr/home/wash/Tools/Dovecot/fts-xapian/src' /bin/sh ../libtool --tag=CXX --mode=compile c++ -DHAVE_CONFIG_H -I. -I.. -I/opt/dovecot2.3/include/dovecot -I/opt/dovecot2.3/include/dovecot -g -O2 -MT fts-backend-xapian.lo -MD -MP -MF .deps/fts-backend-xapian.Tpo -c -o fts-backend-xapian.lo fts-backend-xapian.cpp libtool: compile: c++ -DHAVE_CONFIG_H -I. -I.. -I/opt/dovecot2.3/include/dovecot -I/opt/dovecot2.3/include/dovecot -g -O2 -MT fts-backend-xapian.lo -MD -MP -MF .deps/fts-backend-xapian.Tpo -c fts-backend-xapian.cpp -fPIC -DPIC -o .libs/fts-backend-xapian.o fts-backend-xapian.cpp:3:10: fatal error: 'xapian.h' file not found #include ^~ Well, I installed xapian-core and the xapian.h is in /usr/local/include/ I can overcome the fatal error by doing: env CPPFLAGS=-I/usr/local/include PANDOC=false ./configure --prefix=/opt --with-dovecot=/opt/dovecot2.3/lib/dovecot/ Is that something that you can address within the code or we (*BSD) have to live with it? During `make`, the following warning is generated: /bin/sh ../libtool --tag=CXX --mode=compile c++ -DHAVE_CONFIG_H -I. -I.. -I/opt/dovecot2.3/include/dovecot -I/usr/local/include -I/opt/dovecot2.3/include/dovecot -g -O2 -MT fts-backend-xapian.lo -MD -MP -MF .deps/fts-backend-xapian.Tpo -c -o fts-backend-xapian.lo fts-backend-xapian.cpp libtool: compile: c++ -DHAVE_CONFIG_H -I. -I.. -I/opt/dovecot2.3/include/dovecot -I/usr/local/include -I/opt/dovecot2.3/include/dovecot -g -O2 -MT fts-backend-xapian.lo -MD -MP -MF .deps/fts-backend-xapian.Tpo -c fts-backend-xapian.cpp -fPIC -DPIC -o .libs/fts-backend-xapian.o fts-backend-xapian.cpp:486:14: warning: format string is not a string literal (potentially insecure) [-Wformat-security] i_warning(e.get_msg().c_str()); ^~~ fts-backend-xapian.cpp:486:14: note: treat the string as an argument to avoid this i_warning(e.get_msg().c_str()); ^ "%s", 1 warning generated. Is that something you can look into as well? On Mon, 14 Jan 2019 at 11:43, Joan Moreau wrote: > THank you Odhiambo. I updated accordingly > > > > > > On 2019-01-14 08:07, Odhiambo Washington wrote: > > In your README.md, perhaps "This project intends to provide a > straightforward and simple *procedure *to configure FTS plugin for > Dovecot, leveraging the efforts by the Xapian.org team." is better?? > Also in the part after cloning from git: > > ./configure --prefix=/usr --with-dovecot=/path/to/dovecot [ This > /path/to/dovecot is not obvious. Is it the dovecot binary or what??] > > On Mon, 14 Jan 2019 at 09:42, Joan Moreau via dovecot > wrote: > >> Thank you Stephan. >> >> The version here shall be up and running : >> https://github.com/grosjo/fts-xapian >> >> >> >> >> >> On 2019-01-14 00:07, Stephan Bosch wrote: >> >> >> >> Op 13/01/2019 om 21:25 schreef Joan Moreau via dovecot: >> >> >> I tried to combined it, the "autoreconf" errors are solved >> >> Now, when I type "make install", the lib is not pushed into dovecot >> folder, but somewhere in /usr/local/... >> >> How to adjust this to have it arriving in the proper folder ? >> >> >> Depends on your system. It mostly a matter of setting a proper --prefix >> directory for configure, but other paths are configurable as well. I >> usually check what the official distribution package for Dovecot is doing >> and use that as a basis. >> >> For Debian I use the following configure command: >> >> ./configure --with-ldap=plugin --with-ssl=openssl --with-sql=plugin >> --with-lua=plugin --with-pgsql --with-mysql --with-sqlite \ >> --with-gssapi=plugin --with-solr --with-ioloop=best >> --enable-maintainer-mode \ >> --prefix=/usr --sysconfdir=/etc --libexecdir=/usr/lib >> --localstatedir=/var --mandir=/usr/share/man \ >> --infodir=/usr/share/info >> --with-moduledir=/usr/lib/dovecot/modules --disable-rpath --disable-static >> >> Regards, >> >> Stephan >> >> >> On 2019-01-13 21:01, Tuomi, Aki wrote: >> >> You copied your Makefile.am there. Stephan made you a working version, >> can you try that? >> (sorry for dup) >> Aki >> Original message >> From: Joan Moreau >> Date: 13/01/2019 21:39 (GMT+02:00) >> To: Stephan Bosch >> Cc: Aki Tuomi >> Subject: Re: [FTS Xapian] Beta release >> >> I used the skeleton from Aki : https://github.com/grosj
Re: Freebsd: Fatal error - Support not compiled in for passdb driver 'sql'
So maybe we should tell the OP that he needs to: cd /usr/ports/mail/dovecot make config [ select the MySQL option and save] make install clean. [He's probably coming from Linux world to FreeBSD] On Mon, 14 Jan 2019 at 13:25, Larry Rosenman wrote: > Ports has the options, I'm just not changing the defaults. > > Get Outlook for Android <https://aka.ms/ghei36> > > -- > *From:* dovecot on behalf of Odhiambo > Washington > *Sent:* Monday, January 14, 2019 3:47:43 AM > *To:* gsjarvis > *Cc:* Dovecot Mailing List > *Subject:* Re: Freebsd: Fatal error - Support not compiled in for passdb > driver 'sql' > > > > On Sun, 13 Jan 2019 at 22:15, gsjarvis wrote: > >> Hello, >> >> I was wondering if there was any progress on this. >> >> I just upgraded a FreeBSD box and had the same issue again. >> >> I keep (reasonably) good support notes so I found the one that said I had >> to >> install from ports - so all is well. I was just wondering if there was any >> news. >> >> I look forward to hearing from you. >> >> Thanks, >> >> -Graham- >> >> > > I have run RC versions and well as RELEASE versions on FreeBSD and I > always compile with (/opt path relative to version): > ./configure \ > --prefix=/opt/dovecot2.3 \ > --with-ioloop=kqueue \ > --with-notify=kqueue \ > --with-sql=yes \ > --with-mysql \ > --with-zlib \ > --with-bzlib \ > --with-ssl=openssl > gmake install > > > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", grep ^[^#] :-) > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: Freebsd: Fatal error - Support not compiled in for passdb driver 'sql'
On Sun, 13 Jan 2019 at 22:15, gsjarvis wrote: > Hello, > > I was wondering if there was any progress on this. > > I just upgraded a FreeBSD box and had the same issue again. > > I keep (reasonably) good support notes so I found the one that said I had > to > install from ports - so all is well. I was just wondering if there was any > news. > > I look forward to hearing from you. > > Thanks, > > -Graham- > > I have run RC versions and well as RELEASE versions on FreeBSD and I always compile with (/opt path relative to version): ./configure \ --prefix=/opt/dovecot2.3 \ --with-ioloop=kqueue \ --with-notify=kqueue \ --with-sql=yes \ --with-mysql \ --with-zlib \ --with-bzlib \ --with-ssl=openssl gmake install -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: [FTS Xapian] Beta release
fixing all the inevitable bugs it has
> and maintaining it. We do not want, at this moment, take
> up maintaining and developing yet another FTS plugin as
> we have plenty of things to do already.
>
> I invite you to setup your own repository and provide
> this plugin from there, being the maintainer of this
> plugin. We can add a link to your plugin on our FTS page
> so people can also find it.
>
> There are other plugins like this, e.g.
> https://github.com/st3fan/dovecot-xaps-plugin
>
>
> I turned the code you provided into a separate plugin
> package. The distribution tarball is attached.
>
> Notable changes:
>
> - Added example copyright headers and COPYING and AUTHORS
> files. You should modify those to your preference.
> - Added README and INSTALL files (in markdown using Pandoc).
> Those need to be amended with details.
> - Amended the plugin code to display a debug message with the
> plugin name and version upon plugin load.
>
>
> I advise you to turn this into a git repository and continue from
> there.
>
> I do not recommend releasing this plugin with the
> -fpermissive flag and the resulting warning as it is now. But
> I'm assuming this is still a work in progress, so that is OK.
>
> Regards,
>
> Stephan.
>
>
> On 13 January 2019 at 19:52 Joan Moreau <mailto:j...@grosjo.net>> wrote:
>
>
> The only point here of this fts-xapian is to get rid
> of solr (because it
>
> is just a nightmare to setup) and squat (because it is
> considere
> obsolete).
>
> I already sent the changed in configure.ac, makefile.am
> , etc.. in order
> to include it in the dovecot, and it compiles properly
>
>
> The only remaining point is to push it in hte git (yes,
> everything is
> already done)
>
> On 2019-01-13 18:45, Aki Tuomi wrote:
>
> On 13 January 2019 at 17:05 Joan Moreau via
> dovecot <mailto:dovecot@dovecot.org>> wrote:
>
> Hi
>
> Please find attached the beta release of FTS
> Xapian, with the objective
> to replace fts_squat that is being deprecated.
>
> Configuration is exactly the same as for fts_squat:
>
> plugin {
>
> plugin = fts fts_xapian (...)
> fts = xapian
> fts_autoindex = yes
> fts_enforced = yes
> fts_xapian = partial=2 full=20
>
> This is installed on my production server
> (>120Gb of mailboxes), and I
> will observe it during the coming days.
>
>
> I will definitely appreciate that this is added in
> the core git of
> docevot, in order to have a versionning of
> it, to remove squat and let
>
> basic users able to avoid Solr alternative as much as
> possible.
>
> Thanks
>
> JM
>
> Hi!
>
> I still recommend you setup a, say, github
> repository for your plugin. We are not able to
> currently include your work in dovecot core as it
> is more work than just pushing the code into the
> repo. Maybe it can be included in the future.
>
> If you want, I can help you in setting up the
> required configuration scripts and such to make
> it possible to compile it as plugin.
>
> Then anyone can download it and install it for
> their dovecot, even if dovecot itself has been
> installed from packages, and also makes it
> possible for package maintainers to consider
> including it in distributions.
>
> Aki
>
>
>
>
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", grep ^[^#] :-)
Re: Dovecot Submission Proxy Auth
On Wed, 9 Jan 2019 at 13:09, Jacky wrote:
> Hi Gerald,
>
> in my postfix/main.cf
>
> smtpd_sasl_authenticated_header = yes
> smtpd_sasl_security_options = noanonymous
> smtpd_sasl_local_domain = $myhostname
> smtpd_sasl_type = dovecot
> smtpd_sasl_path = /var/run/dovecot/auth-client
> broken_sasl_auth_clients = yes
>
> I am already using dovecot for SASL
>
> The dovecot submission service authenticates users and already added the
> AUTH= parameter in the MAIL FROM
>
> MAIL FROM: AUTH=ja...@xxx.com SIZE=1430
>
> But, it seems that postfix does not accept the AUTH= parameter and
> reject the sender as no logged in.
>
>
> Best regards,
>
> Jacky
>
>
Hi Jacky,
Your question belongs to postfix mailinng list.
Anyway, the last time I was playing with postfix (I am an Exim user
normally), I had to check that:
smtpd_sasl_path = /var/run/dovecot/auth-client
..the socket is readable by the postfix user:
So, check 10-master.conf for the socket. Something like:
# Postfix smtp-auth
unix_listener var/run/dovecot/auth-client {
mode = 0666
}
Restart dovecot and see...
You can read the https://wiki.dovecot.org/HowTo/PostfixAndDovecotSASL
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", grep ^[^#] :-)
Re: Authentication Problem
On Fri, 21 Dec 2018 at 01:06, Joseph Tam wrote: > On Thu, 20 Dec 2018, Joseph Tam wrote: > > >> At the expense of sounding stupid, could you please expound on the > >> sequence? :) > > If you want the nitty details > > (Starting at bottom of page 18) > https://tools.ietf.org/html/rfc2831 > > Joseph Tam > Thank you very very much! I have now kind of understood what goes own. Initially, the server "has knowledge" of the credentials of the user. It had to be in the RFC and those we always leave for 'others' to read :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: Authentication Problem
On Thu, 20 Dec 2018 at 15:54, Aki Tuomi wrote: > > On 20 December 2018 at 14:33 Odhiambo Washington < odhia...@gmail.com> > wrote: > > > On Thu, 20 Dec 2018 at 15:23, Aki Tuomi < aki.tu...@open-xchange.com> > wrote: > > > > > On 20 December 2018 at 14:10 Odhiambo Washington < odhia...@gmail.com> > wrote: > > > > > You've made this more difficult to understand, even :-) > > So the answer is: > Set the following in 10-auth.conf > > 1. disable_plaintext_auth = no > 2. auth_mechanisms = plain > > And yes, the encrypted passwords are stored in MySQL. > > > > > You cannot use hashed passwords with digest-md5 mechanism. > > Aki > > > So, for the record, whenever passwords are hashed, digest-md5 should be > disabled/removed from auth_mechanisms. > > My question though - for purposes of understanding - how does dovecot take > the sent password from a client and match it against the hashed one stored > in the DB (in my case)? What happens in between the process? > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", grep ^[^#] :-) > > > Dovecot hashes the client sent password using the same salt and compares > the result. > --- > Aki Tuomi > At the expense of sounding stupid, could you please expound on the sequence? :) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: Authentication Problem
On Thu, 20 Dec 2018 at 15:23, Aki Tuomi wrote: > > On 20 December 2018 at 14:10 Odhiambo Washington < odhia...@gmail.com> > wrote: > > > You've made this more difficult to understand, even :-) > > So the answer is: > Set the following in 10-auth.conf > > 1. disable_plaintext_auth = no > 2. auth_mechanisms = plain > > And yes, the encrypted passwords are stored in MySQL. > > > You cannot use hashed passwords with digest-md5 mechanism. > > Aki > So, for the record, whenever passwords are hashed, digest-md5 should be disabled/removed from auth_mechanisms. My question though - for purposes of understanding - how does dovecot take the sent password from a client and match it against the hashed one stored in the DB (in my case)? What happens in between the process? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: Authentication Problem
You've made this more difficult to understand, even :-) So the answer is: Set the following in 10-auth.conf 1. disable_plaintext_auth = no 2. auth_mechanisms = plain And yes, the encrypted passwords are stored in MySQL. On Thu, 20 Dec 2018 at 13:36, Nikolai Lusan wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Greetings > On Thu, 2018-12-20 at 12:20 +0300, Odhiambo Washington wrote: > > I am using SHA512-CRYPT scheme for passwords. > > Yeah, there is a reason MD5 has been preferred to crypt for a very long > time now, and the SHA512 isn't really any better. > > > > In my dovecot-sql.conf.ext, I have: default_pass_scheme = CRYPT > > > > In 10-auth.conf, I have: > > auth_mechanisms = plain login digest-md5 > ^^ > > M$ Outlook is refusing to authenticate, with error: Requested DIGEST-MD5 > > scheme, but we have only CRYPT > > What an I missing?? > > > You are not advertising 3 possible auth methods, I am assuming that plain > will use the SQL extension. Unless you are going to setup a digest-md5 > method I would remove it from the advertised methods as most clients will > default to a digest method before selecting plain. Unless you control all > the clients and can configure them to only use the plain method of auth (I > would also be ensuring that you have TLS enforced in some way for this) > then removal of the digest method is probably the best fix. > > If the plain and/or login methods are failing check your sql config > includes the passdb and userdb sections. > > > - -- > Nikolai Lusan > -BEGIN PGP SIGNATURE- > > iQIzBAEBCgAdFiEEVfd4GW6z4nsBxdLo4ZaDRV2VL6QFAlwbcFwACgkQ4ZaDRV2V > L6T7IxAAjTQQfVngYU92oNfORwIeL6e9YZtvlLfo7V6d2PSgnzJ2Tdzyo2YA4AGy > eApc9SoJra8IVzanv+s6yl0BJ/EXez/ugdZ5DEUzYTf7b1AVMnUYOKkCi4HeOzzx > zttLF/Hd5ovwDRB1StNa5c1dsrN5lfwZy/cFwK+zOWwEZDBpYq3/y+IjsbWhCcW1 > DVbrSshOUaFqZwRE7MFPHiwsyNxhiG8cciglgUKf5HdRaiwx5E1Xy9gASxaqrdqg > GZpGbI7C8sAr92OvTvZlwThSOM6+aSgGIOATRS9S1Lh9x9H14ya1LtOE9XELSQPl > gDI/HJKBym7D8BsnEPSZ+THRwWGQ6QyACZUN8q5OZMEyzS2AGECnSTYMgv4LjqBZ > VbAaPZBAkhsuzVoWsd4xKiN9Qv3wQykDsSq6yahqiDzTXbsCA8HPMEQvw3hISttq > WHdibiBP8cm2/8cz+8PM1+3Q08JMVRqmDLEIQ61gmg8UWhpCPbE3royBkHaj6wOR > GeK4mG3cwYQu0JsoKDsFr7EvABErVRzrvkiMgnz/ivORkJVVtmxyYmG4t5VIT8FD > Hq6A/c1VJ/GYLNHNWRFMRfiXIJB7fM6K0NWK1EN34QoHNbwb5qSL+c6t/BZ5BpzK > c9zkU31FTqtSabUHzNPje6hzHMi5eZLhcH/MCZhD3Xv5+Gwxdug= > =LQQ1 > -END PGP SIGNATURE- > > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Authentication Problem
I am using SHA512-CRYPT scheme for passwords. In my dovecot-sql.conf.ext, I have: default_pass_scheme = CRYPT In 10-auth.conf, I have: auth_mechanisms = plain login digest-md5 M$ Outlook is refusing to authenticate, with error: Requested DIGEST-MD5 scheme, but we have only CRYPT What an I missing?? I hate it that this has taken me round in circles :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
Re: v2.3.4 released
On Sat, 24 Nov 2018 at 13:29, Timo Sirainen wrote:
> On 24 Nov 2018, at 8.33, Odhiambo Washington wrote:
>
>
>
> I installed 2.3.4 and just used it with the config files for 2.3.3 without
> changing anything in the configuration.
> I then realized that the LDA was throwing errors.
>
> 2018-11-24 00:02:51 1gQIaw-000AZS-Bc crownkenya.com/john.doe/Maildir>: dovecot_virtual_delivery transport
> output: lda(john@our.domain.name)Error:
> net_connect_unix(/var/run/dovecot//stats-writer) failed: Permission denied
>
> I checked on the presence of the sockets in /var/run/dovecot:
>
> srw--- 1 root wheel0 Nov 24 09:07 stats-reader
> srw-rw 1 root dovecot 0 Nov 24 09:07 stats-writer
>
>
> What user/group does dovecot_virtual_delivery run as?
>
It runs as the MTA user - mailnull.
> Change the stats-writer socket's owner to be that user. For example:
>
> service stats {
> unix_listener stats-writer {
> user = vmail
> }
> }
>
>
That makes sense.
> Or alternatively change dovecot_virtual_delivery to use dovecot group.
>
That would not be possible because it will not have permissions to write
the mail files.
> I have tried to find any mention of stats-{writer|reader} in the example
> configs shipped with 2.3.4 and found nothing. I have backed-off 2.3.4 for
> now till I can figure out how to assign proper permissions to these sockets
> - or just to figure out why by default, permission is being denied.
>
>
> Looks like this is happening now because in earlier versions the
> dovecot-lda process wasn't sending any statistics.
>
>
BTW, was it an oversight that this config snippet is not documented with
the example-config files? Or on the Wiki? Or my eyes are failing me? :-)
Thank you very much.
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft."
Re: v2.3.4 released
On Sat, 24 Nov 2018 at 12:04, Aki Tuomi wrote: > > On 24 November 2018 at 10:55 Odhiambo Washington < odhia...@gmail.com> > wrote: > > > On Sat, 24 Nov 2018 at 10:56, Aki Tuomi < aki.tu...@open-xchange.com> > wrote: > > > > > On 23 November 2018 at 17:46 Brad Smith < b...@comstyle.com> wrote: > > > > > On 11/23/2018 9:39 AM, Odhiambo Washington wrote: > > > > > On Fri, 23 Nov 2018 at 17:30, The Doctor < doc...@doctor.nl2k.ab.ca > > wrote: > > On Fri, Nov 23, 2018 at 04:02:27PM +0300, Odhiambo Washington > > wrote: > > > On Fri, 23 Nov 2018 at 15:29, Timo Sirainen < t...@iki.fi > > wrote: > > > > > https://dovecot.org/releases/2.3/dovecot-2.3.4.tar.gz > > > https://dovecot.org/releases/2.3/dovecot-2.3.4.tar.gz.sig > > > Binary packages in https://repo.dovecot.org/ > > > > > > * The default postmaster_address is now "postmaster@ domain or > > > server hostname>". If username contains the @domain part, > that's > > > used. If not, then the server's hostname is used. > > > * "doveadm stats dump" now returns two decimals for the "avg" > field. > > > > > > + Added push notification driver that uses a Lua script > > > + Added new SQL, DNS and connection events. > > > See https://wiki2.dovecot.org/Events > > > + Added "doveadm mailbox cache purge" command. > > > + Added events API support for Lua scripts > > > + doveadm force-resync -f parameter performs "index fsck" > while opening > > > the index. This may be useful to fix some types of broken > index files. > > > This may become the default behavior in a later version. > > > - director: Kicking a user crashes if login process is very > > slow > > > > - pop3_no_flag_updates=no: Don't expunge DELEted and RETRed > messages > > > unless QUIT is sent. > > > - auth: Fix crypt() segfault with glibc-2.28+ > > > - imap: Running UID FILTER script with errors assert-crashes > > > - dsync, pop3-migration: POP3 UIDLs weren't added to > > > dovecot.index.cache while mails were saved. > > > - dict clients may have been using 100% CPU while waiting for > dict > > > server to finish commands. > > > - doveadm user: Fixed user listing via HTTP API > > > - All levels of Cassandra log messages were logged as Dovecot > errors. > > > - http/smtp client may have crashed after SSL handshake > > > - Lua auth converted strings that looked like numbers into > numbers. > > > > > > > > > > FreeBSD 9.3 (i386): > > > > > > Making all in lib-master > > gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib > > -I../../src/lib-dns > > > -I../../src/lib-test -I../../src/lib-settings > > -I../../src/lib-ssl-iostream > > -DPKG_RUNDIR=\""/opt/dovecot2.3/var/run/dovecot"\" > > -DPKG_STATEDIR=\""/opt/dovecot2.3/var/lib/dovecot"\" > > -DSYSCONFDIR=\""/opt/dovecot2.3/etc/dovecot"\" > > -DBINDIR=\""/opt/dovecot2.3/bin"\" -std=gnu99 -g -O2 > -fstack-protector > > -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wall -W > > -Wmissing-prototypes > > > -Wmissing-declarations -Wpointer-arith -Wchar-subscripts > > -Wformat=2 > > > -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 > > -I/usr/local/include -MT test-event-stats.o -MD -MP -MF > > .deps/test-event-stats.Tpo -c -o test-event-stats.o > test-event-stats.c > > test-event-stats.c: In function 'kill_stats_child': > > test-event-stats.c:101: warning: implicit declaration of > function 'kill' > > test-event-stats.c:101: error: 'SIGKILL' undeclared (first use > in this > > function) > > test-event-stats.c:101: error: (Each undeclared identifier is > reported only > > once > > test-event-stats.c:101: error: for each function it appears in.) > > test-event-stats.c: In function 'test_no_merging2': > > test-event-stats.c:361: warning: format '%lu' expects type 'long > unsigned > > int', but argument 2 has type 'uint64_t' > > test-event-stats.c: In function 'test_no_merging3': > > test-event-stats.c:387: warning: format '%lu' expects type 'long > unsigned > > int', but argument 2 has type 'uint64_t' > > test-event-stats.c:387: warning: format '%lu' expects type 'long > unsigned > > int', but argument 4 has type 'uint64_t' > > test-event-stats.c:387: warning: format '%lu' expects type 'long > unsigned > > int', but argument 6 has type 'u
Re: v2.3.4 released
On Sat, 24 Nov 2018 at 10:56, Aki Tuomi wrote: > > > On 23 November 2018 at 17:46 Brad Smith wrote: > > > > > > On 11/23/2018 9:39 AM, Odhiambo Washington wrote: > > > > > > > > > > > On Fri, 23 Nov 2018 at 17:30, The Doctor > > <mailto:doc...@doctor.nl2k.ab.ca>> wrote: > > > > > > On Fri, Nov 23, 2018 at 04:02:27PM +0300, Odhiambo Washington > wrote: > > > > On Fri, 23 Nov 2018 at 15:29, Timo Sirainen > > <mailto:t...@iki.fi>> wrote: > > > > > > > > > https://dovecot.org/releases/2.3/dovecot-2.3.4.tar.gz > > > > > https://dovecot.org/releases/2.3/dovecot-2.3.4.tar.gz.sig > > > > > Binary packages in https://repo.dovecot.org/ > > > > > > > > > > * The default postmaster_address is now "postmaster@ > > domain or > > > > >server hostname>". If username contains the @domain part, > > > that's > > > > >used. If not, then the server's hostname is used. > > > > > * "doveadm stats dump" now returns two decimals for the "avg" > > > field. > > > > > > > > > > + Added push notification driver that uses a Lua script > > > > > + Added new SQL, DNS and connection events. > > > > >See https://wiki2.dovecot.org/Events > > > > > + Added "doveadm mailbox cache purge" command. > > > > > + Added events API support for Lua scripts > > > > > + doveadm force-resync -f parameter performs "index fsck" > > > while opening > > > > >the index. This may be useful to fix some types of broken > > > index files. > > > > >This may become the default behavior in a later version. > > > > > - director: Kicking a user crashes if login process is very > slow > > > > > - pop3_no_flag_updates=no: Don't expunge DELEted and RETRed > > > messages > > > > >unless QUIT is sent. > > > > > - auth: Fix crypt() segfault with glibc-2.28+ > > > > > - imap: Running UID FILTER script with errors assert-crashes > > > > > - dsync, pop3-migration: POP3 UIDLs weren't added to > > > > >dovecot.index.cache while mails were saved. > > > > > - dict clients may have been using 100% CPU while waiting for > > > dict > > > > >server to finish commands. > > > > > - doveadm user: Fixed user listing via HTTP API > > > > > - All levels of Cassandra log messages were logged as Dovecot > > > errors. > > > > > - http/smtp client may have crashed after SSL handshake > > > > > - Lua auth converted strings that looked like numbers into > > > numbers. > > > > > > > > > > > > > > > > > > FreeBSD 9.3 (i386): > > > > > > > > > > > > Making all in lib-master > > > > gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib > -I../../src/lib-dns > > > > -I../../src/lib-test -I../../src/lib-settings > > > > -I../../src/lib-ssl-iostream > > > > -DPKG_RUNDIR=\""/opt/dovecot2.3/var/run/dovecot"\" > > > > -DPKG_STATEDIR=\""/opt/dovecot2.3/var/lib/dovecot"\" > > > > -DSYSCONFDIR=\""/opt/dovecot2.3/etc/dovecot"\" > > > > -DBINDIR=\""/opt/dovecot2.3/bin"\"-std=gnu99 -g -O2 > > > -fstack-protector > > > > -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wall -W > -Wmissing-prototypes > > > > -Wmissing-declarations -Wpointer-arith -Wchar-subscripts > -Wformat=2 > > > > -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 > > > > -I/usr/local/include -MT test-event-stats.o -MD -MP -MF > > > > .deps/test-event-stats.Tpo -c -o test-event-stats.o > > > test-event-stats.c > > > > test-event-stats.c: In function 'kill_stats_child': > > > > test-event-stats.c:101: warning: implicit declaration of > > > function 'kill' > > > > test-event-stats.c:101: error: 'SIGKILL' undeclared (first use > > > in this > > > > function) > > > > test-event-stats.c:101:
Re: v2.3.4 released
I installed 2.3.4 and just used it with the config files for 2.3.3 without
changing anything in the configuration.
I then realized that the LDA was throwing errors.
2018-11-24 00:02:51 1gQIaw-000AZS-Bc : dovecot_virtual_delivery transport
output: lda(john@our.domain.name)Error:
net_connect_unix(/var/run/dovecot//stats-writer) failed: Permission denied
I checked on the presence of the sockets in /var/run/dovecot:
srw--- 1 root wheel0 Nov 24 09:07 stats-reader
srw-rw 1 root dovecot 0 Nov 24 09:07 stats-writer
I have tried to find any mention of stats-{writer|reader} in the example
configs shipped with 2.3.4 and found nothing. I have backed-off 2.3.4 for
now till I can figure out how to assign proper permissions to these sockets
- or just to figure out why by default, permission is being denied.
On Fri, 23 Nov 2018 at 16:53, Aki Tuomi wrote:
>
> On 23.11.2018 15.51, Brad Smith wrote:
> > On 11/23/2018 8:23 AM, Aki Tuomi wrote:
> >
> >> On 23.11.2018 15.20, Brad Smith wrote:
> >>> On Fri, Nov 23, 2018 at 02:29:22PM +0200, Timo Sirainen wrote:
> >>>> https://dovecot.org/releases/2.3/dovecot-2.3.4.tar.gz
> >>>> https://dovecot.org/releases/2.3/dovecot-2.3.4.tar.gz.sig
> >>>> Binary packages in https://repo.dovecot.org/
> >>>>
> >>>> * The default postmaster_address is now "postmaster@ >>>> server hostname>". If username contains the @domain part, that's
> >>>> used. If not, then the server's hostname is used.
> >>>> * "doveadm stats dump" now returns two decimals for the "avg" field.
> >>>>
> >>>> + Added push notification driver that uses a Lua script
> >>>> + Added new SQL, DNS and connection events.
> >>>> See https://wiki2.dovecot.org/Events
> >>>> + Added "doveadm mailbox cache purge" command.
> >>>> + Added events API support for Lua scripts
> >>>> + doveadm force-resync -f parameter performs "index fsck" while
> >>>> opening
> >>>> the index. This may be useful to fix some types of broken index
> >>>> files.
> >>>> This may become the default behavior in a later version.
> >>>> - director: Kicking a user crashes if login process is very slow
> >>>> - pop3_no_flag_updates=no: Don't expunge DELEted and RETRed messages
> >>>> unless QUIT is sent.
> >>>> - auth: Fix crypt() segfault with glibc-2.28+
> >>>> - imap: Running UID FILTER script with errors assert-crashes
> >>>> - dsync, pop3-migration: POP3 UIDLs weren't added to
> >>>> dovecot.index.cache while mails were saved.
> >>>> - dict clients may have been using 100% CPU while waiting for dict
> >>>> server to finish commands.
> >>>> - doveadm user: Fixed user listing via HTTP API
> >>>> - All levels of Cassandra log messages were logged as Dovecot
> >>>> errors.
> >>>> - http/smtp client may have crashed after SSL handshake
> >>>> - Lua auth converted strings that looked like numbers into numbers.
> >>> The release does not build. Here is a patch to fix the build.
> >>>
> >>>
> >>>
> >>> test-event-stats.c:101:8: warning: implicit declaration of function
> >>> 'kill' is invalid in C99 [-Wimplicit-function-declaration]
> >>> (void)kill(stats_pid, SIGKILL);
> >>>^
> >>> test-event-stats.c:101:24: error: use of undeclared identifier
> >>> 'SIGKILL'
> >>> (void)kill(stats_pid, SIGKILL);
> >>>^
> >> On *BSD I assume? It would be useful to mention. But we'll think what we
> >> will do with this.
> >
> > Yes, OpenBSD.
> >
> There is a fix pending now for master, and will be released on next
> release.
>
> Aki
>
>
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft."
Re: v2.3.4 released
On Fri, 23 Nov 2018 at 17:31, The Doctor wrote: > On Fri, Nov 23, 2018 at 04:06:53PM +0300, Odhiambo Washington wrote: > > On Fri, 23 Nov 2018 at 15:29, Timo Sirainen wrote: > > > > > https://dovecot.org/releases/2.3/dovecot-2.3.4.tar.gz > > > https://dovecot.org/releases/2.3/dovecot-2.3.4.tar.gz.sig > > > Binary packages in https://repo.dovecot.org/ > > > > > > * The default postmaster_address is now "postmaster@ > >server hostname>". If username contains the @domain part, that's > > >used. If not, then the server's hostname is used. > > > * "doveadm stats dump" now returns two decimals for the "avg" field. > > > > > > + Added push notification driver that uses a Lua script > > > + Added new SQL, DNS and connection events. > > >See https://wiki2.dovecot.org/Events > > > + Added "doveadm mailbox cache purge" command. > > > + Added events API support for Lua scripts > > > + doveadm force-resync -f parameter performs "index fsck" while > opening > > >the index. This may be useful to fix some types of broken index > files. > > >This may become the default behavior in a later version. > > > - director: Kicking a user crashes if login process is very slow > > > - pop3_no_flag_updates=no: Don't expunge DELEted and RETRed messages > > >unless QUIT is sent. > > > - auth: Fix crypt() segfault with glibc-2.28+ > > > - imap: Running UID FILTER script with errors assert-crashes > > > - dsync, pop3-migration: POP3 UIDLs weren't added to > > >dovecot.index.cache while mails were saved. > > > - dict clients may have been using 100% CPU while waiting for dict > > >server to finish commands. > > > - doveadm user: Fixed user listing via HTTP API > > > - All levels of Cassandra log messages were logged as Dovecot errors. > > > - http/smtp client may have crashed after SSL handshake > > > - Lua auth converted strings that looked like numbers into numbers. > > > > > > > > FreeBSD 11.2 (amd64): > > > > gmake[2]: Entering directory > > '/usr/home/wash/Tools/Dovecot/2.3/dovecot-2.3.4/src/lib-master' > > gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-dns > > -I../../src/lib-test -I../../src/lib-settings > -I../../src/lib-ssl-iostream > > -DPKG_RUNDIR=\""/opt/dovecot2.3/var/run/dovecot"\" > > -DPKG_STATEDIR=\""/opt/dovecot2.3/var/lib/dovecot"\" > > -DSYSCONFDIR=\""/opt/dovecot2.3/etc/dovecot"\" > > -DBINDIR=\""/opt/dovecot2.3/bin"\" -std=gnu99 -g -O2 > > -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wall -W > > -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith > > -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime > > -Wstrict-aliasing=2 -I/usr/local/include -MT test-event-stats.o -MD -MP > > -MF .deps/test-event-stats.Tpo -c -o test-event-stats.o > test-event-stats.c > > test-event-stats.c: In function 'kill_stats_child': > > test-event-stats.c:101:2: warning: implicit declaration of function > 'kill' > > [-Wimplicit-function-declaration] > > (void)kill(stats_pid, SIGKILL); > > ^ > > test-event-stats.c:101:24: error: 'SIGKILL' undeclared (first use in this > > function) > > (void)kill(stats_pid, SIGKILL); > > ^ > > test-event-stats.c:101:24: note: each undeclared identifier is reported > > only once for each function it appears in > > gmake[2]: *** [Makefile:656: test-event-stats.o] Error 1 > > gmake[2]: Leaving directory > > '/usr/home/wash/Tools/Dovecot/2.3/dovecot-2.3.4/src/lib-master' > > gmake[1]: *** [Makefile:565: install-recursive] Error 1 > > gmake[1]: Leaving directory > > '/usr/home/wash/Tools/Dovecot/2.3/dovecot-2.3.4/src' > > gmake: *** [Makefile:683: install-recursive] Error 1 > > > > Looks like our porters will have their hands full. > > dovecot-2.3.3 has been in the FreeBSD ports already so I don't think it will be much of a problem. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft."
