* Timo Sirainen :
> >> In v2.0 you can do:
> >>
> >> disable_plaintext_auth = yes
> >> local 10.0.0.0/24 {
> >> disable_plaintext_auth = no
> >> }
> >
> > Can I also specify more than one subnet there?
>
> You can add multiple local {} blocks. Uh. Actually, you want remote {}, not
> local {}.
On 9.2.2011, at 17.13, Ralf Hildebrandt wrote:
> * Timo Sirainen :
>
>> I think that'll work, yes, but it has the additional feature of allowing
>> clients from localnet to fake their IP address.
>
> Yes, I noticed this while reading the checkin message for the feature.
It's also mentioned in
* Timo Sirainen :
> I think that'll work, yes, but it has the additional feature of allowing
> clients from localnet to fake their IP address.
Yes, I noticed this while reading the checkin message for the feature.
> In v2.0 you can do:
>
> disable_plaintext_auth = yes
> local 10.0.0.0/24 {
>
On 9.2.2011, at 15.09, Nick Rosier wrote:
>> How can I force users which are connecting from OUTSIDE our newtworks
>> to user STARTTLS on Port 143?
>>
>> Right now we resort to IMAPS on port 993, but an additional STARTTLS
>> enabled login on the default port would make things easier!
>>
> You c
Ralf Hildebrandt wrote:
Hi!
How can I force users which are connecting from OUTSIDE our newtworks
to user STARTTLS on Port 143?
Right now we resort to IMAPS on port 993, but an additional STARTTLS
enabled login on the default port would make things easier!
You can probably add login_trusted_n
