Re: Courier-IMAPD problem with fam(d)
David Kelly wrote:
On Jul 19, 2005, at 6:36 AM, Kövesdán Gábor wrote:
The mail/courier-imap port installs famd as a dependency, but You
have to manually configure and start it. Take a look at /usr/local/
etc/fam.conf.
I don't see anything about starting there or in fam(1M) other than
"if fam is started by inetd".
Honestly speaking I don't know how to start it. Maybe inetd starts it,
maybe courier-imap or You might start it manually?! Unfortunately I dont
have such problems You have without fam. But if You have found out
please let me know, I'm interested. :)
Anyway, this is a deficiency in the new versions of courier-imap.
There isn't some kind of --without-fam configure options, the new
versions require fam.
/usr/ports/mail/courier-imap/Makefile says fam is disabled by default:
OPTIONS=OPENSSL "Build with OpenSSL
support"on \
FAM "Build in fam support for IDLE
command" off \
DRAC"Build in DRAC
support" off \
TRASHQUOTA "Include deleted mails in the
quota"off \
GDBM"Use gdbm db instead of system
bdb" off \
IPV6"Build with IPv6
support" on
If You take a look what the WITH_FAM macro actually does, You'll see it
only adds fam as a dependency and adds some extra cc flags, but leave
the CONFIGURE_ARGS untouched. Afaik fam can't be actually disabled in
courier-imap.
.if defined(WITH_FAM) || exists(${LOCALBASE}/lib/libfam.so)
CONFIGURE_ENV= CPPFLAGS="-I${LOCALBASE}/include" \
LDFLAGS="${LDFLAGS}"
LDFLAGS+= -L${LOCALBASE}/lib
LIB_DEPENDS+= fam.0:${PORTSDIR}/devel/fam
.endif
I suspect but haven't been able to prove fam is somehow running, if
only as a library linked to imapd. When Mail.app has "connection"
problems its instantly disconnected but sometimes a few messages get
thru. Sometimes a simple ssh to the FreeBSD machine, mutt to view the
mailbox, close it with messages now tagged as old, is all it takes
for Mail.app and courier-imap combination to be happy.
Likely there is the libfam.so linked, as You can see above, but that is
only a prerequisite to use famd. Famd must be running as a separate
process and courier-imap connects to famd with the help of libfam.
Cheers,
Gábor Kövesdán
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Courier-IMAPD problem with fam(d)
On Jul 19, 2005, at 6:36 AM, Kövesdán Gábor wrote: The mail/courier-imap port installs famd as a dependency, but You have to manually configure and start it. Take a look at /usr/local/ etc/fam.conf. I don't see anything about starting there or in fam(1M) other than "if fam is started by inetd". Anyway, this is a deficiency in the new versions of courier-imap. There isn't some kind of --without-fam configure options, the new versions require fam. /usr/ports/mail/courier-imap/Makefile says fam is disabled by default: OPTIONS=OPENSSL "Build with OpenSSL support"on \ FAM "Build in fam support for IDLE command" off \ DRAC"Build in DRAC support" off \ TRASHQUOTA "Include deleted mails in the quota"off \ GDBM"Use gdbm db instead of system bdb" off \ IPV6"Build with IPv6 support" on I suspect but haven't been able to prove fam is somehow running, if only as a library linked to imapd. When Mail.app has "connection" problems its instantly disconnected but sometimes a few messages get thru. Sometimes a simple ssh to the FreeBSD machine, mutt to view the mailbox, close it with messages now tagged as old, is all it takes for Mail.app and courier-imap combination to be happy. -- David Kelly N4HHE, [EMAIL PROTECTED] Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Courier-IMAPD problem with fam(d)
David Kelly wrote: /var/log/maillog is spayed full of the following message repeated hundreds or thousands of times. No matter if the courier-imap port is with or with out FAM. Jul 18 19:44:19 Grumpy imapd: Failed to create cache file: maildirwatch (dkelly) Jul 18 19:44:19 Grumpy imapd: Error: Input/output error Jul 18 19:44:19 Grumpy imapd: Check for proper operation and configuration Jul 18 19:44:19 Grumpy imapd: of the File Access Monitor daemon (famd). The only client used is Apple's Mail.app. This has been going on for the past year. Sometimes in spite of the error log messages all seems to be Good Enough. Then other times Mail.app can't hold a connection. Elsewhere found a suggestion that the following in my FreeBSD-hosted Maildir would help, but has not: % cd Maildir % ln -s . .INBOX % ln -s . .INBOX. Just now when I deleted the above symbolic links, my mail downloaded altho there is another of the above imapd error messages in maillog, apparently one for each mailbox message downloaded. When ever Mail.app gets stuck it seems like all is needed is for the mailbox directory to change somehow, or a message or two downloaded, deleted or something, then Mail.app is perfectly happy. Bulk in maillog is nothing but a nuisance. Failed connection is worse. How the heck is fam supposed to be configured? Or how the heck can I get rid of it? The mail/courier-imap port installs famd as a dependency, but You have to manually configure and start it. Take a look at /usr/local/etc/fam.conf. Anyway, this is a deficiency in the new versions of courier-imap. There isn't some kind of --without-fam configure options, the new versions require fam. As for me, I had the same problem with it. My maillog was full of junk, but I didn't notice any kind of error. I could use imap well, but the junk in my log was very annoying, so I applied a little hack. I did "make patch" and found the logging part of the source code and simply deleted those lines. Now, I had a well-working mail system and there isn't such junk in my maillog. Cheers, Gábor Kövesdán ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Courier-IMAPD problem with fam(d)
/var/log/maillog is spayed full of the following message repeated hundreds or thousands of times. No matter if the courier-imap port is with or with out FAM. Jul 18 19:44:19 Grumpy imapd: Failed to create cache file: maildirwatch (dkelly) Jul 18 19:44:19 Grumpy imapd: Error: Input/output error Jul 18 19:44:19 Grumpy imapd: Check for proper operation and configuration Jul 18 19:44:19 Grumpy imapd: of the File Access Monitor daemon (famd). The only client used is Apple's Mail.app. This has been going on for the past year. Sometimes in spite of the error log messages all seems to be Good Enough. Then other times Mail.app can't hold a connection. Elsewhere found a suggestion that the following in my FreeBSD-hosted Maildir would help, but has not: % cd Maildir % ln -s . .INBOX % ln -s . .INBOX. Just now when I deleted the above symbolic links, my mail downloaded altho there is another of the above imapd error messages in maillog, apparently one for each mailbox message downloaded. When ever Mail.app gets stuck it seems like all is needed is for the mailbox directory to change somehow, or a message or two downloaded, deleted or something, then Mail.app is perfectly happy. Bulk in maillog is nothing but a nuisance. Failed connection is worse. How the heck is fam supposed to be configured? Or how the heck can I get rid of it? -- David Kelly N4HHE, [EMAIL PROTECTED] Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: imapd problem.
> Something running under the name of 'inetd' is binding to port 143 on > all inet4 addresses. Either that, or there's a bug in sockstat or the > kernel structures that it manipulates, though I've not seen mention of > that anywhere. Maybe it's an old instance of inetd from a changed > configuration? Perhaps you changed its configuration but forgot to > restart it? Funny. "killall -HUP inetd" helped. I didn't even need to do changes in inetd.conf. I should've just tried to restart it instead of checking config. No idea what I've been doing. Too much vodka perhaps - I'm from Finland you know. ;P Regards, Perttu Laine ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: imapd problem.
On Tue, 2004-10-05 at 17:40 +0300, Perttu Laine wrote: > > 'sockstat -4 | egrep ":143\W"' > > -cut- > root inetd 531 8 tcp4 *:143 *:* > -cut- > > So. it's inetd. Now the question is why 'cause only ssh is not commented > in inetd.conf (or then I should re-check it few times). > And how I can stop that one? Something running under the name of 'inetd' is binding to port 143 on all inet4 addresses. Either that, or there's a bug in sockstat or the kernel structures that it manipulates, though I've not seen mention of that anywhere. Maybe it's an old instance of inetd from a changed configuration? Perhaps you changed its configuration but forgot to restart it? Trust your tools, for you are lost without them. By the way, please remember to CC the list when responding to people. That way, your responses get archived for all to see years from now when they have the same or similar problems. signature.asc Description: This is a digitally signed message part
Re: imapd problem.
Here's my message to the mailing list too. For some reason my mailer replied to the person who replied and not to the mailing list even tho I tried to do that. :) Damn webmails.. > 'sockstat -4 | egrep ":143\W"' -cut- root inetd 531 8 tcp4 *:143 *:* -cut- So. it's inetd. Now the question is why 'cause only ssh is not commented in inetd.conf (or then I should re-check it few times). And how I can stop that one? Regards, Perttu Laine ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: imapd problem.
"Perttu Laine" <[EMAIL PROTECTED]> writes: > Hello! > > I have problem with imapd. I can't start dovecot 'cause it says this: > > -- > koaze# /usr/local/sbin/dovecot > Fatal: listen(143) failed: Address already in use > koaze# > -- > > But I don't know what could be using that address. I had cyrus for a > while, but I removed it and ps aux show nothing that could use imapd port. > Only other email app running is postfix as smtp. > > So. What could be wrong here? *Something* is holding the port. You can find out what with: sockstat | grep 143 -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org:8088/~lowell/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: imapd problem.
On Tue, 2004-10-05 at 08:59 +0300, Perttu Laine wrote: > I have problem with imapd. I can't start dovecot 'cause it says this: > > -- > koaze# /usr/local/sbin/dovecot > Fatal: listen(143) failed: Address already in use > koaze# I appreciate your choice in IMAP servers. :) > But I don't know what could be using that address. I had cyrus for a > while, but I removed it and ps aux show nothing that could use imapd port. > Only other email app running is postfix as smtp. `ps aux' doesn't show which ports are in use. For that, you should use the most wonderful sockstat(1). Running something like this should show you the "Address already in use" culprit: 'sockstat -4 | egrep ":143\W"' > So. What could be wrong here? Exactly what the error message says: the address is already in use. Trust error messages: they're almost never wrong, especially when they're straight from libc. signature.asc Description: This is a digitally signed message part
imapd problem.
Hello! I have problem with imapd. I can't start dovecot 'cause it says this: -- koaze# /usr/local/sbin/dovecot Fatal: listen(143) failed: Address already in use koaze# -- But I don't know what could be using that address. I had cyrus for a while, but I removed it and ps aux show nothing that could use imapd port. Only other email app running is postfix as smtp. So. What could be wrong here? Regards, Perttu Laine ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
