murder configuration issue

[Gary W. Smith]

Hello, 
 
I'm trying to configure murder in an existing environment.  I have configured 
the one backend server, the master server and I'm trying to confogure the 
frontend server.  On the frontend is where I'm running into a problem.  The 
backends can do a ctl_mboxlist just fine.  I put tcpdump on the master server 
and I can see them making a connection without any problem.  For some reason, 
the frontend server kicks out an error message saing that it can't connect to 
the master server, yet I don't even see any traffic leaving the server or 
hitting the master server on port 3905.
 
Error message:
# runuser -  cyrus  -c ' /usr/lib/cyrus-imapd/ctl_mboxlist -m'
couldn't connect to mupdate server

and when the cyrus-imapd process is running these are all over the log files:
 
Dec  9 09:56:55 mdsfe mupdate[12282]: connect(10.80.72.201) failed: Invalid 
argument
Dec  9 09:56:55 mdsfe mupdate[12282]: couldn't connect to mupdate server
Dec  9 09:56:55 mdsfe mupdate[12282]: retrying connection to mupdate server in 
20 seconds

In the imapd.conf file I have:
 
configdirectory: /var/lib/imap
partition-default: /var/spool/imap
admins: cyrus root

mupdate_authname: murder
#mupdate_username: murder
mupdate_password: mypass
mupdate_server: 10.80.72.201
mupdate_port: 3905
mds01_mechs: PLAIN
mds01_password: mypass
proxy_authname: murder
sasl_pwcheck_method: saslauthd
allowplaintext: yes
sasl_mech_list: PLAIN
sasl_minimum_layer: 0

tls_ca_file: /etc/imap/rapidssl_01.cer
tls_cert_file: /etc/imap/imap.crt
tls_key_file: /etc/imap/imap.pem
 
 
In the cyrus.conf I have:
 
mupdate  cmd=mupdate listen=3905 prefork=1 
imapcmd=proxyd listen=imap prefork=0
imaps  cmd=proxyd -s listen=imaps prefork=0
pop3cmd=pop3d listen=pop3 prefork=0
pop3s  cmd=pop3d -s listen=pop3s prefork=0
sieve   cmd=timsieved listen=sieve prefork=0
lmtpcmd=lmtpproxyd listen=lmtp prefork=0 maxchild=20


Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

RE: murder configuration issue

[Gary W. Smith]

CentOS 5.2 default package 2.3.7 doesn't seem to work as a front end.  
Downloaded FC10 (2.3.12p) and recompiled and frontend seems to be getting 
farther.
 
 



From: [EMAIL PROTECTED] on behalf of Gary W. Smith
Sent: Tue 12/9/2008 6:58 AM
To: info-cyrus@lists.andrew.cmu.edu
Subject: murder configuration issue


Hello, 
 
I'm trying to configure murder in an existing environment.  I have configured 
the one backend server, the master server and I'm trying to confogure the 
frontend server.  On the frontend is where I'm running into a problem.  The 
backends can do a ctl_mboxlist just fine.  I put tcpdump on the master server 
and I can see them making a connection without any problem.  For some reason, 
the frontend server kicks out an error message saing that it can't connect to 
the master server, yet I don't even see any traffic leaving the server or 
hitting the master server on port 3905.
 
Error message:
# runuser -  cyrus  -c ' /usr/lib/cyrus-imapd/ctl_mboxlist -m'
couldn't connect to mupdate server

and when the cyrus-imapd process is running these are all over the log files:
 
Dec  9 09:56:55 mdsfe mupdate[12282]: connect(10.80.72.201) failed: Invalid 
argument
Dec  9 09:56:55 mdsfe mupdate[12282]: couldn't connect to mupdate server
Dec  9 09:56:55 mdsfe mupdate[12282]: retrying connection to mupdate server in 
20 seconds

In the imapd.conf file I have:
 
configdirectory: /var/lib/imap
partition-default: /var/spool/imap
admins: cyrus root

