dovecot connections to mysql
Hello, I'm running a virtual mail hosting system with MySQL as a backend for dovecot to do it's authentication against. I am getting intermediant failures when users attempt mail-related tasks such as checking their inbox or setting up an alias. The error is to many connections. Any ideas? Thanks. Dave.
Re: Coredump: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))
Op 3/5/2018 om 3:14 PM schreef Ralf Hildebrandt:
> Got a coredump:
>
> Mar 5 15:09:42 mail-cbf dovecot:
> lmtp(backup@backup.invalid)<15425><2B+kCaZPnVpBPAAAplP5LA>: Fatal: master:
> service(lmtp): child 15425 killed with signal 6 (core dumped)
Hmm, yes, I think this an unnecessary RFC5322 -> RFC5321 address
translation. Will look at making a fix tomorrow.
Regards,
Stephan.
>
>
> #0 0x7fea19977428 in __GI_raise (sig=sig@entry=6) at
> ../sysdeps/unix/sysv/linux/raise.c:54
> resultvar = 0
> pid = 15425
> selftid = 15425
> #1 0x7fea1997902a in __GI_abort () at abort.c:89
> save_stage = 2
> act = {
> __sigaction_handler = {
> sa_handler = 0x56239d9a3890,
> sa_sigaction = 0x56239d9a3890
> },
> sa_mask = {
> __val = {1, 94710917811261, 140643428345904, 94710917811577, 0,
> 140735221053024, 94710938452648, 513, 7700885895375379200, 0,
> 140643433202867, 94710938452648,
> 140735221053120, 94710938452304, 140643433203225,
> 94710938452648}
> },
> sa_flags = 433895898,
> sa_restorer = 0x5
> }
> sigs = {
> __val = {32, 0 }
> }
> #2 0x7fea19dd2aaf in default_fatal_finish (type=LOG_TYPE_PANIC,
> status=status@entry=0) at failures.c:228
> backtrace = 0x56239bd7c2e0
> "/usr/lib/dovecot/libdovecot.so.0(+0xc6aca) [0x7fea19dd2aca] ->
> /usr/lib/dovecot/libdovecot.so.0(+0xc6bad) [0x7fea19dd2bad] ->
> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fea19d44721] -> /usr/lib/d"...
> recursed = 0
> #3 0x7fea19dd2bad in i_internal_fatal_handler (ctx=0x7fff78dbb710,
> format=, args=) at failures.c:718
> status = 0
> #4 0x7fea19d44721 in i_panic (format=format@entry=0x7fea19e0ec98 "file
> %s: line %d (%s): assertion failed: (%s)") at failures.c:306
> ctx = {
> type = LOG_TYPE_PANIC,
> exit_status = 0,
> timestamp = 0x0,
> timestamp_usecs = 0,
> log_prefix = 0x0
> }
> args = pointer.)>
> #5 0x7fea19d4831d in smtp_address_write (out=0x56239bd7c150,
> address=0x56239bd7c108) at smtp-address.c:530
> quoted =
> p = 0x56239bd7c11b "üller"
> pend = 0x56239bd7c121 ""
> pblock = 0x56239bd7c11a "müller"
> __func__ = "smtp_address_write"
> #6 0x7fea19d48411 in smtp_address_encode (address=0x56239bd7c108) at
> smtp-address.c:567
> str = 0x56239bd7c150
> #7 0x7fea1a3cf774 in mail_deliver_log_update_cache
> (cache=cache@entry=0x56239bddf1c8, pool=0x56239bddf180, mail=0x56239be185c8)
> at mail-deliver.c:111
> message_id = 0x56239d943a4c
> ""
> subject = 0x56239d943b69 "JOMEC Seminar | Von Kennzahlencockpits und
> Lean Hospital Strategien"
> from_envelope = 0x0
> from =
> #8 0x7fea1a3cfabf in mail_deliver_save_finish (ctx=0x56239be14ca0) at
> mail-deliver.c:533
> box =
> mbox = 0x56239be0efc0
> muser = 0x56239bdcb7c0
> dt = 0x56239bddf1c0
> #9 0x7fea1a0c758c in mailbox_save_finish
> (_ctx=_ctx@entry=0x7fff78dbb948) at mail-storage.c:2461
> _data_stack_cur_id = 4
> ctx = 0x56239be14ca0
> t = 0x56239be10ce0
> keywords = 0x0
> pvt_flags = 0
> copying_via_save = true
> ret =
> #10 0x7fea1a0b9eb4 in mail_storage_copy (ctx=0x0,
> ctx@entry=0x56239be14ca0, mail=mail@entry=0x56239bdfdb28) at mail-copy.c:112
> __func__ = "mail_storage_copy"
> #11 0x7fea1a0e03f6 in mdbox_copy (_ctx=0x56239be14ca0,
> mail=0x56239bdfdb28) at mdbox-save.c:461
> ctx = 0x56239be14ca0
> save_mail = 0x56239bdfdb28
> src_mbox =
> rec = {
> map_uid = 2615013952,
> save_date = 22051
> }
> guid_data = 0x7fff78dbb9b0
> wanted_guid = "@\362ݛ#V\000\000\240L\341\233#V\000"
> #12 0x7fea1a3cf999 in mail_deliver_copy (ctx=0x56239be14ca0,
> mail=0x56239bdfdb28) at mail-deliver.c:547
> box =
> mbox = 0x56239be0efc0
> muser = 0x56239bdcb7c0
> dt = 0x56239bddf1c0
> #13 0x7fea1a0c7956 in mailbox_copy_int (_ctx=_ctx@entry=0x7fff78dbba98,
> mail=0x56239bdfdb28) at mail-storage.c:2532
> _data_stack_cur_id = 3
> ctx = 0x56239be14ca0
> t = 0x56239be10ce0
> keywords = 0x0
> pvt_flags = 0
> backend_mail = 0x56239bdfdb28
> ret =
> __func__ = "mailbox_copy_int"
> #14 0x7fea1a0c7c38 in mailbox_save_using_mail
> (_ctx=_ctx@entry=0x7fff78dbba98, mail=) at mail-storage.c:2584
> ctx =
> __func__ = "mailbox_save_using_mail"
> #15 0x7fea1a3d02ac in mail_deliver_save (ctx=ctx@entry=0x7fff78dbbc60,
> mailbox=, flags=flags@entry=0, keywords=keywords@entry=0x0,
> storage_r=storage_r@entry=0x7fff78dbbc50) at mail-deliver.c:363
> open_ctx = {
>
Re: LMTP delivery segfaults when user is over quota.
Op 3/4/2018 om 4:57 PM schreef Reio Remma:
> On 04.03.2018 16:25, Reio Remma wrote:
>> Hello!
>>
>> I'm having crashes with LMTP delivery when user is over quota on the
>> latest CentOS 7.4 with the latest Dovecot 2.3.0.1 from Dovecot repo.
>>
>> I see the issue has been fixed on January 17, but it doesn't seem to
>> have made it into 2.3.0.1 (I compared with the source from
>> https://dovecot.org/releases/2.3/dovecot-2.3.0.1.tar.gz).
>>
>> https://github.com/dovecot/core/commit/2bf919786518d138cc07d9cc21e14ad5e07e5e56#diff-7964e00c46515956a959fa47fc86d605
>>
>> I also noticed a similar construct being used on line 465
>> (rcpt->rcpt.rcpt->path) that was causing the segfault on the above
>> commit on line 136.
>>
>> struct smtp_address *rcpt_to = rcpt->rcpt.rcpt->path;
>>
>> Should that also use rcpt->rcpt.path; ?
>>
>> Thanks from the other side of the gulf!
>> Reio
>>
>
> I now managed to coax a core dump out of CentOS - here it is.
That is this one:
https://github.com/dovecot/core/commit/c23717da4af9d3275cb45cbc67faaa8daa353ec1#diff-7964e00c46515956a959fa47fc86d605
>
> Thanks!
> Reio
>
> Reading symbols from /usr/libexec/dovecot/lmtp...Reading symbols from
> /usr/lib/debug/usr/libexec/dovecot/lmtp.debug...done.
> done.
> [New LWP 18733]
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> Core was generated by `dovecot/lmtp -L'.
> Program terminated with signal 11, Segmentation fault.
> #0 smtp_server_reply (_cmd=0x0, status=552, enh_code=0x562468e05050
> "5.2.2", fmt=0x562468e05042 "<%s> %s") at smtp-server-reply.c:210
> 210 i_assert(cmd->replies_expected <= 1);
> (gdb) bt full
> #0 smtp_server_reply (_cmd=0x0, status=552, enh_code=0x562468e05050
> "5.2.2", fmt=0x562468e05042 "<%s> %s") at smtp-server-reply.c:210
> cmd = address 0x20)>
> args = {{gp_offset = 1790721792, fp_offset = 22052,
> overflow_arg_area = 0x56246abc3f14, reg_save_area = 0x56246ab70b58}}
> __func__ = "smtp_server_reply"
> #1 0x562468e034d7 in lmtp_local_deliver (session=0x56246abe2cd8,
> src_mail=0x56246abde0a8, rcpt=0x56246abada50, trans=0x56246abc3df8,
> cmd=0x56246ab81868, local=0x56246ab7cba0) at lmtp-local.c:621
> set_parser =
> line =
> str = 0x56246ab70068
> proxy_data = {proto = SMTP_PROXY_PROTOCOL_LMTP, source_ip =
> {family = 0, u = {ip6 = {__in6_u = {__u6_addr8 = '\000' times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0,
> 0, 0}}}, ip4 = {s_addr = 0}}},
> source_port = 0, helo = 0x56246abc3c80 "bwo.mrstuudio.ee",
> login = 0x0, ttl_plus_1 = 0, timeout_secs = 0, extra_fields = 0x0,
> extra_fields_count = 0}
> delivery_time_started = {tv_sec = 1520176597, tv_usec = 704043}
> sets =
> rcpt_user = 0x56246abe30e8
> mail_set =
> username =
> rcpt_idx = 0
> smtp_set = 0x56246abcf448
> lda_set = 0x56246abcf4b8
> ns =
> rcpt_to = 0x56246abc3f00
> trcpt = 0x56246abc3ec0
> storage = 0x56246abe8838
> mail_error = MAIL_ERROR_NOQUOTA
> ret =
> client = 0x56246abaf538
> service_user =
> dctx = {pool = 0x56246abe2cb0, set = 0x56246abcf4b8, smtp_set
> = 0x56246abcf448, session = 0x56246abe2cd8, session_time_msecs = 24,
> delivery_time_started = {tv_sec = 1520176597, tv_usec = 704043},
> dup_db = 0x0,
> session_id = 0x56246abadab0 "PAN2KNUNnFotSQAAinc3nQ",
> src_mail = 0x56246abde0a8, mail_from = 0x56246abc3e98, mail_params =
> {auth = 0x0, body = {type = SMTP_PARAM_MAIL_BODY_TYPE_UNSPECIFIED, ext
> = 0x0}, envid = 0x0,
> ret = SMTP_PARAM_MAIL_RET_UNSPECIFIED, size = 0,
> extra_params = {arr = {buffer = 0x0, element_size = 0}, v = 0x0,
> v_modifiable = 0x0}}, rcpt_to = 0x56246abc3f00, rcpt_params = {orcpt =
> {addr_type = 0x0,
> addr = 0x56246abc3f00, addr_raw = 0x0}, notify =
> SMTP_PARAM_RCPT_NOTIFY_UNSPECIFIED, extra_params = {arr = {buffer =
> 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, rcpt_user =
> 0x56246abe30e8,
> rcpt_default_mailbox = 0x562468e05064 "INBOX", dest_mail =
> 0x0, cache = 0x56246abe2df8, tempfail_error = 0x0, tried_default_save
> = true, saved_mail = false, save_dest_mail = false, mailbox_full =
> false, dsn = false}
> input =
> var_table =
> error = 0x56246abfb3a0 "Kasutaja postkast on täis."
> #2 lmtp_local_deliver_to_rcpts (session=0x56246abe2cd8,
> trans=0x56246abc3df8, cmd=0x56246ab81868, local=0x56246ab7cba0) at
> lmtp-local.c:657
> rcpt = 0x56246abada50
> first_uid = 4294967295
> src_mail = 0x56246abde0a8
> count = 1
> i = 0
> rcpts =
> #3 lmtp_local_data (client=client@entry=0x56246abaf538,
> cmd=cmd@entry=0x56246ab81868, trans=trans@entry=0x56246abc3df8,
> input=) at lmtp-local.c:734
> local = 0x56246ab7cba0
> session = 0x56246abe2cd8
> old_uid = 0
Re: LMTP delivery segfaults when user is over quota.
Op 3/4/2018 om 3:25 PM schreef Reio Remma: > Hello! > > I'm having crashes with LMTP delivery when user is over quota on the > latest CentOS 7.4 with the latest Dovecot 2.3.0.1 from Dovecot repo. > > I see the issue has been fixed on January 17, but it doesn't seem to > have made it into 2.3.0.1 (I compared with the source from > https://dovecot.org/releases/2.3/dovecot-2.3.0.1.tar.gz). That release is just about the CVEs afaik. The remaining fixes will be in v2.3.1. > https://github.com/dovecot/core/commit/2bf919786518d138cc07d9cc21e14ad5e07e5e56#diff-7964e00c46515956a959fa47fc86d605 > > I also noticed a similar construct being used on line 465 > (rcpt->rcpt.rcpt->path) that was causing the segfault on the above > commit on line 136. > > struct smtp_address *rcpt_to = rcpt->rcpt.rcpt->path; > > Should that also use rcpt->rcpt.path; ? It would be a bit cleaner maybe, but at the DATA stage it will not segfault anymore, since the recipient path is definitively put in the transaction. Regards, Stephan.
Re: pigeonhole 0.4.22 with sieve_before script crashes
Op 3/3/2018 om 6:29 PM schreef Stephan Bosch: > Op 3/3/2018 om 6:17 PM schreef Jan: > We're looking into it. Right, this is not reproducible in the test suite, but I can reproduce it when I replicate your setup. >>> I created a special test suite that reproduces the problem reliably. >>> This occurs when Sieve editheader, Sieve redirect and LMTP are combined. >>> >>> Now to fix it... >> Hello Stephan! >> >> Thank you for your quick reply and the informations. >> If a fix is available, I will test it. > There is a fix. Pending internal review, I will submit it here. The actual fix (for v2.2/v0.4): https://github.com/dovecot/pigeonhole/commit/14ec6fe861403aa09a3b5790d113247fc1e1f94d Some related changes before and after this change (last commit is unrelated), mainly relating to creating a regression test for this particular problem. https://github.com/dovecot/pigeonhole/commits/master-0.4 Regards, Stephan.
Re: Plugin charset_alias
On 2018-03-02 09:57, Teemu Huovila wrote: On 02.03.2018 09:38, MRob wrote: On 2018-03-01 22:59, John Woods wrote: Hey Everyone, We are getting a compile error for Dovecot 2.2.34 on Solaris 11.3 x86, using Solaris Studio 12.6 compiler, and it doesn't occur with Dovecot 2.2.33. Making all in charset-alias Can someone easily explain what the usage of this plugin is? Maybe example when it is helpful? There is a short explanation at https://wiki2.dovecot.org/Plugins/CharsetAlias It is intended for mapping charactersets to work around some e.g. Windows specific letters being lost when Dovecot converts mail to UTF8 using iconv. I read that page so I wanted more real life example so I can learn should I install this plugin or is it for special use scenario cuz I'm not charset expert sorry. Your explain adds little bit more info but not enough to know do I need it or not. BTW not your fault-- I didn't ask myquestion good enough If Dovecot has trouble to decode some windows charsets and the plugin fixes this problem then why is it a plugin and not built in as a fix?
Re: [ext] Re: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))
On 05/03/18 14:03, Ralf Hildebrandt wrote: > * A.L.E.C : >> On 03/02/2018 03:32 PM, Ralf Hildebrandt wrote: >>> The address causing the error is: >>> >>> From: =?utf-8?Q?Dorit_M=C3=BCller?= >>> >>> Note the "umlaut" in the email address... :) >> This is about SMTPUTF8 (RFC6531). Looks like your only option is to disable >> smtputf8_enable in Postfix config. > It IS already disabled. > Ralph if you compile and enable SMTPUTF8 in Postfix the mails should bounce without getting to dovecot. That may or may not be what you want, but at least they won't stick in the queue. John
Re: Coredump: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))
On 05/03/18 15:14, Ralf Hildebrandt wrote:
> Got a coredump:
>
> Mar 5 15:09:42 mail-cbf dovecot:
> lmtp(backup@backup.invalid)<15425><2B+kCaZPnVpBPAAAplP5LA>: Fatal: master:
> service(lmtp): child 15425 killed with signal 6 (core dumped)
>
>
> #0 0x7fea19977428 in __GI_raise (sig=sig@entry=6) at
> ../sysdeps/unix/sysv/linux/raise.c:54
> resultvar = 0
> pid = 15425
> selftid = 15425
> #1 0x7fea1997902a in __GI_abort () at abort.c:89
> save_stage = 2
> act = {
> __sigaction_handler = {
> sa_handler = 0x56239d9a3890,
> sa_sigaction = 0x56239d9a3890
> },
> sa_mask = {
> __val = {1, 94710917811261, 140643428345904, 94710917811577, 0,
> 140735221053024, 94710938452648, 513, 7700885895375379200, 0,
> 140643433202867, 94710938452648,
> 140735221053120, 94710938452304, 140643433203225,
> 94710938452648}
> },
> sa_flags = 433895898,
> sa_restorer = 0x5
> }
> sigs = {
> __val = {32, 0 }
> }
> #2 0x7fea19dd2aaf in default_fatal_finish (type=LOG_TYPE_PANIC,
> status=status@entry=0) at failures.c:228
> backtrace = 0x56239bd7c2e0
> "/usr/lib/dovecot/libdovecot.so.0(+0xc6aca) [0x7fea19dd2aca] ->
> /usr/lib/dovecot/libdovecot.so.0(+0xc6bad) [0x7fea19dd2bad] ->
> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fea19d44721] -> /usr/lib/d"...
> recursed = 0
> #3 0x7fea19dd2bad in i_internal_fatal_handler (ctx=0x7fff78dbb710,
> format=, args=) at failures.c:718
> status = 0
> #4 0x7fea19d44721 in i_panic (format=format@entry=0x7fea19e0ec98 "file
> %s: line %d (%s): assertion failed: (%s)") at failures.c:306
> ctx = {
> type = LOG_TYPE_PANIC,
> exit_status = 0,
> timestamp = 0x0,
> timestamp_usecs = 0,
> log_prefix = 0x0
> }
> args = pointer.)>
> #5 0x7fea19d4831d in smtp_address_write (out=0x56239bd7c150,
> address=0x56239bd7c108) at smtp-address.c:530
> quoted =
> p = 0x56239bd7c11b "üller"
> pend = 0x56239bd7c121 ""
> pblock = 0x56239bd7c11a "müller"
> __func__ = "smtp_address_write"
> #6 0x7fea19d48411 in smtp_address_encode (address=0x56239bd7c108) at
> smtp-address.c:567
> str = 0x56239bd7c150
> #7 0x7fea1a3cf774 in mail_deliver_log_update_cache
> (cache=cache@entry=0x56239bddf1c8, pool=0x56239bddf180, mail=0x56239be185c8)
> at mail-deliver.c:111
> message_id = 0x56239d943a4c
> ""
> subject = 0x56239d943b69 "JOMEC Seminar | Von Kennzahlencockpits und
> Lean Hospital Strategien"
> from_envelope = 0x0
> from =
> #8 0x7fea1a3cfabf in mail_deliver_save_finish (ctx=0x56239be14ca0) at
> mail-deliver.c:533
> box =
> mbox = 0x56239be0efc0
> muser = 0x56239bdcb7c0
> dt = 0x56239bddf1c0
> #9 0x7fea1a0c758c in mailbox_save_finish
> (_ctx=_ctx@entry=0x7fff78dbb948) at mail-storage.c:2461
> _data_stack_cur_id = 4
> ctx = 0x56239be14ca0
> t = 0x56239be10ce0
> keywords = 0x0
> pvt_flags = 0
> copying_via_save = true
> ret =
> #10 0x7fea1a0b9eb4 in mail_storage_copy (ctx=0x0,
> ctx@entry=0x56239be14ca0, mail=mail@entry=0x56239bdfdb28) at mail-copy.c:112
> __func__ = "mail_storage_copy"
> #11 0x7fea1a0e03f6 in mdbox_copy (_ctx=0x56239be14ca0,
> mail=0x56239bdfdb28) at mdbox-save.c:461
> ctx = 0x56239be14ca0
> save_mail = 0x56239bdfdb28
> src_mbox =
> rec = {
> map_uid = 2615013952,
> save_date = 22051
> }
> guid_data = 0x7fff78dbb9b0
> wanted_guid = "@\362ݛ#V\000\000\240L\341\233#V\000"
> #12 0x7fea1a3cf999 in mail_deliver_copy (ctx=0x56239be14ca0,
> mail=0x56239bdfdb28) at mail-deliver.c:547
> box =
> mbox = 0x56239be0efc0
> muser = 0x56239bdcb7c0
> dt = 0x56239bddf1c0
> #13 0x7fea1a0c7956 in mailbox_copy_int (_ctx=_ctx@entry=0x7fff78dbba98,
> mail=0x56239bdfdb28) at mail-storage.c:2532
> _data_stack_cur_id = 3
> ctx = 0x56239be14ca0
> t = 0x56239be10ce0
> keywords = 0x0
> pvt_flags = 0
> backend_mail = 0x56239bdfdb28
> ret =
> __func__ = "mailbox_copy_int"
> #14 0x7fea1a0c7c38 in mailbox_save_using_mail
> (_ctx=_ctx@entry=0x7fff78dbba98, mail=) at mail-storage.c:2584
> ctx =
> __func__ = "mailbox_save_using_mail"
> #15 0x7fea1a3d02ac in mail_deliver_save (ctx=ctx@entry=0x7fff78dbbc60,
> mailbox=, flags=flags@entry=0, keywords=keywords@entry=0x0,
> storage_r=storage_r@entry=0x7fff78dbbc50) at mail-deliver.c:363
> open_ctx = {
> user = 0x56239bdcacb8,
> lda_mailbox_autocreate = false,
> lda_mailbox_autosubscribe = false
> }
>
Fts solr and https
Hi, Dovecot 2.2.32-34 FreeBSD 10.4 Solr 7.2.1(Centos 6) When I try to use https to connect to solr, I get error when a self-signed certificate: Mar 3 05:15:47 server dovecot: indexer-worker(em...@domain.com): Received invalid SSL certificate: self signed certificate: /C=Country/ ST=State/L=Location/O=Organization/OU=Organizational Unit/CN=solr.domain.com Mar 3 05:15:47 server dovecot: indexer-worker(em...@domain.com): Received invalid SSL certificate: self signed certificate: /C=Country/ ST=State/L=Location/O=Organization/OU=Organizational Unit/CN=solr.domain.com Mar 3 05:15:47 server dovecot: indexer-worker(em...@domain.com): Error: fts_solr: Indexing failed: SSL handshaking with 1.1.1.1: 8983 failed: read(SSL 1.1.1.1:8983) failed: Received invalid SSL certificate: self signed certificate: /C=Country/ST=State/L=L ocation/O=Organization/OU=Organizational Unit/CN=solr.domain.com (2 attempts in 0.043 secs) Mar 3 05:15:47 server dovecot: indexer-worker(em...@domain.com): Received invalid SSL certificate: self signed certificate: /C=Country/ ST=State/L=Location/O=Organization/OU=Organizational Unit/CN=solr.domain.com Mar 3 05:15:47 server dovecot: indexer-worker(em...@domain.com): Received invalid SSL certificate: self signed certificate: /C=Country/ ST=State/L=Location/O=Organization/OU=Organizational Unit/CN=solr.domain.com Mar 3 05:15:47 server dovecot: indexer-worker(em...@domain.com): Error: fts_solr: Indexing failed: SSL handshaking with 1.1.1.1: 8983 failed: read(SSL 1.1.1.1:8983) failed: Received invalid SSL certificate: self signed certificate: /C=Country/ST=State/L=L ocation/O=Organization/OU=Organizational Unit/CN=solr.domain.com (2 attempts in 0.430 secs) Mar 3 05:15:47 server dovecot: indexer-worker(em...@domain.com): Error: Mailbox INBOX: Transaction commit failed: FTS transaction commi t failed: backend deinit (attempted to index 1 messages (UIDs 799975..799975)) or error when letsencrypt: Mar 3 01:26:31 server dovecot: indexer-worker(em...@domain.com): Received invalid SSL certificate: unable to get local issuer certifi cate: /C=US/O=Let\\\'s Encrypt/CN=Let\\\'s Encrypt Authority X3 Mar 3 01:26:31 server dovecot: indexer-worker(em...@domain.com): Received invalid SSL certificate: unable to get local issuer certifi cate: /C=US/O=Let\\\'s Encrypt/CN=Let\\\'s Encrypt Authority X3 Mar 3 01:26:31 server dovecot: indexer-worker(em...@domain.com): Error: fts_solr: Indexing failed: SSL handshaking with 1.1.1.1 3:8983 failed: read(SSL 1.1.1.1:8983) failed: Received invalid SSL certificate: unable to get local issuer certificate: /C=US/ O=Let\\\'s Encrypt/CN=Let\\\'s Encrypt Authority X3 (2 attempts in 0.085 secs) Mar 3 01:26:31 server dovecot: indexer-worker(em...@domain.com): Received invalid SSL certificate: unable to get local issuer certifi cate: /C=US/O=Let\\\'s Encrypt/CN=Let\\\'s Encrypt Authority X3 Mar 3 01:26:31 server dovecot: indexer-worker(em...@domain.com): Received invalid SSL certificate: unable to get local issuer certifi cate: /C=US/O=Let\\\'s Encrypt/CN=Let\\\'s Encrypt Authority X3 Mar 3 01:26:31 server dovecot: indexer-worker(em...@domain.com): Error: fts_solr: Indexing failed: SSL handshaking with 1.1.1.1 3:8983 failed: read(SSL 1.1.1.1:8983) failed: Received invalid SSL certificate: unable to get local issuer certificate: /C=US/ O=Let\\\'s Encrypt/CN=Let\\\'s Encrypt Authority X3 (2 attempts in 0.112 secs) Mar 3 01:26:31 server dovecot: indexer-worker(em...@domain.com): Error: Mailbox INBOX: Transaction commit failed: FTS transaction com mit failed: backend deinit (attempted to index 1 messages (UIDs 104770..104770)) 90-plugins.conf: fts_autoindex=yes fts = solr fts_solr = url=https://login:p...@solr.domain.com:8983/solr/dovecot/ break-imap-search debug curl and other software connect to solr without errors in both cases. Does dovecot have option to disable certificate validation (may be ssl_verify = false etc.) ? Thanks.
Re: Outlook 2016 IMAP trouble
Am 05.03.2018 um 17:44 schrieb Robert Giles: > On 2018-03-05 at 10:40, Robert Schetterer wrote: >> Am 05.03.2018 um 09:45 schrieb G: >>> Hello List, >>> >>> I'm facing an issue with dovecot (2.2.27) IMAP and Outlook as a client. >>> >>> George >> >> i have no Outlook 2016 to test but if you setup is right >> no trouble should come up, however simply look in the dovecot log files >> what your user did, perhaps he was offline and only thinking that he >> synced via imap > > I've observed similar behavior for a user with Outlook 2013 and Panda > IMAP; when synchronization failed for whatever reason, Outlook wasn't > very verbose about it, and the user continued operating for several > months not realizing their local mailbox had entirely diverged from the > "true" contents on the IMAP server. > > Robert > never had this with Outlook 2013 but ost files may brake any time , also with exchange mostly with big mailboxes, and there is less you can do against buggy users, give them webmail to show real imap status on the server Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG, 80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
Re: Outlook 2016 IMAP trouble
On 2018-03-05 at 10:40, Robert Schetterer wrote: Am 05.03.2018 um 09:45 schrieb G: Hello List, I'm facing an issue with dovecot (2.2.27) IMAP and Outlook as a client. >> George i have no Outlook 2016 to test but if you setup is right no trouble should come up, however simply look in the dovecot log files what your user did, perhaps he was offline and only thinking that he synced via imap I've observed similar behavior for a user with Outlook 2013 and Panda IMAP; when synchronization failed for whatever reason, Outlook wasn't very verbose about it, and the user continued operating for several months not realizing their local mailbox had entirely diverged from the "true" contents on the IMAP server. Robert smime.p7s Description: S/MIME Cryptographic Signature
Re: getmail, dovecot, virtual users
Am 05.03.2018 um 15:46 schrieb David Mehler:
> Hello,
>
> I've got a dovecot setup with virtual users coming from a MySQL
> database. The only system user I have is the vmail owner of the email
> store. What i'd like to do is use the program getmail to back up my
> gmail account and place that in my user's virtual mail store. I'm
> having issues making the configuration file and where to put it.
> Should it go in the virtual user's home directory or somewhere else
> and run by which user root or the vmail user?
>
> If anyone has this working any suggestions appreciated.
>
> Thanks.
> Dave.
>
here is a example
https://blog.sys4.de/abholdienst-fur-mail-de.html
...
[destination]
type = MDA_external
path = /usr/lib/dovecot/deliver
arguments = ("-d", "u...@server.com")
user = vmail
group = vmail
may the magic youre looking for
Best Regards
MfG Robert Schetterer
--
[*] sys4 AG
http://sys4.de, +49 (89) 30 90 46 64
Schleißheimer Straße 26/MG, 80333 München
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein
Re: Outlook 2016 IMAP trouble
Am 05.03.2018 um 09:45 schrieb G: > Hello List, > > I'm facing an issue with dovecot (2.2.27) IMAP and Outlook as a client. > I have some users that use > Outlook (2016) as a client . One of them has a desktop PC in the office > and a laptop machine > which I've setup some days ago . The user did some work, during the > weekend, in his laptop > (filling messages into IMAP folders) and to his (and mine) surprise, > today in the office he saw that none of his > work is reflected on the server. Messages are not where they supposed to > be .Tomorrow he will bring the laptop > over to check, but I have seen this problem again in the past again > with outlook 2016 as a client > (specifically I've had a user which during work he was deleting or > renaming folders which appear fine > on his copy of outlook (ost) but not on the server). Anyone has any > experience with dovecot and outlook > and related problems ? > > > thanks in advance > George by the way ost file may broke any time https://support.office.com/en-us/article/repair-outlook-data-files-pst-and-ost-25663bc3-11ec-4412-86c4-60458afc5253 Recreate an offline Outlook Data File (.ost) Some account types, such as Microsoft Exchange Server, use an offline Outlook Data File (.ost). This type of data file is a copy of information saved on your mail server. If you encounter problems with an offline Outlook Data File (.ost), the file can be deleted and recreated by downloading a copy of your items again. We don't recommend repairing an offline Outlook Data File, so if your offline data file isn't usable, you should recreate it. Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG, 80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
Re: Outlook 2016 IMAP trouble
Am 05.03.2018 um 09:45 schrieb G: > Hello List, > > I'm facing an issue with dovecot (2.2.27) IMAP and Outlook as a client. > I have some users that use > Outlook (2016) as a client . One of them has a desktop PC in the office > and a laptop machine > which I've setup some days ago . The user did some work, during the > weekend, in his laptop > (filling messages into IMAP folders) and to his (and mine) surprise, > today in the office he saw that none of his > work is reflected on the server. Messages are not where they supposed to > be .Tomorrow he will bring the laptop > over to check, but I have seen this problem again in the past again > with outlook 2016 as a client > (specifically I've had a user which during work he was deleting or > renaming folders which appear fine > on his copy of outlook (ost) but not on the server). Anyone has any > experience with dovecot and outlook > and related problems ? > > > thanks in advance > George i have no Outlook 2016 to test but if you setup is right no trouble should come up, however simply look in the dovecot log files what your user did, perhaps he was offline and only thinking that he synced via imap Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG, 80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
Re: Sieve filter imapflags with "flagvar" not working
Op 5-3-2018 om 11:47 schreef Konstantinos Tsakiltzidis:
tried also with `require "variables"` doesn't seem to work,
the flag is not added at all
What is your full script? Just adding flags to a variable is not going
to do anything.
Either leave out the variable:
setflag "spam";
In which case it applies implicitly to subsequent fileinto and
(implicit) keep.
Or use the "${flagvar}" variable in a fileinto or keep command:
fileinto :flags "${flagvar}" "Mailbox";
Or
keep :flags "${flagvar}";
Regards,
Stephan.
On 03/03/2018 09:54 AM, Stephan Bosch wrote:
Op 3/2/2018 om 6:09 PM schreef Konstantinos Tsakiltzidis:
Following the rfc5232, Sieve Email Filtering: Imap4flags Extension
the following filter doesn't work when the `"flagvar"` part is added
require "imap4flags";
if header :contains "X-Spam" "Yes" {
setflag "flagvar" "spam";
}
You should be getting an error logged somewhere. Using a flag variable
is not allowed, unless the variables extension is enabled. So, you must
add `require "variables";' for this script to make sense at all.
Regards,
Stephan.
removing the `"flagvar"` part works as expected
# 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.21 (92477967)
# OS: Linux 4.9.0-6-amd64 x86_64 Debian 9.1 ext4
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
mail_debug = yes
mail_location = maildir:/var/vmail/%d/%n
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 =
separator = .
subscriptions = yes
type = private
}
namespace modulus {
list = children
location = maildir:/var/vmail/%d/Public:INDEXPVT=~/public/indexes
mailbox admin {
auto = subscribe
}
mailbox support {
auto = subscribe
}
mailbox telecoms {
auto = subscribe
}
prefix = Public.
separator = .
subscriptions = yes
type = public
}
passdb {
driver = pam
}
plugin {
acl = vfile
mail_log_events = flag_change
mail_log_fields = box flags uid
sieve = ~/dovecot.sieve
sieve_before = /var/vmail/global.sieve
sieve_dir = ~/sieve
sieve_global_dir = /var/vmail/sieve
}
protocols = " imap lmtp sieve lmtp"
service auth {
unix_listener /var/spool/postfix/private/auth {
group = mail
mode = 0666
user = postfix
}
unix_listener auth-userdb {
group = mail
mode = 0666
user = vmail
}
}
service imap-login {
inet_listener imap {
port = 0
}
}
service lmtp {
unix_listener /var/spool/postfix/private/dovecot-lmtp {
group = postfix
mode = 0600
user = postfix
}
}
service managesieve-login {
inet_listener sieve {
port = 4190
}
process_min_avail = 0
service_count = 1
vsz_limit = 64 M
}
service managesieve {
process_limit = 1024
}
ssl = required
ssl_cert =
Outlook 2016 & IMAP Trouble with dovecot
Reposting since it went under another thread somehow... Hello List, I'm facing an issue with dovecot (2.2.27) IMAP and Outlook as a client. I have some users that use Outlook (2016) as a client . One of them has a desktop PC in the office and a laptop machine which I've setup some days ago . The user did some work, during the weekend, in his laptop (filling messages into IMAP folders) and to his (and mine) surprise, today in the office he saw that none of his work is reflected on the server. Messages are not where they supposed to be .Tomorrow he will bring the laptop over to check, but I have seen this problem again in the past again with outlook 2016 as a client (specifically I've had a user which during work he was deleting or renaming folders which appear fine on his copy of outlook (ost) but not on the server). Anyone has any experience with dovecot and outlook and related problems ? thanks in advance George
getmail, dovecot, virtual users
Hello, I've got a dovecot setup with virtual users coming from a MySQL database. The only system user I have is the vmail owner of the email store. What i'd like to do is use the program getmail to back up my gmail account and place that in my user's virtual mail store. I'm having issues making the configuration file and where to put it. Should it go in the virtual user's home directory or somewhere else and run by which user root or the vmail user? If anyone has this working any suggestions appreciated. Thanks. Dave.
Dovecot 2.2.34 FTS-SOLR = inconsistent results
Hello,
I'm trying to figure why I have inconsistent results with my fts-solr
powered search:
My test is to find the string "am5oocobey9hait5Wiex8yohgoob9thu" in the
3 emails containing it that I sent to myself:
- Directly on the server:
doveadm search -u username text am5oocobey9hait5Wiex8yohgoob9thu
e2c58a309323515311083ea484a8 7937
e2c58a309323515311083ea484a8 7938
e0c58a309323515311083ea484a8 36479
e0c58a309323515311083ea484a8 36480
e0c58a309323515311083ea484a8 36481
- RoundCube webmail:
0 Result
- On the server with "telnet localhost imap" (2 identical searches):
[snip...]
a23 SEARCH text am5oocobey9hait5Wiex8yohgoob9thu
* SEARCH
* 14488 FETCH (FLAGS (\Seen NonJunk))
* 14495 EXISTS
a23 OK Search completed (0.015 + 0.000 + 0.004 secs).
a25 SEARCH text am5oocobey9hait5Wiex8yohgoob9thu
* SEARCH
a25 OK Search completed (0.006 + 0.000 + 0.003 secs).
Here is my setup:
root@myMailServer ~ # uname -a
Linux myMailServer.mydomain 3.10.0-693.17.1.el7.x86_64 #1 SMP Thu Jan 25
20:13:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
root@myMailServer ~ # cat /etc/redhat-release
CentOS Linux release 7.4.1708 (Core)
root@plainte ~ # doveconf -n
# 2.2.34 (874deae):
/usr/local/etc/dovecot/dovecot.conf
[50/1259]
# Pigeonhole version 0.4.22 (22940fb7)
# OS: Linux 3.10.0-693.17.1.el7.x86_64 x86_64 CentOS Linux release
7.4.1708 (Core) ext4
# Hostname: myMailServer.mydomain
auth_cache_size = 10 M
auth_master_user_separator = *
auth_socket_path = /var/run/dovecot/auth-userdb
auth_username_chars =
abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@*
auth_verbose = yes
base_dir = /var/run/dovecot/
debug_log_path = /var/log/dovecot-debug.log
default_client_limit = 5120
default_process_limit = 1024
default_vsz_limit = 2 G
hostname = mydomain
info_log_path = /var/log/dovecot.log
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
listen = *
log_path = /var/log/dovecot-error.log
login_greeting = Welcome
login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c
mail_gid = vmail
mail_location = maildir:/var/vmail/%Ln
mail_plugins = fts fts_solr quota stats
mail_uid = vmail
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 = yes
location = maildir:/var/vmail/%Ln
mailbox Drafts {
auto = subscribe
special_use = \Drafts
}
mailbox Sent {
auto = subscribe
special_use = \Sent
}
mailbox "Sent Messages" {
special_use = \Sent
}
mailbox Trash {
auto = subscribe
special_use = \Trash
}
prefix =
type = private
}
passdb {
args = /usr/local/etc/dovecot/deny-users
deny = yes
driver = passwd-file
}
passdb {
args = /usr/local/etc/dovecot/master-users
driver = passwd-file
master = yes
}
passdb {
args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext
driver = ldap
}
plugin {
fts = solr
fts_autoindex = yes
fts_autoindex_max_recent = 1000
fts_solr = url=http://127.0.0.1:8983/solr/dovecot/
quota = maildir:User quota
quota_rule = *:storage=20GB
quota_rule2 = Trash:storage=+200M
quota_warning = storage=95%% quota-warning 95 %u
quota_warning2 = storage=80%% quota-warning 80 %u
sieve = /var/sieve-scripts/%Ln.sieve
sieve_dir = /var/vmail/%Ln/home/sieve
stats_command_min_time = 1 mins
stats_domain_min_time = 12 hours
stats_ip_min_time = 12 hours
stats_memory_limit = 16 M
stats_refresh = 30 secs
stats_session_min_time = 15 mins
stats_track_cmds = yes
stats_user_min_time = 1 hours
}
postmaster_address = postmaster@mydomain
protocols = imap pop3 sieve sieve
service auth-worker {
user = root
}
service auth {
unix_listener /var/spool/postfix/private/auth {
mode = 0777
user = vmail
}
}
service imap-login {
inet_listener imaps {
port = 993
ssl = yes
}
process_min_avail = 10
}
service imap {
process_limit = 2128
}
service managesieve-login {
inet_listener sieve {
port = 4190
}
}
service pop3-login {
inet_listener pop3s {
port = 995
ssl = yes
}
}
service quota-warning {
executable = script /usr/local/bin/quota-warning.sh
user = nobody
}
service stats {
fifo_listener stats-mail {
mode = 0600
user = vmail
}
}
ssl_cert = http://127.0.0.1:8983/solr/dovecot/update?optimize=true > /dev/null 2>&1
*/5 * * * * /usr/bin/curl
http://127.0.0.1:8983/solr/dovecot/update?commit=true > /dev/null 2>&1
I would be very grateful if someone can point me where my error is, as
I've been on this problem for weeks :(
Thanks,
kfx
Coredump: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))
Got a coredump:
Mar 5 15:09:42 mail-cbf dovecot:
lmtp(backup@backup.invalid)<15425><2B+kCaZPnVpBPAAAplP5LA>: Fatal: master:
service(lmtp): child 15425 killed with signal 6 (core dumped)
#0 0x7fea19977428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
resultvar = 0
pid = 15425
selftid = 15425
#1 0x7fea1997902a in __GI_abort () at abort.c:89
save_stage = 2
act = {
__sigaction_handler = {
sa_handler = 0x56239d9a3890,
sa_sigaction = 0x56239d9a3890
},
sa_mask = {
__val = {1, 94710917811261, 140643428345904, 94710917811577, 0,
140735221053024, 94710938452648, 513, 7700885895375379200, 0, 140643433202867,
94710938452648,
140735221053120, 94710938452304, 140643433203225, 94710938452648}
},
sa_flags = 433895898,
sa_restorer = 0x5
}
sigs = {
__val = {32, 0 }
}
#2 0x7fea19dd2aaf in default_fatal_finish (type=LOG_TYPE_PANIC,
status=status@entry=0) at failures.c:228
backtrace = 0x56239bd7c2e0 "/usr/lib/dovecot/libdovecot.so.0(+0xc6aca)
[0x7fea19dd2aca] -> /usr/lib/dovecot/libdovecot.so.0(+0xc6bad) [0x7fea19dd2bad]
-> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fea19d44721] ->
/usr/lib/d"...
recursed = 0
#3 0x7fea19dd2bad in i_internal_fatal_handler (ctx=0x7fff78dbb710,
format=, args=) at failures.c:718
status = 0
#4 0x7fea19d44721 in i_panic (format=format@entry=0x7fea19e0ec98 "file %s:
line %d (%s): assertion failed: (%s)") at failures.c:306
ctx = {
type = LOG_TYPE_PANIC,
exit_status = 0,
timestamp = 0x0,
timestamp_usecs = 0,
log_prefix = 0x0
}
args =
#5 0x7fea19d4831d in smtp_address_write (out=0x56239bd7c150,
address=0x56239bd7c108) at smtp-address.c:530
quoted =
p = 0x56239bd7c11b "üller"
pend = 0x56239bd7c121 ""
pblock = 0x56239bd7c11a "müller"
__func__ = "smtp_address_write"
#6 0x7fea19d48411 in smtp_address_encode (address=0x56239bd7c108) at
smtp-address.c:567
str = 0x56239bd7c150
#7 0x7fea1a3cf774 in mail_deliver_log_update_cache
(cache=cache@entry=0x56239bddf1c8, pool=0x56239bddf180, mail=0x56239be185c8) at
mail-deliver.c:111
message_id = 0x56239d943a4c
""
subject = 0x56239d943b69 "JOMEC Seminar | Von Kennzahlencockpits und
Lean Hospital Strategien"
from_envelope = 0x0
from =
#8 0x7fea1a3cfabf in mail_deliver_save_finish (ctx=0x56239be14ca0) at
mail-deliver.c:533
box =
mbox = 0x56239be0efc0
muser = 0x56239bdcb7c0
dt = 0x56239bddf1c0
#9 0x7fea1a0c758c in mailbox_save_finish (_ctx=_ctx@entry=0x7fff78dbb948)
at mail-storage.c:2461
_data_stack_cur_id = 4
ctx = 0x56239be14ca0
t = 0x56239be10ce0
keywords = 0x0
pvt_flags = 0
copying_via_save = true
ret =
#10 0x7fea1a0b9eb4 in mail_storage_copy (ctx=0x0, ctx@entry=0x56239be14ca0,
mail=mail@entry=0x56239bdfdb28) at mail-copy.c:112
__func__ = "mail_storage_copy"
#11 0x7fea1a0e03f6 in mdbox_copy (_ctx=0x56239be14ca0, mail=0x56239bdfdb28)
at mdbox-save.c:461
ctx = 0x56239be14ca0
save_mail = 0x56239bdfdb28
src_mbox =
rec = {
map_uid = 2615013952,
save_date = 22051
}
guid_data = 0x7fff78dbb9b0
wanted_guid = "@\362ݛ#V\000\000\240L\341\233#V\000"
#12 0x7fea1a3cf999 in mail_deliver_copy (ctx=0x56239be14ca0,
mail=0x56239bdfdb28) at mail-deliver.c:547
box =
mbox = 0x56239be0efc0
muser = 0x56239bdcb7c0
dt = 0x56239bddf1c0
#13 0x7fea1a0c7956 in mailbox_copy_int (_ctx=_ctx@entry=0x7fff78dbba98,
mail=0x56239bdfdb28) at mail-storage.c:2532
_data_stack_cur_id = 3
ctx = 0x56239be14ca0
t = 0x56239be10ce0
keywords = 0x0
pvt_flags = 0
backend_mail = 0x56239bdfdb28
ret =
__func__ = "mailbox_copy_int"
#14 0x7fea1a0c7c38 in mailbox_save_using_mail
(_ctx=_ctx@entry=0x7fff78dbba98, mail=) at mail-storage.c:2584
ctx =
__func__ = "mailbox_save_using_mail"
#15 0x7fea1a3d02ac in mail_deliver_save (ctx=ctx@entry=0x7fff78dbbc60,
mailbox=, flags=flags@entry=0, keywords=keywords@entry=0x0,
storage_r=storage_r@entry=0x7fff78dbbc50) at mail-deliver.c:363
open_ctx = {
user = 0x56239bdcacb8,
lda_mailbox_autocreate = false,
lda_mailbox_autosubscribe = false
}
box = 0x56239be0e6b8
trans_flags =
t = 0x56239be10ce0
save_ctx = 0x0
headers_ctx = 0x0
kw = 0x0
dest_mail =
error = MAIL_ERROR_NONE
mailbox_name = 0x56239a9d0a54 "INBOX"
errstr = 0x0
guid = 0x6adf0aebb9aa5b00
changes =
Re: [ext] Re: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))
Mine ended up in /tmp on CentOS 7. Good luck! Reio On 05.03.18 16:02, Ralf Hildebrandt wrote: * Ralf Hildebrandt : From the code in lib-smtp/smtp-address.c function smtp_address_write, it looks as though the assertion will happen whenever there is a non ascii char that is also non qpair in the local part, ie !smtp_char_is_atext(*p) and !smtp_char_is_qpair(*p). Could somebody please point me in the direction how to obtain a coredump here? I found sysctl -w fs.suid_dumpable=2 but where will coredumps be written?
Re: [ext] Re: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))
* Ralf Hildebrandt : > > From the code in lib-smtp/smtp-address.c function smtp_address_write, it > > looks as though the assertion will happen whenever there is a non ascii > > char that is also non qpair in the local part, ie > > !smtp_char_is_atext(*p) and !smtp_char_is_qpair(*p). > > Could somebody please point me in the direction how to obtain a > coredump here? I found sysctl -w fs.suid_dumpable=2 but where will coredumps be written? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de signature.asc Description: PGP signature
Re: [ext] Re: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))
> From the code in lib-smtp/smtp-address.c function smtp_address_write, it > looks as though the assertion will happen whenever there is a non ascii > char that is also non qpair in the local part, ie > !smtp_char_is_atext(*p) and !smtp_char_is_qpair(*p). Could somebody please point me in the direction how to obtain a coredump here? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de signature.asc Description: PGP signature
Re: [ext] Re: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))
* John Fawcett : > Postfix already permitted UTF8 in message headers and local part of the > address before the introduction of SMTPUTF8 and that has remained so. I > don't believe turning off SMTPUTF8 in Postfix will change the behaviour > in this case. I agree. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de signature.asc Description: PGP signature
Re: [ext] Re: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))
* A.L.E.C : > On 03/02/2018 03:32 PM, Ralf Hildebrandt wrote: > > The address causing the error is: > > > > From: =?utf-8?Q?Dorit_M=C3=BCller?= > > > > Note the "umlaut" in the email address... :) > > This is about SMTPUTF8 (RFC6531). Looks like your only option is to disable > smtputf8_enable in Postfix config. It IS already disabled. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de signature.asc Description: PGP signature
Re: [ext] Re: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))
> I wasn't able to confirm it since I've not moved to 2.3 yet and the 2.2 > code is different, but this should happen if there are characters from > 0x01 to 0x1f or from 0x7f to 0xff in the local part. Yeah, I was running 2.2.x prior to my upgrade and never encountered this. > By the way I noticed that if Postfix has SMTPUTF8 enabled, then it won't > hand off messages with this content to Dovecot since Dovecot does not > advertise support for SMTPUTF8. If SMTPUTF8 is unavailable or disabled > then Postfix passes on those characters. I suspect that Ralph has > SMTPUTF8 turned off. Ah I see: When a message is received with the SMTPUTF8 request, Postfix will deliver the message to a non-SMTPUTF8 SMTP or LMTP server ONLY if: * No message header value contains UTF-8. * The envelope sender address contains no UTF-8, * No envelope recipient address for that specific SMTP/LMTP delivery transaction contains UTF-8. I wonder if this will break a lot. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Re: Sieve filter fileinto doesn't preserve flags
This was an error with the ACLs
logging doesn't seem to log any related error.
On 03/03/2018 09:56 AM, Stephan Bosch wrote:
Op 3/2/2018 om 6:41 PM schreef Konstantinos Tsakiltzidis:
Using `fileinto` to move a mail into another mailbox removes flags
that have been set with a previous sieve filter with `addflag`.
I need to see your script to help you.
Regards,
Stephan Bosch.
# 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.21 (92477967)
# OS: Linux 4.9.0-6-amd64 x86_64 Debian 9.1 ext4
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
mail_debug = yes
mail_location = maildir:/var/vmail/%d/%n
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 =
separator = .
subscriptions = yes
type = private
}
namespace modulus {
list = children
location = maildir:/var/vmail/%d/Public:INDEXPVT=~/public/indexes
mailbox admin {
auto = subscribe
}
mailbox support {
auto = subscribe
}
mailbox telecoms {
auto = subscribe
}
prefix = Public.
separator = .
subscriptions = yes
type = public
}
passdb {
driver = pam
}
plugin {
acl = vfile
mail_log_events = flag_change
mail_log_fields = box flags uid
sieve = ~/dovecot.sieve
sieve_before = /var/vmail/global.sieve
sieve_dir = ~/sieve
sieve_global_dir = /var/vmail/sieve
}
protocols = " imap lmtp sieve lmtp"
service auth {
unix_listener /var/spool/postfix/private/auth {
group = mail
mode = 0666
user = postfix
}
unix_listener auth-userdb {
group = mail
mode = 0666
user = vmail
}
}
service imap-login {
inet_listener imap {
port = 0
}
}
service lmtp {
unix_listener /var/spool/postfix/private/dovecot-lmtp {
group = postfix
mode = 0600
user = postfix
}
}
service managesieve-login {
inet_listener sieve {
port = 4190
}
process_min_avail = 0
service_count = 1
vsz_limit = 64 M
}
service managesieve {
process_limit = 1024
}
ssl = required
ssl_cert =
Re: Deprecations for schema.xml and newest Solr version (7.2.x)
What came to my mind : are there any changes needed on the dovecot side? Esp. because there is also a field type change in it Am 4. März 2018 18:26:06 schrieb TG Servers : Hi, the schema.xml example provided for dovecot in /usr/share/doc/dovecot- does not work anymore with the newest Solr Version (as I know of 7.2.x) because some field classes and filter classes are deprecated in this version. The changes (according to the Solr documentation) would have to be : In the index analyzer : into . into and because this is used in the index analyzer it has to be followed by .. In the query analyzer : into ... into . Don't know if you want to mention this somewhere in your docs. Cheers, Thomas
Re: Sieve filter imapflags with "flagvar" not working
tried also with `require "variables"` doesn't seem to work,
the flag is not added at all
On 03/03/2018 09:54 AM, Stephan Bosch wrote:
Op 3/2/2018 om 6:09 PM schreef Konstantinos Tsakiltzidis:
Following the rfc5232, Sieve Email Filtering: Imap4flags Extension
the following filter doesn't work when the `"flagvar"` part is added
require "imap4flags";
if header :contains "X-Spam" "Yes" {
setflag "flagvar" "spam";
}
You should be getting an error logged somewhere. Using a flag variable
is not allowed, unless the variables extension is enabled. So, you must
add `require "variables";' for this script to make sense at all.
Regards,
Stephan.
removing the `"flagvar"` part works as expected
# 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.21 (92477967)
# OS: Linux 4.9.0-6-amd64 x86_64 Debian 9.1 ext4
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
mail_debug = yes
mail_location = maildir:/var/vmail/%d/%n
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 =
separator = .
subscriptions = yes
type = private
}
namespace modulus {
list = children
location = maildir:/var/vmail/%d/Public:INDEXPVT=~/public/indexes
mailbox admin {
auto = subscribe
}
mailbox support {
auto = subscribe
}
mailbox telecoms {
auto = subscribe
}
prefix = Public.
separator = .
subscriptions = yes
type = public
}
passdb {
driver = pam
}
plugin {
acl = vfile
mail_log_events = flag_change
mail_log_fields = box flags uid
sieve = ~/dovecot.sieve
sieve_before = /var/vmail/global.sieve
sieve_dir = ~/sieve
sieve_global_dir = /var/vmail/sieve
}
protocols = " imap lmtp sieve lmtp"
service auth {
unix_listener /var/spool/postfix/private/auth {
group = mail
mode = 0666
user = postfix
}
unix_listener auth-userdb {
group = mail
mode = 0666
user = vmail
}
}
service imap-login {
inet_listener imap {
port = 0
}
}
service lmtp {
unix_listener /var/spool/postfix/private/dovecot-lmtp {
group = postfix
mode = 0600
user = postfix
}
}
service managesieve-login {
inet_listener sieve {
port = 4190
}
process_min_avail = 0
service_count = 1
vsz_limit = 64 M
}
service managesieve {
process_limit = 1024
}
ssl = required
ssl_cert =
Re: Sieve filter fileinto doesn't preserve flags
my script is as simple as:
require ["imap4flags", "fileinto"];
if hasflag :contains "spam" {
fileinto "Public.telecoms.Spam";
}
the mails is correctly delivered in the above mailbox
but the flags have been removed
On 03/03/2018 09:56 AM, Stephan Bosch wrote:
Op 3/2/2018 om 6:41 PM schreef Konstantinos Tsakiltzidis:
Using `fileinto` to move a mail into another mailbox removes flags
that have been set with a previous sieve filter with `addflag`.
I need to see your script to help you.
Regards,
Stephan Bosch.
# 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.21 (92477967)
# OS: Linux 4.9.0-6-amd64 x86_64 Debian 9.1 ext4
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
mail_debug = yes
mail_location = maildir:/var/vmail/%d/%n
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 =
separator = .
subscriptions = yes
type = private
}
namespace modulus {
list = children
location = maildir:/var/vmail/%d/Public:INDEXPVT=~/public/indexes
mailbox admin {
auto = subscribe
}
mailbox support {
auto = subscribe
}
mailbox telecoms {
auto = subscribe
}
prefix = Public.
separator = .
subscriptions = yes
type = public
}
passdb {
driver = pam
}
plugin {
acl = vfile
mail_log_events = flag_change
mail_log_fields = box flags uid
sieve = ~/dovecot.sieve
sieve_before = /var/vmail/global.sieve
sieve_dir = ~/sieve
sieve_global_dir = /var/vmail/sieve
}
protocols = " imap lmtp sieve lmtp"
service auth {
unix_listener /var/spool/postfix/private/auth {
group = mail
mode = 0666
user = postfix
}
unix_listener auth-userdb {
group = mail
mode = 0666
user = vmail
}
}
service imap-login {
inet_listener imap {
port = 0
}
}
service lmtp {
unix_listener /var/spool/postfix/private/dovecot-lmtp {
group = postfix
mode = 0600
user = postfix
}
}
service managesieve-login {
inet_listener sieve {
port = 4190
}
process_min_avail = 0
service_count = 1
vsz_limit = 64 M
}
service managesieve {
process_limit = 1024
}
ssl = required
ssl_cert =
Re: [enhancement] fts-solr low performance
On 05.03.2018 11:07, azurIt wrote: >> Hi, >> >> we have activated fts-solr about a week ago and immediately started to >> experience really *low* performance with MOVE and EXPUNGE commands. >> After several days of googling, tcpdumping and straceing i was able to >> find and resolve the problem. >> >> We are using Dovecot 2.2.27 from Debian Jessie (jessie-backports), >> which is doing a soft commit in solr after every MOVE or EXPUNGE >> command - this behavior cannot be, currently, changed. The problem is >> that this was causing every MOVE/EXPUNGE to take about 6 seconds to >> complete. The problem appears to be in very old version of Solr - >> 3.6.2 (!!). This is the only version which is shipped with current >> (Jessie) and also next (Stretch) version of Debian, don't ask my why, >> i don't understand it either. Solr versions below 4.0 are NOT >> supporting soft commits, so all commits are hard and this was the >> problem. Finally, i decided to patch our Dovecot to not send a commit >> at all and everything started to be super fast. I'm doing hard commits >> every minute via cron so the only consequence of this is that you >> cannot search for messages delivered before less then a minute (which >> you, usually, don't need to do anyway). >> >> While googling i also find out that Solr supports autoCommit function >> (and from version 4.0 also autoSoftCommit), so there's no reason for >> Dovecot to handle this on it's own (and potentially doing hundreds or >> thousands of soft commits every second) - you can just set Solr to, >> for example, do autoSoftCommit every second and autoCommit every minute: >> https://cwiki.apache.org/confluence/display/solr/UpdateHandlers+in+SolrConfig#UpdateHandlersinSolrConfig-autoCommit >> >> Also this wiki page should be updated with warning about old versoins >> of Solr not supporting soft commits (you could also mention the >> auto[Soft]Commit function): >> http://wiki2.dovecot.org/Plugins/FTS/Solr >> >> I suggest to allow completely disable Solr commits in Dovecot by >> configuration, so people like me can handle this easily. What do you >> think? >> >> azur > > > > Hi, > > any news on this? Even Solr documentation suggests to NOT doing commits from > applications: > https://lucene.apache.org/solr/guide/6_6/shards-and-indexing-data-in-solrcloud.html#ShardsandIndexingDatainSolrCloud-IgnoringCommitsfromClientApplicationsinSolrCloud > > Thanks for not ignoring me. > > azur You are not being ignored. We'll attend to this eventually. Aki
Re: [enhancement] fts-solr low performance
>Hi, > >we have activated fts-solr about a week ago and immediately started to >experience really *low* performance with MOVE and EXPUNGE commands. >After several days of googling, tcpdumping and straceing i was able to >find and resolve the problem. > >We are using Dovecot 2.2.27 from Debian Jessie (jessie-backports), >which is doing a soft commit in solr after every MOVE or EXPUNGE >command - this behavior cannot be, currently, changed. The problem is >that this was causing every MOVE/EXPUNGE to take about 6 seconds to >complete. The problem appears to be in very old version of Solr - >3.6.2 (!!). This is the only version which is shipped with current >(Jessie) and also next (Stretch) version of Debian, don't ask my why, >i don't understand it either. Solr versions below 4.0 are NOT >supporting soft commits, so all commits are hard and this was the >problem. Finally, i decided to patch our Dovecot to not send a commit >at all and everything started to be super fast. I'm doing hard commits >every minute via cron so the only consequence of this is that you >cannot search for messages delivered before less then a minute (which >you, usually, don't need to do anyway). > >While googling i also find out that Solr supports autoCommit function >(and from version 4.0 also autoSoftCommit), so there's no reason for >Dovecot to handle this on it's own (and potentially doing hundreds or >thousands of soft commits every second) - you can just set Solr to, >for example, do autoSoftCommit every second and autoCommit every minute: >https://cwiki.apache.org/confluence/display/solr/UpdateHandlers+in+SolrConfig#UpdateHandlersinSolrConfig-autoCommit > >Also this wiki page should be updated with warning about old versoins >of Solr not supporting soft commits (you could also mention the >auto[Soft]Commit function): >http://wiki2.dovecot.org/Plugins/FTS/Solr > >I suggest to allow completely disable Solr commits in Dovecot by >configuration, so people like me can handle this easily. What do you >think? > >azur Hi, any news on this? Even Solr documentation suggests to NOT doing commits from applications: https://lucene.apache.org/solr/guide/6_6/shards-and-indexing-data-in-solrcloud.html#ShardsandIndexingDatainSolrCloud-IgnoringCommitsfromClientApplicationsinSolrCloud Thanks for not ignoring me. azur
Outlook 2016 IMAP trouble
Hello List, I'm facing an issue with dovecot (2.2.27) IMAP and Outlook as a client. I have some users that use Outlook (2016) as a client . One of them has a desktop PC in the office and a laptop machine which I've setup some days ago . The user did some work, during the weekend, in his laptop (filling messages into IMAP folders) and to his (and mine) surprise, today in the office he saw that none of his work is reflected on the server. Messages are not where they supposed to be .Tomorrow he will bring the laptop over to check, but I have seen this problem again in the past again with outlook 2016 as a client (specifically I've had a user which during work he was deleting or renaming folders which appear fine on his copy of outlook (ost) but not on the server). Anyone has any experience with dovecot and outlook and related problems ? thanks in advance George
