similar to: IMAPC feature description

Hi, I'm considering patching Dovecot to work as a transparent (and virus scanning) IMAP proxy. What is the appropriate feature to extend? (I've considered the following: IMAPC and reverse proxying, with IMAPC looking more promising since it actually parses IMAP communication). Can anyone who is familiar with the IMAPC code recommend what are the most appropriate locations in the

Dear sir, I have to set up a mail gateway which will be explored to Internet and a secure mail server in the Intranet. I need a smart imap proxy in the mail gateway which will fetch the mail from server and present to user through either a stand alone mail client or a web mail client. All authentication is through ldap server. I followed the instructions given in

I'm trying to adapt http://wiki2.dovecot.org/HowTo/ImapcProxy to our Exchange Server, which has LOGINDISABLED on Port 143, and I offering LOGIN on Port 993. How do I go about this? Simply changing imapc_port to: imapc_port = 993 doesnt work: Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS

On 09/11/2017 10:42 AM, Sami Ketola wrote: >> On 11 Sep 2017, at 11.24, Nagy, Attila <bra at fsn.hu> wrote: >> I use dovecot with a broken IMAP server (which doesn't properly implement command pipelining amongst others) as an imapc backend. >> Dovecot issues the above command sequence (SELECT and UID FETCH pipelined), which doesn't work with this server. >>

100% reproducible. User is using alpine to write an email. Continue postponed composition (answering "No" won't erase it)? y -> [>Empty folder! No messages really postponed!<] Can't delete {mproxy.charite.de/ssl/novalidate-cert/user=theusername}postponed-msgs Setup: ====== http://wiki2.dovecot.org/HowTo/ImapcProxy coredump available for further inspection Full

On 09/11/2017 11:14 AM, Aki Tuomi wrote: > > On 11.09.2017 11:59, Nagy, Attila wrote: >> On 09/11/2017 10:42 AM, Sami Ketola wrote: >>>> On 11 Sep 2017, at 11.24, Nagy, Attila <bra at fsn.hu> wrote: >>>> I use dovecot with a broken IMAP server (which doesn't properly >>>> implement command pipelining amongst others) as an imapc backend.

Hello, I try to setup a IMAP proxy for my old Exchange server. Running Dovecot v2.x on Centos 7. So far I follow http://wiki2.dovecot.org/HowTo/ImapcProxy and it seem to work. The only but major thing is with this setup - the communication between proxy and backend is not encrypted. :( To fix this, I changed the config and add: imapc_ssl=imaps imapc_port=993 but it doesnt work, because of

Hello (Timo), yes, I know... maybe it's a bit far fetched, but I do have a use case. Would it be (reasonably easily) possible to implement IMAP ACL support for "imported" imapc namespaces/mailboxes? There is no local directory (like with the virtual plugin) yet... Greetings, Lutz -- Lutz Pre?ler <Lutz.Pressler at SerNet.DE> http://www.SerNet.DE/ SerNet Service

I just committed a very early initial implementation of "imapc" storage backend to v2.1 hg: http://hg.dovecot.org/dovecot-2.1 You can't really do anything except open INBOX and read mails from it, so it's currently only intended for initial testing. It sucks in many ways right now, but I'll be improving it. The idea is that you could set for example: mail_location =

Hi, I am doing a mass migration of users from Cyrus imap on a solaris server to dovecot 1:2.2.9-1ubuntu1 and am getting this weird issue with dsync if I try to do a "full" sync. Debug output below: dsync(user at example.com): Error: Mailbox INBOX: Save commit failed: Mailbox was deleted under us dsync(user at example.com): Debug: brain M: out box 'INBOX'

Hi all, I'm trying to migrate messages from icewarp (merak) mailserver to dovecot via dsync, IMAP migration is looking fine, but I'm unable to migrate pop3 uidls from originating server, probably is something wrong with configuration, but I don't know what. The only documentation i found is on the wiki: http://wiki2.dovecot.org/Migration/Dsync where is bad writen mail_plugins =

Originally I was planning on allowing all kinds of mail settings inside namespace {}, including imapc_* settings. But that's a bit difficult to implement (although I think it will happen some day). So for now I was thinking: imapc foo { host = imap.foo.com master_user = foomaster password = foopass } imapc bar { host = imap.bar.com ... } namespace { prefix = foo/ location =

On 09/11/2017 09:17 AM, Aki Tuomi wrote: > > On 08.09.2017 15:29, Nagy, Attila wrote: >> On 09/08/2017 01:53 PM, Aki Tuomi wrote: >>> On 08.09.2017 14:50, Nagy, Attila wrote: >>>> Hi, >>>> >>>> I've a broken IMAP server, which doesn't support pipelining and fails >>>> on dovecot's attempt to do this ([C] is

On 09/08/2017 01:53 PM, Aki Tuomi wrote: > > On 08.09.2017 14:50, Nagy, Attila wrote: >> Hi, >> >> I've a broken IMAP server, which doesn't support pipelining and fails >> on dovecot's attempt to do this ([C] is dovecot's imapc, [S] is the >> IMAP server): >> >> [C] 24 LOGIN "user" "pass" >> [S] 23 OK

Hi *, I can't find any decent information about the capabilities of imapc in the planned future dovecot releases. As I think about using imapc, I'll just give the two use-cases I see for me. Will this be possible with imapc? 1) One (or more) folders in a mailbox which are proxied? 2) Proxy a whole mailbox _and use the folders in it as shared folders_. That means account X on Server 1

I am trying to backup a gmail account (not the one I am writing from) to dovecot, using doveadm-backup and imapc, but am having ssl connection problems. ted at expectation:~# doveadm backup -D -R -u ted imapc: dsync(ted): Info: imapc(imap.gmail.com:993): Connected to 74.125.71.108:993 (local 10.7.1.179:53852) dsync(ted): Warning: imapc(imap.gmail.com:993): Server disconnected unexpectedly:

Hi, I've a broken IMAP server, which doesn't support pipelining and fails on dovecot's attempt to do this ([C] is dovecot's imapc, [S] is the IMAP server): [C] 24 LOGIN "user" "pass" [S] 23 OK [C] 25 SELECT "INBOX" [C] 23 UID FETCH 2 (INTERNALDATE) [S] 25 OK [S] 23 BAD No mailbox selected Sadly, fixing the server would be a hard task, turning off

Hi, I've got two questions regarding imapc and namespaces: 1) Is there a way of stating, that I only want part of the hierarchy on the end of an imapc connection to be available here? My "problem": On the other end the layout is: INBOX.Shared.{some,nice,folders} If I mirror this into my dovecot hierarchy with prefix "Gemeinsam" I get the following folder structure:

Doing an imapc migration with the pop3 migration plugin, using doveadm backup -R. I occasionally get the following output: dsync(user at domain.tld): Error: imapc(mail01.domain.tld:143): Server disconnected unexpectedly dsync(user at domain.tld): Error: imapc(mail01.domain.tld:143): Server disconnected unexpectedly dsync(user at domain.tld): Error: imapc(mail01.domain.tld:143): Server

This seems to be happening only when using the pop3c plugin. Any advice? root at imap01:/etc/dovecot# doveadm -D -o imapc_user=chat_logs at xxxxxx.com -o 'imapc_password=*******' -o pop3c_user=chat_logs at xxxxxx.com -o 'pop3c_password=*****' backup -u chat_logs at xxxxxx.com -R imapc: doveadm(root): Debug: Loading modules from directory: /usr/lib/dovecot/modules doveadm(root):