Re: trouble settting up cyrus
Does your imapd.conf have the parameter 'servername' configured? If so, you must specify that particular domain name while creating users. Try this before you change anything: imtest -a cyrus -m login localhost *** I can't get cyrus working. I'm trying to install version 2.1.12 with SASLv2 on a debian 3.0 system. I don't want to create debian users for every imap user so I'd like to use the sasldb athentication. I don't want to use PAM/mySQL. I've got the cyrus daemon running but I can't login either with cyradm nor imtest. I've already created a sasl user with saslpasswd2, but the log still says: badlogin: X.XXX[XXX.XXX.XXX.XXX] DIGEST-MD5 [SASL(-13): user not found: no secret in database] imtest says: imtest -u cyrus localhost S: * OK SF111 Cyrus IMAP4 v2.1.12-Debian-2.1.12-6 server ready C: C01 CAPABILITY S: * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ MAILBOX-REFERRALS NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES IDLE AUTH=NTLM AUTH=DIGEST-MD5 AUTH=CRAM-MD5 LISTEXT LIST-SUBSCRIBED ANNOTATEMORE S: C01 OK Completed C: A01 AUTHENTICATE DIGEST-MD5 [...] Please enter your password: C: [...] S: A01 NO user not found Authentication failed. generic failure Security strength factor: 128 entries in imapd.conf: sasl_pwcheck_method: auxprop sasl_auxprop_plugin: sasldb sasl_sasldb_path: /etc/sasldb2 I have no clue about auxprop. Do I have to conifigure it separately? Am I missing something? regards
postfix and cyrus
I am running postfix with cyrus 2.1.2. I ocasionally get the following error message in the log: Apr 3 10:16:46 mail lmtpd[1983]: duplicate_mark: closing /var/lib/imap/deliverdb/deliver-b.db: DB_INCOMPLETE: Cache flush was unable to complete Apr 3 10:16:46 mail lmtpd[2226]: duplicate_check: closing /var/lib/imap/deliverdb/deliver-b.db: DB_INCOMPLETE: Cache flush was unable to complete I suspect that postifx is feeding cyrus faster than cyrus can take it. If that seems likely, is there a good way to throttle the flow? John Lederer
Re: postfix and cyrus
John Lederer wrote: I am running postfix with cyrus 2.1.2. I ocasionally get the following error message in the log: Apr 3 10:16:46 mail lmtpd[1983]: duplicate_mark: closing /var/lib/imap/deliverdb/deliver-b.db: DB_INCOMPLETE: Cache flush was unable to complete Apr 3 10:16:46 mail lmtpd[2226]: duplicate_check: closing /var/lib/imap/deliverdb/deliver-b.db: DB_INCOMPLETE: Cache flush was unable to complete I suspect that postifx is feeding cyrus faster than cyrus can take it. If that seems likely, is there a good way to throttle the flow? John Lederer try setting XXX_destination_concurrency_limit (where XXX could be local/virtual/etc, what you use to deliver to lmtpd) in main.cf. mitu
Re: postfix and cyrus
Thanks -- but I see it has a value of 2, making me suspect that I am totally wrong about the cause. Anyone have any good ideas? John Mitrana Cristian wrote: John Lederer wrote: I am running postfix with cyrus 2.1.2. I ocasionally get the following error message in the log: Apr 3 10:16:46 mail lmtpd[1983]: duplicate_mark: closing /var/lib/imap/deliverdb/deliver-b.db: DB_INCOMPLETE: Cache flush was unable to complete Apr 3 10:16:46 mail lmtpd[2226]: duplicate_check: closing /var/lib/imap/deliverdb/deliver-b.db: DB_INCOMPLETE: Cache flush was unable to complete I suspect that postifx is feeding cyrus faster than cyrus can take it. If that seems likely, is there a good way to throttle the flow? John Lederer try setting XXX_destination_concurrency_limit (where XXX could be local/virtual/etc, what you use to deliver to lmtpd) in main.cf. mitu
cyrus server and backup
I have never used the Cyrus IMAP server before and have just intalled it on a test system to evaluate it, with a view to moving our service over to it. We have over 20,000 users and need to upgrade our current system. One of our fundamental requirements is to be able to take security backups. These are primarily for recovery in case of hardware failures. The backups are conventional periodic full backups with intermediate incrementals. I am concerned that because Cyrus is a black box system which keeps track of its own internal organisation we may have problems if we restore a disc from our backups. It will take hours to do a backup and the files within the Cyrus structure will be changing as we do it. Are there going to be problems with inconsistencies between files? There is a secondary, but important use of our current backup service, which is to dig users out of a hole when they make mistakes: Occasionally a user will accidentally delete a message or even a whole folder and then come and ask if I can recover it for them. With our current backup system it is ussually very easy because I have no problem identifying the relevant files to be recovered. I seems to that it will be impossible to recover deleted messages because I will not be able to identify the files which I need. If I can identify the files, presumably there is no way to get them back into the Cyrus system? The only information I have been able to find which says anything about recovery is in the Server Overview and Concepts document. However, this does not go into sufficient detail and includes statements like Many objects in the configuration directory are discussed in the Database Recover section. I cannot find any section anywhere with a title of Database Recover! Any advice will be much appreciated. Phil. --- Phil Chambers ([EMAIL PROTECTED]) University of Exeter
AW: trouble settting up cyrus
Maik Knittel wrote: I can't get cyrus working. I'm trying to install version 2.1.12 with SASLv2 on a debian 3.0 system. I don't want to create debian users for every imap user so I'd like to use the sasldb athentication. I don't want to use PAM/mySQL. I've got the cyrus daemon running but I can't login either with cyradm nor imtest. I've already created a sasl user with saslpasswd2, but the log still says: badlogin: X.XXX[XXX.XXX.XXX.XXX] DIGEST-MD5 [SASL(-13): user not found: no secret in database] imtest says: imtest -u cyrus localhost S: * OK SF111 Cyrus IMAP4 v2.1.12-Debian-2.1.12-6 server ready C: C01 CAPABILITY S: * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ MAILBOX-REFERRALS NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES IDLE AUTH=NTLM AUTH=DIGEST-MD5 AUTH=CRAM-MD5 LISTEXT LIST-SUBSCRIBED ANNOTATEMORE S: C01 OK Completed C: A01 AUTHENTICATE DIGEST-MD5 [...] Please enter your password: C: [...] S: A01 NO user not found Authentication failed. generic failure Security strength factor: 128 entries in imapd.conf: sasl_pwcheck_method: auxprop sasl_auxprop_plugin: sasldb sasl_sasldb_path: /etc/sasldb2 Does the cyrus user have read access to /etc/sasldb2? thats it - thank you very much
postfix doesn't know cyrus user
hello, after weve got cyrus running, we have another problem. We cant send mail with postfix (smtp). It seems that Postfix doesnt know the cyrus user. from mail.log: Apr 4 16:13:03 X postfix/smtpd[1343]: 3C6A3137: reject: RCPT from unknown[XXX.XXX.XXX.XXX]: 550 [EMAIL PROTECTED]: User unknown in local recipient table; from=[EMAIL PROTECTED] proto=ESMTP helo=X main.cf local_transport = cyrus mydestination = localhost, XXX.XXX.XXX.XXX thanks again
Re: cyrus server and backup
On Fri, 04 Apr 2003, Phil Chambers wrote: I am concerned that because Cyrus is a black box system which keeps track of its own internal organisation we may have problems if we restore a disc from our backups. It will take hours to do a backup and the files within the Cyrus structure will be changing as we do it. Are there going to be problems with inconsistencies between files? There are two answers to this. The first is that doing snapshot backups should be possible on most plausible platforms, either by dropping a mirror off (requires mirroring, of course) or using fssnap (Sun) or LVM (Linux) to do a hot backup. The second is that in practice you can recover a mailbox by spinning on the files and then using reconstruct to rebuild the metadata. The worst you're going to do is break the unread flags and suchlike. There is a secondary, but important use of our current backup service, which is to dig users out of a hole when they make mistakes: Occasionally a user will accidentally delete a message or even a whole folder and then come and ask if I can recover it for them. We do that all the time. We pull the entire mailbox back, then grep for what the punter wants. With our current backup system it is ussually very easy because I have no problem identifying the relevant files to be recovered. I seems to that it will be impossible to recover deleted messages because I will not be able to identify the files which I need. If I can identify the files, presumably there is no way to get them back into the Cyrus system? If you can identify them by size or date, you just put them back into the mailbox and reconstruct it. ian
Re: cyrus server and backup
Phil Chambers wrote: I have never used the Cyrus IMAP server before and have just intalled it on a test system to evaluate it, with a view to moving our service over to it. We have over 20,000 users and need to upgrade our current system. One of our fundamental requirements is to be able to take security backups. These are primarily for recovery in case of hardware failures. The backups are conventional periodic full backups with intermediate incrementals. I am concerned that because Cyrus is a black box system which keeps track of its own internal organisation we may have problems if we restore a disc from our backups. It will take hours to do a backup and the files within the Cyrus structure will be changing as we do it. Are there going to be problems with inconsistencies between files? There is a secondary, but important use of our current backup service, which is to dig users out of a hole when they make mistakes: Occasionally a user will accidentally delete a message or even a whole folder and then come and ask if I can recover it for them. With our current backup system it is ussually very easy because I have no problem identifying the relevant files to be recovered. I seems to that it will be impossible to recover deleted messages because I will not be able to identify the files which I need. If I can identify the files, presumably there is no way to get them back into the Cyrus system? The only information I have been able to find which says anything about recovery is in the Server Overview and Concepts document. However, this does not go into sufficient detail and includes statements like Many objects in the configuration directory are discussed in the Database Recover section. I cannot find any section anywhere with a title of Database Recover! Any advice will be much appreciated. Search the list archives for detailed discussion of this topic. What we do is folder-level restores (we haven't had to restore more than one at a time yet -- the same approach works but it would be a lot of work), and we create a top-level folder that will be the restore target, restore the contents of the directory containing the user's folder that needs to be restored into the directory containing the restore folder, reconstruct that folder, and grant access to the user. It is up to the user to do whatever they want, presumably copying messages that were deleted accidentally. After one week, the restore folder is deleted. We decided to use a top-level folder rather than put it under each user to avoid quota issues (we could set a quotaroot on the restore subtree, but it is easier this way) and to make it easier to clean up expired restore folders. If this were a non-user error (we haven't had one of those), we would probably just restore the whole cyrus directory structure (depending on the damage) if reconstruct couldn't fix it. -- John A. Tamplin Unix System Administrator Emory University, School of Public Health +1 404/727-9931
Sieve existing
Does anyone know how to run sieve rules on existing mail? Regards, Matthew __ Matthew Tagg +27 21 409 7850 +27 82 964-0426 (Mobile) Diginet - Web Africa http://www.webafrica.co.za (business.sig) smime.p7s Description: S/MIME cryptographic signature
Re: postfix doesn't know cyrus user
On Fri, 4 Apr 2003 16:32:39 +0200 Maik Knittel [EMAIL PROTECTED] wrote: hello, after we've got cyrus running, we have another problem. We can't send mail with postfix (smtp). It seems that Postfix doesn't know the cyrus user. you have to set up the local_recipient_table map that lists all users that you want to accept mail for. how you do that greatly depends on your setup. -- Jure Pecar
Re: Sieve existing
Matthew Tagg wrote: Does anyone know how to run sieve rules on existing mail? You'd either have to feed them back into lmtpd or perhaps find an IMAP client which can do client-side Sieve (Mulberry?). -- 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
Sieveshell scripting and automation issues
Firstly I am using sieveshell to update my scripts however I want to be able to just edit a file a run a simple command for it to take effect, to that end I've had little success. I tried using sieveshell --user=matt --authname=matt --exec=sievescript localhost but it never executes the script. Also I cant find any docs on the format of the script. The second irriation with sieveshell is that it has a 1 to 2 second delay and prompts for a password hence foiling my automation efforts. Any suggestions would be welcome :) Regards, Matthew __ Matthew Tagg +27 21 409 7850 +27 82 964-0426 (Mobile) Diginet - Web Africa http://www.webafrica.co.za (business.sig) smime.p7s Description: S/MIME cryptographic signature
Re: postfix doesn't know cyrus user
On Fri, 2003-04-04 at 16:32, Maik Knittel wrote: after weve got cyrus running, we have another problem. We cant send mail with postfix (smtp). It seems that Postfix doesnt know the cyrus user. from mail.log: Apr 4 16:13:03 X postfix/smtpd[1343]: 3C6A3137: reject: RCPT from unknown[XXX.XXX.XXX.XXX]: 550 [EMAIL PROTECTED]: User unknown in local recipient table; from=[EMAIL PROTECTED] proto=ESMTP helo=X Try setting local_recipient_maps = in main.cf, to tell postfix not to try lookup local users first main.cf local_transport = cyrus mydestination = localhost, XXX.XXX.XXX.XXX -- -+-- Chris Picton | PGP Key ID: 9D28A988 (wwwkeys.pgp.net) Solutions Developer | PGP Key Fingerprint: Tangent Systems | 2B46 29EA D530 79EC D9EA 3ED0 229D 6DD6 9D28 A988 [EMAIL PROTECTED] | http://www.tangent.co.za/keys/chrisp.asc -+-- signature.asc Description: This is a digitally signed message part
AW: postfix doesn't know cyrus user
after weÿve got cyrus running, we have another problem. We canÿt send mail with postfix (smtp). It seems that Postfix doesnÿt know the cyrus user. from mail.log: Apr 4 16:13:03 X postfix/smtpd[1343]: 3C6A3137: reject: RCPT from unknown[XXX.XXX.XXX.XXX]: 550 [EMAIL PROTECTED]: User unknown in local recipient table; from=[EMAIL PROTECTED] proto=ESMTP helo=X Try setting local_recipient_maps = in main.cf, to tell postfix not to try lookup local users first main.cf local_transport = cyrus mydestination = localhost, XXX.XXX.XXX.XXX thats it - thank you very much
imclient_input
This just moves the plainlen==0 test, if it's needed at all - the
rest is just formatting.
Cheers,
Patrick
Index: imclient.c
===
RCS file: /cvs/src/cyrus/lib/imclient.c,v
retrieving revision 1.77
diff -u -r1.77 imclient.c
--- imclient.c 13 Feb 2003 20:15:40 - 1.77
+++ imclient.c 4 Apr 2003 19:43:50 -
@@ -685,18 +693,18 @@
assert(buf);
if (imclient-saslcompleted == 1) {
- /* decrypt what we have */
- if ((result = sasl_decode(imclient-saslconn, buf, len,
- plainbuf, plainlen)) != SASL_OK) {
- (void) shutdown(imclient-fd, 0);
- }
-
- if (plainlen == 0) return;
+ /* decrypt what we have */
+ if ((result = sasl_decode(imclient-saslconn, buf, len,
+ plainbuf, plainlen)) != SASL_OK) {
+ (void) shutdown(imclient-fd, 0);
+ }
} else {
- plainbuf = buf;
- plainlen = len;
+ plainbuf = buf;
+ plainlen = len;
}
+ if (plainlen == 0) return;
+
/* Ensure replybuf has enough space to take the input */
if (imclient-replylen + plainlen = imclient-alloc_replybuf) {
/* If there is unused space at the front, move the plaintext there */
imclient_writeastring
Currently class is initialised as 2, which means that the charclass check
is bypassed (max(charclass)=2 = class always = charclass), and quoted
strings are never emitted. Does this mean that there was a problem with
quoted strings at some time?
It's more obvious what is going on in the following replacement switch
statement version. (Seems to work with class = 0)
Cheers,
Patrick
static int imclient_writeastring(struct imclient *imclient, const char *str)
{
const char *p;
unsigned len = 0;
int class = 0;
char buf[30];
assert(imclient);
assert(str);
for (p = str; *p; p++) {
len++;
if (class charclass[(unsigned char)*p]) {
class = charclass[(unsigned char)*p];
}
}
if (len == 0) return 0;
if (len = 1024) class = 0;
switch (class) {
case 2: /* Atom */
imclient_write(imclient, str, len);
break;
case 1: /* Quoted-string */
imclient_write(imclient, \, 1);
imclient_write(imclient, str, len);
imclient_write(imclient, \, 1);
break;
case 0: /* Literal */
if (imclient-flags IMCLIENT_CONN_NONSYNCLITERAL) {
snprintf(buf, sizeof(buf), {%u+}\r\n, len);
imclient_write(imclient, buf, strlen(buf));
} else {
imclient-readytag = imclient-gensym;
snprintf(buf, sizeof(buf), {%u}\r\n, len);
imclient_write(imclient, buf, strlen(buf));
while (imclient-readytag) {
imclient_processoneevent(imclient);
}
if (!imclient-readytxt) return 1;
}
imclient_write(imclient, str, len);
break;
}
return 0;
}
struct imclient, outbuf
In trying to figure out what is going on in imclient_write, I simplified
struct imclient, and moved from pointers to indices - a matter of taste,
I know, but it seems the reply buffer is handled that way..
(One could also s/writelen/imclient-outlen/g)
Cheers,
Patrick
Index: imclient.c
===
RCS file: /cvs/src/cyrus/lib/imclient.c,v
retrieving revision 1.77
diff -u -r1.77 imclient.c
--- imclient.c 13 Feb 2003 20:15:40 - 1.77
+++ imclient.c 4 Apr 2003 19:37:33 -
@@ -120,9 +120,7 @@
/* Data to be output to server */
char outbuf[IMCLIENT_BUFSIZE];
-char *outptr;
-size_t outleft;
-char *outstart;
+size_t outlen;
/* Replies being received from server */
char *replybuf;
@@ -263,8 +261,10 @@
(*imclient)-saslconn = NULL;
(*imclient)-saslcompleted = 0;
(*imclient)-servername = xstrdup(hp-h_name);
-(*imclient)-outptr = (*imclient)-outstart = (*imclient)-outbuf;
-(*imclient)-outleft = (*imclient)-maxplain = sizeof((*imclient)-outbuf);
+(*imclient)-outlen = 0;
+(*imclient)-replylen = 0;
+(*imclient)-alloc_replybuf = 0;
+ (*imclient)-maxplain = sizeof((*imclient)-outbuf);
(*imclient)-interact_results = NULL;
imclient_addcallback(*imclient,
, 0, (imclient_proc_t *) 0, (void *)0,
@@ -626,41 +625,50 @@
*/
void imclient_write(struct imclient *imclient, const char *s, size_t len)
{
+ size_t outleft;
+
assert(imclient);
assert(s);
-/* If no data pending for output, reset the buffer */
-if (imclient-outptr == imclient-outstart) {
- imclient-outstart = imclient-outptr = imclient-outbuf;
- imclient-outleft = imclient-maxplain;
-}
-
+ outleft = imclient-maxplain - imclient-outlen;
/* While we don't have room to buffer all the output */
-while (len imclient-outleft) {
- /* Copy as much data as will fit in output buffer */
- memcpy(imclient-outptr, s, imclient-outleft);
- imclient-outptr += imclient-outleft;
- s += imclient-outleft;
- len -= imclient-outleft;
- imclient-outleft = 0;
-
- /* Process events until output buffer is flushed */
- while (imclient-outptr != imclient-outstart) {
- imclient_processoneevent(imclient);
- }
-
- /* Reset the buffer */
- imclient-outstart = imclient-outptr = imclient-outbuf;
- imclient-outleft = imclient-maxplain;
+while (len outleft) {
+ /* Copy as much data as will fit in output buffer */
+ memcpy(imclient-outbuf+imclient-outlen, s, outleft);
+ imclient-outlen += outleft;
+ s += outleft;
+ len -= outleft;
+
+ /* Process events until output buffer is flushed */
+ while (imclient-outlen) {
+ imclient_processoneevent(imclient);
+ } /* Should only be called once. If not, then not all plain text
+ * was successfully writen in non sasl case
+ */
+ outleft = imclient-maxplain; /* - imclient-outlen; == 0 */
}
/* Copy remaining data to output buffer */
-memcpy(imclient-outptr, s, len);
-imclient-outptr += len;
-imclient-outleft -= len;
+memcpy(imclient-outbuf+imclient-outlen, s, len);
+imclient-outlen += len;
}
/*
+ * http://bugzilla.andrew.cmu.edu/show_bug.cgi?id=333
+ *
+ * Opened: 2000-10-13 00:02
+ *
+ * imclient doesn't correctly parse literals. this will bite any
+ * serious imclient application that consistently fetches things with
+ * literals.
+ *
+ * imclient.c, around line 730, uses the variable 'len' in a place
+ * where it clearly isn't applicable. this is the heart of the bug,
+ * but we need to fix it so that literals that don't end lines are
+ * still handled correctly.
+ */
+
+/*
* On the connection 'imclient', handle the input 'buf' of size 'len'
* from the server. Invoke callbacks as appropriate.
*/
@@ -1006,13 +1014,13 @@
assert(imclient);
for (;;) {
- writelen = imclient-outptr - imclient-outstart;
+ writelen = imclient-outlen;
if ((imclient-saslcompleted==1) (writelen0)) {
unsigned int cryptlen=0;
const char *cryptptr=NULL;
- if (sasl_encode(imclient-saslconn, imclient-outstart, writelen,
+ if (sasl_encode(imclient-saslconn, imclient-outbuf, writelen,
cryptptr,cryptlen)!=SASL_OK)
{
/* XXX encoding error */
@@ -1032,7 +1040,7 @@
#endif /* HAVE_SSL */
if (n 0) {
- imclient-outstart += writelen;
+ imclient-outlen = 0; /* what if cryptlen != n ? */
return;
}
@@ -1047,17 +1055,17 @@
#ifdef HAVE_SSL
if (imclient-tls_on==1)
{
- n = SSL_write(imclient-tls_conn, imclient-outstart, writelen);
+ n =
Re: internaldate
On Wed, 2003-04-02 at 16:55, Ken Murchison wrote:
Alexander Brill wrote:
I am trying to set the internaldate for a message, but it doesn't store
properly.
This is what I try (using python)
imap.store(1,+FLAGS,INTERNALDATE 22-Mar-2003 02:10:31 +0100)
('OK', ['1 (FLAGS (INTERNALDATE 22-Mar-2003 02:10:31 +0100))'])
It replies with an OK (prefixed with an ), and that the INTERNALDATE
has been altered.
But when I try to fetch the same message it tells me that the
INTERNALDATE is:
('OK', ['1 (INTERNALDATE 25-Mar-2003 02:10:31 +0100)'])
So it doesn't store the values, even though it returns an OK. Any hints?
You can't change INTERNALDATE with STORE, only flags can be changed (see
sec 6.4.6 of RFC 3501). Typically, INTERNALDATE is a read-only
attribute which is set when a message gets stored in a mailbox, either
by SMTP/LMTP, COPY or APPEND (see sec 2.3.3 of RFC 3501).
Is there some other way of setting it then? I have a bunch of mails
dated the 25 of March :)
--
Alexander Brill [EMAIL PROTECTED]
http://www.project23.no
PGP-key: http://www.nettstudio.no/pgp/alexander.brill.asc
signature.asc
Description: This is a digitally signed message part
Deliver Problem, trying Simon's lmtp patch.
I'm trying to use cyrus-imap with mailboxes using the email of the user. Ex: [EMAIL PROTECTED] is the mailbox. Everything works fine, I'm using unixhierarchysep and I can log in the imap server and download my messages, create folders,etc. The only think that I can't do is to deliver messages using the deliver command. Looking in the net I found a answer to that from Simon : lmtpd / deliver seas the @ as splitting a realm there is a one line mod ( search archive I posted a diff once) which will enable @`s to work Allright! Found the bug, but can't find the patch for cyrus-imapd-2.1.12 . Found one in the list, but I counl't make it work. Got lots of rejects. Does any know where I can find it to download? Looked in Simon's website (www.surf.org.uk i think) and counl't find anything about it. regards. Thiago Madeira de Lima
error marking messages as read
Hello, I got the following error in my syslog trying to mark 1930 messages as read. I am using Cyrus 2.1.12 as the server, and Mozilla 1.2.1 as my mail client. Apr 4 14:04:47 kang imapd[51441]: Fatal error: word too long Is this a problem with the IMAP server, or the client?
RE: Deliver Problem, trying Simon's lmtp patch.
Well, I got the old patch and fixed (I hope) the errors. When I deliver some mail it does not show me that user unknow, but it seens to be delivering the mail not correctly. In the logs I can see : Apr 4 18:13:37 vishnu lmtpd[10962]: duplicate_mark: [EMAIL PROTECTED] [EMAIL PROTECTED] 1049490817 Look's good right? Unfortunaly no. The user.jungle should be jungle/jungle. It is not delivering the mail in my mailbox, but it is not giving a error. Any tips? Thanks alot again Thiago MAdeira de lima. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thiago Lima Sent: Friday, April 04, 2003 5:55 PM To: [EMAIL PROTECTED] Subject: Deliver Problem, trying Simon's lmtp patch. I'm trying to use cyrus-imap with mailboxes using the email of the user. Ex: [EMAIL PROTECTED] is the mailbox. Everything works fine, I'm using unixhierarchysep and I can log in the imap server and download my messages, create folders,etc. The only think that I can't do is to deliver messages using the deliver command. Looking in the net I found a answer to that from Simon : lmtpd / deliver seas the @ as splitting a realm there is a one line mod ( search archive I posted a diff once) which will enable @`s to work Allright! Found the bug, but can't find the patch for cyrus-imapd-2.1.12 . Found one in the list, but I counl't make it work. Got lots of rejects. Does any know where I can find it to download? Looked in Simon's website (www.surf.org.uk i think) and counl't find anything about it. regards. Thiago Madeira de Lima
[no subject]
Hi, I'm running cyrus-imapd-2.1.12 with sendmail 8.12.9. I have an issue where lmtpd seems to refuse connections. This behaviour seems to occur when a large volume of mail is delivered to the box. I notice that there is an lmtpd process fo each message that is being delivered so if i send a few hundred emails i get a few hundred ltmpd processes. Is this normal ? I have specified FEATURE(local_lmtp) in sendmail.mc and have the following in my cyrus.conf file. lmtpunix cmd=lmtpd listen=/var/imap/socket/lmtp prefork=0 The error in my maillog is: Apr 5 10:00:55 myserver sm-mta[58837]: h3500t9u058768: SYSERR(root): Could not connect to socket /var/imap/socket/lmtp: Connection refused by localhost Can anyone offer any advice ? Thanks.
Using SASL or Cyrus type database in Postfix
Since so many of us use Postfix I was wondering if we could solve the Postfix needs userdb entry before delivery problem by adding a method by which Postfix could lookup the mailbox in one of Cyrus' databases. Originally I was thinking of pointing Postfix at mailboxes.db and adding a new DB class called cyrus to read from it, but I then wondered if the SASL database couldn't be used as well (since the mailbox names match the authorization names). Anybody have any thoughts, or done any Postfix hacking that could tell how easy or difficult this would be? The intent would be to give Postfix a native method for using one of Cyrus' databases as a virtual map. This would alleviate the requirement that adding users to Postfix is either pulling double duty by entering them twice, or turning off virtual user lookups entirely by using the mydomains entry. A third possibility would be to enhance somehow enhance Cyrus to pull it's User DB from LDAP (or some other DB Postfix already supports) and automatically create a user's mailbox they have been authorized and some hasMailbox flag has been set in the outside DB. Just an idea and some thoughts, anyone have any other feedback on this? -- Michael --
lmtp behaviour
Hi, I'm running cyrus-imapd-2.1.12 with sendmail 8.12.9. I have an issue where lmtpd seems to refuse connections. This behaviour seems to occur when a large volume of mail is delivered to the box. I notice that there is an lmtpd process fo each message that is being delivered so if i send a few hundred emails i get a few hundred ltmpd processes. Is this normal ? I have specified FEATURE(local_lmtp) in sendmail.mc and have the following in my cyrus.conf file. lmtpunix cmd=lmtpd listen=/var/imap/socket/lmtp prefork=0 The error in my maillog is: Apr 5 10:00:55 myserver sm-mta[58837]: h3500t9u058768: SYSERR(root): Could not connect to socket /var/imap/socket/lmtp: Connection refused by localhost Can anyone offer any advice ? Thanks.
bare newline problem
Hi all! I 've been using postfix and cyrus for my email system. Everything seem OK and I can say thanks to opensource community for such great products. But now, some time my system have bounced a message with log error: 554 5.6.0 Message contains bare newlines. Sorry for my limit knowledge but I dunno what 's wrong. I 've searched in some cyrus maillist but I 'v not found solution yet. I only know there some ellegal in message comming with CRLF in line. Can you all tell me more detail and how to allow my system accept these type of messages Thanks for all idea! -- Do Duc Huy Centre for Development Infomation Technology - CDITThe 4th floor VCCI buiding #9 Dao Duy Anh Str. Dong Da Dstr. HanoiTel: 84-04-5742879
