Re: followup: stuck lmtpd processes
On Wed, 24 Sep 2003, Henrique de Moraes Holschuh wrote: On Wed, 24 Sep 2003, Etienne Goyer wrote: On Wed, Sep 24, 2003 at 11:27:46AM -0400, Rob Siemborski wrote: However, I have looked into this and to my surprise, Linux is indeed restarting the system calls instead of returning with EINTR. However, the answer here is to set up the alarm() handler with sigaction without setting SA_RESTART, not to jump through select() hoops or make nonblocking lock attempts. I consult my local Unix guru on the subject, and he point me to Advanced Programming in the Unix Environment by W. Richard Stevens, section 10.5 (page 275 in my edition) Interrupted System Calls. The revelancy of this text may be questionned since it was published in 1992, but the behavior of SVR4 vs BSD differ substantially in this regard according to it. My guru concluded that system call interuption by signal is an assumption that may lead to portability problem. In the fud case, he is right. With SYSV you will get the interrupted system call, unless you tell it somehow not to do it (the SA_RESTART stuff). If we are to accomodate the BSDs, we can: 1. Let them have the short end of the stick (they get what we have now, that is, deadlocks). Not good. 2. Let them use the low-performance non-blocking mode (good solution). 3. Find out how to get EINTR from BSD (it should be possible nowadays). As for old legacy systems (too old BSDs, SunOS 4, very old Linux), well, I am inclined to simply ignore them. Let them use solution (2) above. That is the least of their problems, given the amount of annoying and dangerous bugs those old kernels have. #2 doesn't sound like a good option for anyone. It is not clear from the context in this message whether you want restartable system calls or not. BSD4.2 introduced restartable system calls. BSD4.3 introduced siginterrupt() to disable restartable system calls for a certain signal. So even with SunOS 4, you'd have the option. Newer BSDs have SA_RESTART via sigaction(). sigaction() is supposed to conform to the POSIX.1 standard, and therefore probably works the same as Linux. -- 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 Tom
Cyrdump
Hello, Is there a way re-inject the mails produced by cyrdump back into Cyrus ? Cyrdump makes a good job at backing up the mails and I was wondering if there is a complementary program that could just put them back. tia, mitu
Re: followup: stuck lmtpd processes
On Fri, 26 Sep 2003, Tom wrote: On Wed, 24 Sep 2003, Henrique de Moraes Holschuh wrote: With SYSV you will get the interrupted system call, unless you tell it somehow not to do it (the SA_RESTART stuff). If we are to accomodate the BSDs, we can: 1. Let them have the short end of the stick (they get what we have now, that is, deadlocks). Not good. 2. Let them use the low-performance non-blocking mode (good solution). 3. Find out how to get EINTR from BSD (it should be possible nowadays). As for old legacy systems (too old BSDs, SunOS 4, very old Linux), well, I am inclined to simply ignore them. Let them use solution (2) above. That is the least of their problems, given the amount of annoying and dangerous bugs those old kernels have. #2 doesn't sound like a good option for anyone. It is not clear from It is tried and true, and the patch is here NOW. the context in this message whether you want restartable system calls or not. BSD4.2 introduced restartable system calls. BSD4.3 introduced siginterrupt() to disable restartable system calls for a certain signal. So even with SunOS 4, you'd have the option. I have the code ready for POSIX. If anyone who uses SunOS and BSD4.2/4.3 wants to contribute the autoconf code and changes to get non-restartable syscalls for a signal, they're welcome... I don't like to write code I can't test. -- 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
[PATCH] lockbreak using sigalarm (was followup: stuck lmtpd processes)
There is now a preliminary patch available. http://bugzilla.andrew.cmu.edu/show_bug.cgi?id=1177 Please test the second patch, and report back using the bug tracking system. -- 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
cant login to cyradm
Hi! I just installed CYRUS with SASL 2.0 on my RedHat 8 server.. But I not know what is default password for cyrus?? I know from .conf file that admin user is cyrus.. but whats its passowrd..i dont know.. It would be of great help if you can tell how to log in? Thanks in advance Dasmeet
1....
Title: 555
Re: cant login to cyradm
Hi! I just installed CYRUS with SASL 2.0 on my RedHat 8 server.. But I not know what is default password for cyrus?? I know from .conf file that admin user is cyrus.. but whats its passowrd..i dont know.. It would be of great help if you can tell how to log in? It depends on where your passwords are stored. If you're using PAM against /etc/shadow, then you can simply use passwd cyrus to give the cyrus user a password. Regards, Simon Thanks in advance Dasmeet
Re: cant login to cyradm
I guess you installed Simon Matter's rpm. If this is the case, the cyrus user have been created, but no password had been set. Set one with passwd cyrus. From there on, still assuming you are using Simon Matter's rpm, you can start the cyrus administration utility by running : cyradm --user=cyrus localhost Type 'help' at the prompt for online help. You will need to create mailbox for your user. The command would most likely be cm user/username. I installed Simon Matter's rpm on RH 8 last wednesday and noticed that that the perl package don't work out of the box. If you get perl error when starting cyradmin, you will need to follow these instruction to recompile and reinstall the rpm : - Grab the cyrus-imapd.2.1.15-1.src.rpm - Install with rpm -ivh cyrus-imapd.2.1.15-1.src.rpm - cd to /usr/src/redhat/SPECS - Edit the cyrus-imapd.spec file, increment the Release from 1 to 2. - Build the rpm with rpmbuild -bb cyrus-imapd.spec. Hopefully, you won't stumble on dependency problem. If you do, you will need to resolve them :( - Upgrade to your freshly built rpm with rpm -Uvh /usr/src/redhat/RPMS/i386/cyrus-* - Profit !!! Ask for help for any problem arise, we'll be glad to give a hand. I do think however that you should read the doc first. On Fri, Sep 26, 2003 at 07:35:19AM -0400, [EMAIL PROTECTED] wrote: Hi! I just installed CYRUS with SASL 2.0 on my RedHat 8 server.. But I not know what is default password for cyrus?? I know from .conf file that admin user is cyrus.. but whats its passowrd..i dont know.. It would be of great help if you can tell how to log in? Thanks in advance Dasmeet -- Etienne GoyerLinux Québec Technologies Inc. http://www.LinuxQuebec.com [EMAIL PROTECTED]
Re: Preserving seen state when converting from mbox
Ho boy ... that make me cry ... However, after verification I was *WAY* off-track concerning the size of the mbox we need to transfer. Apparently, there is only around 800 MB (phew!). The machine is a recent quad-XEON box 2 GB of RAM. By contrast, what does your hardware looked like ? On Thu, Sep 25, 2003 at 10:52:59PM +0200, Jure Pecar wrote: On Thu, 25 Sep 2003 15:04:48 -0400 (EDT) Igor Brezac [EMAIL PROTECTED] wrote: I do not think you have enough time to transfer several gigs (if not more) of email in just a few hours over IMAP protocol. Just for the reference, it took us about two weeks to transfer about 300gb of mailspool from one live system to another (with perdition in front), on a reasonably fast hw, with custom php scripts doing imap2imap copy (and related user imgration) in parallel. -- Jure Pecar -- Etienne GoyerLinux Québec Technologies Inc. http://www.LinuxQuebec.com [EMAIL PROTECTED]
Re: cant login to cyradm
In fact you should always recompile the rpms if you're not running RedHat 7.2 (I build the binaries on 7.2). Just do it like this: rpmbuild --rebuild cyrus-imapd.2.1.15-1.src.rpm rpm -Uvh /usr/src/redhat/RPMS/i386/cyrus-* /usr/src/redhat/RPMS/i386/perl-Cyrus* And BTW, if you're using the default configuration which uses PAM, try: passwd cyrus cyradm --user=cyrus --auth=login localhost cm user.username Regards, Simon I guess you installed Simon Matter's rpm. If this is the case, the cyrus user have been created, but no password had been set. Set one with passwd cyrus. From there on, still assuming you are using Simon Matter's rpm, you can start the cyrus administration utility by running : cyradm --user=cyrus localhost Type 'help' at the prompt for online help. You will need to create mailbox for your user. The command would most likely be cm user/username. I installed Simon Matter's rpm on RH 8 last wednesday and noticed that that the perl package don't work out of the box. If you get perl error when starting cyradmin, you will need to follow these instruction to recompile and reinstall the rpm : - Grab the cyrus-imapd.2.1.15-1.src.rpm - Install with rpm -ivh cyrus-imapd.2.1.15-1.src.rpm - cd to /usr/src/redhat/SPECS - Edit the cyrus-imapd.spec file, increment the Release from 1 to 2. - Build the rpm with rpmbuild -bb cyrus-imapd.spec. Hopefully, you won't stumble on dependency problem. If you do, you will need to resolve them :( - Upgrade to your freshly built rpm with rpm -Uvh /usr/src/redhat/RPMS/i386/cyrus-* - Profit !!! Ask for help for any problem arise, we'll be glad to give a hand. I do think however that you should read the doc first. On Fri, Sep 26, 2003 at 07:35:19AM -0400, [EMAIL PROTECTED] wrote: Hi! I just installed CYRUS with SASL 2.0 on my RedHat 8 server.. But I not know what is default password for cyrus?? I know from .conf file that admin user is cyrus.. but whats its passowrd..i dont know.. It would be of great help if you can tell how to log in? Thanks in advance Dasmeet -- Etienne GoyerLinux Québec Technologies Inc. http://www.LinuxQuebec.com [EMAIL PROTECTED]
Re: cant login to cyradm
On Fri, Sep 26, 2003 at 03:13:48PM +0200, Simon Matter wrote: And BTW, if you're using the default configuration which uses PAM, try: Did'nt it use saslauthd with the shadow plugin ? -- Etienne GoyerLinux Québec Technologies Inc. http://www.LinuxQuebec.com [EMAIL PROTECTED]
Re: Preserving seen state when converting from mbox
On Thu, Sep 25, 2003 at 03:04:48PM -0400, Igor Brezac wrote:
On Thu, 25 Sep 2003, Etienne Goyer wrote:
On Thu, Sep 25, 2003 at 01:29:30PM -0400, Igor Brezac wrote:
mailutil append /path/to/mbox
{new.cyrus.server/user=mbox_cyrus_user/authuser=proxy_user/norsh}INBOX
You made my day !!! Exactly what I needed.
You will be prompted for the 'proxy_user' password. You can hardcode the
password with a small change in mailutil.c. Let me know if you need help
with this...
I'd like help, if possible. The code is pretty dense, so if you know
where I have to plug the password, that would save me ton of time.
Thanks a lot !
--
Etienne GoyerLinux Québec Technologies Inc.
http://www.LinuxQuebec.com [EMAIL PROTECTED]
Re: cant login to cyradm
On Fri, Sep 26, 2003 at 03:13:48PM +0200, Simon Matter wrote: And BTW, if you're using the default configuration which uses PAM, try: Did'nt it use saslauthd with the shadow plugin ? The cyrus-imapd rpm uses saslauthd per default. You're right, the RedHat cyrus-sasl rpms use shadow per default. To use PAM you still run saslauthd but with different config: [EMAIL PROTECTED] root]# cat /etc/sysconfig/saslauthd MECH=pam Simon -- Etienne GoyerLinux Québec Technologies Inc. http://www.LinuxQuebec.com [EMAIL PROTECTED]
mailbox.db problem?
Hello, I'm running Cyrus imapd 2.2.1 BETA and around 5:20 yesterday some accounts started having problems logging into cyrus. It doesn't appear to be affecting everyone on the server. When I try to pop one of the accounts the error is [SYS/PERM] Unable to locate mail drop. This is on a Red Hat 9 box. I'm wondering if going into cyradm and add the mbox back would fix the problem? Or is there a better course of action. -- Hank Beatty [EMAIL PROTECTED]
Re: mailbox.db problem?
OK. It appears that all the mailboxes after the letter c do not appear in the mailboxes.db file anymore. Any new accounts are still being added properly. Any ideas on where to look to figure out what caused this? Any ideas on a way to fix it? I was thinking of running the reconstruct -m. I also did a test of one mailbox with reconstruct -f mailbox, but that did not seem to help. The mailbox still isn't in the mailboxes.db file. Thanks, Hank On Fri, 2003-09-26 at 10:21, Hank Beatty wrote: Hello, I'm running Cyrus imapd 2.2.1 BETA and around 5:20 yesterday some accounts started having problems logging into cyrus. It doesn't appear to be affecting everyone on the server. When I try to pop one of the accounts the error is [SYS/PERM] Unable to locate mail drop. This is on a Red Hat 9 box. I'm wondering if going into cyradm and add the mbox back would fix the problem? Or is there a better course of action. -- Hank Beatty [EMAIL PROTECTED]
Re: Preserving seen state when converting from mbox
On Fri, 26 Sep 2003, Etienne Goyer wrote:
On Thu, Sep 25, 2003 at 03:04:48PM -0400, Igor Brezac wrote:
On Thu, 25 Sep 2003, Etienne Goyer wrote:
On Thu, Sep 25, 2003 at 01:29:30PM -0400, Igor Brezac wrote:
mailutil append /path/to/mbox
{new.cyrus.server/user=mbox_cyrus_user/authuser=proxy_user/norsh}INBOX
You made my day !!! Exactly what I needed.
You will be prompted for the 'proxy_user' password. You can hardcode the
password with a small change in mailutil.c. Let me know if you need help
with this...
I'd like help, if possible. The code is pretty dense, so if you know
where I have to plug the password, that would save me ton of time.
Try:
--- mailutil.c.orig Fri Sep 26 11:39:12 2003
+++ mailutil.c Fri Sep 26 11:39:38 2003
@@ -598,7 +598,7 @@
username[NETMAXUSER-1] = '\0';
if (s = strchr (username,'\n')) *s = '\0';
}
- strcpy (password,getpass (password: ));
+ strcpy (password, your_pass);
}
--
Igor
Re: mailbox.db problem?
Do you happen to run my RPMs? If yes, then you should find a mailbox dump of last night in /var/lib/imap/backup/mboxlist.gz. There are also copies of the last week in mboxlist.1.gz, mboxlist.2.gz... HTH Simon OK. It appears that all the mailboxes after the letter c do not appear in the mailboxes.db file anymore. Any new accounts are still being added properly. Any ideas on where to look to figure out what caused this? Any ideas on a way to fix it? I was thinking of running the reconstruct -m. I also did a test of one mailbox with reconstruct -f mailbox, but that did not seem to help. The mailbox still isn't in the mailboxes.db file. Thanks, Hank On Fri, 2003-09-26 at 10:21, Hank Beatty wrote: Hello, I'm running Cyrus imapd 2.2.1 BETA and around 5:20 yesterday some accounts started having problems logging into cyrus. It doesn't appear to be affecting everyone on the server. When I try to pop one of the accounts the error is [SYS/PERM] Unable to locate mail drop. This is on a Red Hat 9 box. I'm wondering if going into cyradm and add the mbox back would fix the problem? Or is there a better course of action. -- Hank Beatty [EMAIL PROTECTED] -- Simon Matter Tel: +41 61 695 57 35 Fr.Sauter AG / CITFax: +41 61 695 53 30 Im Surinam 55 CH-4016 Basel [mailto:[EMAIL PROTECTED]
Re: mailbox.db problem?
No. Bummer. :( I would really appreciate it if you could send me (or let me know where I could find) the scripts that are doing the backups that you mention. Hank On Fri, 2003-09-26 at 12:09, Simon Matter wrote: Do you happen to run my RPMs? If yes, then you should find a mailbox dump of last night in /var/lib/imap/backup/mboxlist.gz. There are also copies of the last week in mboxlist.1.gz, mboxlist.2.gz... HTH Simon OK. It appears that all the mailboxes after the letter c do not appear in the mailboxes.db file anymore. Any new accounts are still being added properly. Any ideas on where to look to figure out what caused this? Any ideas on a way to fix it? I was thinking of running the reconstruct -m. I also did a test of one mailbox with reconstruct -f mailbox, but that did not seem to help. The mailbox still isn't in the mailboxes.db file. Thanks, Hank On Fri, 2003-09-26 at 10:21, Hank Beatty wrote: Hello, I'm running Cyrus imapd 2.2.1 BETA and around 5:20 yesterday some accounts started having problems logging into cyrus. It doesn't appear to be affecting everyone on the server. When I try to pop one of the accounts the error is [SYS/PERM] Unable to locate mail drop. This is on a Red Hat 9 box. I'm wondering if going into cyradm and add the mbox back would fix the problem? Or is there a better course of action. -- Hank Beatty [EMAIL PROTECTED] -- Hank Beatty [EMAIL PROTECTED]
Script to dump sasldb2 to a text file
Howdy all, I've got a shell script I created to dump sasldb2 to a text file. I created the script so that I could migrate my users from my old mailserver, running in one domain, to my new mailserver running in a new domain. I'm also migrating to the 2.2 codebase so that I can do virtual hosting. Since I didn't have any way to easily migrate the users properly, I created this script to dump the data from my sasldb2 database into a text format. The output file is contains tab-separated values with one entry per line and has the format: username realm password If the list has any interest in the script, I'd be happy to post it. Will William K. Hardeman [EMAIL PROTECTED] http://www.wkh.org The most exciting phrase to hear in science, the one that heralds new discoveries, is not Eureka! (I found it!) but That's funny ... -- Isaac Asimov Always listen to experts. They'll tell you what can't be done and why. Then do it. --Robert A. Heinlein
Re: mailbox.db problem?
No. Bummer. :(
I would really appreciate it if you could send me (or let me know where
I could find) the scripts that are doing the backups that you mention.
The rpms are here http://home.teleport.ch/simix/
-Simon
[EMAIL PROTECTED] /root]# cat /etc/cron.daily/cyrus-imapd
#!/bin/sh
#
# This file is run on a daily basis to perform a backup of your
# mailbox list which can be used to recreate mailboxes.db from backup.
# Restore is done using ctl_mboxlist after uncompressing the file.
backdir=/var/lib/imap/backup
mboxlist=${backdir}/mboxlist
[ -x /usr/lib/cyrus-imapd/ctl_mboxlist ] || exit 0
# rotate mailbox lists
[ -f ${mboxlist}.5.gz ] mv -f ${mboxlist}.5.gz ${mboxlist}.6.gz
[ -f ${mboxlist}.4.gz ] mv -f ${mboxlist}.4.gz ${mboxlist}.5.gz
[ -f ${mboxlist}.3.gz ] mv -f ${mboxlist}.3.gz ${mboxlist}.4.gz
[ -f ${mboxlist}.2.gz ] mv -f ${mboxlist}.2.gz ${mboxlist}.3.gz
[ -f ${mboxlist}.1.gz ] mv -f ${mboxlist}.1.gz ${mboxlist}.2.gz
[ -f ${mboxlist}.gz ] mv -f ${mboxlist}.gz ${mboxlist}.1.gz
# export mailboxes.db
su - cyrus -c umask 077 ; /usr/lib/cyrus-imapd/ctl_mboxlist -d | gzip
${mboxlist}.gz
exit 0
# EOF
Hank
On Fri, 2003-09-26 at 12:09, Simon Matter wrote:
Do you happen to run my RPMs? If yes, then you should find a mailbox
dump
of last night in /var/lib/imap/backup/mboxlist.gz. There are also copies
of the last week in mboxlist.1.gz, mboxlist.2.gz...
HTH
Simon
OK. It appears that all the mailboxes after the letter c do not
appear
in the mailboxes.db file anymore. Any new accounts are still being
added
properly.
Any ideas on where to look to figure out what caused this? Any ideas
on
a way to fix it?
I was thinking of running the reconstruct -m. I also did a test of one
mailbox with reconstruct -f mailbox, but that did not seem to help.
The
mailbox still isn't in the mailboxes.db file.
Thanks,
Hank
On Fri, 2003-09-26 at 10:21, Hank Beatty wrote:
Hello,
I'm running Cyrus imapd 2.2.1 BETA and around 5:20 yesterday some
accounts started having problems logging into cyrus. It doesn't
appear
to be affecting everyone on the server.
When I try to pop one of the accounts the error is [SYS/PERM] Unable
to
locate mail drop.
This is on a Red Hat 9 box.
I'm wondering if going into cyradm and add the mbox back would fix
the
problem? Or is there a better course of action.
--
Hank Beatty [EMAIL PROTECTED]
--
Hank Beatty [EMAIL PROTECTED]
--
Simon Matter Tel: +41 61 695 57 35
Fr.Sauter AG / CITFax: +41 61 695 53 30
Im Surinam 55
CH-4016 Basel [mailto:[EMAIL PROTECTED]
Re: Preserving seen state when converting from mbox
Thank you very much, work perfectly.
On Fri, Sep 26, 2003 at 11:43:15AM -0400, Igor Brezac wrote:
On Fri, 26 Sep 2003, Etienne Goyer wrote:
On Thu, Sep 25, 2003 at 03:04:48PM -0400, Igor Brezac wrote:
On Thu, 25 Sep 2003, Etienne Goyer wrote:
On Thu, Sep 25, 2003 at 01:29:30PM -0400, Igor Brezac wrote:
mailutil append /path/to/mbox
{new.cyrus.server/user=mbox_cyrus_user/authuser=proxy_user/norsh}INBOX
You made my day !!! Exactly what I needed.
You will be prompted for the 'proxy_user' password. You can hardcode the
password with a small change in mailutil.c. Let me know if you need help
with this...
I'd like help, if possible. The code is pretty dense, so if you know
where I have to plug the password, that would save me ton of time.
Try:
--- mailutil.c.orig Fri Sep 26 11:39:12 2003
+++ mailutil.c Fri Sep 26 11:39:38 2003
@@ -598,7 +598,7 @@
username[NETMAXUSER-1] = '\0';
if (s = strchr (username,'\n')) *s = '\0';
}
- strcpy (password,getpass (password: ));
+ strcpy (password, your_pass);
}
--
Igor
--
Etienne GoyerLinux Québec Technologies Inc.
http://www.LinuxQuebec.com [EMAIL PROTECTED]
[no subject]
=?ISO-8859-1?Q?=BE?= [EMAIL PROTECTED] Subject: =?ISO-8859-1?Q?=C6=F3=D2=B5=BD=E2=BE=F6=B7=BD=B0=B8?= To: [EMAIL PROTECTED] Content-Type: text/html;charset=GB2312 Reply-To: [EMAIL PROTECTED] Date: Sat, 27 Sep 2003 04:21:11 +0800 X-Priority: 3 X-Mailer: Foxmail 4.2 [cn] html head meta http-equiv=Content-Type content=text/html; charset=gb2312 meta name=GENERATOR content=Microsoft FrontPage 4.0 meta name=ProgId content=FrontPage.Editor.Document titleÉÌÕ½²Ð¿á/title /head body pspan style=mso-bidi-font-size: 12.0ptspan style=mso-bidi-font-size: 12.0pt; mso-hansi-font-family: ÐÂËÎÌåÉÌÕ½²Ð¿á£¬ÆóÒµÏëÐû´«×Ô¼º¿É¾Þ¶î·ÑÓÃÁîÈËÍ·Í´/spanspan style=mso-hansi-font-family: ÐÂËÎÌå¡£/span/span/p pspan style=mso-bidi-font-size: 12.0pta href=http://www.dhkjweb.com;span style=mso-hansi-font-family: ÐÂËÎÌå; mso-bidi-font-size: 12.0ptfont color=#FFÖ»ÒªÔڴ˵ã»÷/font/spanspan style=mso-bidi-font-size: 12.0pt; mso-ascii-font-family: Times New Romanfont color=#008000¡¶Óʼþר¼Ò¡·/fontÁ¢¼´ÎªÄúÌṩ½â¾ö·½°¸/spanspan style=mso-ascii-font-family: Times New Roman; mso-bidi-font-size: 12.0pt£¡/span/a/span/p /body /html
Murder question : restarting the mupdate master daemon, mailbox list incoherent on frontend
Bonjour à tous, I just noticed something and wonder if there is something I am missing. I changed altnamespace across a Murder (not yet in production). Modified /etc/imapd.conf and restart master on frontend, then mupdate and then backend. I was playing around in IMP and deleted a few folders. Then, I tried recreating a folder I just deleted with the same name. It complained that the folder already exist. I check with cyradm on the backend and can see that they are really gone. I then checked on the frontend and, to my surprise, all the folder I thought I had deleted where still shown in cyradm! I restarted cyrus on the frontend, checked again with cyradm and now they are gone. I can then recreate my folder correctly. I guess what happened is that the information the frontend held about the mailbox list and their location was stale. I thought that the mupdate master server would push change in folder list back to frontend but apparently, it's the frontend that pull (or at least, initiate the update) that information instead. Is that right ? If yes, does that imply that when cyrus need restarting across a murder, we should do backend first, mupdate master second and frontend last ? Thanks for your insight ! -- Etienne GoyerLinux Québec Technologies Inc. http://www.LinuxQuebec.com [EMAIL PROTECTED]
Installing Cyrus/Postfix
Hello, I try to setup a mailserver on RedHat 7.3 with the following configuration: Postfix 2.0.14 Cyrus SASL 2.1.15 Cyrus Imapd 2.1.15 pam_mysql web-cyradmin 0.5.3-1 Finally I want a mailserver which is completely setup by the mySQL database and all authentification and domain/user setups should be done there. As of the http://ldp.mirror.techno-link.com/HOWTO/Postfix-Cyrus-Web-cyradm-HOWTO/moreinfo.html HOWTO it should work as supposed. The installation went smoothly with some path problems (BDB, SSL, ...) which could be fixed. Compilation of pam_mysql ended with some warnings but no fatal error, so I think it is working. When testing my setup there are the problems appearing. Postfix is running well, I can authenticate myself by plain-authentication. But authentication by software CRAM-MD5 don't work. Can I get this working too? Anyways mails can be sent and thats the most important thing :) [well and not-authenticated users can't, just as important ;)]. The second problem is getting Imapd to work and with this POP3. All services are running without error (cyrus with saslauthd, postfix) but I can't access accounts which are setup by web-cyradmin. When I try Imap, my mail client (The Bat) tells me that it's logged on but I can't access the INBOX or create new Imap directories because of a permission denied. When I try Pop3, it tells me Unable to open maildrop. Testing the setup like the HOWTO describes it, isn't working either. I added a cyrus user to sasldb and run cyradm --user cyrus --server localhost --auth plain. It tells me cyradm: cannot authenticate to server with plain as cyrus. So thats where I can't get any further. Anyone can help me? I got the imap.conf, cyrus.conf, main.cf, master.cf and the pam from the HOWTO, so I didn't attach them to this text... Sincerely, Glenn Kusardi
Re: +details delivery
I've already asked for help with the +detail delivery and (thanks a lot, Rob) I got an answer on that: As long as sendmail isn't stripping what is between the + and the @ this should be easy, just give anyone the p right on the folders in question. Then rjs3+foo will file into user.rjs3.foo I tried that and added the p right (lam user.* anyone p) - didn't help. I tried to add/remove the FEATURE(`preserve_local_plus_detail') to my sendmail.mc - does not make any difference. I googled around but did not find anything that would have helped me with that. I assume that my sendmail does not strip off the details from the addresses, because I receive the letters in my INBOX with as 'user+details'. The /var/log/maillog does not show anything suspicious (and logs theuser+details addresses, by the way): Sep 26 15:00:08 station sm-mta[8275]: h8QM07Eb009927:to=[EMAIL PROTECTED], delay=00:00:00, xdelay=00:00:00, mailer=cyrusv2, pri=30713, relay=localhost, dsn=2.0.0, stat=Sent I have nothing special in my sendmail.conf: define(`confLOCAL_MAILER', `cyrusv2')dnl MAILER(local)dnl MAILER(smtp)dnl MAILER(cyrusv2)dnl I am really sorry for disturbing you guys again with the same question, but what elase I should check? Is there something I can read about proper set up of sendmail for detailed delivery? Thanks a lot for your help. -- Best regards, Denis mailto:[EMAIL PROTECTED]
Re: +details delivery
--On Friday, September 26, 2003 15:18:30 -0700 Denis V. Suhanov [EMAIL PROTECTED] wrote: Then rjs3+foo will file into user.rjs3.foo I tried that and added the p right (lam user.* anyone p) Was that a typo? It should have been 'sam', not 'lam' to change the acl. Once you've changed the acl, use lam to show the permissions on user.rjs3.foo to make sure it was actually set. Then try another delivery. There is one other thing that may or may not be an issue. Do you have a sieve script activated for your INBOX ? -Pat
Re[2]: +details delivery
Hello Pat, Friday, September 26, 2003, 4:16:48 PM, you wrote: I tried that and added the p right (lam user.* anyone p) PL Was that a typo? It should have been 'sam', not 'lam' to change Yes, that was a type. Sorry about that. I used (sam user.* anyone p) and I can see that the acls are set for all of the folder (by using lam) PL There is one other thing that may or may not be an issue. Do you have a sieve script activated for your INBOX ? No, I do not have any sieve script activated. timsieved is running on the system though (if it makes any difference Is there anything special I have to add to the sendmail config file? Should I or should I not keep the preserve_local_plus_delivery feature? Is there any way to turn on the local delivery so I know for sure that it does not modify the delivery address or something like that? Thank you very much for the reply though. -- Best regards, Denismailto:[EMAIL PROTECTED]
Re: Re[2]: +details delivery
--On Friday, September 26, 2003 16:26:18 -0700 Denis V. Suhanov
[EMAIL PROTECTED] wrote:
PL There is one other thing that may or may not be an issue. Do you
have a sieve script activated for your INBOX ? No, I do not have any
sieve script activated. timsieved is running on the system though (if it
makes any difference
No, just having timsieved running shouldn't have any effect on this.
Is there anything special I have to add to the sendmail config file?
Haven't a clue. I cheerfully abandoned sendmail in favor Exim years
ago; and have never looked back.
Should I or should I not keep the preserve_local_plus_delivery feature?
Is there any way to turn on the local delivery so I know for sure that it
does not modify the delivery address or something like that?
Try running 'sendmail -bt' - that should put you in address testing
mode where you enter addresses and it shows you the steps used for
parsing. As I said, I haven't done this with Sendmail for quite a
while; so I'm not sure how helpful this will actually be. (With Exim
the output is very clean and to the point.)
If you've read the LMTP RFC, you could try to telnet to the lmtp
port and manually type in the commands to give it a message with
a +detail in the address. That would help identify whether the
problem is on the cyrus side or the sendmail side.
You could also try setting up a sieve script using the subaddress
extension. Something like:
require fileinto ;
require envelope ;
require subaddress ;
if envelope :detail to foo {
fileinto INBOX.foo ;
}
else {
keep ;
}
Even if you don't plan on using sieve; this will provide an indication
of whether the detail part is surviving the sendmail-lmtpd transition.
Once you've got the problem ironed out, you can remove the sieve script
again.
-Pat
Re: Murder question : restarting the mupdate master daemon, mailbox list incoherent on frontend
On Fri, 26 Sep 2003, Etienne Goyer wrote: I was playing around in IMP and deleted a few folders. Then, I tried recreating a folder I just deleted with the same name. It complained that the folder already exist. I check with cyradm on the backend and can see that they are really gone. I then checked on the frontend and, to my surprise, all the folder I thought I had deleted where still shown in cyradm! I restarted cyrus on the frontend, checked again with cyradm and now they are gone. I can then recreate my folder correctly. How long did you wait between restarting all of these services and then performing mailbox operations? If the frontend loses its connection to the mupdate master, it'll be a minute or two before it reattempts the connection. After that, the resynch process takes some time before updates will again be processed. I guess what happened is that the information the frontend held about the mailbox list and their location was stale. I thought that the mupdate master server would push change in folder list back to frontend but apparently, it's the frontend that pull (or at least, initiate the update) that information instead. Is that right ? If yes, does that imply that when cyrus need restarting across a murder, we should do backend first, mupdate master second and frontend last ? Changes are pushed from backend to mupdate master to frontend. The frontend initiates the connection to the mupdate master, but the mupdate master independently pushes the updates down (sort of like the IMAP IDLE extention). Its probably not a terribly good idea to restart a backend if the mupdate master is down, but I don't think that will explicitly hurt anything. They should all be independently restartable. Certainly, when I do upgrades locally, I generally do the mupdate master first, then I restart backends and frontends at the same time. -Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper
