On 2012-01-11 2:05 PM, huret deffgok wrote:
On Wed, Jan 11, 2012 at 7:04 PM, Charles Marcus wrote:
On 2012-01-11 1:00 PM, huret deffgok wrote:
This post is slightly OT, I hope no one will take offense. I was
following the wiki on using dovecot LDA with postfix and
implemented, for our future ma
On Wed, Jan 11, 2012 at 7:04 PM, Charles Marcus
wrote:
> On 2012-01-11 1:00 PM, huret deffgok wrote:
>
>> Hi list,
>>
>> This post is slightly OT, I hope no one will take offense.
>> I was following the wiki on using dovecot LDA with postfix and
>> implemented,
>> for our future mail server, the
On 2012-01-11 1:00 PM, huret deffgok wrote:
Hi list,
This post is slightly OT, I hope no one will take offense.
I was following the wiki on using dovecot LDA with postfix and implemented,
for our future mail server, the address extensions mechanism: an email sent
to "validuser+foldern...@mydoma
Hi list,
This post is slightly OT, I hope no one will take offense.
I was following the wiki on using dovecot LDA with postfix and implemented,
for our future mail server, the address extensions mechanism: an email sent
to "validuser+foldern...@mydomain.com" will have dovecot-lda automagically
cre
On Wed, 2007-05-23 at 21:25 -0400, Tom Metro wrote:
> Can the "userdb sql" directive be added to the "protocol lda" section?
> Or perhaps instead create a new "auth lda" section, and move the "userdb
> sql" and "socket listen" directives to that section?
In Dovecot v2.0 there might be some bette
I'm converting over a virtual user installation that used Postfix and
maildrop with a MySQL back-end for mailbox lookups to use Dovecot LDA.
The maildrop setup used a database table like:
+-++-++
| address | owner
