similar to: managesieve proxying not working

Stephan, Imap/pop shows proxying in mail log, but managesieve differs. Apr 03 03:21:04 pop3-login: Info: proxy(hawk_chen at itsnow.com): started proxying to 10.1.4.6:110: user=<hawk_chen at itsnow.com>, method=PLAIN, rip=218.82.239.224, lip=183.131.52.136, TLS, session=<uJeOZYUvrgDaUu/g> Apr 03 03:21:04 pop3-login: Info: proxy(hawk_chen at itsnow.com): disconnecting 218.82.239.224

I'm using roundcube webmail managesieve plugin. Webmail can login managesieve to a specific mailstore successfully without proxying. Because I have mutiple mailstores, I have to use proxying to redirect the correct mailstores just as imap/pop3. ???? Stephan Bosch ????? 2016-04-03 22:50 ???? Hawk Chen; dovecot ??? Re: ??: Re: managesieve proxying not working Op 3-4-2016 om 16:32 schreef

We have dovecot on a pop/imap server working as a proxy to dovecot on the backend storage servers. This is working fine, but the difficulty is that if I use, for example, avelsieve in squirrelmail, it doesn't know where to connect. I imagine the same problem would exist with sieve-capable mail clients such as KMail, especially since the outside world isn't allowed to connect directly to

Hello all, I've configured a dovecot server in proxy mode. It seems to work well but. I've tested managesieve with squirrelmail and it's working correctly but I can't connect to cyrus sieve server : timsieved Does anybody here have configure a sieve proxy to do this ? Or is it a normal behavior and dovecot sieve proxy can't speak with cyrus sieve ? Thanks. --------------

Hello, On a dovecot 2.0.14 proxy, I found that proxying managesieve works well when using 'starttls' option in pass_attrs, but does not work when using 'ssl' option. The backend server is also dovecot 2.0.14; when using the ssl option, it reports "no auth attempts" in the logs about managesieve-login, and meanwhile the MUA, Thunderbird with sieve plugin, reports

Hello Everyone, I have set up a xen server with 10 physical network devices using the bridge mode of XEN. This is because I want to split and separate the network traffic for security reasons. Maybe the best way is to use pci back hide. But I want to understand what is going on here. For all testings I have only activated eth[0-3]. My first tests were successful. I have created a VM using

Ok, I reinstalled pkg-config from apt-get and now I think it?s all good. Man, PJSIP has been a chore to get working right on this server and on the last. Though the last server wasn?t near the issue this was. Lol I think what happened was that after initial trouble, I ran the ?install prereq? or something like that and it must have did it?s own install of pjsip that sent me down a duplicate path,

I am trying to mount the same partition from a KVM ubuntu 8.04.1 virtual machine and on an ubuntu 8.04.1 host server. I am able to mount the partition just on fine on two ubuntu host servers, they both talk to each other. The logs on both servers show the other machine mounting and unmounting the drive. However, when I mount the drive in the KVM VM I get no communication to the host

Hi to all in the list, we are trying to do some tests lab for a large scale mail system having this requirements: - Scale to maybe 1million users(Only for testing). - Server side filters. - User quotas. - High concurrency. - High performance and High Availability. We plan to test this using RHEL5 and maybe RHEL6. As a storage we are going to use an HP EVA 8400 FC(8 GB/s) We defined this

Hi, Software: AIX 5.3 dovecot-2.0-pigeonhole revision 1234:7b3db97399de with dovecot revision 10621:a978089d090b I'm having problems installing managesieve. I modified the Makefile because DESTDIR was not being found. Here is what I changed to make it work: echo " $(INSTALL_PROGRAM_ENV) $(LIBTOOL) --mode=install $(dovecot_pkglibexecPROGRAMS_INSTALL) '$$p'

Hello Dovecot users, This is a simultaneous release of new versions of Sieve-related software for Dovecot v1.1 and v1.2. Only the Sieve implementation itself has seen significant development. The ManageSieve packages only have small fixes and the ManageSieve patches are updated as usual to match the new Dovecot releases. Changelog Sieve v0.1.5: * Ported the implementation of the Sieve

Hello Dovecot users, This is a simultaneous release of new versions of Sieve-related software for Dovecot v1.1 and v1.2. Only the Sieve implementation itself has seen significant development. The ManageSieve packages only have small fixes and the ManageSieve patches are updated as usual to match the new Dovecot releases. Changelog Sieve v0.1.5: * Ported the implementation of the Sieve

?Hi! ? ?? How must I adjust Dovecot for proxying all users from the Internet to the internal Exchange Mail Server? ?This is my config files (most important): ?? dovecot.conf ? ? ? protocol imap { ??? #listen = *:10143 ??? ssl_listen = 194.0.148.10:993 ? ?? auth default { ?????????? mechanisms = plain login ?????? ? ? ?? ? ? passdb passwd-file { ?? ? ?? ?? args =

I would like to configure Dovecot for POP3S proxying all users from the Internet to the internal Exchange Mail Server. Dovecot proxy have to authenticate the POP3S user (with ldap database) and redirect to exchange server. Is it possible ? Could you give me a dovecot.conf example file ? Regards

We are running dovecot 1.1.8 and are currently running it with 4 master processes (one for each of the protocols: imap, imaps, pop3, pop3s). The idea was to spread out the load so as to not overwhelm any one master. This has worked well. To take it further, we're contemplating running masters across multiple IP addresses, where the host/service name DNS records would be something like this:

Hi, I understand from earlier discussions that the reason dovecot doesn't support proxying of other SASL mechanisms than those which supply the plaintext password is that in general it would be possible to proxy any SASL mechanism since it might protect against man-in-the-middle attacks (which would prevent proxying). However, that has led to choice between letting users use PLAIN (or

Hello, Searching in the archives, I saw the following posting from Timo Sirainen: [Dovecot] Roadmap to future (06 Dec 2007): [...] > Proxying > -------- > > - These could be implemented to v1.2. - Log in normally (no proxying) > if destination IP is the server itself. > > - Support for per-namespace proxying: > > namespace public { > prefix = Public/ >

Hi, I have a "ubuntu10.04 + dovecot-2.0.13" configuration in my server. It works fine with ~50k accounts. Recently I enabled TLS: $ cat /etc/dovecot/dovecot.conf ... # Use SSL ? ssl = yes ... The goal was to provide only IMAPS and POP3S. But Managesieve says "STARTTLS": $ telnet _MY_IP_ 2000 Trying _MY_IP_... Connected to _MY_IP_. Escape character is '^]'.

Hi, the director service have implemented any support for managesieve-login?. I get the error: managesieve-login: Error: proxy: host not given: user=<xxx>, method=PLAIN, ... any workaround? thanks Xavier

I'm reading http://wiki.dovecot.org/ManageSieve/Install . I already use mercurial queues. These are the steps I see to install: hg clone http://hg.dovecot.org/dovecot-1.2 cd dovecot-1.2 hg clone http://hg.rename-it.nl/dovecot-1.2-managesieve-patch .hg/ patches hg qpush Do the steps change? Thanks, Jonathan -------------- next part -------------- A non-text attachment was scrubbed... Name: