On Sun, 31 Aug 2003, Ken Murchison wrote:
> > Also, what recommendations are there for running squatter? Should I run
> > it daily? What would an entry in cyrus.conf for squatter look like?
>
># index mailing list archives
>squat cmd="squatter archive.*" at=0415
>
>
> Note that
Andrew Morgan wrote:
The man page for squatter says:
Any messages appended to the mailbox after squatter is run, will NOT be
included in the index.
NOTE: Messages and mailboxes that have not been indexed CAN still be
SEARCHed, just not as quickly as those with a SQUAT index.
One thing is not e
Andrew Morgan wrote:
Does the sieve vacation module use the duplicate delivery database to
track which email addresses it has already responded to?
Yes.
By default I create vacation messages for my users through a web interface
and it sets the vacation history to 7 days. However, I am currentl
The man page for squatter says:
Any messages appended to the mailbox after squatter is run, will NOT be
included in the index.
NOTE: Messages and mailboxes that have not been indexed CAN still be
SEARCHed, just not as quickly as those with a SQUAT index.
One thing is not entirely clear to me.
I've had this problem as well..but with IMAP (never checked sieve)..
The issue is cyrus imap checks the domain and if it is not the "Default"
domain or listed in the loginrealms: config line in /etc/imapd.conf.
However, the check seems to only occur when using a sasl mech other than
login with IMA
Does the sieve vacation module use the duplicate delivery database to
track which email addresses it has already responded to?
By default I create vacation messages for my users through a web interface
and it sets the vacation history to 7 days. However, I am currently
pruning my duplicate deliv
The difference is that IMAP and POP have their own plaintext login
commands (LOGIN and USER/PASS respecitively) which your clients are
probably using. Even though SASL is still used to veirfy the passwords,
these commands have no concept of realms. MANAGESIEVE on the other
hand, has no built-
I have a virtual domain system set up under Debian Woody with exim, ldap
as an auth backend, and cyrus 2.1.15 (backported to Woody). I am using
althierarchy and unixsep. Saslauthd is configured to use PAM as an
authentication mechanism.
Mailboxes are created with the name "[EMAIL PROTECTED]". D
Gary C. New wrote:
I am gearing up to migrate our systems to a high availability email
topology and was wondering what the current solutions are to provide
such an architecture?
I need a solution that synchronizes/mirrors/replicates user mail stores
across several physical servers for redundenc