3 messages in net.sourceforge.lists.courier-usersRe: [courier-users] FreeBSD, ipv6, bi...
FromSent OnAttachments
Roberto de IriarteSep 20, 2001 10:20 am 
Roland SchneiderSep 20, 2001 12:10 pm 
Sam VarshavchikSep 20, 2001 2:36 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] FreeBSD, ipv6, bind 9.1.3, and IMAP thoughtsActions...
From:Roland Schneider (rol@serv.ch)
Date:Sep 20, 2001 12:10:54 pm
List:net.sourceforge.lists.courier-users

--Roberto de Iriarte wrote on 20.09.2001 13:31 -0400:

FreeBSD 4.3 Release,i386 , stock kernel Bind 9.1.3 Courier 0.35-1 no ipv6 address.

Courier name resolving does not work unless it's compiled without ipv6 support. I believe the problem to be either the FreeBSD ipv6 Stack being active or (most likely) Bind 9.1.3, or a combination thereof. I expect to do more experiments during the week to try to isolate the problem.

I dont use 'INET6' in the kernel, and after replacing Bind 8.x with dnscache some months ago troubles with the resolver stopped.

Other than that courier works great. (Now learning to configure maildrop filters for authmysql based virtual users, any advise?)

Nothing special, just follow the documentation and the source :) I set HOME=/full/path/into/maildir; MAILDIR=./ and simply drop everything into the same directory for the 'cheap' virtual users with only one catchall-mailbox.

Be careful: cachall-forwarding via SQWebmail/Mailfiter will cause a classical loop if the destination is not valid, just like any other poorly written receipe. This gets worse if the recipient- domain dont exist: a few thousend bounces/sec sent locally from courier-dsn could take the whole server down because there is no built in limitation (except the cpu). This needs some changes in the SQWebmail/Mailfilter-generator.

a) catchall-forwarded mail should keep the original envelope-sender b) mail sent from <> (or anything from courier-dsn) should not be blindly forwarded again into the loop. c) courier-dsn should keep the original headers in the reply just like other automated responders, and also use some delay. d) add selection for 'Catch-All-Forwarding' in the mailfilters-form, the condition (size>0) works but is too difficult for most users.

Also check out the mysql-percenthack from Alessandro Vesely: http://courier.serv.ch/patches/percenthack/percenthack-0.35.1.patch

BTW, while i have problems with most imap server <-> clients, i have not found something speccialy wrong with courier-imap (it even works with old Netscape clients if compiled with --enable-workarounds-for-imap-client-bugs). Is there something i have missed

This is the most basic option for configure, and my other favourite: --disable-root-check

Roland