On Wed, Nov 21, 2001 at 12:35:02AM -0600, Amos Gouaux wrote: > 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.)
Doh! *sound of Terje slapping his forehead* Trying to always find the solutions on own my I've gone through the example configs, documentation, mailing list (searching it went surprisingly fast using mutt against the anonymous imap folder) etc. Since I forgot to actually check out imapd.conf, probably as a result of having been used to always finding the answers in the well commented example config, the most important answer just had to be here. /me goes to sit in the corner for a while. > 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. Thankfully I'm using postfix, so I'll be able to block these addresses as needed :) > 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.) This is actually the perfect answer to what I was looking for. Only limitation is that without sieve filtering I'm left without the ability to properly filter mailing lists administered elsewhere which I subcribe to as a regular user to archive for public use at my site. I could always stack a procmail in front of this, but then I'm back to an extra process fork. Chances that someone will abuse this have historically speaking been pretty low, so the option of implementing better access control on a need by need basis is there. Lots of grateful thanks, Terje
