Good afternoon list<br><br>I am prospecting the Cyrus Murder with 1 frontend, 1 mupdate and 3 backends, the environment is almost all in full operation, I already create, alter, delete, and modify the mailboxes by the frontend, I have tested it with Evolution (worked OK), ThunderBird (worked OK too ) and a Webmail called Expresso, it's ok too, but I'm having a trouble with the Sieve (sieve is a scripting language that Webmail Expresso uses to create filters with the mailboxes in cyrus), Expresso webmail has an option to direct requests from the sieve to a cyrus server where the mailboxes are stored, my test was to create an account on the backend, eg "carlos.veiga", to point the Sieve requests of Webmail Expresso to the Frontend of cyrus murder, the frontend failed to pass the request to the respective backend where the mailbox "carlos.veiga" is stored, when I point the sieve requests directly to the backend where my mailbox is stored, the filters are created with no problem, i will post the logs.<br>
<br>Log of imapd.log when I point the sieve of Expresso webmail to the frontend<br><br>FR01 Feb 2 02:46:15 master [4118]: about to exec /usr/cyrus/bin/timsieved<br>Feb 2 02:46:15 FR01 sieve [4118]: executed<br>Feb 2 02:46:15 FR01 sieve [4118]: accepted connection<br>
Feb 2 02:46:15 FR01 sieve [4118]: fetching user_deny.db entry for 'carlos.veiga'<br>Feb 2 02:46:15 FR01 sieve [4118]: login: [10.82.0.90] ^ Carlos Veiga PLAIN User logged in<br>this log is Wrong<br><br>Log of imapd.log when I point the sieve of Expresso webmail to the backend where my mailbox is stored<br>
<br>Bck02 Feb 1 20:14:26 master [2493]: about to exec /usr/cyrus/bin/timsieved<br>Feb 1 20:14:26 bck02 sieve [2493]: executed<br>Feb 1 20:14:26 bck02 sieve [2493]: accepted connection<br>Feb 1 20:14:26 bck02 sieve [2493]: fetching user_deny.db entry for 'carlos.veiga'<br>
Feb 1 20:14:26 bck02 sieve [2493]: login: [10.82.0.90] ^ Carlos Veiga PLAIN User logged in<br><b style="background-color: rgb(255, 0, 0);">Feb 1 20:14:26 bck02 sieve [2493]: entered with bc_action_emit FileLen: 16 </b><span style="background-color: rgb(255, 0, 0);"></span><br>
<br>this log is really OK<br>
<br>And the strange thing is the manual installation Cyrus show the configuration that i followed, says that works with the backends fine<br><br><br>This is the amount deducted from the Installation Manual Cyrus Murder that informs the operation of Murder with the Sieve, whose which I followed<br>
Setup for Murder<br><br>link:<br><br><a href="http://cyrusimap.web.cmu.edu/imapd/install-murder.html" target="_blank">http://cyrusimap.web.cmu.edu/imapd/install-murder.html</a><br><br> mupdate cmd = "/usr/cyrus/bin/mupdate" listen = 3905 prefork = 1<br>
imap cmd = "proxyd" listen = "imap" prefork = 5<br> imaps cmd = "proxyd-s" listen = "imaps" prefork = 1<br> pop3 cmd = "pop3d" listen = "pop3" prefork = 0<br>
pop3s cmd = "pop3d-s" listen = "pop3s" prefork = 0<br> kpop cmd = "pop3d-k" listen = "kpop" prefork = 0<br> nntp cmd = "nntpd" listen = "nntp" prefork = 0<br>
NNTPS cmd = "nntpd-s" listen = "NNTPS" prefork = 0<br> sieve cmd = "timsieved" listen = "sieve" prefork = 0<br> lmtp cmd = "lmtpproxyd" listen = "/var/imap/socket/lmtp" prefork = 0<br>
<br>Note that timsieved does not need a proxy daemon, the managesieve protocol deals with the murder with referrals to the backends internally.<br><br><br><br>att.<br>Carlos Bernal Ricardo Veiga<br>Analyst T.I.<br>DATAPREV/UDSL/SsLaA<br>