trouble with sieve and cyrus murder

[Carlos Ricardo Bernal Veiga]

Good afternoon list

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.

Log of imapd.log when I point the sieve of Expresso webmail to the frontend

FR01 Feb 2 02:46:15 master [4118]: about to exec /usr/cyrus/bin/timsieved
Feb 2 02:46:15 FR01 sieve [4118]: executed
Feb 2 02:46:15 FR01 sieve [4118]: accepted connection
Feb 2 02:46:15 FR01 sieve [4118]: fetching user_deny.db entry for
'carlos.veiga'
Feb 2 02:46:15 FR01 sieve [4118]: login: [10.82.0.90] ^ Carlos Veiga PLAIN
User logged in
this log is Wrong

Log of imapd.log when I point the sieve of Expresso webmail to the backend
where my mailbox is stored

Bck02 Feb 1 20:14:26 master [2493]: about to exec /usr/cyrus/bin/timsieved
Feb 1 20:14:26 bck02 sieve [2493]: executed
Feb 1 20:14:26 bck02 sieve [2493]: accepted connection
Feb 1 20:14:26 bck02 sieve [2493]: fetching user_deny.db entry for
'carlos.veiga'
Feb 1 20:14:26 bck02 sieve [2493]: login: [10.82.0.90] ^ Carlos Veiga PLAIN
User logged in
*Feb 1 20:14:26 bck02 sieve [2493]: entered with bc_action_emit FileLen: 16
*

this log is really OK

And the strange thing is the manual installation Cyrus show the
configuration that i followed, says that works with the backends fine


This is the amount deducted from the Installation Manual Cyrus Murder that
informs the operation of Murder with the Sieve, whose which I followed
Setup for Murder

link:

http://cyrusimap.web.cmu.edu/imapd/install-murder.html

  mupdate cmd = "/usr/cyrus/bin/mupdate" listen = 3905 prefork = 1
  imap cmd = "proxyd" listen = "imap" prefork = 5
  imaps cmd = "proxyd-s" listen = "imaps" prefork = 1
  pop3 cmd = "pop3d" listen = "pop3" prefork = 0
  pop3s cmd = "pop3d-s" listen = "pop3s" prefork = 0
  kpop cmd = "pop3d-k" listen = "kpop" prefork = 0
  nntp cmd = "nntpd" listen = "nntp" prefork = 0
  NNTPS cmd = "nntpd-s" listen = "NNTPS" prefork = 0
  sieve cmd = "timsieved" listen = "sieve" prefork = 0
  lmtp cmd = "lmtpproxyd" listen = "/var/imap/socket/lmtp" prefork = 0

Note that timsieved does not need a proxy daemon, the managesieve protocol
deals with the murder with referrals to the backends internally.



att.
Carlos Bernal Ricardo Veiga
Analyst T.I.
DATAPREV/UDSL/SsLaA
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.andrew.cmu.edu/pipermail/info-cyrus/attachments/20100202/bc99db93/attachment.html