Hi.
Am Montag, 15. Oktober 2007 schrieb Bernd Wurst:
> For testing purposes, I have an account "[EMAIL PROTECTED]" and a
> catch-all-account "[EMAIL PROTECTED]". User "vmail" has both, .courier
> and .courier-default in place. .courier-default is needed for the
> catch-all, AFAIK. But the existance of .courier-default also allows
> arbitary expansions to regular accounts ("[EMAIL PROTECTED]").
>
> Does anybody have hint what I can do to keep catch-all working and disable
> expansion-addresses for non-catchall?Okay, composing questions is the best way leading to solution. :) I have done the following now: My database treats catch-all-accounts different from others and reports /home/vmail/catchall as the associated home-directory for them and /home/vmail for regular accounts. Now I have ~vmail/.courier and ~vmail/catchall/.courier-default files around and it seems to do what I want from it. One thing is there that I don't like: In the constellation described above, mail to [EMAIL PROTECTED] gets rejected although a catch-all is defined for this domain (and [EMAIL PROTECTED] is working correctly). I would call this really unexpected behaviour. Is this fixable? cu, Bernd -- Eine Schraube ohne Nagel ist ein Gewinde.
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
