Re: what is better ?
Wed, 13 Nov 2002, Simon Matter ÐÉÓÁÌ(Á): > Squirrelmail with the avelsieve plugin is really cool. This is what I'm > using because I have squirrelmail installed. If there is no Squirrel, > Smartsieve looks good too. Thanks, I'll give it a try... Best regards, Andrei V. Loukinykh , Evpatoria Ukrtelecom ISP, +380 6569 29376 ~~~ "UNIX is like a vigvam - no Windows, no Gates and an Apache inside"
to live or to fight
Well, now I have Cyrus installed (yet not completely tested though) The only 2 things left, which are bothering me now , 2 king of messages in syslog: 1: "lmtpd[10260]: DBERROR db4: 9 lockers" 2: "master: setrlimit: Unable to set file descriptors limit to -1: Operation not permitted" As I explored this list, the first is related to Berkeley DB (4.0.14) bug, since its counters got incremented ... I've read on sleepycat, that it had been fixed in 4.1. , but this version of DB is not supported by Cyrus.. The second seemes to be kernel , or cyrus-kernel problem ( or not? ), and as I found in list I shouldn't pay much attention to it too.. But, may be there's something I can do to fix those bugs , to live with clean logs...? Best regards, Andrei V. Loukinykh , Evpatoria Ukrtelecom ISP, +380 6569 29376 ~~~ "UNIX is like a vigvam - no Windows, no Gates and an Apache inside"
Re: what is better ?
Andrei Loukinykh schrieb: > > Since Websieve wasn't updated since 2001, cat it still work with > the last Cyrus ( 2.1.9 ), or it is better to get something newer > (smartsieve...) ? Has anyone had an experience? Squirrelmail with the avelsieve plugin is really cool. This is what I'm using because I have squirrelmail installed. If there is no Squirrel, Smartsieve looks good too. Simon > > Best regards, > Andrei V. Loukinykh , Evpatoria Ukrtelecom ISP, +380 6569 29376 > ~~~ > "UNIX is like a vigvam - no Windows, no Gates and an Apache inside"
what is better ?
Since Websieve wasn't updated since 2001, cat it still work with the last Cyrus ( 2.1.9 ), or it is better to get something newer (smartsieve...) ? Has anyone had an experience? Best regards, Andrei V. Loukinykh , Evpatoria Ukrtelecom ISP, +380 6569 29376 ~~~ "UNIX is like a vigvam - no Windows, no Gates and an Apache inside"
Re: ipurge -s option?
Quoting [EMAIL PROTECTED]: > What about the following? I was thinking it might be nice if ipurge > had a -s option for skipping "special" messages. That is, if you > flag certain messages as special[*], then run ipurge -s on that > folder, these flagged messages would not be deleted even if they > otherwise matched the criteria for being removed. Thoughts? > > Amos > > *-- some clients refer to flagged messages as "special" or > "important". I'm not sure if there's an official name for this. I doubt that a patch which implemented this would be refused. Simply checking for \Flagged _shouldn't_ be that hard. In fact, I could see myself using this option when purging newsgroups (eg, keep articles which are flagged as keepers). -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
Re: Sieve not processing
Note that if you use a -m with the deliver program (as invoked from sendmail, procmail, etc), it appears to bypass Sieve. Hope that helps.. On Tue, 12 Nov 2002 [EMAIL PROTECTED] wrote: > I used the smartsieve application from source forge to create a vacation script, > only nothing happens. :( I don't see anything in the logs, etc >
ipurge -s option?
What about the following? I was thinking it might be nice if ipurge had a -s option for skipping "special" messages. That is, if you flag certain messages as special[*], then run ipurge -s on that folder, these flagged messages would not be deleted even if they otherwise matched the criteria for being removed. Thoughts? Amos *-- some clients refer to flagged messages as "special" or "important". I'm not sure if there's an official name for this.
Re: Unable to auth (saslauthd on Red Hat 7.3)
On Tue, 12 Nov 2002, Jonathan Marsden wrote: > The socket location used by cyrus-imapd is the one compiled into the > libsasl2.so shared library, as far as I can tell it is not directly > set or used within the imapd code at all. So there is no option to > imapd to change it, either at run-time or at compile-time -- you'd > need to recompile the sasl libraries. This is not true. Cyrus IMAP will pass options to the sasl library that start with the sasl_ prefix. The sasl library has an option "saslauthd_path". So, in imapd.conf you can set something like: sasl_saslauthd_path: /somewhere/else Be sure to include the trailing /mux. Also, this isn't as globally useful as you might think, since saslauthd and libsasl should always agree on the default location. -Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper
Re: Unable to auth (saslauthd on Red Hat 7.3)
On 12 Nov 2002, Gerke Kok writes: > This was what I feared all along: the cyrus-imap server looked at: > /var/state/saslauthd/mux iso /var/run/saslauthd/mux. Don't realy > know why. It might be because I had tried to install the two > (cyrus-sasl and cyrus-imapd) from source first. This must have > messed it up. It's a pity I could not find the setting/option that > I would need to give to cyrus-imapd where to find the mux-socket. I > was looking for it, see. It sounds as though you have solved your problem (by using RPMs for both cyrus-sasl and cyrus-imapd), but just for completeness: The socket location is a runtime option for saslauthd, you can set it (using the Red Hat RPM version) in /etc/init.d/saslauthd or (better) by adding a line to /etc/sysconfig/saslauthd that says something like: SOCKET=/whatever/path/you/want/mux Or, for debugging purposes, you can set it "by hand" using the -m option to saslauthd directly. The socket location used by cyrus-imapd is the one compiled into the libsasl2.so shared library, as far as I can tell it is not directly set or used within the imapd code at all. So there is no option to imapd to change it, either at run-time or at compile-time -- you'd need to recompile the sasl libraries. I suspect that your imapd was loading a copy of the sasl libraries from /usr/local/lib (where you compiled things by hand earlier) instead of the sasl libs from /usr/lib, and that was how the two pieces got out of sync with each other? Did you put /usr/local/lib into the /etc/ld.so.conf file, perhaps? > Thanks again: it works nicely! Good :-) Take care, Jonathan -- Jonathan Marsden| Internet: [EMAIL PROTECTED] | Making electronic 1252 Judson Street | Phone: +1 (909) 795-3877 | communications work Redlands, CA 92374 | Fax: +1 (909) 795-0327 | reliably for Christian USA | http://www.xc.org/jonathan| missions worldwide
Re: Unable to auth (saslauthd on Red Hat 7.3)
Hi Jonathan, nice to hear from you this way :-) This was what I feared all along: the cyrus-imap server looked at: /var/state/saslauthd/mux iso /var/run/saslauthd/mux. Don't realy know why. It might be because I had tried to install the two ( cyrus-sasl and cyrus-imapd) from source first. This must have messed it up. It's a pity I could not find the setting/option that I would need to give to cyrus-imapd where to find the mux-socket. I was looking for it, see. Thanks again: it works nicely! wkr, Gerke Jonathan Marsden wrote: Hi Gerke, On 12 Nov 2002, Gerke Kok writes: I have a problem to get Cyrus running on RedHat 7.3. I used the rpm's provided by Simon Matter. They install nicely. But I keep getting errors on the authentication ( via saslauthd) Could anyone give any pointers to a solution, please? This is what syslog sais: imapd[28564]: cannot connect to saslauthd server: No such file or directory imapd[28564]: badlogin: localhost.localdomain[127.0.0.1] plaintext gerkek SASL(-1): generic failure: checkpass failed Is saslauthd actually running? If it is, what socket is it listening on (should be /var/run/saslauthd/mux)? Is /etc/sysconfig/saslauthd set the way you want it (ie. for whatever actual authentication method you want to use on this server)? These RPMs work fine for us on Red Hat 7.2 and 7.3 here (modified to use the CVS code for virtual domain support in some cases). You might want to include the contents of /etc/imapd.conf, /etc/sysconfig/saslauthd, and /usr/lib/sasl*/*.conf as well as the exact versions of the cyrus-imapd and cyrus-sasl-* RPMs you are using. Jonathan -- Jonathan Marsden | Internet: [EMAIL PROTECTED] | Making electronic 1252 Judson Street | Phone: +1 (909) 795-3877 | communications work Redlands, CA 92374 | Fax: +1 (909) 795-0327 | reliably for Christian USA | http://www.xc.org/jonathan | missions worldwide ( cannot connect to saslauthd server: No such file or directory ( just for the desperate :-) to find this))
Re: Unable to auth
Okay, then imapd and saslauthd are in disagreement about where the socket should be. Run truss/strace on imapd and find out where its trying to open the socket insted of /var/run/saslauthd/mux -Rob On Tue, 12 Nov 2002, Gerke Kok wrote: > Yes, I have. I even tested it with the testsaslauthd program that comes > with the source of curys-sasl. The socket is there ( > /var/run/saslauth/mux) but that does not help. > Please, I'd love this would all work. I've been digging for two days now... > wkr, > Gerke > > Rob Siemborski wrote: > > >Have you started the saslauthd daemon? > > > >-Rob > > > >On Tue, 12 Nov 2002, Gerke Kok wrote: > > > > > > > >>Hello, > >>I have a problem to get Cyrus running on RedHat 7.3. I used the rpm's > >>provided by Simon Matter. They install nicely. But I keep getting errors > >>on the authentication ( via saslauthd) Could anyone give any pointers to > >>a solution, please? > >>This is what syslog sais: > >>imapd[28564]: cannot connect to saslauthd server: No such file > >> or directory > >>imapd[28564]: badlogin: localhost.localdomain[127.0.0.1] > >> plaintext gerkek SASL(-1): generic failure: checkpass failed > >> > >>wkr, > >>Gerke > >> > >> > >> > >> > >> > > > >-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > >Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 > >Research Systems Programmer * /usr/contributed Gatekeeper > > > > > > > > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper
Re: Unable to auth (saslauthd on Red Hat 7.3)
Hi Gerke, On 12 Nov 2002, Gerke Kok writes: > I have a problem to get Cyrus running on RedHat 7.3. I used the > rpm's provided by Simon Matter. They install nicely. But I keep > getting errors on the authentication ( via saslauthd) Could anyone > give any pointers to a solution, please? > This is what syslog sais: > imapd[28564]: cannot connect to saslauthd server: No such file > or directory > imapd[28564]: badlogin: localhost.localdomain[127.0.0.1] > plaintext gerkek SASL(-1): generic failure: checkpass failed Is saslauthd actually running? If it is, what socket is it listening on (should be /var/run/saslauthd/mux)? Is /etc/sysconfig/saslauthd set the way you want it (ie. for whatever actual authentication method you want to use on this server)? These RPMs work fine for us on Red Hat 7.2 and 7.3 here (modified to use the CVS code for virtual domain support in some cases). You might want to include the contents of /etc/imapd.conf, /etc/sysconfig/saslauthd, and /usr/lib/sasl*/*.conf as well as the exact versions of the cyrus-imapd and cyrus-sasl-* RPMs you are using. Jonathan -- Jonathan Marsden| Internet: [EMAIL PROTECTED] | Making electronic 1252 Judson Street | Phone: +1 (909) 795-3877 | communications work Redlands, CA 92374 | Fax: +1 (909) 795-0327 | reliably for Christian USA | http://www.xc.org/jonathan| missions worldwide
Re: Unable to auth
Yes, I have. I even tested it with the testsaslauthd program that comes with the source of curys-sasl. The socket is there ( /var/run/saslauth/mux) but that does not help. Please, I'd love this would all work. I've been digging for two days now... wkr, Gerke Rob Siemborski wrote: Have you started the saslauthd daemon? -Rob On Tue, 12 Nov 2002, Gerke Kok wrote: Hello, I have a problem to get Cyrus running on RedHat 7.3. I used the rpm's provided by Simon Matter. They install nicely. But I keep getting errors on the authentication ( via saslauthd) Could anyone give any pointers to a solution, please? This is what syslog sais: imapd[28564]: cannot connect to saslauthd server: No such file or directory imapd[28564]: badlogin: localhost.localdomain[127.0.0.1] plaintext gerkek SASL(-1): generic failure: checkpass failed wkr, Gerke -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper
Re: Cyrus case issues
in lib/auth_unix.c:
/* Copy the string and look up values in the allowedchars array above.
* If we see any we don't like, reject the string.
*/
sawalpha = 0;
for(p = retbuf; *p; p++) {
switch (allowedchars[*(unsigned char*) p]) {
case 0:
return NULL;
case 2:
sawalpha = 1;
/* FALL THROUGH */
+case 3:
+ sawalpha = 1;
+ *p = tolower((unsigned char) *p);
default:
;
}
}
Gardiner Leverett wrote:
A while back, I sent mail to the list about our efforts to get
Cyrus/SASL/LDAP all working together with FreeBSD.
Okay, that all works, but now we have a different issue:
We were transitioning users from Cyrus 1.5.19 (on Solaris)
to 2.1.9 (on FreeBSD). The users have been connecting via
IMAP to the new server with their user ids in uppercase.
The problem is this:
On the new machine, a user mailbox is "foobar" for example.
The user connects (through the client) as "FOOBAR". SASL
authenticates the user fine, but the user can't see the INBOX
or any other folders. If the user connects as "foobar", SASL
authenticates correctly, and the user can see their mailbox.
I can test the saslauths with upper and lower case fine,
and I can test (using imtest) to connect to the Cyrus server,
but what can I do about this client side case issue?
Is there something in the Cyrus code that I can turn off or
turn on to recognize an connection from "FOOBAR" to the
mailbox "foobar" as the same?
--
Gardiner Leverett[EMAIL PROTECTED]
Merit Network, Inc.Phone: 734-647-9888
4251 Plymouth Rd., Suite 2000 Ann Arbor, MI 48105-2785
http://www.merit.edu
Re: Cyrus case issues
.
/* Map of which characters are allowed by auth_canonifyid.
* Key: 0 -> not allowed (special, ctrl, or would confuse Unix or imapd)
* 1 -> allowed, but requires an alpha somewhere else in the string
* 2 -> allowed, and is an alpha
*
* At least one character must be an alpha.
*
* This may not be restrictive enough.
* Here are the reasons for the restrictions:
*
* &forbidden because of MUTF-7. (This could be fixed.)
* :forbidden because it's special in /etc/passwd
* /forbidden because it can't be used in a mailbox name
* * % forbidden because they're IMAP magic in the LIST/LSUB commands
* ?it just scares me
* ctrl chars, DEL
* can't send them as IMAP characters in plain folder names, I think
* 80-FF forbidden because you can't send them in IMAP anyway
* (and they're forbidden as folder names). (This could be fixed.)
*
* + and - are *allowed* although '+' is probably used for userid+detail
* subaddressing and qmail users use '-' for subaddressing.
*
* Identifiers don't require a digit, really, so that should probably be
* relaxed, too.
*/
static char allowedchars[256] = {
/* 0 1 2 3 4 5 6 7 8 9 A B C D E F */
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, /* 00-0F */
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, /* 10-1F */
#ifdef ENABLE_EDUNET
0, 1, 1, 1, 1, 0, 0, 1, 1, 1, 0, 1, 1, 1, 1, 0, /* 20-2F */
1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 0, 1, 1, 1, 1, 0, /* 30-3F */
1, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, /* 40-4F */
3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 1, 1, 1, 1, 1, /* 50-5F */
#else
1, 1, 1, 1, 1, 0, 0, 1, 1, 1, 0, 1, 1, 1, 1, 0, /* 20-2F */
1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 0, 1, 1, 1, 1, 0, /* 30-3F */
1, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, /* 40-4F */
2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 1, 1, 1, 1, 1, /* 50-5F */
#endif
1, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, /* 60-6F */
2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 1, 1, 1, 1, 0, /* 70-7F */
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
};
/*
* Convert 'identifier' into canonical form.
* Returns a pointer to a static buffer containing the canonical form
* or NULL if 'identifier' is invalid.
*
* XXX If any of the characters marked with 0 are valid and are
cropping up,
* the right thing to do is probably to canonicalize the identifier to two
* representations: one for getpwent calls and one for folder names. The
* latter canonicalizes to a MUTF7 representation.
*/
char *auth_canonifyid(identifier, len)
const char *identifier;
size_t len;
{
static char retbuf[81];
#ifndef ENABLE_EDUNET
struct group *grp;
#endif
char sawalpha;
char *p;
if(!len) len = strlen(identifier);
if(len >= sizeof(retbuf)) return NULL;
if (strcasecmp(identifier, "anonymous") == 0) {
return "anonymous";
}
if (strcasecmp(identifier, "anybody") == 0 ||
strcasecmp(identifier, "anyone") == 0) {
return "anyone";
}
memcpy(retbuf, identifier, len);
retbuf[len] = '\0';
/* This used to be far more restrictive, but many sites seem to
ignore the
* ye olde Unix conventions of username. Specifically, we used to
* - drop case on the buffer
* - disallow lots of non-alpha characters ('-', '_', others)
* Now we do neither of these, but impose a very different policy
based on
* the character map above.
*/
if (!strncmp(retbuf, "group:", 6)) {
#ifndef ENABLE_EDUNET
grp = getgrnam(retbuf+6);
if (!grp) return 0;
strcpy(retbuf+6, grp->gr_name);
#endif
return retbuf;
}
/* Copy the string and look up values in the allowedchars array above.
* If we see any we don't like, reject the string.
*/
sawalpha = 0;
for(p = retbuf; *p; p++) {
switch (allowedchars[*(unsigned char*) p]) {
case 0:
return NULL;
case 2:
sawalpha = 1;
/* FALL THROUGH */
#ifdef ENABLE_EDUNET
case 3:
sawalpha = 1;
*p = tolower((unsigned char) *p);
#endif
default:
;
}
}
if (!sawalpha) return NULL; /* has to be one alpha char */
return retbuf;
}
Gardiner Leverett wrote:
Gardiner Leverett wrote:
The problem is this:
On the new machine, a user mailbox is "foobar" for example.
The user connects (through the client) as "FOOBAR". SASL
authenticates the user fine, but the user can't see the INBOX
or any other folders. If the user connects as "foobar", SASL
authenticates correctly, and the user can see their mailbox.
On
Re: Unable to auth
Have you started the saslauthd daemon? -Rob On Tue, 12 Nov 2002, Gerke Kok wrote: > Hello, > I have a problem to get Cyrus running on RedHat 7.3. I used the rpm's > provided by Simon Matter. They install nicely. But I keep getting errors > on the authentication ( via saslauthd) Could anyone give any pointers to > a solution, please? > This is what syslog sais: > imapd[28564]: cannot connect to saslauthd server: No such file > or directory > imapd[28564]: badlogin: localhost.localdomain[127.0.0.1] > plaintext gerkek SASL(-1): generic failure: checkpass failed > > wkr, > Gerke > > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper
Unable to auth
Hello, I have a problem to get Cyrus running on RedHat 7.3. I used the rpm's provided by Simon Matter. They install nicely. But I keep getting errors on the authentication ( via saslauthd) Could anyone give any pointers to a solution, please? This is what syslog sais: imapd[28564]: cannot connect to saslauthd server: No such file or directory imapd[28564]: badlogin: localhost.localdomain[127.0.0.1] plaintext gerkek SASL(-1): generic failure: checkpass failed wkr, Gerke
Re: Cyrus case issues
Gardiner Leverett wrote: > The problem is this: > On the new machine, a user mailbox is "foobar" for example. > The user connects (through the client) as "FOOBAR". SASL > authenticates the user fine, but the user can't see the INBOX > or any other folders. If the user connects as "foobar", SASL > authenticates correctly, and the user can see their mailbox. One other note: if the user is using Outlook and they connect as uppercase, Cyrus will CREATE a new mailbox for the uppercase user. When I tried using Netscape, this did not happen. I don't know if it's a config issue with Outlook, but either way, the mailbox is created, and the user FOOBAR has access to the new mailbox "FOOBAR" and not "foobar".
Cyrus case issues
A while back, I sent mail to the list about our efforts to get Cyrus/SASL/LDAP all working together with FreeBSD. Okay, that all works, but now we have a different issue: We were transitioning users from Cyrus 1.5.19 (on Solaris) to 2.1.9 (on FreeBSD). The users have been connecting via IMAP to the new server with their user ids in uppercase. The problem is this: On the new machine, a user mailbox is "foobar" for example. The user connects (through the client) as "FOOBAR". SASL authenticates the user fine, but the user can't see the INBOX or any other folders. If the user connects as "foobar", SASL authenticates correctly, and the user can see their mailbox. I can test the saslauths with upper and lower case fine, and I can test (using imtest) to connect to the Cyrus server, but what can I do about this client side case issue? Is there something in the Cyrus code that I can turn off or turn on to recognize an connection from "FOOBAR" to the mailbox "foobar" as the same? -- Gardiner Leverett [EMAIL PROTECTED] Merit Network, Inc. Phone: 734-647-9888 4251 Plymouth Rd., Suite 2000 Ann Arbor, MI 48105-2785 http://www.merit.edu
Re: Migrating from BSD style mailbox to Cyrus v2
Thanks for the tip that's already half of the work done, now there is still the password from the source (UW-IMAP) IMAP server... Also how will Cyrus know which user I am copying the folders to ? Will it still prompt for a username and then simply skip the password ? Regards Marc |+-> || | || Henrique de Moraes Holschuh| || <[EMAIL PROTECTED]> | || Sent by: | || [EMAIL PROTECTED]| || ew.cmu.edu | || | || | || 11/12/02 05:09 PM | || | |+-> >---| | | | To: [EMAIL PROTECTED] | | cc: [EMAIL PROTECTED] | | Subject: Re: Migrating from BSD style mailbox to Cyrus v2 | >---| On Tue, 12 Nov 2002, [EMAIL PROTECTED] wrote: > The best would be to somehow fully automate this withtout requiring > passwords and such, does someone have any experience doing that, I am sure > it is somehow possible to do that but how ? We are surely not the only ones > migrating to the great Cyrus. 1. lock down the network 2. set sasl_pwcheck_method: alwaystrue in imapd.conf That will turn off all password verification. You may try to do a direct conversion, though. Good luck there... -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
Re: Migrating from BSD style mailbox to Cyrus v2
On Tue, 12 Nov 2002, [EMAIL PROTECTED] wrote: > The best would be to somehow fully automate this withtout requiring > passwords and such, does someone have any experience doing that, I am sure > it is somehow possible to do that but how ? We are surely not the only ones > migrating to the great Cyrus. 1. lock down the network 2. set sasl_pwcheck_method: alwaystrue in imapd.conf That will turn off all password verification. You may try to do a direct conversion, though. Good luck there... -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
Migrating from BSD style mailbox to Cyrus v2
Hello,
We are currently going to migrate from our current mail server, an OpenBSD
box running UW-IMAP and therfore having BSD style mailboxes to a Cyrus v2
mail server.
We currently tested mbxcvt and mailutil from the UW-IMAP utils to
copy/transfer all the mails to the new Cyrus mail server but the problem
that we've encoutered is that using for example:
mailutil transfer '{oldmailserver/imap}' '{newmailserver/imap}'
is that we need to enter the user's name and password. This gives us
problems because:
1) we don't know the user's password
2) we have a LOT of users to migrate
The best would be to somehow fully automate this withtout requiring
passwords and such, does someone have any experience doing that, I am sure
it is somehow possible to do that but how ? We are surely not the only ones
migrating to the great Cyrus.
It would be possible for us to copy all the users mailboxes to the new
mailserver if that helps. The user's INBOX is in /var/mail and the user's
folders are in /home/username
Regards
Marc
Full hash dir & sieve
Hello all, Is there any reason for not including the case of full hash dir in user_deletesieve ? Thanks Nikos Voutsinas
Re: Re: cluster howto ?
On Tue, 12 Nov 2002, [iso-8859-1] [EMAIL PROTECTED] wrote: > Linux :). what about using Berkeley DB cluster facility ? Since databases don't hold all of the information (namely, mailboxes are all made up of flat message files and some custom index files), this isn't good enough. -Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper
Cyrus imap and AIX 5L
Anyone has any experience on running Cyrus IMAP on AIX 5L? -- -- Leena Heino (liinu at uta.fi)
Re: cluster howto ?
> Quoting "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>: > > > > On Sun, 10 Nov 2002, [iso-8859-1] [EMAIL PROTECTED] wrote: > > > > > > > hello, howto cluster for load balancing cyrus imap server ? > > > > > > There is doc/install-murder.html, but I suspect that isn't really what > > you > > > want. > > > > :) yes isn't what i want. I mean it is possible to split across several > > server the same mailboxdb (shared file system? CXFS?). > > I've never tried it, but I've maintained all along that CXFS *should* work. > > What platforms are you using? All SGI, or a mixture of SGI and Sun? Linux :). what about using Berkeley DB cluster facility ?
RE: websieve 0.61/can only connect as cyrus admin user/error says no error...?
Hi Darrell. Using funclib.cyrus in place of funclib.pl will solve the 'System Error: No Errors' problem. I had a similar problem with Sieve apparently not replying, too. Cyrus' deliver program was adding an erroneous second Return-Path, pointing to the local mail account of the user who ran it; sieve then tries to send the mail there. The solution is either to deliver through an LMTP socket, or pass deliver the correct return-path using the -r switch. regards, Adam. Adam Stephens Unix Administrator, ILRT [EMAIL PROTECTED] On Fri, 8 Nov 2002, Darrell Berry wrote: > oops, actually the rules look like the following. I have sendmail: > /usr/sbin/sendmail set in /etc/imapd.conf, but still not seeing any response > being sent back to the senders of messages -- i've seen lots of discussion > about sieve and vacation in the maciling lists, but nothing conclusive -- > any ideas? i;m running cyrus imapd 2.0.16, built from the > cyrus-imapd-2.0.16-5rm.src.rpm package. otherwise all seems fine. > > thx > > --- > > # Mail rules for user darrellb > # Created by Websieve version 0.61h > require ["fileinto","vacation"]; > > > vacation :days 1 :addresses ["[EMAIL PROTECTED]", "[EMAIL PROTECTED]", > "[EMAIL PROTECTED]"] text: > Autogenerated Message: > Not Here. Leave a message please > . > ; > > > ##PSEUDO script start > #vacation&&1&&"[EMAIL PROTECTED]", "[EMAIL PROTECTED]", > "[EMAIL PROTECTED]"&&Not Here. Leave a message please&&on > #mode&&basic > > >
Sieve not processing
I used the smartsieve application from source forge to create a vacation script, only nothing happens. :( I don't see anything in the logs, etc Nov 12 05:25:52 sardine timsieved[1540]: login: sardine.morrison.iserv.net[127.0.0.1] adam PLAIN User logged in $sieveshell --user=adam sardine > ls smartsieve <- active scrip > get smartsieve #Mail filter rules for adam #Generated by SmartSieve 0.3.1-devel Tuesday 12th of November 2002 04:48:23 AM require ["vacation"]; vacation :days 2 :addresses ["[EMAIL PROTECTED]"] text: test
