Re: Dovecot release v2.3.6

2019-04-30 Thread Michael Slusarz via dovecot
> On April 30, 2019 at 12:06 PM "@lbutlr via dovecot"  
> wrote:
> 
> pkg adult shows the following, not mentioned in the changes:
> 
> dovecot-2.3.5.1 is vulnerable:
> dovecot -- json encoder crash
> CVE: CVE-2019-10691
> WWW: 
> https://vuxml.FreeBSD.org/freebsd/a64aa22f-61ec-11e9-85b9-a4badb296695.html

https://dovecot.org/pipermail/dovecot-news/2019-April/000407.html

michael


Re: SMTPUTF8 support

2019-04-08 Thread Michael Slusarz via dovecot
Dovecot does not work as the "final mile" delivery host in a fully-compliant 
SMTPUTF8 chain.

This is on the (long) list of things todo.

michael


> On April 6, 2019 at 6:53 AM "@lbutlr via dovecot"  wrote:
> 
> 
> On 5 Apr 2019, at 13:47, André Rodier via dovecot  wrote:
> > 
> >> root@portal:/etc/postfix# postmap -q andré@homebox.space 
> >> ldap:/etc/postfix/ldap-aliases.cf 
> >> andre@homebox.space
> 
> You have a solution that properly maps UTF to a non-UTF namespace. As I 
> understand it, SMTPUTF8 uses a UTF8 namespace.
> 
> So, this would indicate SMTPUTF8
> 
> # postmap -q andré@homebox.space ldap:/etc/postfix/ldap-aliases.cf 
> andré@homebox.space
> 
> It's a hard problem to solve because you have to, as you've already 
> discovered, replace the entire chain with SMTPUTF8 compatible tools all at 
> once.


Re: SMTPUTF8 support

2019-04-03 Thread Michael Slusarz via dovecot
> On April 3, 2019 at 10:12 PM sylvhem--- via dovecot  
> wrote:
> 
> I'm currently trying to set up SMTPUTF8 on my mail stack, but I can't 
> find any information on Dovecot's RFC 6531 support. Has it been 
> implemented yet? 

No.

michael


Re: Repository / builds for Debian "buster"?

2019-04-01 Thread Michael Slusarz via dovecot
Support for Buster will be added once 10/buster is a stable release.

We only provide builds for the current stable version, and the previous 
version, so Debian 8/jessie support will be dropped when this happens.  But it 
is premature to do that now.

michael


> On March 31, 2019 at 6:04 AM Kostya Vasilyev via dovecot 
>  wrote:
> 
> 
> Speaking of repositories...
> 
> Debian "buster" (future version 10) has for some time been "stage 1 frozen" 
> (if I have the terminology right) and quite usable.
> 
> Perhaps it's starting to make sense to make a repo / start producing builds?
> 
> -- 
> Kostya Vasilyev
> k...@fastmail.com


Re: Dovecot crashing when attempting to search in virtual folder with fts_squat activated

2019-03-20 Thread Michael Slusarz via dovecot
fts_squat was deprecated in 2.1.  There's a high likelihood it is buggy in a 
variety of ways in any recent Dovecot release.

michael


> On March 20, 2019 at 1:21 PM Benjamin Godbersen via dovecot 
>  wrote:
> 
> Hi everyone,
> 
> I have now updated to dovecot 2.3.4.1 - unfortunately the issue still 
> persists. Can anyone help me figure out if this is due to a misconfiguration 
> on my part or another error?
> 
> Any help is greatly appreciated!
> 
> Cheers
> Benjamin
> 
> Am 14.03.2019 um 23:28 schrieb benja...@godbersen.info 
> mailto:benja...@godbersen.info :
> 
> > > Hi everyone,
> > 
> > I am running into a problem when trying to use fts_squat in a 
> > virtual folder. Without fts_squat plugin the search (from, subject...) 
> > works in all folders. With activated fts the search on the inbox folders 
> > works expectedly well but any attempt to search anything in any virtual 
> > folder leads to the following error. Similarly when attempting "doveadm fts 
> > lookup". I also noticed that no search index for the virtual folders gets 
> > build - is this expected behaviour?
> > 
> > > > > Mar 14 23:14:58 *** dovecot: service=imap, user=***, 
> > ip=[::1]. Panic: file mail-storage.c: line 1913 (mailbox_get_open_status): 
> > assertion failed: (box->opened)
> > > Mar 14 23:14:58 *** dovecot: service=imap, user=***, 
> > > ip=[::1]. Error: Raw backtrace: 
> > > /usr/lib/x86_64-linux-gnu/dovecot/libdovecot.so.0(+0xba731) 
> > > [0x7f553a7ff731] -> 
> > > /usr/lib/x86_64-linux-gnu/dovecot/libdovecot.so.0(+0xba7fa) 
> > > [0x7f553a7ff7fa] -> 
> > > /usr/lib/x86_64-linux-gnu/dovecot/libdovecot.so.0(i_fatal+0) 
> > > [0x7f553a771638] -> 
> > > /usr/lib/x86_64-linux-gnu/dovecot/libdovecot-storage.so.0(mailbox_get_open_status+0x68)
> > >  [0x7f553aae4a78] -> 
> > > /usr/lib/dovecot/modules/lib21_fts_squat_plugin.so(+0x3684) 
> > > [0x7f553677a684] -> 
> > > /usr/lib/dovecot/modules/lib21_fts_squat_plugin.so(+0x3820) 
> > > [0x7f553677a820] -> 
> > > /usr/lib/dovecot/modules/lib20_fts_plugin.so(fts_backend_lookup_multi+0x163)
> > >  [0x7f5539b016a3] -> 
> > > /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0xd728) [0x7f5539b06728] -> 
> > > /usr/lib/dovecot/modules/lib20_fts_plugin.so(fts_search_lookup+0xeb) 
> > > [0x7f5539b06bbb] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0xf8b8) 
> > > [0x7f5539b088b8] -> dovecot/imap(imap_search_start+0x6a) [0x5654cb5a0d6a
 ] -> dovecot/imap(cmd_sort+0x293) [0x5654cb593553] -> 
dovecot/imap(command_exec+0x64) [0x5654cb599874] -> dovecot/imap(+0x1bd22) 
[0x5654cb597d22] -> dovecot/imap(+0x1bdbc) [0x5654cb597dbc] -> 
dovecot/imap(client_handle_input+0x1b5) [0x5654cb5981c5] -> 
dovecot/imap(client_input+0xa4) [0x5654cb5987e4] -> 
/usr/lib/x86_64-linux-gnu/dovecot/libdovecot.so.0(io_loop_call_io+0x69) 
[0x7f553a8174a9] -> 
/usr/lib/x86_64-linux-gnu/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x12e)
 [0x7f553a818d1e] -> 
