How to use a Dovecot passwd file in place of /etc/passwd?

How does one use a Dovecot passwd file in place of /etc/passwd to validate local recipients? I'm not looking for authentication, just validation. Documentation is good on how to configure Postfix with Dovecot as an LDA except for the part about setting local_recipient_maps =. Avoiding

Re: How to use a Dovecot passwd file in place of /etc/passwd?

Pat wrote: How does one use a Dovecot passwd file in place of /etc/passwd to validate local recipients? I'm not looking for authentication, just validation. Documentation is good on how to configure Postfix with Dovecot as an LDA except for the part about setting local_recipient_maps =.

Re: How to use a Dovecot passwd file in place of /etc/passwd?

How does one use a Dovecot passwd file in place of /etc/passwd to validate local recipients? I'm not looking for authentication, just validation. Any known table lookup type can be used in local_recipient_maps. For a list of known table types on your system, use 'postconf -m'. Alternate

Re: How to use a Dovecot passwd file in place of /etc/passwd?

Pat wrote: How does one use a Dovecot passwd file in place of /etc/passwd to validate local recipients? I'm not looking for authentication, just validation. Any known table lookup type can be used in local_recipient_maps. For a list of known table types on your system, use 'postconf -m'. You

Re: How to use a Dovecot passwd file in place of /etc/passwd?

On Wednesday 19 August 2009 12:20:28 Pat wrote: Alternate passwd files are not a supported map/table type (per postconf -m and other documentation). That's the crux of this Would be a nice feature, IMO. There are workarounds of various ugliness, but the ability to read password(**)-formatted