mupdate_authname: murder
#mupdate_username: murder
mupdate_password: mypass
mupdate_server: 10.80.72.201
mupdate_port: 3905
mds01_mechs: PLAIN
mds01_password: mypass
proxy_authname: murder
sasl_pwcheck_method: saslauthd
allowplaintext: yes
sasl_mech_list: PLAIN
sasl_minimum_layer: 0

tls_ca_file: /etc/imap/rapidssl_01.cer
tls_cert_file: /etc/imap/imap.crt
tls_key_file: /etc/imap/imap.pem
 
 
In the cyrus.conf I have:
 
mupdate  cmd=mupdate listen=3905 prefork=1 
imapcmd=proxyd listen=imap prefork=0
imaps  cmd=proxyd -s listen=imaps prefork=0
pop3cmd=pop3d listen=pop3 prefork=0
pop3s  cmd=pop3d -s listen=pop3s prefork=0
sieve   cmd=timsieved listen=sieve prefork=0
lmtpcmd=lmtpproxyd listen=lmtp prefork=0 maxchild=20


Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: murder configuration issue

[Wesley Craig]

On 09 Dec 2008, at 09:58, Gary W. Smith wrote:
 Dec  9 09:56:55 mdsfe mupdate[12282]: connect(10.80.72.201) failed:  
 Invalid argument

Perhaps an IPv4 vs IPv6 problem?

:wes

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Murder + Sieve + multiple backends problem

[Wesley Craig]

On 02 Dec 2008, at 10:54, Juergen Wolf wrote:
 The mlookup
 thing is indeed very simple and already working. The cmd_append() part
 is a bit tricky tho, as the LMTPD does not have any imap connection to
 the backend as far as I see. I guess LMTP will be the wrong way to
 transport the mail to the right backend server.

