Displaying 3 results from an estimated 3 matches for "mailallowincoming".
2019 Sep 03
2
Different passdb backends for different services
...configure a separate passdb backend just for submission.
I habe LDAP attributes that differ sending or receiving permissions. It would be nice, if I had a second passdb backend just for submission, which has a LDAP filter for locking this service.
Example for IMAP, POP3, Sieve:
(&(mail=%s)(mailAllowIncoming=TRUE))
Example for Submission:
(&(mail=%s)(mailAllowOutgoing=TRUE))
Use case is to lock compromised accounts that send spam. An operator can notify the account owner by placing a warning messegae into his/her mailbox.
Is this possible?
Thanks in advance
Christian
2019 Sep 03
0
Different passdb backends for different services
...d just for submission.
>
> I habe LDAP attributes that differ sending or receiving permissions. It would be nice, if I had a second passdb backend just for submission, which has a LDAP filter for locking this service.
>
>
> Example for IMAP, POP3, Sieve:
>
> (&(mail=%s)(mailAllowIncoming=TRUE))
protocol imap {
passdb {
...
}
}
>
>
> Example for Submission:
>
> (&(mail=%s)(mailAllowOutgoing=TRUE))
protocol submission {
passdb {
...
}
}
etc.
Sami
2019 Sep 03
2
Different passdb backends for different services
...gt;
>> I habe LDAP attributes that differ sending or receiving permissions. It would be nice, if I had a second passdb backend just for submission, which has a LDAP filter for locking this service.
>>
>>
>> Example for IMAP, POP3, Sieve:
>>
>> (&(mail=%s)(mailAllowIncoming=TRUE))
>
> protocol imap {
> passdb {
> ...
> }
> }
>
>
>>
>>
>> Example for Submission:
>>
>> (&(mail=%s)(mailAllowOutgoing=TRUE))
>
> protocol submission {
> passdb {
> ...
> }
> }
I tried this, but I ha...