RE: Signaled to death by 11
Oliver Pitzeier wrote:
> > Rob Siemborski wrote:
> > > > Copying mails between two imap-servers is normally no
> > > > problem and works with all my servers, except this one...
> > > >
> > > > Any ideas?
> > >
> > > Do you have a protocol trace of what outlook is feeding cyrus?
> > > Alternatively, do you have a backtrace of the core dump?
Here we go:
DONE
001S OK Completed
001Y APPEND "INBOX" (\Seen) "26-Mar-2003 11:12:21 +0100" {8167}
This seems right for me.
Best regards,
Oliver
Configure: BerkeleyDB 4.1 (Re: Signaled to death by 11)
> In <[EMAIL PROTECTED]> > Christian Schulte <[EMAIL PROTECTED]> wrote: > Oliver Pitzeier wrote: [...] > Hhm! No real answers to my questions for now... I now know how to debug > a cyrus installation but I really need to know how to upgrade from db3.2 > to db4.1 ! Do ./configure --help, and read docs, maybe you could found that you want to know. Have a fun. -- Shinichiro HIDA mailto:[EMAIL PROTECTED] GPG fingerprint = 5F2D 1656 FFF6 F691 A51C 5E61 E416 D398 470C 1CE9
Does Cyrus-IMAP support client-defined keyword?
Hello everyone. (B (BI have three questions now. Please teach me the answer. (B(Sory, I try the setup of cyrus-imap. However, I failed.) (B (BQ1. Does Cyrus-IMAP support client-defined keyword? (B (Flags Message Attribute) (BQ2. Does Cyrus-IMAP support MySQL to the authentication? (BQ3. Does Cyrus-IMAP support Maildir? (B (BThank you.
RE: Signaled to death by 11
Oliver Pitzeier wrote:
> Now I'll dig into tmcomp(atmp, btmp) :-)
OK... I solved the problem... It's not OK to do it this way - I know, but it
actually helps for the moment...
--- mkgmtime.c.orig Wed Mar 26 14:03:34 2003
+++ mkgmtime.c Wed Mar 26 14:04:19 2003
@@ -100,6 +100,8 @@
{
register intresult;
+ if(!atmp) return;
+
if ((result = (atmp->tm_year - btmp->tm_year)) == 0 &&
(result = (atmp->tm_mon - btmp->tm_mon)) == 0 &&
(result = (atmp->tm_mday - btmp->tm_mday)) == 0 &&
So, this works, which means, that atmp is not defined at the second run (it
always dies at the second run!) of tmcomp...
Best regards,
Oliver
Re: Signaled to death by 11
On Wednesday 26 March 2003 05:35 am, Oliver Pitzeier wrote:
> Oliver Pitzeier wrote:
> > > Rob Siemborski wrote:
> > > > > Copying mails between two imap-servers is normally no
> > > > > problem and works with all my servers, except this one...
> > > > >
> > > > > Any ideas?
> > > >
> > > > Do you have a protocol trace of what outlook is feeding cyrus?
> > > > Alternatively, do you have a backtrace of the core dump?
>
> Here we go:
>
> DONE
> 001S OK Completed
> 001Y APPEND "INBOX" (\Seen) "26-Mar-2003 11:12:21 +0100" {8167}
>
> This seems right for me.
>
> Best regards,
> Oliver
This has been on this list in the past, this post is on an older release, but
is the problem is the same. The imap server dumps when a message from Outlook
or Outlook Express is copied to it. Machine is an older alpha ev5.6. Here's a
recap:
---
From: Jeremy Rumpf <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Date: 08/19/02 15:05 pm
Recompiled cyrus with debug support, reproduced the segv, loaded the core file
into gdb. Here's the goodies:
Copyright 2001 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "alpha-redhat-linux"...
(gdb) core-file core
Core was generated by `imapd -s'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/lib/libsasl2.so.2...done.
Loaded symbols for /usr/lib/libsasl2.so.2
Reading symbols from /lib/libssl.so.2...done.
Loaded symbols for /lib/libssl.so.2
Reading symbols from /lib/libcrypto.so.2...done.
Loaded symbols for /lib/libcrypto.so.2
Reading symbols from /lib/libdb-3.2.so...done.
Loaded symbols for /lib/libdb-3.2.so
Reading symbols from /lib/libresolv.so.2.1...done.
Loaded symbols for /lib/libresolv.so.2.1
Reading symbols from /lib/libcom_err.so.2...done.
Loaded symbols for /lib/libcom_err.so.2
Reading symbols from /lib/libnsl.so.1.1...done.
Loaded symbols for /lib/libnsl.so.1.1
Reading symbols from /lib/libc.so.6.1...done.
Loaded symbols for /lib/libc.so.6.1
Reading symbols from /lib/libdl.so.2.1...done.
Loaded symbols for /lib/libdl.so.2.1
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /usr/lib/sasl2/libsasldb.so.2...done.
Loaded symbols for /usr/lib/sasl2/libsasldb.so.2
Reading symbols from /usr/lib/sasl2/libcrammd5.so.2...done.
Loaded symbols for /usr/lib/sasl2/libcrammd5.so.2
Reading symbols from /usr/lib/sasl2/libdigestmd5.so.2...done.
Loaded symbols for /usr/lib/sasl2/libdigestmd5.so.2
Reading symbols from /usr/lib/sasl2/libotp.so.2...done.
Loaded symbols for /usr/lib/sasl2/libotp.so.2
Reading symbols from /usr/lib/sasl2/libplain.so.2...done.
Loaded symbols for /usr/lib/sasl2/libplain.so.2
Reading symbols from /lib/libcrypt.so.1.1...done.
Loaded symbols for /lib/libcrypt.so.1.1
Reading symbols from /usr/lib/sasl2/libanonymous.so.2...done.
Loaded symbols for /usr/lib/sasl2/libanonymous.so.2
Reading symbols from /usr/lib/sasl2/liblogin.so.2...done.
Loaded symbols for /usr/lib/sasl2/liblogin.so.2
Reading symbols from /lib/libnss_files.so.2...done.
Loaded symbols for /lib/libnss_files.so.2
Reading symbols from /lib/libnss_ldap.so.2...done.
Loaded symbols for /lib/libnss_ldap.so.2
Reading symbols from /usr/lib/sasl/libanonymous.so...done.
Loaded symbols for /usr/lib/sasl/libanonymous.so
Reading symbols from /usr/lib/sasl/libcrammd5.so...done.
Loaded symbols for /usr/lib/sasl/libcrammd5.so
Reading symbols from /usr/lib/sasl/libdigestmd5.so...done.
Loaded symbols for /usr/lib/sasl/libdigestmd5.so
Reading symbols from /usr/lib/sasl/liblogin.so...done.
Loaded symbols for /usr/lib/sasl/liblogin.so
Reading symbols from /lib/libpam.so.0...done.
Loaded symbols for /lib/libpam.so.0
Reading symbols from /usr/lib/sasl/libplain.so...done.
Loaded symbols for /usr/lib/sasl/libplain.so
#0 0x12006cf0c in tmcomp (atmp=0x0, btmp=0x11fffddd0) at mkgmtime.c:102
102 if ((result = (atmp->tm_year - btmp->tm_year)) == 0 &&
(gdb)
(gdb)
(gdb)
(gdb) bt
#0 0x12006cf0c in tmcomp (atmp=0x0, btmp=0x11fffddd0) at mkgmtime.c:102
#1 0x12006d0e4 in mkgmtime (tmp=0x11fffde60) at mkgmtime.c:138
#2 0x120020c78 in getdatetime (date=0x11fffe0a0) at imapd.c:6870
#3 0x1200104d4 in cmd_append (tag=0x1201a24c0 "000E", name=0x1201a25a0
"INBOX") at imapd.c:2382
#4 0x120009e20 in cmdloop () at imapd.c:876
#5 0x120009158 in service_main (argc=2, argv=0x11908, envp=0x11920)
at imapd.c:665
#6 0x120006a4c in main (argc=2, argv=0x11908, envp=0x11920) at
service.c:464
#7 0x23a70ec in __libc_start_main (main=0x1200060a0 , argc=2,
ubp_av=0x11908, init=0x120005890 <_init>, fini=0x202e788
<_dl_debug_mask>, rtld_fini=0xa9,
stack_end=0x118f0) at ../sysdeps/gener
Cyrus debugging
Hi! The problem I'm currently working on shows me, that there is not a very good error catching in Cyrus IMAP. It also shows me, that there are too few debug possibilities. Look at this: [EMAIL PROTECTED] imap]$ grep -i debug imap* imapd.c:syslog(LOG_DEBUG, "open: user %s opened %s", imapd_userid, name); Only ONE(!) line??? [EMAIL PROTECTED] lib]$ grep -i debug *|wc -l 26 I believe there are too few lines with "syslog(LOG_DEBUG, "bla");" What about a configure-option --extreme-debugging or --devel-debug. Then we/you could add more statements like: #ifdef EXTREME_DEBUG syslog(LOG_DEBUG, "I'm a crazy debug guy. :-)"); #endif Or is there nobody who can do that? Best regards, Oliver
RE: Signaled to death by 11
Jeremy Rumpf wrote: > This has been on this list in the past, this post is on an > older release, but is the problem is the same. The imap server > dumps when a message from Outlook or Outlook Express is copied > to it. Machine is an older alpha ev5.6. Here's a recap: [ ... ] Thanks a lot Jeremy. But nobody had a solution, I'm I correct? Because the problem still exists... I do now have a solution wich is not fine... Maybe one of the cyrus developers helps me to do it better... Best regards, Oliver
Re: Does Cyrus-IMAP support client-defined keyword?
[EMAIL PROTECTED] wrote: > > Hello everyone. > > I have three questions now. Please teach me the answer. > (Sory, I try the setup of cyrus-imap. However, I failed.) > > Q1. Does Cyrus-IMAP support client-defined keyword? >(Flags Message Attribute) Yes. > Q2. Does Cyrus-IMAP support MySQL to the authentication? Yes, if used with with a recent version of SASL. > Q3. Does Cyrus-IMAP support Maildir? Its format is similar to Maildir (each mailbox in its own directory, each message in its own file), but you can't use an existing Maildir spool with Cyrus if that's what you're asking. -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
Re: Cyrus debugging
Oliver Pitzeier wrote: > > Hi! > > The problem I'm currently working on shows me, that there is not a very good > error catching in Cyrus IMAP. There is a big difference between error catching and tracing execution with DEBUG messages. If you're trying to track down a crash, then you should be looking at a core file. > It also shows me, that there are too few debug possibilities. > > Look at this: > [EMAIL PROTECTED] imap]$ grep -i debug imap* > imapd.c:syslog(LOG_DEBUG, "open: user %s opened %s", imapd_userid, name); > > Only ONE(!) line??? The majority of imapd's work is not done in imap* files. There are 80 LOG_DEBUG entries in the imap/ directory, and 141 in 2.1.12. This is in addition to all of the LOG_INFO, LOG_NOTICE, ... -- 990 total!! I personally wouldn't want the performance of Cyrus bogged down trying to report every little detail to log files. -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
Re: ctl_cyrusdb -r performance over NFS
On Wed, 26 Mar 2003, Andrew McNamara wrote: > We've noticed that "ctl_cyrusdb -r" is quite slow when working against an > NFS spool (Netapp) on an otherwise quiesent system. Looking at a gcore, > I see that the slow part is preening the mailboxes (deleting reserved > mailboxes), rather than rolling the checkpoints forward. The process > is looping doing stat(), fstat() and fcntl(F_SETLKW) calls, the last > of which in the case of NFS requires a round-trip to the server, and I > suspect this is where the slowdown comes from. You probably don't want to be running cyrus on an NFS partition. > Running ctl_cyrusdb with -x option results in near-instantaneous startups. > What are mailbox reservations used for, and what side-effects will we see > running with -x? > > The only other answer I see is to modify ctl_cyrusdb so that it avoids > locking the mailboxes.db for each row, but rather aquires a "table lock". > This may require an intrusive modification to the db api. Reserved mailboxes will pop up after a crash halfway through a create, you then won't be able to access that mailbox name until the reservation is cleared. -Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper
Re: sendmail 8.12.8 + procmail 3.22 + cyrus 2.1.12
On Thu, Mar 20, 2003 at 06:48:27PM -0600, Scott McDaniel wrote:
> I am in the process of replacing a solaris 6 imap server to solaris 8.
> I am trying to use the following software; however, I am still unable to
> get incoming messages into the users' inbox. Any assistance you can
> provide in helping me configure sendmail to send messages to procmail
> and then get procmail to "deliver" to the cyrus box would be greatly
> appreciated.
[...]
> What I think I ultimately want to do is remove all the cyrus references
> in my sendmail.mc file and use procmail as the local delivery agent.
> Unfortunately, I've been unable to come up with the magical sendmail.mc
> file to make this work.
>
> If you could provide me examples of sendmail.mc files and/or
> /etc/procmailrc recipes, that would be best.
Try this in the sendmail.mc:
define(`confLOCAL_MAILER',`cyrus')dnl
define(`CYRUS_MAILER_PATH',`/path/to/bin/procmail')
define(`CYRUS_MAILER_FLAGS', `A5@')dnl
define(`CYRUS_MAILER_ARGS', `procmail -p /path/to/etc/cyrus/procmail.global
CYRUSUSER=$u')
MAILER(smtp)
MAILER(cyrus)
#!EOF
And maybe this in the procmail.global:
##
## GLOBAL procmail recipes
VERBOSE=on
LOGFILE=/var/tmp/procmail.global.log
###
## Which rc files should we include
#INCLUDERC="/path/to/etc/rc/$CYRUSUSER-lists.rc"
#INCLUDERC="/path/to/etc/rc/$CYRUSUSER.rc"
#INCLUDERC="/path/to/etc/rc/$CYRUSUSER-default.rc"
###
## Set Cyrus IMAP Variables
DELIVER=/path/to/cyrus/bin/deliver
SPAMASS=/path/to/spamassassin/bin/spamc
:0fw
|${SPAMASS} -u cyrus
:0
|${DELIVER} -e -a $CYRUSUSER -m user.$CYRUSUSER
#!EOF
But, I would suggest kicking both procmail and deliver out and start
thinking about delivering via LMTP, use sendmail with the milter API
for spamtagging (which you didn't mention - I know - but couldn't resist ;)
Delivery with LMTP would look like this in the sendmail.mc:
define(`CYRUS_MAILER_PATH',`[IPC]')
define(`CYRUS_MAILER_FLAGS', `A5@/:|SmXz')dnl
define(`CYRUS_MAILER_ARGS', `FILE /var/run/lmtp')
Done to a unix socket (lmtpunix cmd="lmtpd" listen="/var/run/lmtp" prefork=1)
in the SERVICES part in your cyrus.conf.
HTHHAND
--
Henk Roose [EMAIL PROTECTED]
Centre for Mathematics and Computer Science
Kruislaan 413, 1098 SJ Amsterdam, The Netherlands
Phone: +31 20 5929333 Fax: +31 20 5924199
RE: Cyrus debugging
Ken Murchison wrote: > The majority of imapd's work is not done in imap* files. > There are 80 LOG_DEBUG entries in the imap/ directory, and > 141 in 2.1.12. Sorry, but I believe there are enough interessting parts in imapd and also in some lib/* file that could be logged for debugging reasons... [ ... ] > I personally wouldn't want the performance of Cyrus bogged > down trying to report every little detail to log files. Only for development and _real_ debug reasons... That's why I said that there must be a configure option which must be enabled and is disabled by default of course. -Oliver
Re: Signaled to death by 11
On Wednesday 26 March 2003 08:57 am, Oliver Pitzeier wrote:
> Jeremy Rumpf wrote:
> > This has been on this list in the past, this post is on an
> > older release, but is the problem is the same. The imap server
> > dumps when a message from Outlook or Outlook Express is copied
> > to it. Machine is an older alpha ev5.6. Here's a recap:
>
> [ ... ]
>
> Thanks a lot Jeremy. But nobody had a solution, I'm I correct? Because the
> problem still exists... I do now have a solution wich is not fine... Maybe
> one of the cyrus developers helps me to do it better...
>
> Best regards,
> Oliver
Actually, I think someone a while ago had come up with a solution. I'm not
sure how proper it is, you can decide. Here's a copy of the post from Fritz
Test <[EMAIL PROTECTED]> :
Recently I ran into the same trouble (signalled to death by 11) with
Outlook Clients moving mails to a Cyrus folder as Jeremy described in
his mail on the info-cyrus list in August last year (see URL above).
I'm using Simon Matter's last SRPM Packages on COMPAQ DS20, RedHat Linux
7.2/Alpha.
With help of the analysis of Jeremy (Thanks) I patched the function
mkgmtime, such that it works for me now. The problem is, that gmtime(&t)
returns a null pointer for my 64-bit system if t is out of some range. I
don't know exactly what range, but I assume that the generated value for
the year must fit in 32 bits?.
Here's a snipped of my code in mkgmtime.c
---
/*
** If time_t is signed, then 0 is the median value,
** if time_t is unsigned, then 1 << bits is median.
*/
t = (t < 0) ? 0 : ((time_t) 1 << bits)
;
/* Patch begin */
/*
** On my 32-bit Debian GNU/Linux 3.0 AMD K6 PC, the algorithm
** converges in a range
** from
** 1901-12-13 20:46:00 GMT -> -2147483640
** to
** 2038-01-19 03:14:07 GMT -> 2147483647
*/
/*
** It segfaults on RedHat 7.2/Alpha if bits > 56, since gmtime (&t)
** returns null pointer.
** Hence, set bits to a resonable value <= 56.
**
** Setting, e.g. bits=40, the algorithm converges in a range
** from
**-32873-11-12 23:24:00 GMT -> -1099511627760
** to
** 36812-02-20 00:36:59 GMT -> 1099511627819
*/
if (bits > 40) {
bits = 40;
}
/* patch end */
for ( ; ; ) {
prt (t);
fprintf (stderr, " ");
--
Hope this helps
Tom
Re: delivering to bb folders
Lawrence Greenfield wrote: I know it's vaguely off topic, but it's certainly related to cyrus-imap; can anyone point to some sendmail config tips that make it pass this info to LMTP? Is this passing of "authid" supposed to happen by default with SMTP auth enabled? You might have to add -D_FFR_AUTH_PASSING=1 to your site.config.m4, Just one comment. You realise that this feature of sendmail (was already available in early releases of 8.12) combined with an MSA server and cyrus ACLs can really boost cyrus functionality. (The "anyone p", mentioned in cyrus documentation, has been always inaccurate, underestimating cyrus capabilities). PS: No need to argue why cyrus is the only opensource imap server (the argue refers to "imap server"). PS: No need to argue, again :), for a proper groupmembership backend.
Re: Cyrus debugging
Oliver Pitzeier wrote: Sorry, but I believe there are enough interessting parts in imapd and also in some lib/* file that could be logged for debugging reasons... Complaints about the code quality of Cyrus coming from someone who tries to pass an int where a char* is expected, whose patch results in returning random garbage from the comparison function, and who can't produce a stack backtrace from the problem seems a bit out of place. The purpose of the syslog logging is not to output every possible thing you might want to look at while debugging a code problem, but rather to output helpful information at various levels on a running production system to report that there is a problem or to trace how something is being handled (at the debug levels). When I want to debug an actual problem such as the core dump you refer to, I run the program under a debugger or at least investigate the core dump with a debugger. -- John A. Tamplin Unix System Administrator Emory University, School of Public Health +1 404/727-9931
Re: Cyrus debugging
John Alton Tamplin wrote: > > Oliver Pitzeier wrote: > > >Sorry, but I believe there are enough interessting parts in imapd and also in > >some lib/* file that could be logged for debugging reasons... > > > > > Complaints about the code quality of Cyrus coming from someone who tries > to pass an int where a char* is expected, whose patch results in > returning random garbage from the comparison function, and who can't > produce a stack backtrace from the problem seems a bit out of place. > > The purpose of the syslog logging is not to output every possible thing > you might want to look at while debugging a code problem, but rather to > output helpful information at various levels on a running production > system to report that there is a problem or to trace how something is > being handled (at the debug levels). When I want to debug an actual > problem such as the core dump you refer to, I run the program under a > debugger or at least investigate the core dump with a debugger. Nicely phrased. Thank you. -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
RE: Cyrus debugging
John Alton Tamplin wrote: > Oliver Pitzeier wrote: > > Sorry, but I believe there are enough interessting parts in > > imapd and > > also in some lib/* file that could be logged for debugging reasons... > > Complaints about the code quality of Cyrus coming from > someone who tries to pass an int where a char* is expected, whose > patch results in returning random garbage from the comparison function, > and who can't produce a stack backtrace from the problem seems a > bit out of place. I'm sorry, I didn't want to _complain_. I just wanted to give feedback! And that I passed an int to syslog was really a mistake, but comes from programming too much Perl, where I normally do not need to think about types... I had an idea, you don't like it. That's OK. :-) Best regards, Oliver
Re: Cyrus debugging
John Alton Tamplin wrote: When I want to debug an actual problem such as the core dump you refer to, I run the program under a debugger or at least investigate the core dump with a debugger. How does one run PHP code under a debugger? And how does one investigate a core dump with a debuger? Thanks, Wayne
Re: Signaled to death by 11
On Wed, 26 Mar 2003, Jeremy Rumpf wrote:
> Actually, I think someone a while ago had come up with a solution. I'm not
> sure how proper it is, you can decide. Here's a copy of the post from Fritz
> Test <[EMAIL PROTECTED]> :
[snip]
Hmmm, I probably should have looked at it then... but I don't think this
is as correct as just checking the result of gmtime() directly for if it
is NULL or not (and then testing the result of mkgmtime, of course).
What are opinions on this patch?
Note that I suspect this will only stop cyrus from crashing, I don't think
this will actually result in "correct" behavior, since it seems that the
gmtime() implementation on systems with a 64 bit time_t is broken. (I'm
not comfortable with an arbitrary limit on the size of a time_t just to
get around this, though).
Index: imap/imapd.c
===
RCS file: /afs/andrew.cmu.edu/system/cvs/src/cyrus/imap/imapd.c,v
retrieving revision 1.425
diff -u -r1.425 imapd.c
--- imap/imapd.c13 Feb 2003 20:15:24 - 1.425
+++ imap/imapd.c26 Mar 2003 15:48:14 -
@@ -6755,6 +6755,7 @@
struct tm tm;
int old_format = 0;
char month[4], zone[4], *p;
+time_t tmp_gmtime;
int zone_off;
memset(&tm, 0, sizeof tm);
@@ -6924,7 +6925,11 @@
c = prot_getc(imapd_in);
tm.tm_isdst = -1;
-*date = mkgmtime(&tm) - zone_off*60;
+
+tmp_gmtime = mkgmtime(&tm);
+if(tmp_gmtime == -1) goto baddate;
+
+*date = tmp_gmtime - zone_off*60;
return c;
Index: lib/mkgmtime.c
===
RCS file: /afs/andrew.cmu.edu/system/cvs/src/cyrus/lib/mkgmtime.c,v
retrieving revision 1.6
diff -u -r1.6 mkgmtime.c
--- lib/mkgmtime.c 13 Feb 2003 20:15:41 - 1.6
+++ lib/mkgmtime.c 26 Mar 2003 15:52:20 -
@@ -135,6 +135,9 @@
t = (t < 0) ? 0 : ((time_t) 1 << bits);
for ( ; ; ) {
mytm = gmtime(&t);
+
+ if(!mytm) return WRONG;
+
dir = tmcomp(mytm, &yourtm);
if (dir != 0) {
if (bits-- < 0)
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456
Research Systems Programmer * /usr/contributed Gatekeeper
Re: Cyrus debugging
Date: Wed, 26 Mar 2003 09:17:02 -0500 From: Ken Murchison <[EMAIL PROTECTED]> [...] The majority of imapd's work is not done in imap* files. There are 80 LOG_DEBUG entries in the imap/ directory, and 141 in 2.1.12. This is in addition to all of the LOG_INFO, LOG_NOTICE, ... -- 990 total!! I personally wouldn't want the performance of Cyrus bogged down trying to report every little detail to log files. Indeed. Every syslog call does IPC which actually can be a significant performance problem for some systems. Additional and better logging capabilities are bug #115. Larry
Re: delivering to bb folders
Nikos, Sorry, I don't understand your post. Was it a request for some change? Additional documentation? confused, Larry
Re: lmtp read error
You are correct about the MX records, though mail addressed directly to the machine gets delivered correctly. As far as I have read, LMTP does not require or use MX records. The socket method gives me a "connection refused" error. lmtpd is running. Here is the appropriate sections of my cyrus.conf file: # at least one LMTP is required for delivery lmtpunix cmd="lmtpd" listen="/var/imap/socket/lmtp" prefork=1 # lmtp cmd="lmtpd" listen="/var/imap/socket/lmtp" prefork=0 lmtp cmd="lmtpd" listen="63.105.30.19:lmtp" prefork=1 Sebastian Konstanty Zdrojewski wrote: The relay none message seems to indicate the MX record for the recipient domain is not properly configured... I am using a similar configuration, but using socket lmtp connection. Do you have lmtpd daemon running? Morgan Sackett wrote: I have a freshly configured Cyrus IMAP system set up. I am using Postfix to deliver mail to the system, and I currently have it set up to deliver via lmtp over tcp. Whenever postfix tries to deliver a message, I get an error. Here is an example Mar 25 14:42:06 kang postfix/lmtp[10398]: 537991FCA07: to=<[EMAIL PROTECTED]>, relay=none, delay=10231, status=deferred (connect to 127.0.0.1[127.0.0.1]: read timeout) I get the same error when I use a local socket. When I try to telnet to the lmtp port this is what I get: kang# telnet localhost lmtp Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Then it just hangs. What is going on? -- Sebastian Konstanty Zdrojewski IT Analyst Neticon S.r.l. via Valtellina, 16 - 20159 Milano Tel. +39 02 68.80.731 FAX +39 02.60.85.70.41 Cell. +39 349.33.04.311 ICQ # 97334916 -- Web: http://www.neticon.it/ E-mail: [EMAIL PROTECTED]
Problem with cyradm and krb5 */admin principals
We make use of SASL/GSSAPI authentication with our cyrus installation. The man page for imapd.conf says that the "admins:" field may contain a kerberos admin principal, enabling that admin principal to, well administer the cyrus installation. I can't get that to work with cyradm. I've tried repeatedly over the last two years. If I add "benp/admin" to the "admins:" line in imapd.conf and then try to connect to the imap server (while having a tgt for benp/admin), cyradm fails with this error: cyradm: cannot authenticate to server with as benp And imapd logs this: Mar 26 11:36:02 x imapd[14556]: bad userid authenticated Mar 26 11:36:02 x imapd[14556]: badlogin: x.reed.edu[xxx.xxx.xxx.xxx] GSSAPI [SASL(-13): authentication failure: bad userid authenticated] My lame solution has been to use a dedicated "regular" (no / in the name) principal. But if possible it sure would be great to be able to reuse our */admin principals. I'm currently using cyrus-imapd-2.1.12. I've wondered if this is a problem with / characters and have tried a lot of \ escaping and single tick quoting, to no avail. What am I missing? Anyone out there using */admin principals with cyradm? Ben -- --- Ben Poliakoff email: <[EMAIL PROTECTED]> Reed College tel: (503)-788-6674 Unix System Administrator PGP key: http://www.reed.edu/~benp/key.html --- 0x6AF52019 fingerprint = A131 F813 7A0F C5B7 E74D C972 9118 A94D 6AF5 2019
Bayesspam Filter
I have been trying to get the BayesSpam filter to work under Squirrelmail and Cyrus. The filter recognizes spam for what it is, but doesn't send it to the proper mailbox. I have been emailing the author and he has been helpful, but he believes the solution is with Cyrus. Below are two excerpts from one of his responses: ---8<--8<-- The only common factor I can find with people that have the problem is that none of them (that I know of) are using Courier IMAP, so the problem could be related to that somehow. ---8<--8<-- Other than that, if you happen to know of a document somewhere that outlines exactly how your IMAP server impliments the RFCs, I could use that to possibly figure out where the problem is. ---8<--8<-- I did find http://asg.web.cmu.edu/cyrus/1994-techoverview.html, but it seemed to be too brief since he said "exactly how your IMAP server impliments the RFCs". Is/Are there any other document(s) out there? TIA, Jon -- Trooper Jon S. Nelson, Linux Certified Admin. Pa. State Police, Bureau of Criminal Investigation Computer Crimes Unit Work: 610.344.4471 Page: 866.284.1603 [EMAIL PROTECTED]
Re: Problem with cyradm and krb5 */admin principals
--On Wednesday, March 26, 2003 11:47:34 -0800 Ben Poliakoff <[EMAIL PROTECTED]> wrote: Anyone out there using */admin principals with cyradm? I tried and gave up, so I'd like to discover the way to do this too... It worked under 2.0.x releases of Cyrus IMAPd. Rudy
Re: lmtp read error
* Morgan Sackett <[EMAIL PROTECTED]> [26-03-03 16:37]: > You are correct about the MX records, though mail addressed directly to > the machine gets delivered correctly. As far as I have read, LMTP does > not require or use MX records. The socket method gives me a "connection > refused" error. > > lmtpd is running. Here is the appropriate sections of my cyrus.conf file: > > # at least one LMTP is required for delivery > lmtpunix cmd="lmtpd" listen="/var/imap/socket/lmtp" prefork=1 > # lmtp cmd="lmtpd" listen="/var/imap/socket/lmtp" prefork=0 > lmtp cmd="lmtpd" listen="63.105.30.19:lmtp" prefork=1 > Unless localhost=63.105.30.19 then your lmtpd server is not listening to localhost network address. So obviossly postfix won't deliver the messages, nor telnet will connect to localhost:lmtp. mitu
Re: Problem with cyradm and krb5 */admin principals
The / is considered an illegal character under auth_unix. I wrote a regular expression based auth module which will work with Kerb V. That is how we solved the problem.. Rudolph T Maceyko wrote: --On Wednesday, March 26, 2003 11:47:34 -0800 Ben Poliakoff <[EMAIL PROTECTED]> wrote: Anyone out there using */admin principals with cyradm? I tried and gave up, so I'd like to discover the way to do this too... It worked under 2.0.x releases of Cyrus IMAPd. Rudy
Re: Problem with cyradm and krb5 */admin principals
That certainly would explain this behavior. How involved is your regex auth module? And would you feel comfortable sharing it? Ben * Paul M Fleming <[EMAIL PROTECTED]> [030326 13:10]: > The / is considered an illegal character under auth_unix. I wrote a > regular expression based auth module which will work with Kerb V. That > is how we solved the problem.. > > > > Rudolph T Maceyko wrote: > >--On Wednesday, March 26, 2003 11:47:34 -0800 Ben Poliakoff > ><[EMAIL PROTECTED]> wrote: > > > >>Anyone out there using */admin principals with cyradm? > > > > > >I tried and gave up, so I'd like to discover the way to do this too... > >It worked under 2.0.x releases of Cyrus IMAPd. > > > >Rudy > > > > -- --- Ben Poliakoff email: <[EMAIL PROTECTED]> Reed College tel: (503)-788-6674 Unix System Administrator PGP key: http://www.reed.edu/~benp/key.html --- 0x6AF52019 fingerprint = A131 F813 7A0F C5B7 E74D C972 9118 A94D 6AF5 2019
Re: delivering to bb folders
> On Wed, 26 Mar 2003 17:05:22 +0200, > Nikos Voutsinas <[EMAIL PROTECTED]> (nv) writes: nv> Lawrence Greenfield wrote: >> You might have to add -D_FFR_AUTH_PASSING=1 to your site.config.m4, nv> You realise that this feature of sendmail (was already available in nv> early releases of 8.12) combined with an MSA server and cyrus ACLs nv> can really boost cyrus functionality. (The "anyone p", mentioned in nv> cyrus documentation, has been always inaccurate, underestimating nv> cyrus capabilities). Alas, not all MTAs are capable of passing SMTP-AUTH onto the LMTP session, Postfix being at least one that I know of. In fact, I am skeptical that this -AUTH communication will ever be incorporated into Postfix without some sort of RFC to back it up. (Unless I'm mistaken, this continuity of -AUTH credentials isn't covered too well, but please correct me if I'm wrong.) -- Amos
Re: ctl_cyrusdb -r performance over NFS
>> We've noticed that "ctl_cyrusdb -r" is quite slow when working against an >> NFS spool (Netapp) on an otherwise quiesent system. Looking at a gcore, >> I see that the slow part is preening the mailboxes (deleting reserved >> mailboxes), rather than rolling the checkpoints forward. The process >> is looping doing stat(), fstat() and fcntl(F_SETLKW) calls, the last >> of which in the case of NFS requires a round-trip to the server, and I >> suspect this is where the slowdown comes from. > >You probably don't want to be running cyrus on an NFS partition. The only other option would be a SAN, and people here trust them even less. BTW, they've successfully been running a large, heavily used, Oracle instance for several years now over NFS to a Netapp with several terabytes of storage, which surprised me. We're in the process of doing some agressive testing on the resulting mail system to find out if it corrupts messages under load, etc. >> Running ctl_cyrusdb with -x option results in near-instantaneous startups. >> What are mailbox reservations used for, and what side-effects will we see >> running with -x? >> >> The only other answer I see is to modify ctl_cyrusdb so that it avoids >> locking the mailboxes.db for each row, but rather aquires a "table lock". >> This may require an intrusive modification to the db api. > >Reserved mailboxes will pop up after a crash halfway through a create, you >then won't be able to access that mailbox name until the reservation is >cleared. Okay - that's what I wanted to know. Can a mailbox be "unreservered" via an admin login - could I get the user creation script to detect a stale reservation and try again? -- Andrew McNamara, Senior Developer, Object Craft http://www.object-craft.com.au/
Re: ctl_cyrusdb -r performance over NFS
Andrew McNamara wrote: You probably don't want to be running cyrus on an NFS partition. The only other option would be a SAN, and people here trust them even less. BTW, they've successfully been running a large, heavily used, Oracle instance for several years now over NFS to a Netapp with several terabytes of storage, which surprised me. We're in the process of doing some agressive testing on the resulting mail system to find out if it corrupts messages under load, etc. A SAN is just a different transport mechanism between the host and the drives -- the protocol is the same old SCSI that has been around for years. That said, there is less interoperability than one would like at this point. The basic problem with NFS is that either you violate standard Unix filesystem semantics or you have pitiful performance (by disabling client-side caching). Add to that the idea that locking was an after-thought (the design goal of a stateless filesystem doesn't exactly fit with maintaining locks) and it is really a mess. As long as you only have one machine writing to the data, you don't have to worry so much about broken filesystem semantics (which is why your Oracle instance works), but you still have lousy performance. Locking in particular is hundreds of times more painful on an NFS filesystem than a local one because it requires a network round-trip, XDR, etc. Theoretically, if you only have one writer you could keep the locks in the client and avoid this performance penalty, but I am not aware of any such implementation. Presumably you could hack the code to maintain its own locks in a shared memory segment, but it would be a lot of work and only useful for your particular situation. -- John A. Tamplin Unix System Administrator Emory University, School of Public Health +1 404/727-9931
Re: lmtp read error
Mitrana Cristian wrote: * Morgan Sackett <[EMAIL PROTECTED]> [26-03-03 16:37]: You are correct about the MX records, though mail addressed directly to the machine gets delivered correctly. As far as I have read, LMTP does not require or use MX records. The socket method gives me a "connection refused" error. lmtpd is running. Here is the appropriate sections of my cyrus.conf file: # at least one LMTP is required for delivery lmtpunix cmd="lmtpd" listen="/var/imap/socket/lmtp" prefork=1 # lmtp cmd="lmtpd" listen="/var/imap/socket/lmtp" prefork=0 lmtp cmd="lmtpd" listen="63.105.30.19:lmtp" prefork=1 Unless localhost=63.105.30.19 then your lmtpd server is not listening to localhost network address. So obviossly postfix won't deliver the messages, nor telnet will connect to localhost:lmtp. mitu I changed it between posts to see if it would make a diference. I also modified my postfix delivery address to point to the corresponding IP address. It didn't seem to matter. Morgan
Re: ctl_cyrusdb -r performance over NFS
>A SAN is just a different transport mechanism between the host and the >drives -- the protocol is the same old SCSI that has been around for >years. That said, there is less interoperability than one would like at >this point. > >The basic problem with NFS is that either you violate standard Unix >filesystem semantics or you have pitiful performance (by disabling >client-side caching). Add to that the idea that locking was an >after-thought (the design goal of a stateless filesystem doesn't exactly >fit with maintaining locks) and it is really a mess. > >As long as you only have one machine writing to the data, you don't have >to worry so much about broken filesystem semantics (which is why your >Oracle instance works), but you still have lousy performance. You assume I don't already know this... 8-) BTW, I don't think it's "violate unix semantics OR pitiful perfomance" - the protocol is flawed in ways that make that "violate unix semantics AND pitiful perfomance". In particular, lost, out of order or replayed requests are not fully addressed by the stateless design. For what it's worth, we go to extraordinary lengths to ensure only one host hits a given NFS volume at a time, we spend silly amounts of money to keep the latency down and the bandwidth up, and we use the best quality NFS implementations we can. I'm not convined that SAN (where "storage" is a euphemism for "disk") is really the answer to anything. Network attached storage (where "storage" is a euphemism for "file server") is a far more convenient model. We just need a better protocol. If only Plan9 had gained a critical mass... 8-) -- Andrew McNamara, Senior Developer, Object Craft http://www.object-craft.com.au/
RE: lmtp read error
Why aren't you using unix:/var/spool/imap/lmtp There is absolutely no reason to use TCP LMTP unless you have to. In this case since it's obvious you are not using Cyrus Murder and don't need the proxy's to pass the messages back to the backend servers. Save us all some patience. Put that in the method to deliver, and be done with it. Thanks, goodbye... good riddance. --- The word bipartisan usually means some larger-than-usual deception is being carried out. - George Carlin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mitrana Cristian Sent: Wednesday, March 26, 2003 5:46 PM To: [EMAIL PROTECTED] * Morgan Sackett <[EMAIL PROTECTED]> [26-03-03 16:37]: > You are correct about the MX records, though mail addressed directly to > the machine gets delivered correctly. As far as I have read, LMTP does > not require or use MX records. The socket method gives me a "connection > refused" error. > > lmtpd is running. Here is the appropriate sections of my cyrus.conf file: > > # at least one LMTP is required for delivery > lmtpunix cmd="lmtpd" listen="/var/imap/socket/lmtp" prefork=1 > # lmtp cmd="lmtpd" listen="/var/imap/socket/lmtp" prefork=0 > lmtp cmd="lmtpd" listen="63.105.30.19:lmtp" prefork=1 > Unless localhost=63.105.30.19 then your lmtpd server is not listening to localhost network address. So obviossly postfix won't deliver the messages, nor telnet will connect to localhost:lmtp. mitu
RE: lmtp read error
On Wed, 26 Mar 2003, Scott M. Likens wrote: > There is absolutely no reason to use TCP LMTP unless you have to. In this > case since it's obvious you are not using Cyrus Murder and don't need the > proxy's to pass the messages back to the backend servers. Not that Cyrus Murder is the only reason the use TCP LMTP. Its entirely reasonable to have your MTA on a separate machine and have delivery to cyrus happen via TCP LMTP over the network. Though, if your MTA is sharing a machine with cyrus, its generally to your advantage to use the unix socket. -Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper
Re: lmtp read error
On Wed, 26 Mar 2003, Rob Siemborski wrote: > Not that Cyrus Murder is the only reason the use TCP LMTP. Its entirely > reasonable to have your MTA on a separate machine and have delivery to > cyrus happen via TCP LMTP over the network. Indeed. That's my setup exactly. However, I just run lmtpd -a, bound to a private network where only the LMTP servers and the SMTP servers are connected to. Thus, no authorization worries, and no SASL overhead. > Though, if your MTA is sharing a machine with cyrus, its generally to > your advantage to use the unix socket. It is MUCH faster to use Unix sockets in most OSes, for one thing... -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
Re: lmtp read error
Scott M. Likens wrote: Why aren't you using unix:/var/spool/imap/lmtp If you had taken the time to read through the previous message, I had stated that I recieve a "connection refused" error using the socket method. There is absolutely no reason to use TCP LMTP unless you have to. In this case since it's obvious you are not using Cyrus Murder and don't need the proxy's to pass the messages back to the backend servers. I might need to deliver from a remote machine to this one near in the future, but I am trying to get anything working at this point. Murder might be an option down the road. Save us all some patience. Put that in the method to deliver, and be done with it. I'm not using deliver. I have also tried that, but with the same results as deliver just talks to lmtpd. Since postfix does this directly I decided to lose some overhead. Thanks, goodbye... good riddance. I thank everyone that has been helpfull and polite. You message almost qualifie
Re: lmtp read error
Rob Siemborski wrote: Not that Cyrus Murder is the only reason the use TCP LMTP. Its entirely reasonable to have your MTA on a separate machine and have delivery to cyrus happen via TCP LMTP over the network. This is my planned usage. I am migrating mail services from one machine to another on a different network, and would like to just move delivery of messages to the new machine while DNS info updates.However, I am having troubles getting lmtpd to listen to anything. Though, if your MTA is sharing a machine with cyrus, its generally to your advantage to use the unix socket. This is my prefered method once all mail is accepted by the local MTA. However, sockets don't seem to be working either. I have tried configuring lmtp via tcp listening on both localhost(127.0.0.1) and the public interface. I would prefer not to use the public interface for long as it poses some security risks. Both configurations result in a "read error" message from the MTA. I have also tried using sockets, but get a "connection refused error". What could possible causes be? As far as system setup goes, I am running FreeBSD 4.7-RELEASE, and have built both postfix and all Cyrus software from the ports collection. Is there an incompatiblity with any of this? It would be great if all I needed was to rev a version. Is there a configuration option I should check? Any help would be greatly appreciated. If anyone has Cyrus + Postfix running on a FreeBSD 4.7 box, I'd like to hear how you have it configured. Morgan
Re: lmtp read error
Henrique de Moraes Holschuh wrote > Indeed. That's my setup exactly. However, I just run lmtpd -a, bound to a > private network where only the LMTP servers and the SMTP servers are > connected to. Thus, no authorization worries, and no SASL overhead. Here is the error that I get using sockets: Mar 26 18:21:08 kang postfix/lmtp[12575]: 26CD51FE9DE: to=<[EMAIL PROTECTED]>, r elay=none, delay=141474, status=deferred (connect to /var/imap/socket/lmtp[/var/ imap/socket/lmtp]: Connection refused) I'll give the -a switch a try.
Re: delivering to bb folders
Amos Gouaux wrote: > > > On Wed, 26 Mar 2003 17:05:22 +0200, > > Nikos Voutsinas <[EMAIL PROTECTED]> (nv) writes: > > nv> Lawrence Greenfield wrote: > >> You might have to add -D_FFR_AUTH_PASSING=1 to your site.config.m4, > > nv> You realise that this feature of sendmail (was already available in > nv> early releases of 8.12) combined with an MSA server and cyrus ACLs > nv> can really boost cyrus functionality. (The "anyone p", mentioned in > nv> cyrus documentation, has been always inaccurate, underestimating > nv> cyrus capabilities). > > Alas, not all MTAs are capable of passing SMTP-AUTH onto the LMTP > session, Postfix being at least one that I know of. In fact, I am > skeptical that this -AUTH communication will ever be incorporated > into Postfix without some sort of RFC to back it up. (Unless I'm > mistaken, this continuity of -AUTH credentials isn't covered too > well, but please correct me if I'm wrong.) I think section 5 of RFC 2554 covers it fairly well. -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
RE: lmtp read error
If you are getting connection refused trying to connect to the socket, then you have the line commented out in the configuration file for the binding of the lmtp socket. I've used lmtp over socket for quite some time and found it to be the best method to date. --- The word bipartisan usually means some larger-than-usual deception is being carried out. - George Carlin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Henrique de Moraes Holschuh Sent: Wednesday, March 26, 2003 6:52 PM To: [EMAIL PROTECTED] On Wed, 26 Mar 2003, Rob Siemborski wrote: > Not that Cyrus Murder is the only reason the use TCP LMTP. Its entirely > reasonable to have your MTA on a separate machine and have delivery to > cyrus happen via TCP LMTP over the network. Indeed. That's my setup exactly. However, I just run lmtpd -a, bound to a private network where only the LMTP servers and the SMTP servers are connected to. Thus, no authorization worries, and no SASL overhead. > Though, if your MTA is sharing a machine with cyrus, its generally to > your advantage to use the unix socket. It is MUCH faster to use Unix sockets in most OSes, for one thing... -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
Re[2]: Does Cyrus-IMAP support client-defined keyword?
Hello. Thank you for the reply.I understood. Thank you. On Wed, 26 Mar 2003 09:10:50 -0500 Ken Murchison <[EMAIL PROTECTED]> wrote: > > > > Q1. Does Cyrus-IMAP support client-defined keyword? > >(Flags Message Attribute) > > Yes. > > > Q2. Does Cyrus-IMAP support MySQL to the authentication? > > Yes, if used with with a recent version of SASL. > > > Q3. Does Cyrus-IMAP support Maildir? > > Its format is similar to Maildir (each mailbox in its own directory, > each message in its own file), but you can't use an existing Maildir > spool with Cyrus if that's what you're asking. >
Re: lmtp read error
Did you compile cyrus with tcp wrapper? -Igor On Wed, 26 Mar 2003, Morgan Sackett wrote: > Rob Siemborski wrote: > > >Not that Cyrus Murder is the only reason the use TCP LMTP. Its entirely > >reasonable to have your MTA on a separate machine and have delivery to > >cyrus happen via TCP LMTP over the network. > > > This is my planned usage. I am migrating mail services from one machine > to another on a different network, and would like to just move delivery > of messages to the new machine while DNS info updates.However, I am > having troubles getting lmtpd to listen to anything. > > >Though, if your MTA is sharing a machine with cyrus, its generally to > >your advantage to use the unix socket. > > > > > > > This is my prefered method once all mail is accepted by the local MTA. > However, sockets don't seem to be working either. > > I have tried configuring lmtp via tcp listening on both > localhost(127.0.0.1) and the public interface. I would prefer not to > use the public interface for long as it poses some security risks. Both > configurations result in a "read error" message from the MTA. > > I have also tried using sockets, but get a "connection refused error". > What could possible causes be? > > As far as system setup goes, I am running FreeBSD 4.7-RELEASE, and have > built both postfix and all Cyrus software from the ports collection. Is > there an incompatiblity with any of this? It would be great if all I > needed was to rev a version. Is there a configuration option I should > check? > > Any help would be greatly appreciated. If anyone has Cyrus + Postfix > running on a FreeBSD 4.7 box, I'd like to hear how you have it configured. > > Morgan > > > -- Igor
Re: lmtp read error
* Morgan Sackett <[EMAIL PROTECTED]> [27-03-03 00:39]: > Henrique de Moraes Holschuh wrote > > > Indeed. That's my setup exactly. However, I just run lmtpd -a, > bound to a > > private network where only the LMTP servers and the SMTP > servers are > > connected to. Thus, no authorization worries, and no SASL > overhead. > > Here is the error that I get using sockets: > > Mar 26 18:21:08 kang postfix/lmtp[12575]: 26CD51FE9DE: > to=<[EMAIL PROTECTED]>, r > elay=none, delay=141474, status=deferred (connect to > /var/imap/socket/lmtp[/var/ > imap/socket/lmtp]: Connection refused) > > I'll give the -a switch a try. > Maybe postfix cannot write to the socket (/var/imap/socket/lmtp), can you make sure the socket is writable by postfix user or the group postfix is running under ? Make sure no firewall rules are in place that can prevent you from connecting telnet-ing to the lmtp port. If you run lmtpd over localhost can you connect to localhost:lmtp ? What's netstat saying about listening ports ? mitu
Thank you all.
(Please reply privately for the sanity of the other lists, if you feel a reply is needed; or at least trim out the lists you're not a member of) I just wanted to drop a line to all the developers of the programs I setup recently for our mailserver, and thank you all. Sometimes the people who work hard to bring the good programs to us don't get the recognition they deserve (especially when reading lists like these where you usually only hear of the problems people have). Everything's working very well, was painless to install, heck even the users here like it. So again, thanks for all your work. It is not unappreciated :> -- Steve Huston - Unix Systems Admin, Dept. of Astrophysical Sciences Princeton University | ICBM Address: 40.346525 -74.651285 126 Peyton Hall |"On my ship, the Rocinante, wheeling through Princeton, NJ 08544 | the galaxies; headed for the heart of Cygnus, (609) 258-7375 | headlong into mystery." -Rush, 'Cygnus X-1'
