>>>>> On Tue, 20 Nov 2001 18:36:59 +0100, >>>>> Terje Elde <[EMAIL PROTECTED]> (te) writes:
te> With the 1.6 series all I had to do was to call deliver such that it would te> deliver a message to the correct folder. With the 2.x series there are te> advantages to using lmtp for deliveries instead, avoiding the extra fork of te> the deliver process. So I'm wondering if there's any RightWay (tm) way to te> deliver mailing list messages to a shared folder? I don't know if I've ever seen a manifesto as to the RightWay for doing this. This is the current hack we've arranged. Before we switched to the altnamespace we had all our shared folders under a "bb." prefix. Now we've moved all these folders up a level. To send mail to such a folder, just put a "+" before the address. If you don't like that, see the "postuser" setting in imapd.conf. (When we adjusted to the altnamespace I overlooked this "postuser" setting, otherwise we might have used it.) Suppose we created a Listar (or now eCartis) list of mylist. If we created a shared folder for it, it would be "mylist". So the cyradm command would just be: cm mylist shared In this example "shared" might be a partition for this folder. Continuing, allow posting to it: sam mylist anyone p If you're using LMTP-AUTH then you might be able to do something better here, but this opens another can of worms because not all MTA will pass the AUTH from SMTP over to LMTP. Anyway, if you want this folder to get the mail from the list, just add it to the list. Since we use Listar, the users entry might be: +mylist@domain : |PROTECTED|HIDDEN| Some lists we auto-generate on a daily basis so our code skips over entries that are listed as PROTECTED. Actually, some of the features of Listar is part of the reason we chose it as it made it easy to manipulate for out environment. If you want to block direct email to the shared folder and only allow the mail from the list, you might have to do something tricky. When we were using Sendmail a couple of years back this was really problematic because the maps applied to both port 25 mail and local mail. One of the reasons why I liked Postfix is because blocks on port 25 do not necessarily apply to blocks on local "client" mail. Consequently, we can block incoming mail to the address "+mylist@domain" and yet Listar can still direct mail to that address. Well, I said it was a hack, but at least it seems to have worked out fairly well. Now if only we could get Sieve scripts to work on shared folders. :-P (Actually, I wouldn't use Sieve for these folders that mirror a list, but it would still be nice to have. We have plenty of shared folders were this would be really handy.) -- Amos