Right, you'd want an IMAP connection, I would think.

 +/* Mailbox not existent, and murder setup ? */
 +if (r == IMAP_MAILBOX_NONEXISTENT  config_mupdate_server) {
 +  /* check the mupdate master */

You don't really want to talk to the mupdate master.  You want to  
look in the local mailboxes.db (this only works in a unified murder,  
obviously).

If you look at cmd_append() in imapd.c, you see mlookup() used to  
obtain mailbox information.  sieve_fileinto() in lmtp_sieve.c is  
structurally similar: it internalizes the mailbox, and then delivers  
it.  The deliver_mailbox() in lmtpd.c is just an append, just like  
cmd_append() is!  At least the part after:

/* local mailbox */

in cmd_append() is analogous to the append code in deliver_mailbox 
().  The portion of cmd_append() that's missing from deliver_mailbox 
() is the first bit:

 if (!r  (mbtype  MBTYPE_REMOTE)) {
/* remote mailbox */
struct backend *s = NULL;
...
s = proxy_findserver(newserver, imap_protocol,
 proxy_userid, backend_cached,
 backend_current, backend_inbox, imapd_in);
if (!s) r = IMAP_SERVER_UNAVAILABLE;

if (!r) {
int is_active = 1;
s-context = (void*) is_active;
if (imapd_mailbox) {
prot_printf(s-out, %s Localappend { SIZE_T_FMT +}\r\n%s
 { SIZE_T_FMT +}\r\n%s ,
tag, strlen(name), name,
strlen(imapd_mailbox-name), imapd_mailbox-name);
} else {
prot_printf(s-out, %s Localappend { SIZE_T_FMT +}\r\n%s
 { SIZE_T_FMT +}\r\n%s ,
tag, strlen(name), name, 0, );
}
if (!(r = pipe_command(s, 16384))) {
pipe_including_tag(s, tag, 0);
}
s-context = NULL;
} else {
eatline(imapd_in, prot_getc(imapd_in));
}

if (r) {
prot_printf(imapd_out, %s NO %s\r\n, tag,
prot_error(imapd_in) ? prot_error(imapd_in) :
error_message(r));
}

return;
 }

Obviously, it would need a little work to merge this in, but I think  
it's pretty trivial.

:wes

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

RE: murder configuration issue

[Gary W. Smith]

I updated to the FC10 package and now it seems to be working better.  On the 
backend I can see the mailboxes that are synching with the master, but the 
front end doesn't seem to be pulling the information.  That is, it connects, I 
can see that in the log on the master, and says it pulls the mailbox data but 
when I connect via pop3 it says that it can't find the mailbox.  I'm probably 
just missing something minor at this point.  I'm going to down everything and 
resync a little later to see if that cures my wows.
 
Gary



From: Wesley Craig [mailto:[EMAIL PROTECTED]
Sent: Tue 12/9/2008 11:00 AM
To: Gary W. Smith
Cc: info-cyrus@lists.andrew.cmu.edu
Subject: Re: murder configuration issue



On 09 Dec 2008, at 09:58, Gary W. Smith wrote:
 Dec  9 09:56:55 mdsfe mupdate[12282]: connect(10.80.72.201) failed: 
 Invalid argument

Perhaps an IPv4 vs IPv6 problem?

:wes



Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: murder configuration issue

[Wesley Craig]

On 09 Dec 2008, at 15:04, Gary W. Smith wrote:
 I updated to the FC10 package and now it seems to be working  
 better.  On the backend I can see the mailboxes that are synching  
 with the master, but the front end doesn't seem to be pulling the  
 information.  That is, it connects, I can see that in the log on  
 the master, and says it pulls the mailbox data but when I connect  
 via pop3 it says that it can't find the mailbox.  I'm probably just  
 missing something minor at this point.  I'm going to down  
 everything and resync a little later to see if that cures my wows.

Does ctl_mboxlist -d on the frontend show mailboxes?

:wes

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

RE: murder configuration issue

[Gary W. Smith]

No it does not.  This is what shows in the master server log:
 
Dec  9 15:37:17 mdr01 mupdate[14222]: accepted connection
Dec  9 15:37:18 mdr01 mupdate[14222]: login: mdsfe [10.80.72.205] murder PLAIN 
User logged in
 
On the Front End I get nothing in the log file.
 
doing a tcpdump on port 3905, I can see then communicating (which I didn't see 
under 2.3.7 -- CentOS default version).  
 
I think I'm almost there.  I've blown away the /var/lib/imap/mailboxes.db file 
and ran runuser -  cyrus  -c ' /usr/lib/cyrus-imapd/ctl_mboxlist -m'  but 
that only created a 144 byte db file (still no mailboxes when I do a dump).
 
Gary





From: Wesley Craig [mailto:[EMAIL PROTECTED]
Sent: Tue 12/9/2008 12:36 PM
To: Gary W. Smith
Cc: info-cyrus@lists.andrew.cmu.edu
Subject: Re: murder configuration issue



On 09 Dec 2008, at 15:04, Gary W. Smith wrote:
 I updated to the FC10 package and now it seems to be working 
 better.  On the backend I can see the mailboxes that are synching 
 with the master, but the front end doesn't seem to be pulling the 
 information.  That is, it connects, I can see that in the log on 
 the master, and says it pulls the mailbox data but when I connect 
 via pop3 it says that it can't find the mailbox.  I'm probably just 
 missing something minor at this point.  I'm going to down 
 everything and resync a little later to see if that cures my wows.

Does ctl_mboxlist -d on the frontend show mailboxes?

:wes



Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Easy bug: undocumented option sasl_saslauthd_path to imapd

[Christopher DeMarco]

imapd.conf will accept an option:

   sasl_saslauthd_path: /var/spool/postfix/var/run/saslauthd/mux

instructing it to connect to the saslauthd socket in a non-standard
location (usually /var/run).  This is very useful if e.g. you're
running Postfix in a chroot.

A recursive grep for ``sasl_saslauthd_path'' in the source yields no
occurances of this option anywhere!  It should at least be in the
imapd.conf or imapd manpages, correct?


-- 
Christopher DeMarco [EMAIL PROTECTED]
IT Director
MAYA Group
+1-412-708-9660


Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

RE: murder configuration issue

[Gary W. Smith]

Added cyrus and root, now frontend is pulling mailboxes.
 
mupdate_admins: murder cyrus root
 
 



From: [EMAIL PROTECTED] on behalf of Gary W. Smith
Sent: Tue 12/9/2008 12:37 PM
To: Wesley Craig
Cc: info-cyrus@lists.andrew.cmu.edu
Subject: RE: murder configuration issue


No it does not.  This is what shows in the master server log:
 
Dec  9 15:37:17 mdr01 mupdate[14222]: accepted connection
Dec  9 15:37:18 mdr01 mupdate[14222]: login: mdsfe [10.80.72.205] murder PLAIN 
User logged in
 
On the Front End I get nothing in the log file.
 
doing a tcpdump on port 3905, I can see then communicating (which I didn't see 
under 2.3.7 -- CentOS default version).  
 
I think I'm almost there.  I've blown away the /var/lib/imap/mailboxes.db file 
and ran runuser -  cyrus  -c ' /usr/lib/cyrus-imapd/ctl_mboxlist -m'  but 
that only created a 144 byte db file (still no mailboxes when I do a dump).
 
Gary





From: Wesley Craig [mailto:[EMAIL PROTECTED]
Sent: Tue 12/9/2008 12:36 PM
To: Gary W. Smith
Cc: info-cyrus@lists.andrew.cmu.edu
Subject: Re: murder configuration issue



On 09 Dec 2008, at 15:04, Gary W. Smith wrote:
 I updated to the FC10 package and now it seems to be working 
 better.  On the backend I can see the mailboxes that are synching 
 with the master, but the front end doesn't seem to be pulling the 
 information.  That is, it connects, I can see that in the log on 
 the master, and says it pulls the mailbox data but when I connect 
 via pop3 it says that it can't find the mailbox.  I'm probably just 
 missing something minor at this point.  I'm going to down 
 everything and resync a little later to see if that cures my wows.

Does ctl_mboxlist -d on the frontend show mailboxes?

:wes



Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Another cache bug!

[Bron Gondwana]

Wow, this is the thanks I get for doing sanity checks on files, find more bugs!

This one is due to delayed expunge, plain and simple.  Cyrus decides what cache
records to copy during an IMAP COPY command by reading the cache offsets for
msgno and msgno+1 (or the end of the cache file if it's the last msgno).

Obviously if some intervening messages have already been deleted from the
cyrus.index then it will be copying all those cache records as well to the
destination folder.  Oops.

The attached patch reworks mailbox_cache_size into two functions, the second
being mailbox_cache_size_detail that takes memory locations for the cache mmap
rather than a mailbox object (because imapd doesn't update the locations in
the object correctly according to my testing, *sigh*.  Gotta love global
variables)

It then uses mailbox_cache_size_detail to calculate the ACTUAL record length
for this single cache item rather than blindly copying everything up to the
next index record's pointer.

Also note: in the event of cache corruption, mailbox_cache_size_detail returns
zero bytes, which correctly makes append_copy re-parse the message file.  It's
all shiny :)

Wes/Ken - please apply to CVS :)

Thanks,

Bron.
-- 
  Bron Gondwana
  [EMAIL PROTECTED]

Index: cyrus-imapd-2.3.13/imap/index.c
===
--- cyrus-imapd-2.3.13.orig/imap/index.c	2008-12-07 23:51:36.0 +
+++ cyrus-imapd-2.3.13/imap/index.c	2008-12-08 01:51:28.0 +
@@ -3574,13 +3574,9 @@ void *rock;
 	/* Force copy and re-parse of message */
 	copyargs-copymsg[copyargs-nummsg].cache_len = 0;
 }
-else if (msgno  (unsigned) imapd_exists) {
-	copyargs-copymsg[copyargs-nummsg].cache_len =
-	  CACHE_OFFSET(msgno+1) - CACHE_OFFSET(msgno);
-}
 else {
 	copyargs-copymsg[copyargs-nummsg].cache_len =
-	  cache_end - CACHE_OFFSET(msgno);
+	  mailbox_cache_size_detail(copyargs-copymsg[copyargs-nummsg].cache_begin, cache_base, cache_end);
 }
 copyargs-copymsg[copyargs-nummsg].seen = seenflag[msgno];
 copyargs-copymsg[copyargs-nummsg].system_flags = SYSTEM_FLAGS(msgno);
Index: cyrus-imapd-2.3.13/imap/mailbox.c
===
--- cyrus-imapd-2.3.13.orig/imap/mailbox.c	2008-12-08 01:46:02.0 +
+++ cyrus-imapd-2.3.13/imap/mailbox.c	2008-12-08 02:04:34.0 +
@@ -301,8 +301,6 @@ unsigned long mailbox_cache_size(struct 
 {
 const char *p;
 unsigned long cache_offset;
-unsigned int cache_ent;
-const char *cacheitem, *cacheitembegin;
 
 assert((msgno  0)  (msgno = mailbox-exists));
 
@@ -310,22 +308,33 @@ unsigned long mailbox_cache_size(struct 
  ((msgno-1) * mailbox-record_size));
 
 cache_offset = ntohl(*((bit32 *)(p+OFFSET_CACHE_OFFSET)));
-if (cache_offset  mailbox-cache_size) {
+
+return mailbox_cache_size_detail(mailbox-cache_base + cache_offset,
+ mailbox-cache_base,
+ mailbox-cache_size);
+}
+
+unsigned long mailbox_cache_size_detail(const char *cache_item,
+const char *cache_base,
+	unsigned long cache_size)
+{
+unsigned int cache_ent;
+const char *begin = cache_item;
+
+if (begin  cache_base || begin = cache_base + cache_size) {
+	/* already not in the area */
 	return 0;
 }
 
 /* Compute size of this record */
-cacheitembegin = cacheitem = mailbox-cache_base + cache_offset;
-if (cache_offset = mailbox-cache_size)
-	return 0;
 for (cache_ent = 0; cache_ent  NUM_CACHE_FIELDS; cache_ent++) {
-	cacheitem = CACHE_ITEM_NEXT(cacheitem);
-	if (cacheitem  cacheitembegin ||
-	cacheitem  cacheitembegin + mailbox-cache_size) {
+	cache_item = CACHE_ITEM_NEXT(cache_item);
+	if (cache_item  begin ||
+	cache_item  cache_base + cache_size) {
 	return 0; /* clearly bogus */
 	}
 }
-return (cacheitem - cacheitembegin);
+return (cache_item - begin);
 }
 
 /* function to be used for notification of mailbox changes/updates */
Index: cyrus-imapd-2.3.13/imap/mailbox.h
===
--- cyrus-imapd-2.3.13.orig/imap/mailbox.h	2008-12-08 01:51:37.0 +
+++ cyrus-imapd-2.3.13/imap/mailbox.h	2008-12-08 02:03:23.0 +
@@ -292,6 +292,9 @@ unsigned mailbox_cached_header(const cha
 unsigned mailbox_cached_header_inline(const char *text);
 
 unsigned long mailbox_cache_size(struct mailbox *mailbox, unsigned msgno);
+unsigned long mailbox_cache_size_detail(const char *cache_item, 
+	const char *cache_base, 
+	unsigned long cache_size);
 
 typedef unsigned mailbox_decideproc_t(struct mailbox *mailbox, void *rock,
   unsigned char *indexbuf,

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

RE: murder configuration issue final stretch

[Gary W. Smith]

Wesley, 
 
I'm on the final stretch.  I have mailboxes seen at all angles.  If I telnet to 
the frontend I can see the backend mailboxes on both servers.  Yay.  The 
problem now is delivery.  I tried setting up lmtpproxyd but I get some errors 
and the email gets queued up on the frontend server.  This is fine for now 
while we have the mail going to the proper places on the backend but going 
forward we will need to be able to deliver via the frontend (or murder server).
 
on the frontend:
/etc/cyrus.conf
lmtp  cmd=lmtpproxyd listen=/var/lib/imap/socket/lmtp prefork=0
 
/var/lib/imap/socket
srwxrwxrwx  1 root  root0 Dec  9 19:38 lmtp
 
mailq contains:
(host mdsfe[/var/lib/imap/socket/lmtp] said: 451 4.4.3 Remote server 
unavailable (in reply to end of DATA command))
 
Please correct me if I'm wrong but my understanding is that lmtp will be used 
to deliver the message from the frontend to the backend (thus bypassing postfix 
in this case).  When I do a netstat -atunep on the backend server, I don't see 
the lmtp port open.  I would assume that this could be part of the problem.  
 
On the backend servers, we have this line in the /etc/cyrus.conf
 
lmtpunix  cmd=lmtpd listen=/var/lib/imap/socket/lmtp prefork=1
I've also tried
lmtp  cmd=lmtpd listen=/var/lib/imap/socket/lmtp prefork=1 (with 
prefork 0 and 1 -- example show zero).
 
Any ideas on how to resolve this part?  Or better question, what am I missing 
(besides a few screws).
 
Gary

 



From: Wesley Craig [mailto:[EMAIL PROTECTED]
Sent: Tue 12/9/2008 12:36 PM
To: Gary W. Smith
Cc: info-cyrus@lists.andrew.cmu.edu
Subject: Re: murder configuration issue



On 09 Dec 2008, at 15:04, Gary W. Smith wrote:
 I updated to the FC10 package and now it seems to be working 
 better.  On the backend I can see the mailboxes that are synching 
 with the master, but the front end doesn't seem to be pulling the 
 information.  That is, it connects, I can see that in the log on 
 the master, and says it pulls the mailbox data but when I connect 
 via pop3 it says that it can't find the mailbox.  I'm probably just 
 missing something minor at this point.  I'm going to down 
 everything and resync a little later to see if that cures my wows.

Does ctl_mboxlist -d on the frontend show mailboxes?

:wes



Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

RE: murder configuration issue final stretch

[Andrew Morgan]

On Tue, 9 Dec 2008, Gary W. Smith wrote:

 Wesley,

 I'm on the final stretch.  I have mailboxes seen at all angles.  If I telnet 
 to the frontend I can see the backend mailboxes on both servers.  Yay.  The 
 problem now is delivery.  I tried setting up lmtpproxyd but I get some errors 
 and the email gets queued up on the frontend server.  This is fine for now 
 while we have the mail going to the proper places on the backend but going 
 forward we will need to be able to deliver via the frontend (or murder 
 server).

 on the frontend:
 /etc/cyrus.conf
 lmtp  cmd=lmtpproxyd listen=/var/lib/imap/socket/lmtp prefork=0

 /var/lib/imap/socket
 srwxrwxrwx  1 root  root0 Dec  9 19:38 lmtp

 mailq contains:
 (host mdsfe[/var/lib/imap/socket/lmtp] said: 451 4.4.3 Remote server 
 unavailable (in reply to end of DATA command))

 Please correct me if I'm wrong but my understanding is that lmtp will be used 
 to deliver the message from the frontend to the backend (thus bypassing 
 postfix in this case).  When I do a netstat -atunep on the backend server, I 
 don't see the lmtp port open.  I would assume that this could be part of the 
 problem.

 On the backend servers, we have this line in the /etc/cyrus.conf

 lmtpunix  cmd=lmtpd listen=/var/lib/imap/socket/lmtp prefork=1
 I've also tried
 lmtp  cmd=lmtpd listen=/var/lib/imap/socket/lmtp prefork=1 (with 
 prefork 0 and 1 -- example show zero).

That should probably be:

   lmtp  cmd=lmtpd listen=lmtp prefork=1 maxchild=100

You want one of them to listen on the lmtp network socket, rather than 
both listening on the lmtp unix socket.

Andy

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

RE: murder configuration issue final stretch

[Gary W. Smith]

Andrew, 
 
Made the change on the backend server.  Now is complains that remote server is 
unavailable and the corresponding log on the backend is saying badlogin: 
10.80.72.205 PLAIN SASL(-13): authentication failure: Password verification 
failed.  At least they are talking now.  
 
I tried it with _mechs: PLAIN but when I do that I can't connect to the backend 
boxes from the frontend using telnet
 
#mds01_mechs: PLAIN
mds01_password: mypassword
 
On the backend I have:
 
proxyservers: murder
 
and I set the password with both saslpasswd -c murder and passwd as well.  
 
Gary




From: Andrew Morgan [mailto:[EMAIL PROTECTED]
Sent: Tue 12/9/2008 5:32 PM
To: Gary W. Smith
Cc: Wesley Craig; info-cyrus@lists.andrew.cmu.edu
Subject: RE: murder configuration issue final stretch



On Tue, 9 Dec 2008, Gary W. Smith wrote:

 Wesley,

 I'm on the final stretch.  I have mailboxes seen at all angles.  If I telnet 
 to the frontend I can see the backend mailboxes on both servers.  Yay.  The 
 problem now is delivery.  I tried setting up lmtpproxyd but I get some errors 
 and the email gets queued up on the frontend server.  This is fine for now 
 while we have the mail going to the proper places on the backend but going 
 forward we will need to be able to deliver via the frontend (or murder 
 server).

 on the frontend:
 /etc/cyrus.conf
 lmtp  cmd=lmtpproxyd listen=/var/lib/imap/socket/lmtp prefork=0

 /var/lib/imap/socket
 srwxrwxrwx  1 root  root0 Dec  9 19:38 lmtp

 mailq contains:
 (host mdsfe[/var/lib/imap/socket/lmtp] said: 451 4.4.3 Remote server 
 unavailable (in reply to end of DATA command))

 Please correct me if I'm wrong but my understanding is that lmtp will be used 
 to deliver the message from the frontend to the backend (thus bypassing 
 postfix in this case).  When I do a netstat -atunep on the backend server, I 
 don't see the lmtp port open.  I would assume that this could be part of the 
 problem.

 On the backend servers, we have this line in the /etc/cyrus.conf

 lmtpunix  cmd=lmtpd listen=/var/lib/imap/socket/lmtp prefork=1
 I've also tried
 lmtp  cmd=lmtpd listen=/var/lib/imap/socket/lmtp prefork=1 (with 
 prefork 0 and 1 -- example show zero).

That should probably be:

   lmtp  cmd=lmtpd listen=lmtp prefork=1 maxchild=100

You want one of them to listen on the lmtp network socket, rather than
both listening on the lmtp unix socket.

Andy



Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Easy bug: undocumented option sasl_saslauthd_path to imapd

[Rudy Gevaert]

Christopher DeMarco wrote:
 imapd.conf will accept an option:
 
sasl_saslauthd_path: /var/spool/postfix/var/run/saslauthd/mux
 
 instructing it to connect to the saslauthd socket in a non-standard
 location (usually /var/run).  This is very useful if e.g. you're
 running Postfix in a chroot.
 
 A recursive grep for ``sasl_saslauthd_path'' in the source yields no
 occurances of this option anywhere!  It should at least be in the
 imapd.conf or imapd manpages, correct?

Hi please file a bug in the bugtracker, then your remark will not be 
lost and will be looked at asap.

Rudy

-- 
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Rudy Gevaert  [EMAIL PROTECTED]  tel:+32 9 264 4734
Directie ICT, afd. Infrastructuur  Direction ICT, Infrastructure dept.
Groep Systemen Systems group
Universiteit Gent  Ghent University
Krijgslaan 281, gebouw S9, 9000 Gent, Belgie   www.UGent.be
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

RE: murder configuration issue final stretch

[Gary W. Smith]

Andy/Wesley,
 
First off, thanks for all of the help.  I've gotten pretty far I think.  I ran 
into a couple problems and some notes on some list groups about dead options 
that were shown in examples.
 
http://garysmith.pbwiki.com/Cyrus
 
I have put all of my configs into a wiki (broken down by server/type).  The 
problem that I'm running into right now is that if I log into the frontend box 
using cyradmin (as root or cyrus) I can see mailboxes but when I go to create 
one on a backend server, cyradm prompts me for the password for the 
corresponding account on the remote machine.  I'm not sure if this is by design 
or an issue.
 
The other big issue is that I have lmtp configured on the frontend to forward 
to the backend.  The lmtp process is running on the backend as I can telnet to 
it (telnet ip lmtp).  On the backend I seem to be getting a SASL2 auth error.  
 
badlogin: 10.80.72.1 PLAIN SASL(-13): authentication failure: Password 
verification failed
 
I believe this is the final problem.  Now there is another crazy setting in the 
mix (but it shoudln't be an impact).  We use pam/nss mysql.  This has been 
working for some time and is working well on stand alone servers.  I have 
configured it on the frontend server as well.  I can login to the frontend just 
fine (which is a mysql account).
 
That's my outstanding issues at this time that (as I can't get past those).  
 
The last thing that I'm looking into is autocreatequota setting.  We used this 
on the standalone boxes and it worked well for us.  When we attempt to create 
an account on the frontend it fails as we don't have it enabled on the 
frontend.  When we enable it on the frontend the account is created on the 
frontent and attempts to delete or move (rename) fail.  Is there any hope for 
autocreate?
 
 



From: Andrew Morgan [mailto:[EMAIL PROTECTED]
Sent: Tue 12/9/2008 5:32 PM
To: Gary W. Smith
Cc: Wesley Craig; info-cyrus@lists.andrew.cmu.edu
Subject: RE: murder configuration issue final stretch



On Tue, 9 Dec 2008, Gary W. Smith wrote:

 Wesley,

 I'm on the final stretch.  I have mailboxes seen at all angles.  If I telnet 
 to the frontend I can see the backend mailboxes on both servers.  Yay.  The 
 problem now is delivery.  I tried setting up lmtpproxyd but I get some errors 
 and the email gets queued up on the frontend server.  This is fine for now 
 while we have the mail going to the proper places on the backend but going 
 forward we will need to be able to deliver via the frontend (or murder 
 server).

 on the frontend:
 /etc/cyrus.conf
 lmtp  cmd=lmtpproxyd listen=/var/lib/imap/socket/lmtp prefork=0

 /var/lib/imap/socket
 srwxrwxrwx  1 root  root0 Dec  9 19:38 lmtp

 mailq contains:
 (host mdsfe[/var/lib/imap/socket/lmtp] said: 451 4.4.3 Remote server 
 unavailable (in reply to end of DATA command))

 Please correct me if I'm wrong but my understanding is that lmtp will be used 
 to deliver the message from the frontend to the backend (thus bypassing 
 postfix in this case).  When I do a netstat -atunep on the backend server, I 
 don't see the lmtp port open.  I would assume that this could be part of the 
 problem.

 On the backend servers, we have this line in the /etc/cyrus.conf

 lmtpunix  cmd=lmtpd listen=/var/lib/imap/socket/lmtp prefork=1
 I've also tried
 lmtp  cmd=lmtpd listen=/var/lib/imap/socket/lmtp prefork=1 (with 
 prefork 0 and 1 -- example show zero).

That should probably be:

   lmtp  cmd=lmtpd listen=lmtp prefork=1 maxchild=100

You want one of them to listen on the lmtp network socket, rather than
both listening on the lmtp unix socket.

Andy



Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html