/usr/lib/x86_64-linux-gnu/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) 
[0x7f553a8175ac] -> 
/usr/lib/x86_64-linux-gnu/dovecot/libdovecot.so.0(io_loop_run+0x38) 
[0x7f553a8177b8] -> 
/usr/lib/x86_64-linux-gnu/dovecot/libdovecot.so.0(master_service_run+0x13) 
[0x7f553a7940a3] -> dovecot/imap(main+0x339) [0x5654cb58a539] -> 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f553a375b97] -> 
dovecot/imap(_start+0x2a) [0x5654cb58a71a]
> > > Mar 14 23:14:58 *** dovecot: service=imap, user=***, 
> > > ip=[::1]. Fatal: master: service(imap): child 6436 killed with signal 6 
> > > (core dumps disabled)
> > > 
> > > > > This is my config:
> > 
> > > > > # 2.3.0.1 (ffd8a29): /etc/dovecot/dovecot.conf
> > > # Pigeonhole version 0.5.0.1 (d33dca20)
> > > # OS: Linux 4.15.0-46-generic x86_64 Ubuntu 18.04.2 LTS ext4
> > > auth_mechanisms = plain login digest-md5 cram-md5 apop
> > > auth_username_chars = 
> > > abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890&.-_@'
> > > default_vsz_limit = 8096 M
> > > disable_plaintext_auth = no
> > > first_valid_uid = 30
> > > imap_client_workarounds = delay-newmail
> > > imap_logout_format = rcvd=%i, sent=%o
> > > mail_home = /var/qmail/mailnames/%Ld/%Ln
> > > mail_location = maildir:/var/qmail/mailnames/%Ld/%Ln/Maildir
> > > mail_log_prefix = "service=%s, user=%u, ip=[%r]. "
> > > mail_max_userip_connections = 100
> > > mail_plugins = quota fts fts_squat virtual
> > > managesieve_logout_format = rcvd=%i, sent=%o
> > > managesieve_notify_capability = mailto
> > > managesieve_sieve_capability = fileinto reject envelope 
> > > encoded-character vacation subaddress comparator-i;ascii-numeri$
> > > namespace inbox {
> > >   inbox = yes
> > >   location =
> > >  

Re: index problems after update

2019-02-15 Thread Michael Slusarz via dovecot
> On February 15, 2019 at 3:35 AM Hajo Locke via dovecot  
> wrote:
> 
> Thanks for your reply, so iam not the only one. I think downgrading is 
> not an option for me. Ubuntu 18.04 comes with openssl 1.1.0 and it seems that 
> older versions like 2.2.22 not compile successful.
> Best way for me would be a patch from Ubuntu-side, but without any 
> errormessage or something its wasted time to file a bugreport.  Though Ubuntu 
> 18.04 should run for next 5 years.
> 
https://repo.dovecot.org/

michael


Re: Using SHA256/512 for SQL based password

2019-02-12 Thread Michael Slusarz via dovecot
> On February 12, 2019 at 4:33 PM Robert Moskowitz via dovecot 
>  wrote:
> 
> 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?

https://password-hashing.net/

michael


Re: Dovecot v2.2.36.1 released

2019-02-05 Thread Michael Slusarz
> On February 5, 2019 at 8:36 AM Eric Broch  wrote:
> 
> What's the difference between 2.2.x and 2.3.x version of Dovecot? And 
> why do you maintain both?

https://dovecot.org/pipermail/dovecot-news/2018-August/000386.html

michael


FOSDEM

2019-01-21 Thread Michael Slusarz via dovecot
Hello all,

Several Open-Xchange/Dovecot folks will be attending FOSDEM in Brussels on 2-3 
February 2019.

For those of you planning to attend: we would love to meet and chat with 
members of the Dovecot community!  Come find us wandering around the talks, or 
look for us in the evening.  Rumor is Brussels has some good beer...

Also, we'd love to invite everyone to a talk we are giving on the Chat Over 
IMAP initiative we have been working on.  It takes place Sunday at 1105 in the 
Real-Time Communications room:

https://fosdem.org/2019/schedule/event/chat_over_imap/

Hope to see some of you there!

michael


Re: Solr -> Xapian ?

2019-01-07 Thread Michael Slusarz
Maybe a dumb question (I admit I haven't followed this thread very closely)...

But why are you writing a new FTS driver?  If squat allegedly does everything 
you need it to do, why don't you just take that plugin and fix it up to do what 
you need?  That seems way easier than trying to create a FTS driver from 
scratch.

michael


> On January 7, 2019 at 7:05 AM Joan Moreau via dovecot  
> wrote:
> 
> 
> Hi
> 
> ANyone to answer specifically ?
> 
> Q1 : get_last_uid -> Is this the last UID indexed (which may be not the 
> greatest value), or the gratest value (which may not be the latest) (the code 
> of existing plugins is unclear about this, Solr looks for the greatest for 
> insance)
> 
> Q2 : WHen Indexing an email, the data is not passed by "build_key". Why 
> so ? What is the link with "build_more" ?
> 
> Q3 : Searching/Lookup : THe fheader in which to llok for (must be a least 
> among "cc, to, from, subject, body") is not appearing in the 'struct' data. 
> WHere to find it ?
> 
> Q4 : Refresh : this is very unclear. How come there would not be the 
> "latest" view on index. What is the real meaning of this function ?
> 
> Q5 : Rescan : is it just a bout remonving all indexes for a specific 
> mailbox ?
> 
> Q6 : lokkup_multi : isn't the function the same for all plugnins (see 
> below) ?
> 


Re: QUERY string clarification

2018-12-10 Thread Michael Slusarz
> On December 9, 2018 at 3:02 AM Ralf Hildebrandt  
> wrote:
> 
> 
> The manpage
> https://wiki.dovecot.org/Tools/Doveadm/SearchQuery
> specifies:
> 
> BODY string
> Matches messages, which contain string in the body part.
> 
> and a bit further down:
> 
> TEXT string
> Matches messages, which contain string in the message body.
> 
> Where's the difference?

BODY = body part (meaning, the non-header part of the message)
TEXT = entire message (header + body)

michael


Re: BUG: sieve does not set seen-Flag

2018-12-04 Thread Michael Slusarz
> On December 4, 2018 at 8:48 AM Jakobus Schürz  
> wrote:
> 
> I have an additional information.
> 
> Moving a already seen messsage to another imap-folder (drag in
> thunderbird) shows this email in the other folder as unseen and recent.
> 
> Is this normal behaviour?

Depends on what Thunderbird is doing.  If it is doing a COPY, flags will be 
preserved per IMAP spec.  If it is doing an APPEND, then Thunderbird would be 
responsible for transferring the flags (and clearing the recent flag) to match 
COPY semantics.

michael


Re: [2.3.4] Segmentation faults

2018-12-04 Thread Michael Slusarz
> On December 4, 2018 at 8:18 AM Aki Tuomi  wrote:
> 
> We don't consider it as "very early beta". We consider it production ready. 
> It is bit more work to set up though.

FWIW, Squat has been deprecated since 2.0, so none of this should come as a 
surprise.

https://wiki.dovecot.org/Plugins/FTS


> Aki
> 
> > On 04 December 2018 at 17:16 Joan Moreau  wrote:
> > 
> > 
> > Thanks for mySql 
> > 
> > For Squat vs Solr, Solr does not reach Squat by very far in terms of
> > results : If I setup Solr, and search (via the search in Roundbube or
> > Evolution) for a keyword or part of the keyword, the results are
> > complete non sense. The diference between "search in full body" and
> > "search in fields" does not even work. 
> > 
> > Solr with Dovecot seems very early beta isnt'it ? 
> > 
> > On 2018-12-04 15:57, Aki Tuomi wrote:
> > 
> > > On 04 December 2018 at 16:46 Joan Moreau via dovecot 
> > >  wrote:
> > > 
> > > Hi 
> > > 
> > > How to solve this ? 
> > > 
> > > So many similar segfaults 
> > > 
> > > Thank you 
> > > 
> > > On 2018-11-30 06:11, Joan Moreau wrote:
> > > 
> > > ANother (very very long) example : 
> > > 
> > > # gdb /usr/libexec/dovecot/indexer-worker 
> > > core.indexer-worker.0.3a33f56105e043de802a7dfcee265a07.21017.154353342400
> > > GNU gdb (GDB) 8.2
> > > Copyright (C) 2018 Free Software Foundation, Inc.
> > > License GPLv3+: GNU GPL version 3 or later 
> > > 
> > > This is free software: you are free to change and redistribute it.
> > > There is NO WARRANTY, to the extent permitted by law.
> > > Type "show copying" and "show warranty" for details.
> > > This GDB was configured as "x86_64-pc-linux-gnu".
> > > Type "show configuration" for configuration details.
> > > For bug reporting instructions, please see:
> > > .
> > > Find the GDB manual and other documentation resources online at:
> > > . 
> > > 
> > > For help, type "help".
> > > Type "apropos word" to search for commands related to "word"...
> > > Reading symbols from /usr/libexec/dovecot/indexer-worker...done.
> > > [New LWP 21017]
> > > [Thread debugging using libthread_db enabled]
> > > Using host libthread_db library "/usr/lib/libthread_db.so.1".
> > > Core was generated by `dovecot/indexer-worker'.
> > > Program terminated with signal SIGSEGV, Segmentation fault.
> > > #0 0x7f768b62b13e in file_lock_do (fd=18, path=0x564540376790 
> > > "/data/mail/grosjo.net/admin/mailboxes/QoS/dbox-Mails/dovecot.index.search",
> > >  lock_type=0, 
> > > lock_method=FILE_LOCK_METHOD_FCNTL, timeout_secs=60, 
> > > error_r=0x7fff045010b0) at file-lock.c:173
> > > 173 {
> > > (gdb) bt full
> > > #0 0x7f768b62b13e in file_lock_do (fd=18, path=0x564540376790 
> > > "/data/mail/grosjo.net/admin/mailboxes/QoS/dbox-Mails/dovecot.index.search",
> > >  lock_type=0, 
> > > lock_method=FILE_LOCK_METHOD_FCNTL, timeout_secs=60, 
> > > error_r=0x7fff045010b0) at file-lock.c:173
> > > lock_type_str = 
> > > started = 
> > > ret = 
> > > __func__ = "file_lock_do"
> > > #1 0x7f768b62b5b6 in file_wait_lock_error (fd=18, path=0x564540376790 
> > > "/data/mail/grosjo.net/admin/mailboxes/QoS/dbox-Mails/dovecot.index.search",
> > >  lock_type=0, 
> > > lock_method=FILE_LOCK_METHOD_FCNTL, timeout_secs=, 
> > > lock_r=0x7fff04501118, error_r=0x7fff045010b0) at file-lock.c:318
> > > lock = 
> > > ret = 
> > > #2 0x7f768b62b660 in file_wait_lock (fd=, 
> > > path=, lock_type=lock_type@entry=0, lock_method= > > out>, timeout_secs=timeout_secs@entry=60, 
> > > lock_r=lock_r@entry=0x7fff04501118) at file-lock.c:303
> > > error = 0x564540376490 ""
> > > ret = 
> > > #3 0x7f768a976c87 in squat_trie_lock (trie=0x564540376490, 
> > > lock_type=0, file_lock_r=0x7fff04501118, dotlock_r=0x7fff04501120) at 
> > > squat-trie.c:294
> > > ret = 
> > > dotlock_r = 0x7fff04501120
> > > file_lock_r = 0x7fff04501118
> > > trie = 0x564540376490
> > > ret = 
> > > __func__ = "squat_trie_lock"
> > > lock_type = 0
> > > ret = 
> > > __func__ = "squat_trie_lock"
> > > #4 0x7f768a978627 in squat_trie_map (trie=0x564540376490, 
> > > building=) at squat-trie.c:1487
> > > file_lock = 0x0
> > > dotlock = 0x0
> > > changed = 
> > > ret = 
> > > #5 0x7f768a97b19d in squat_uidlist_map_header 
> > > (uidlist=0x5645403767f0) at squat-uidlist.c:378
> > > No locals.
> > > #6 squat_uidlist_map (uidlist=0x5645403767f0) at squat-uidlist.c:477
> > > mmap_hdr = 
> > > ret = 
> > > #7 0x7f768a97b432 in squat_uidlist_open (uidlist=0x5645403767f0) at 
> > > squat-uidlist.c:546
> > > No locals.
> > > #8 0x7f768a97b5aa in squat_uidlist_refresh (uidlist=) 
> > > at squat-uidlist.c:569
> > > No locals.
> > > #9 0x7f768a9787c2 in squat_trie_map (trie=0x564540376490, 
> > > building=) at squat-trie.c:1526
> > > file_lock = 0x56454210c850
> > > dotlock = 0x0
> > > changed = 
> > > ret = 
> > > #10 0x7f768a97b19d in squat_uidlist_map_header 

Re: Event 0x2b1a5f270bd0 leaked (parent=(nil)): auth-client-connection.c:338

2018-11-23 Thread Michael Slusarz
> On November 23, 2018 at 7:06 AM Mart Pirita  wrote:
>
> FYI, this is not fixed in v2.3.4:

Correct.  This is not a critical issue, so it will be fixed eventually but was 
not a priority for this release.

michael

> Nov 23 16:03:24 xxx dovecot: master: Dovecot v2.3.4 (0ecbaf23d) starting
> up for imap, pop3, lmtp (core dumps disabled)
> Nov 23 16:03:53 xxx dovecot: auth: Warning: Event 0x80c2f28 leaked
> (parent=(nil)): auth-client-connection.c:338
> Nov 23 16:03:53 xxx dovecot: auth: Warning: Event 0x80d71e0 leaked
> (parent=(nil)): auth-client-connection.c:338
> Nov 23 16:03:53 xxx dovecot: auth: Warning: Event 0x80c3220 leaked
> (parent=(nil)): auth-client-connection.c:338
> 
> ...
> 
> 
> Aki Tuomi wrote:
> > It will be fixed.
> >
> > Aki
> >
> > On 6.11.2018 8.57, Mart Pirita wrote:
> >> Hi,
> >>
> >>
> >> I'm not using rsyslog and instead of hiding, this event leak should be
> >> fixed.
> >>
> >>
> >>
> >> Michael Slusarz wrote:
> >>>> On November 3, 2018 at 9:41 AM Mart Pirita  
> >>>> wrote:
> >>>>
> >>>>
> >>>> Hi,
> >>>>
> >>>>
> >>>> But this harmless is spamming logs, so how to disable it:
> >>>>
> >>>> grep auth-client-connection.c:338 maillog | wc -l
> >>>>    1259
> >>> If using something like rsyslog, it is trivial to filter out unwanted 
> >>> entries.
> >>>
> >>> michael
> >>>
> >>>
> >>>> Aki Tuomi wrote:
> >>>>>> On 03 November 2018 at 12:12 Mart Pirita < sysad...@e-positive.ee 
> >>>>>> <mailto:sysad...@e-positive.ee>> wrote:
> >>>>>>
> >>>>>>
> >>>>>> Hi,
> >>>>>>
> >>>>>>
> >>>>>> Noticed with latest v2.3.3 some new warning in logs, for example:
> >>>>>>
> >>>>>> dovecot: auth: Warning: Event 0x80a6fc0 leaked (parent=(nil)):
> >>>>>> auth-client-connection.c:338: 1 Time(s)
> >>>>>> dovecot: auth: Warning: Event 0x80aa1c8 leaked (parent=(nil)):
> >>>>>> auth-client-connection.c:338: 1 Time(s)
> >>>>>> dovecot: auth: Warning: Event 0x80aa718 leaked (parent=(nil)):
> >>>>>> auth-client-connection.c:338: 1 Time(s)
> >>>>>> dovecot: auth: Warning: Event 0x80adac0 leaked (parent=(nil)):
> >>>>>> auth-client-connection.c:338: 1 Time(s)
> >>>>>> dovecot: auth: Warning: Event 0x80b6c38 leaked (parent=(nil)):
> >>>>>> auth-client-connection.c:338: 1 Time(s)
> >>>>>> dovecot: auth: Warning: Event 0x80c0e00 leaked (parent=(nil)):
> >>>>>> auth-client-connection.c:338: 1 Time(s)
> >>>>>> dovecot: auth: Warning: auth client 0 disconnected with 1 pending
> >>>>>> requests: EOF: 12 Time(s)
> >>>>>>
> >>>>>>
> >>>>>> What are they?
> >>>>>>
> >>>>>>
> >>>>>> -- 
> >>>>>> Mart
> >>>>> Hi! It's harmless event leak. This is a known issue to us.
> 
> 
> -- 
> Mart
> 
>


Re: different TLS protocols on different ports

2018-11-14 Thread Michael Slusarz
> On November 14, 2018 at 12:46 PM "A. Schulze"  wrote:
<
> I stumbled upon RFC 8314 *) and I found it a welcome option to enforce more 
> modern protocols/ciphers.
> IMAPS/SUBMISSIONS aren't used widely (at least to my knowlege, many 
> postmaster used to configure IMAP+SUBMISSION and STARTTLS)

"IMAPS" has been used forever.  Every installation I can think of supports 993.

Same with submission.  465/587 has been a standard port for awhile now.

In fact, these are the only ports someone like a Google will allow you to 
connect to.
https://support.google.com/mail/answer/7126229?hl=en


> Switching Clients to complete new ports is a chance to separate and dry out 
> legacy MUA's

There is no switch to do.  These ports are well-known and well used.


> I just tried this but that's no valid syntax tough:
> 
>   service imap-login {
> inet_listener imap {
>   port = 143
> # using default protocols and ciphers...
> }
> inet_listener imaps {
>   port = 993
>   ssl_protocols = TLSv1.2 TLSv1.3
> ssl_cipher_list = ...
> 
> }
>   }
> 
> 
> Postfix let me easily define different TLS protocols on different ports.
> For that it would be cool if dovecot could assist on such migrations, too.
> 
> Andreas
> 
> *) see https://tools.ietf.org/html/rfc8314
>as well as the draft 
> https://tools.ietf.org/html/draft-lvelvindron-tls-for-email-02 to deprecate 
> TLSv1.1


Re: Event 0x2b1a5f270bd0 leaked (parent=(nil)): auth-client-connection.c:338

2018-11-05 Thread Michael Slusarz
> On November 3, 2018 at 9:41 AM Mart Pirita  wrote:
> 
> 
> Hi,
> 
> 
> But this harmless is spamming logs, so how to disable it:
> 
> grep auth-client-connection.c:338 maillog | wc -l
>    1259

If using something like rsyslog, it is trivial to filter out unwanted entries.

michael


> Aki Tuomi wrote:
> > > On 03 November 2018 at 12:12 Mart Pirita < sysad...@e-positive.ee 
> > > > wrote:
> > >
> > >
> > > Hi,
> > >
> > >
> > > Noticed with latest v2.3.3 some new warning in logs, for example:
> > >
> > > dovecot: auth: Warning: Event 0x80a6fc0 leaked (parent=(nil)):
> > > auth-client-connection.c:338: 1 Time(s)
> > > dovecot: auth: Warning: Event 0x80aa1c8 leaked (parent=(nil)):
> > > auth-client-connection.c:338: 1 Time(s)
> > > dovecot: auth: Warning: Event 0x80aa718 leaked (parent=(nil)):
> > > auth-client-connection.c:338: 1 Time(s)
> > > dovecot: auth: Warning: Event 0x80adac0 leaked (parent=(nil)):
> > > auth-client-connection.c:338: 1 Time(s)
> > > dovecot: auth: Warning: Event 0x80b6c38 leaked (parent=(nil)):
> > > auth-client-connection.c:338: 1 Time(s)
> > > dovecot: auth: Warning: Event 0x80c0e00 leaked (parent=(nil)):
> > > auth-client-connection.c:338: 1 Time(s)
> > > dovecot: auth: Warning: auth client 0 disconnected with 1 pending
> > > requests: EOF: 12 Time(s)
> > >
> > >
> > > What are they?
> > >
> > >
> > > -- 
> > > Mart
> >
> > Hi! It's harmless event leak. This is a known issue to us.


Re: split auth from other logging

2018-10-01 Thread Michael Slusarz
For later versions of 2.3.x, it will eventually be possible to use log 
filtering to accomplish this entirely within Dovecot.  We are not quite there 
yet though.

michael


> On September 26, 2018 at 1:21 AM Kai Schaetzl  wrote:
> 
> 
> Is there a way to split the auth logging (logins and failed logins) from 
> the other logging that goes to 
> info_log_path = /var/log/dovecot/dovecot.log
> ?
> This log gets a lot of other info as well, most notably the lmtp 
> notifications about every filed mail (with no level stamping, btw).
> This makes it really hard to find authentication errors quickly and 
> comfortably.
> It would be nice to be able to split at least the lmtp messages away.
> 
> Kai
> 
> 
>


Re: Best way to move mail from one server to another

2018-09-04 Thread Michael Slusarz
Sami is correct.  imapsync loses data.

Source -> imapsync -> destination : the mailboxes are different to an IMAP 
client
Source -> dsync -> destination (running Dovecot w/doveadm): the mailboxes are 
the same

You may not care that your users w/100,000 message mailboxes that have been 
cached on their client now have to invalidate that entire cache (and most 
likely re-download all of those messages).

So there is zero argument that, due to IMAP metadata loss, this is something 
that doesn't happen if dsync (or rsync) is used.

michael


> On September 4, 2018 at 9:45 AM Rick Romero  wrote:
> 
> 
> Quoting Robert Schetterer mailto:r...@sys4.de >:
> 
> > > 
> > Am 04.09.2018 um 17:18 schrieb Sami Ketola:
> > 
> > > > > 
> > > > > > > 
> > > > On 4 Sep 2018, at 18.00, Robert Schetterer 
> > > > mailto:r...@sys4.de > wrote:
> > > > 
> > > > Am 04.09.2018 um 16:52 schrieb Sami Ketola:
> > > > 
> > > > > > > > > 
> > > > > > > > > > > 
> > > > > > On 4 Sep 2018, at 17.47, Robert Schetterer 
> > > > > > mailto:r...@sys4.de > wrote:
> > > > > > 
> > > > > > Am 04.09.2018 um 09:41 schrieb Sami Ketola:
> > > > > > 
> > > > > > > > > > > > > 
> > > > > > > imapsync always loses data
> > > > > > > 
> > > > > > > > > > > > > never saw this, be carefull 
> > > > > > > by anounce such myths
> > > > > > 
> > > > > > > > > > > It is a fact. Imapsync works over 
> > > > > > IMAP only and IMAP protocol does not even support transferring all 
> > > > > > data. At most at least UID numbering will be lost and end users 
> > > > > > need to invalidate their local caches.
> > > > > 
> > > > > > > > > but using "looses data" might others think it 
> > > > > also may fail with imap,
> > > > so be more detailed next time
> > > > 
> > > > > > > UID number is also data that is saved on the IMAP 
> > > > backend. If that is lost then it's "lost data".
> > > 
> > > Sami
> > > 
> > > > > Sorry i migrated terrabytes of mail with imapsync and never 
> > > had a
> > problem, it works as designed, also with maildir rsync did a good 
> > job,
> > what never worked as it should was dsync ,cause of bugs ,that may
> > changed now
> > 
> > so this is my answer to topic
> > 
> > "Best way to move mail from one server to another"
> >  
> > 
> > > 
> https://imapsync.lamiral.info/FAQ.d/FAQ.Duplicates.txt
> 
> Seems to use UIDs so that 'data' isn't lost.
> 
> 




Re: Doveadm protocol; dovecot v2.2.10

2018-07-30 Thread Michael Slusarz
> On July 30, 2018 at 2:07 PM David White  wrote:
>
> I’m currently on v2.2.10 and it appears the doveadm protocol command set is 
> limited to just the “mailbox” commands and the http protocol hasn’t been 
> implemented.
> 
> Is the doveadm http protocol still experimental in v2.3.2?

No.

michael


Re: 100% Dovecot MTA Replacement Setup

2018-07-19 Thread Michael Slusarz
> On July 19, 2018 at 9:41 AM David Favor  wrote:
> 
> 
> Working out upgrade of old 1.x + 2.x Dovecot installs to
> latest 2.3.2.1 out of Ubuntu Bionic repositories.
> ___
> 
> https://wiki.dovecot.org/Services suggests Dovecot can
> be used for full mail infrastructure, avoiding the
> complexity of exim4 or other MTA setup/management.
> 
> Let me know if I understand this correctly.
> 
> 1) https://wiki.dovecot.org/Submission can be used to
> listen on port 25 + port 587 (with auth).

This is a proxy only.  For any non-local delivery, you still need a submission 
server to deliver (and queue) mail remotely.  That requires a full SMTP service 
running somewhere.


> 2) https://wiki.dovecot.org/Pigeonhole can be used for
> filtering, including forwarding email to other machines.
> 
> 3) https://wiki.dovecot.org/Pigeonhole/ManageSieve/Configuration
> can be used to forward off machine email, for example flowing
> through a relay service like MailGun, using a simple script
> or service like ESMTPD.
> 
> 4) https://wiki.dovecot.org/LMTP can be used to deposit messages
> into filesystem as Maildir or dbox or mdbox backing stores.

michael


Re: Storing Messages in the cloud

2018-07-11 Thread Michael Slusarz
> On July 10, 2018 at 12:37 PM "M. Balridge"  wrote:

[snip]

> I also imagine the hard-working crew at Timo, Inc. have such things for sale
> to facilitate this with security and good performance, but they won't be
> inexpensive.
> 
> See: http://www.dovecot.fi/products/

More up-to-date link is:
https://www.open-xchange.com/portfolio/dovecot-pro/

It's fairly easy to write support for storing message blobs in object storage.  
In fact, we are working on open sourcing the generic Dovecot object storage 
interface in the near future as part of core that would allow this kind of 
message storage.

But:

1) if you have to store indexes in a separate block storage system, that kind 
of defeats the purpose of having a single storage layer and, alternately
2) using object storage in a block-storage like mode for indexes does not scale 
at all - block storage access patterns do not work well at object storage 
latencies and I/O capacity.

There are several other components on top of generic object storage access that 
are used by Dovecot Pro to address these concerns.  This allows Dovecot Pro's 
object storage support to store all data (messages, indexes, FTS) in a single 
object storage bucket while remaining performant and scalable.

These additional components are expensive to develop and maintain, and mainly 
useful for very large installations, so they will remain part of the commercial 
Dovecot Pro package when the basic object storage support is released.

michael


Re: IMAP_ID_LOG

2018-04-09 Thread Michael Slusarz
ID is an IMAP specific protocol command (RFC 2971).  There is no POP or SMTP 
equivalent.


> On April 9, 2018 at 10:19 AM "j.emerlik"  wrote:
> 
> Hi,
> there in configuration is possibile to set imap_id_log for logging Client 
> ID e.g.:  ID sent: name=Thunderbird, version=52.7.0.
> 
> Is possible to set same but for POP3 or SMTP Auth ?
> 
> Ideally, it would be possible to log in to the database e.g. using 
> postlogin script.
> 
> Regards,
> MattX
> 
> 
> 


Re: `mail_crypt` Doesn't Appear to be Working

2018-02-16 Thread Michael Slusarz
> On February 16, 2018 at 7:31 PM "jorda...@startmail.com 
> mailto:jorda...@startmail.com " wrote:
> 
> 
> Dovecot version: 2.2.22 (fe789d2)
> 

>From the mail_crypt page:

“This feature is available in v2.2.27+”


> I generated an EC key from the page https://wiki2.dovecot.org/Plugins/. 
> For
> reference here's my /etc/dovecot/conf.d/10-mail-crypt.conf file:
> 
> 
> mail_plugins = $mail_plugins mail_crypt
> 
> plugin {
> # mail_crypt_global_private_key =  mail_crypt_global_public_key =  mail_crypt_save_version = 2
> }
> 
> 
> I saw in a previous message on this mailing list that messages can be
> encrypted without the private key, so it's stored elsewhere. :-)
> 
> After restarting dovecot and sending myself a message I found that the 
> message
> was still unencrypted. Nothing in /var/log/dovecot/*.log files or syslog
> indicated any problem loading the plugin (I even made some mistakes with 
> the
> filename beforehand, and errors indicated it was trying to find the 
> plugin).
> 
> In case in matters dovecot was installed as part of the automated iredmail
> install (https://iredmail.org). I didn't modify the dovecot.conf file 
> after
> installation (except for thinking I needed to add `mail_crypt` to 
> `plugins`,
> then figuring I didn't).
> 
> Any help is appreciated.
> 
> Thank you.
> 


Re: Recommended tool for migrating IMAP servers

2017-12-04 Thread Michael Slusarz
> On December 4, 2017 at 8:46 AM Paolo  wrote:
> 
> 
> Il 04/12/2017 14:33, x9p ha scritto:
> >
> >> Can I use this tool even if I do not know the other remote server
> >> typology?
> >>
> > sure. just need both IMAP ports reachable and valid user/pass for both
> > servers.
> I think Davide was asking about dsync. If so, the answer is no: dsync 
> works only when both servers are Dovecot and needs some additional 
> configuration to work through the network (see 
> https://wiki2.dovecot.org/Replication).

This is entirely incorrect.  The source platform for dsync can be ANY IMAP/POP 
server.

The recommended tool for migrating into Dovecot is dsync.  You don't need any 
other tool, and other tools aren't going to preserve state so they are pretty 
much worthless for a real-world in-place migration.

michael


Re: Plugin virtual, Horde BAD IMAP QRESYNC not enabled

2017-11-14 Thread Michael Slusarz
Probably better to get the full protocol debug log from the Horde/IMP side.  
Instructions on how to enable that can be found in imp/config/backends.php. See:
https://github.com/horde/imp/blob/master/config/backends.php#L288

rawlog output below only shows what Dovecot is returning - would be more useful 
to see the entire client round-trip transactions however.


> On November 14, 2017 at 4:15 PM Jakob Schürz  
> wrote:
> 
> 
> Hi there!
> 
> I'm new on this list, so hello to all!
> First i want say, that dovecot is a really great mailserver. I use it
> since many years for my private usecase. I'm planning to setup a new
> Mailserver, so i'm fiddeling around to understand dovecot better and get
> a "perfect" Mailserver. (Linux and Win10) Outlook, k9mail and the
> gmail-app on android.
> 
> I want to leave google behind me, so i'm searching for a good server for
> cloudbased  and selfhosted calendar- and addressbook-server.
> On some discussion in debianforum.de i got the hint, to use horde.
> 
> So i installed horde from pear. Got ActiveSync working with the Android
> and Outlook. Mails, Calendar and Addressbook... very fine.
> 
> But then i run into a gotcha.
> 
> There is a problem  with some mails in dovecots virtual mailboxes.
> I tried a lot to find out, how to debug this. First i thought, it's a
> problem from horde, because the problem is only with horde-client.
> 
> Some Emails are not shown in horde. Exactly, they are not shown in horde
> on dovecots virtual mailboxes (plugin virtual in a separate virtual
> namespace)
> If i try to open this email in its original directory, it gets opened
> without any problem.
> 
> So, when i try to open it from within the virtual mailbox, i get this error:
> ---8<--
> Nov 14 23:29:52 aldebaran dovecot[2495]: imap(jakob): Panic: file
> index-mail-binary.c: line 586 (index_mail_get_binary_stream): assertion
> failed: (mail->data.stream != NULL)
> Nov 14 23:29:52 aldebaran dovecot[2495]: imap(jakob): Error: Raw
> backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x95272) [0x7f671137e272]
> -> /usr/lib/dovecot/libdovecot.so.0(+0x9536d) [0x7f671137e36d] ->
> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f6711314951] ->
> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_get_binary_stream+0x238)
> [0x7f67116b3de8] ->
> /usr/lib/dovecot/libdovecot-storage.so.0(mail_get_binary_stream+0x60)
> [0x7f6711640fa0] ->
> /usr/lib/dovecot/libdovecot-storage.so.0(imap_msgpart_open+0x139)
> [0x7f67116f40f9] -> dovecot/imap [jakob 192.168.0.14 UID
> FETCH](+0x1ebbc) [0x55bef3095bbc] -> dovecot/imap [jakob 192.168.0.14
> UID FETCH](+0x1cfb6) [0x55bef3093fb6] -> dovecot/imap [jakob
> 192.168.0.14 UID FETCH](imap_fetch_more+0x39) [0x55bef30950e9] ->
> dovecot/imap [jakob 192.168.0.14 UID FETCH](cmd_fetch+0x33b)
> [0x55bef3086d9b] -> dovecot/imap [jakob 192.168.0.14 UID
> FETCH](command_exec+0xa5) [0x55bef3092735] -> dovecot/imap [jakob
> 192.168.0.14 UID FETCH](+0x199c2) [0x55bef30909c2] -> dovecot/imap
> [jakob 192.168.0.14 UID FETCH](+0x19a4c) [0x55bef3090a4c] ->
> dovecot/imap [jakob 192.168.0.14 UID FETCH](client_handle_input+0x1b5)
> [0x55bef3090e55] -> dovecot/imap [jakob 192.168.0.14 UID
> FETCH](client_input+0x86) [0x55bef30913c6] ->
> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7f6711392dd2]
> -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x109)
> [0x7f6711394409] ->
> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c)
> [0x7f6711392e6c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38)
> [0x7f6711393018] ->
> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13)
> [0x7f671131ae93] -> dovecot/imap [jakob 192.168.0.14 UID
> FETCH](main+0x328) [0x55bef3083e68] ->
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7f6710f6a2b1]
> -> dovecot/imap [jakob 192.168.0.14 UID FETCH](_start+0x2a) [0x55bef3083fea]
> Nov 14 23:29:52 aldebaran dovecot[2495]: imap(jakob): Fatal: master:
> service(imap): child 2704 killed with signal 6 (core dumps disabled)
> ---8<--
> 
> So i activated rawlog as after-login executeable. The IMAP-dialog when
> opening this email is:
> ---8<--
> 9 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE
> IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS
> THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN
> NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH
> ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE XDOVECOT
> SPECIAL-USE QUOTA ACL RIGHTS=texk] Logged in
> 10 BAD Error in IMAP command SELECT: QRESYNC not enabled (0.000 + 0.000
> secs).
> 11 OK No quota (0.000 + 0.000 secs).
> ---8<--
> 
> If found only one Report for this problem, but on regular imap-folders,
> and there was not really a solution. This report is from 2015.
> On regular folders, i have no problem with this emails, only on virtual
> folders.
> So i think, it is a problem of the virtual-plugin.
> 
> Here is one of this 

Re: IMAP From sort uses only local-part

2017-08-07 Thread Michael Slusarz
> On August 7, 2017 at 3:09 PM Paul wrote:
> 
> As far as I can tell, when I ask Dovecot to sort an IMAP mailbox by the 
> From address, it ignores the part of the address after the '@'. So, for 
> instance, mails from i...@abc.org, i...@xyz.org, and i...@ghi.org are 
> all mingled together in arrival order.
> 
> Is there a way to change this? Thanks!

This is the RFC 5256 compliant behavior.  From is sorted on addr-mailbox.  If 
those are equal:

  If two or more messages exactly match according to the sorting
  criteria, these messages are sorted according to the order in
  which they appear in the mailbox.  In other words, there is an
  implicit sort criterion of "sequence number".

RFC 5256, Section 3.

michael


Re: Conditionally Filter Mails During IMAP Fetch

2017-05-17 Thread Michael Slusarz
> On May 16, 2017 at 1:05 AM Ory Drilon  wrote:
> 
> 
> Hi, is there a way to arbitrarily filter out mails at the moment the
> IMAP request is made, based on properties of the IMAP session and the
> mail itself?
> 
> All the filtering methods I find occur during delivery time.

imapsieve: https://tools.ietf.org/html/rfc6785

Although obviously triggering filtering based on a FETCH itself doesn't make 
much sense and isn't supported by imapsieve (triggering based on flag change 
*caused* by FETCH is supported however).

michael


Re: javamail imap listing

2017-04-19 Thread Michael Slusarz
"A non-empty reference name argument is the name of a mailbox or a level of 
mailbox hierarchy, and indicates the context in which the mailbox name is 
interpreted."

If Dovecot is using "." as the separator in the base level of hierarchy, then 
it correctly is returning nothing for 'LIST / "*"' - since no mailboxes in 
Dovecot live under that base level of hierarchy.

Gmail returns data because it is using "/" as a separator.

If you want Dovecot to return LIST entries for 'LIST "/" "*"', then configure 
the base namespace to use "/" as a separator.  Of course then 'LIST "." "*"' 
would return nothing...

michael

> On April 18, 2017 at 2:38 AM Matthew Broadhead 
> <matthew.broadh...@nbmlaw.co.uk> wrote:
> 
> 
> Thanks Michael.  I have forwarded that link to the Geronimo JavaMail 
> team in case they think of anything their end.
> 
> But in the documentation you sent it seems that Dovecot should respond 
> in the case of
> LIST / "*"
> if my understanding is correct
> 
> Is there any way to adjust this behaviour in the settings?  I am 
> struggling to search for a solution to the problem given the limited 
> information.
> 
> On 18/04/2017 05:46, Michael Slusarz wrote:
> > You probably want to read the description of "reference name argument" to 
> > understand what is happening here.
> >
> > https://tools.ietf.org/html/rfc3501#section-6.3.8
> >
> > michael
> >
> >> On April 17, 2017 at 8:33 AM Matthew Broadhead 
> >> <matthew.broadh...@nbmlaw.co.uk> wrote:
> >>
> >> Hi,
> >>
> >> i am using dovecot-2.2.10-7.el7.x86_64 on
> >> centos-release-7-3.1611.el7.centos.x86_64.
> >>
> >> if i follow this tutorial
> >> https://delog.wordpress.com/2011/05/10/access-imap-server-from-the-command-line-using-openssl/
> >> i can login to my server and successfully list the folders using
> >> tag LIST "" "*"
> >>
> >> *   LIST (\HasNoChildren) "." INBOX
> >> tag OK List completed.
> >>
> >> no folders are listed using
> >> tag LIST / "*"
> >> tag OK List completed.
> >>
> >> when i request a folder listing using JavaMail it similarly sends the
> >> following command and no folders are listed
> >> a97 LIST / "*"
> >> a97 OK List completed.
> >>
> >> if i follow the tutorial again and use my gmail account instead of my
> >> dovecot installation i can successfully list folders using both methods
> >> tag LIST / "*"
> >>
> >> *   LIST (\HasNoChildren) "/" "youtube"
> >> tag OK List completed.
> >>
> >> is there some way to make dovecot list folders when it receives the command
> >> LIST / "*"
> >>
> >> i note that in the listings my dovecot installation has "." in the
> >> middle and gmail has a "/"


Re: javamail imap listing

2017-04-17 Thread Michael Slusarz
You probably want to read the description of "reference name argument" to 
understand what is happening here.

https://tools.ietf.org/html/rfc3501#section-6.3.8

michael

> On April 17, 2017 at 8:33 AM Matthew Broadhead 
>  wrote:
> 
> Hi,
> 
> i am using dovecot-2.2.10-7.el7.x86_64 on
> centos-release-7-3.1611.el7.centos.x86_64.
> 
> if i follow this tutorial
> https://delog.wordpress.com/2011/05/10/access-imap-server-from-the-command-line-using-openssl/
> i can login to my server and successfully list the folders using
> tag LIST "" "*"
> 
> *   LIST (\HasNoChildren) "." INBOX
> tag OK List completed.
> 
> no folders are listed using
> tag LIST / "*"
> tag OK List completed.
> 
> when i request a folder listing using JavaMail it similarly sends the
> following command and no folders are listed
> a97 LIST / "*"
> a97 OK List completed.
> 
> if i follow the tutorial again and use my gmail account instead of my
> dovecot installation i can successfully list folders using both methods
> tag LIST / "*"
> 
> *   LIST (\HasNoChildren) "/" "youtube"
> tag OK List completed.
> 
> is there some way to make dovecot list folders when it receives the command
> LIST / "*"
> 
> i note that in the listings my dovecot installation has "." in the
> middle and gmail has a "/"


Re: How to migration my mails from another server ?

2017-04-10 Thread Michael Slusarz
impasync doesn't preserve IMAP state if Dovecot is the destination server.  You 
should use dsync instead.


> 
> On April 8, 2017 at 3:11 AM Adrian Minta <adrian.mi...@gmail.com> wrote:
> 
> Use imapsync: https://imapsync.lamiral.info/
> 
> On 04/08/2017 12:02 PM, Mik J wrote:
> 
> > > 
> > Hello,
> > 
> > I would like to host my mails and I would like to retrieve my 
> > existing mailbox content from my ISP
> > 
> > My ISP
> > ==
> > I don't have root access on the server
> > The server seem to use Dovecot according to the banner.
> > 
> > My machine
> > ==
> > I have root access on the server
> > I use Dovecot 2.2.21
> > I use Maildir
> > 
> > I read this page multiple times but it's not clear to me
> > https://wiki2.dovecot.org/Migration/Dsync
> > 
> > "Set up configuration for the IMAP server you wish to migrate from"
> > Is it my ISP's server or my server ?
> > In which configuration file should I do this ?
> > 
> > The same for this option
> > dsync_features = empty-header-workaroundwhere is it supposed to be 
> > configured ?
> > 
> > My most important case is quite "simple": the mailboxes (there are 
> > 2 or 3) I want to migrate don't exist on my machine, so there is no such 
> > problems as merge existing mails.
> > Will this migration use imap and retrieve the content of the mails 
> > ? Will it use port 143 or 993 ?
> > I'll use the backup option
> > 
> > I have another case which there are mails on both servers. So I 
> > would like to keep existing mails on my machine.
> > I'll use the sync -1 option ?
> > 
> > Thank you
> > 
> > > 
> --
> Best regards,
> Adrian Minta
> 


--

kind regards,

Michael Slusarz
Senior Sales Engineer


Phone:  +1 (303) 888-1090
Skype:  michael.m.slusarz
Email:  michael.slus...@open-xchange.com mailto:michael.slus...@open-xchange.com
 
Twitter: @openexchange http://twitter.com/openexchange - Facebook: OpenXchange 
https://www.facebook.com/OpenXchange - Web: www.open-xchange.com 
http://www.open-xchange.com
Open-Xchange AG, Rollnerstr. 14, 90408 Nuremberg, District Court Nuremberg HRB 
24738
Managing Board: Rafael Laguna de la Vera, Carsten Dirks, Uwe Reumuth
Chairman of the Board: Richard Seibt

European Office:
Open-Xchange GmbH, Olper Huette 5f, D-57462 Olpe, Germany, District Court 
Siegen, HRB 8718
Managing Directors: Frank Hoberg, Martin Kauss

US Office:
Open-Xchange. Inc., 530 Lytton Avenue, Palo Alto, CA 94301, USA
 
Confidentiality Warning: This message and any attachments are intended only for 
the use of the intended recipient(s), are confidential, and may be privileged. 
If you are not the intended recipient, you are hereby notified that any review, 
retransmission, conversion to hard copy, copying, circulation or other use of 
this message and any attachments is strictly prohibited. If you are not the 
intended recipient, please notify the sender immediately by return e-mail, and 
delete this message and any attachments from your system.


Re: Problem with Dovecot and BlackBerry

2017-04-06 Thread Michael Slusarz
> On April 4, 2017 at 5:07 AM Luca Bertoncello  wrote:
> 
> Hi all,
> 
> i've got a strange behaviour with a BlackBerry Classic Phone (BBOS
> 10.3.2.2876) in combination with Dovecot 2.2.13 while trying to fetch
> mails.
> 
> Before burying myself into debugging sessions, i try to get an
> understanding if the following is a Client- or a Server-specific error
> in the behaviour:
> 
> CIGA8 UID FETCH 10009:10035 (UID FLAGS) (CHANGEDSINCE NOMODSEQ)
> CIGA8 BAD Error in IMAP command UID FETCH: Invalid CHANGEDSINCE modseq.

That's a broken client.

https://tools.ietf.org/html/rfc7162#section-3.1.4.1

"CHANGEDSINCE :  The CHANGEDSINCE FETCH modifier allows
   the client to further subset the list of messages described by the
   sequence set.  The information described by message data items is
   only returned for messages that have a mod-sequence bigger than
   ."

michael


Re: Replacement for antispam plugin

2017-02-10 Thread Michael Slusarz

> On February 10, 2017 at 12:13 PM Ralph Seichter wrote:
> 
> On 10.02.17 18:34, Michael Slusarz wrote:
> > > Can we add an exception for the Trash folder?
> > This is handled in the sieve script. E.g.:
> > 
> > require "environment";
> > if environment "imap.mailbox" "Trash" {
> >  stop;
> > }
> 
> This does not work for me, and I don't really expect it to work either.
> https://tools.ietf.org/html/rfc6785#section-4.4 states:
> 
>  The implementation MUST set the Environment [RFC5183] item "imap.mailbox"
>  to the name of the mailbox that the affected message is in, in the
>  case of existing messages, or is targeted to be stored into, in the
>  case of new messages.
> 
> The message already exists in the Spam folder, hence imap.mailbox should
> be "Spam" instead of "Trash", correct?

Incorrect.

When you move a message to a new mailbox, that is a "new message" event (a new 
UID in the target mailbox is created; the message count increases).  So 
imap.mailbox is set to the name of the *target* mailbox.

> Is there perhaps another way to ensure that manually deleted spam is not
> erroneously learned as ham?
> 
> -Ralph


Re: Replacement for antispam plugin

2017-02-10 Thread Michael Slusarz
> On February 10, 2017 at 9:25 AM George Kontostanos  
> wrote:

[snip]

> I think that this needs some change:
> 
>  # From Spam folder to elsewhere
>   imapsieve_mailbox2_name = *
>   imapsieve_mailbox2_from = Spam
>   imapsieve_mailbox2_causes = COPY
>   imapsieve_mailbox2_before = file:/usr/lib/dovecot/sieve/report-ham.sieve
> 
> When a message from Spam is moved to Trash then the report-ham.sieve is
> being executed.
> 
> Can we add an exception for the Trash folder?

This is handled in the sieve script.  E.g.:

require "environment";
if environment "imap.mailbox" "Trash" {
stop;
}

michael


Re: Simple way to get mailbox size by folder.

2016-12-05 Thread Michael Slusarz

On 12/3/2016 2:53 PM, Aki Tuomi wrote:



On December 3, 2016 at 11:16 PM Vijay Sarvepalli  wrote:


Is there a simple way to get each mailbox size using dovecot's IMAP
interface?  The GETQUOTAROOT and GETQUOTA seems to work with the full
maildir size and not the individual folders.

I am finding a simple way for the webmail client to show usage of each
folder.

Thanks
Vijay


$ doveadm mailbox status -u cmouse all INBOX
INBOX messages=9206 recent=0 uidnext=33115 uidvalidity=1451655531 unseen=7 
highestmodseq=39954  vsize=538582181 guid=d595a62d65818656f72c74be03de

$ doveadm -fjson mailbox status -u cmo...@cmouse.fi all INBOX
[{"mailbox":"INBOX","messages":"9206","recent":"0","uidnext":"33115","uidvalidity":"1451655531","unseen":"7","highestmodseq":"39954","vsize":"538582181","guid":"d595a62d65818656f72c74be03de"}]


If you want an IMAP specific method (rather than doveadm), you are 
stuck with "FETCH 1:* (RFC822.SIZE)".  With the nasty requirement - if 
you want 100% full accuracy - that you need to track responses to ensure 
that each size is only counted once.  Practically speaking this 
shouldn't happen by any reasonable server, but the warning needs to be made.


michael


Re: "anvil: Error: connect limit: disconnection for unknown pid 17659 + ident lmtp/backup@backup.invalid"

2016-07-07 Thread Michael Slusarz
> On July 7, 2016 at 7:45 AM Frank Elsner  wrote:
> 
> On Thu, 7 Jul 2016 14:31:04 +0200 Ralf Hildebrandt wrote:
> 
> > I updated to 2.3.0 today, and now I'm getting these entries in my log:
> >  ^
> 
> Hey, what's that? Typo or secret version?

Development (git master) version.

michael


Re: FTS search used / useful on an IMAP proxy?

2016-06-28 Thread Michael Slusarz
> 
> On June 28, 2016 at 7:07 AM Luca Lesinigo  wrote:
> 
> We are preparing an IMAP proxy based on dovecot-2.2.22, basic proxy 
> functionality is already working and I’m trying to understand if having the 
> FTS service configured on the dovecot *proxy* would be of any use.
> 
> I do suspect it would be useless, I guess dovecot in imap proxy mode just 
> forwards any command to the backend and does not bother to do anything about 
> it, but I’m failing to find a definitive answer in the documentation. If I am 
> guessing correctly, an fts service would only be useful if configured and 
> working on the actual backend.
> 

FTS only makes sense on backend, where the search would be executed.

michael


Re: password expire warning for dovecot users in IMAP/POP login

2016-06-08 Thread Michael Slusarz
The correct way to handle this IMAP-wise would be to return the EXPIRED 
response code (https://tools.ietf.org/html/rfc5530#section-3).  But this 
requires client support to report to the end user.  (And also requires that 
Dovecot would be able to determine from authentication source that the 
credentials are expired, as opposed to incorrect.)

michael

> On June 8, 2016 at 2:51 AM "A.L.E.C"  wrote:
> 
> On 06/08/2016 10:39 AM, mkaw...@redhat.com wrote:
> 
> > To make it happen, no need to add any other configurations on LDAP end
> > once possword policy is correctly set?
> 
> You've got me wrong. I just responded to Aki's question. ALERT feature
> could be used to send the message to the client, but there's no code to
> handle such LDAP password policies/notices yet.
> 
> --
> Aleksander 'A.L.E.C' Machniak
> Kolab Groupware Developer [http://kolab.org]
> 
> Roundcube Webmail Developer [http://roundcube.net]
> 
> ---
> PGP: 19359DC1 @@ GG: 2275252 @@ WWW: http://alec.pl


Re: New feature: HTTP API

2016-05-24 Thread Michael Slusarz
> 
> On May 24, 2016 at 12:20 PM Peer Heinlein 
>  wrote:
> 
> Thanks for the new HTTP API.
> 
> I get the API with some commands up and running, but I'm still not able
> to create folder.
> 
> curl -k -H "Content-Type: application/json" -H "Authorization: Basic
> secret" -d
> 
> '[["mailboxCreate",{"user":"u...@example.org","mailbox":["INBOX/TEST"]},c01]]'
> https://xxx.xxx.xxx.xxx.:8080/doveadm/v1
> 

The identifier is a JSON string (c01) and needs to be in quotes, at a minimum.

> 
> and also
> 
> curl -k -H "Content-Type: application/json" -H "Authorization: Basic
> secret" -d
> 
> '[["mailboxList",{"user":"u...@example.org","mailboxMask":["INBOX/TEST"]},c01]]'
> https://xxx.xxx.xxx.xxx.:8080/doveadm/v1
> 
> doesn't work.
> 
> It /should/ create INBOX/TEST -- but doveadm always says it's "Invalid
> JSON input".
> 
> What am I doing wrong?
> 

michael


Re: Kernel panic in dovecot-ee-lmtp on Debian 8

2016-04-25 Thread Michael Slusarz
Fixed -- Publicly accessible link to commit:

https://github.com/dovecot/pigeonhole/commit/a95b0579b89c13fb3ee5700e76cbe6a4a3e898e0


> On April 25, 2016 at 10:46 AM Stephan Bosch  wrote:
> 
> 
> 
> 
> Op 25-4-2016 om 18:01 schreef Timo Sirainen:
> > On 25 Apr 2016, at 13:48, Tobi  wrote:
> >> Hi list
> >>
> >> I just realized that that I don not receive all mails in my mailbox
> >> (running dovecot-ee 2.2.23.1-1 on Debian 8). On my frontend servers
> >> (running postfix) the queue fills up with mails that cannot be delivered
> >> via lmtp to my backend servers. The error message on the frontend is
> >> "lost connection with backend while sending data"
> >> When I checked the logs on the backend server I found upon every
> >> delivery attempt kernel panics
> >>
> >> Apr 25 12:33:36 mbox1 dovecot: lmtp(REDACTED): Panic: epoll_ctl(del, 18)
> >> failed: Bad file descriptor
> >> Apr 25 12:33:36 mbox1 dovecot: lmtp(REDACTED): Error: Raw backtrace:
> > Can you get a core dump and gdb backtrace? See 
> > http://dovecot.org/bugreport.html#coredumps
> >
> >> /usr/lib/dovecot/libdovecot-sieve.so.0(program_client_run+0xe8)
> >> [0x7faa17d3b308] ->
> >> /usr/lib/dovecot/modules/sieve/lib90_sieve_extprograms_plugin.so(+0x45b8) 
> >> [0x7faa15d855b8]
> >> ->
> >> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_interpreter_continue+0x7c)
> >> [0x7faa17cfa2ac] ->
> >>
> >> the weird thing is that this is not concerning all incoming mails. From
> >> time to time the frontends can deliver messages to my backends. I just
> >> tested it with a mail from work. It arrived via a frontend that has
> >> other mails in queue that could not be delivered so far.
> >>
> >> Does anyone have an idea where I could look for the root cause of this
> >> panic messages?
> > Looks like somehow caused by sieve extprograms.
> 
> Probably this bug:
> 
> https://git.dovecot.net/pigeonhole/core/commit/a95b0579b89c13fb3ee5700e76cbe6a4a3e898e0
> 
> Fixed for upcoming release.
> 
> Regards,
> 
> Stephan.


Re: Content-Enconding

2015-12-04 Thread Michael Slusarz

On 12/4/2015 6:11 AM, Leander Schäfer wrote:


With Apache one may use "mod_deflate" in order to reduce bandwidth by
using e.g. gzip to compress the http traffic. I would like to use
something similar for email traffic between mail clients to dovecote and
postfix. My questions are:


https://tools.ietf.org/html/rfc4978

michael


Re: Interpreting keywords

2015-12-04 Thread Michael Slusarz

On 12/3/2015 12:30 AM, Steffen Kaiser wrote:


On Wed, 2 Dec 2015, Mark Foley wrote:


I've marked several messages in Thunderbird using tags. Tags used are:

0 Important




The messages so tagged appear to have the flag fields set in the IMAP
Maildir:

cur/1449002162.8993_0.mail:2,Sb
cur/1449001929.28087_0.mail:2,Sad

I've looked in dovecot-keywords and find:

$ more dovecot-keywords
0 $label1

I assume these "$label" values are macros that possibly refer to
"Important", "Work", etc., but
where are these $label's defined? Are they defined in the dovecot
configs somewhere or does the
mail client just "know" what these correspond to?


The latter, see
http://superuser.com/questions/983401/import-export-or-retrieve-thunderbird-tags-from-imap-server


IMAP flags are annoying since they are limited to a subset of ASCII 
(e.g. no spaces), thus the need to do flag mappings on the client side.


michael


Re: Content-Enconding

2015-12-04 Thread Michael Slusarz

On 12/4/2015 8:04 AM, Leander Schäfer wrote:

Thank you for your quick feedback. I added it to my plugins in the
config. How can I make sure my mailclients are using it? Is there a way
to check this like I can check headers with additional Firefox plug-in
you may recomment?


I will be used automatically if the client supports it (and Dovecot is 
configured to enable compression).


You'd have to look at raw protocol data to determine whether it is being 
used or not. Like using a packet sniffer.


michael


Re: ESEARCH multiple folders

2015-07-07 Thread Michael Slusarz

On 7/7/2015 12:20 AM, Peter Chiochetti wrote:

FTS-Solr is blazingly fast; yet searching e.g. an archive with
subfolders still is slow; I learned, that this is a feature/bug of the
imap protocol. So I'd like to ask:

Does or will dovecot support the IMAP4 Multimailbox SEARCH Extension
specified in RFC 7377?


The speed (or lack thereof) has very little to do with the IMAP protocol 
limitations. RFC 7377 is not going to appreciably speed this process up; 
you'll probably get almost identical results pipelining all the 
subfolder searches.


This sounds more like an indexing issue.

michael