Ah, thought so. Been trying to learn the new cool ways of doing things in 2.0. Thanks for you help!
On 7/11/10 7:42 PM, Timo Sirainen wrote: > It doesn't work this way with v1.x. > > On 12.7.2010, at 0.40, Steven King wrote: > >> Ah that makes sense. Was this a change for 2.0 or is this recommended >> for 1.x as well? >> >> On 7/11/10 5:39 PM, Timo Sirainen wrote: >>> On 11.7.2010, at 21.53, Steven King wrote: >>> >>>> Ah ok, what is the difference between loading the plugin outside of >>>> protocol sections vs inside them? >>> Inside protocol section it affects only programs using that protocol. You >>> can have: >>> >>> mail_plugins = foo >>> protocol imap { >>> mail_plugins = bar >>> } >>> protocol pop3 { >>> mail_plugins = $mail_plugins bar >>> } >>> >>> Now IMAP uses only "bar" plugin, POP3 uses "foo bar" plugins and everything >>> else uses "foo". A realistic good setup could look like: >>> >>> mail_plugins = quota acl autocreate >>> protocol imap { >>> mail_plugins = $mail_plugins imap_acl imap_quota >>> } >>> >>> Usually you want to enable plugins globally, and IMAP is the special case >>> which has IMAP-specific plugins (well, sieve also for LDA). >> -- >> Steve King >> >> Senior Linux Engineer - Advance Internet, Inc. >> Cisco Certified Network Associate >> CompTIA Linux+ Certified Professional >> CompTIA A+ Certified Professional >> -- Steve King Senior Linux Engineer - Advance Internet, Inc. Cisco Certified Network Associate CompTIA Linux+ Certified Professional CompTIA A+ Certified Professional