Displaying 7 results from an estimated 7 matches for "hfs9qwk03sbtbnrn".
2016 May 30
2
logging TLS SNI hostname
...ki.dovecot.org/Variables ). Please consider this to be a feature
request.
The goal is to be able to see which hostname client used like:
May 30 08:21:19 xxx dovecot: pop3-login: Login: user=<abc>, method=PLAIN,
rip=1.1.1.1, lip=2.2.2.2, mpid=17135, TLS, SNI=pop3.somehost.org,
session=<hfS9Qwk03sBTBnrN>
--
Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org )
2016 Oct 17
2
logging TLS SNI hostname
...ture
>> request.
>>
>> The goal is to be able to see which hostname client used like:
>>
>> May 30 08:21:19 xxx dovecot: pop3-login: Login: user=<abc>, method=PLAIN,
>> rip=1.1.1.1, lip=2.2.2.2, mpid=17135, TLS, SNI=pop3.somehost.org,
>> session=<hfS9Qwk03sBTBnrN>
>
> Dear dovecot team, would be possible to add such variable ^^^^^ ?
>
> That would be neat feature because server operator would know what hostname
> client uses to connect to server (which is really usefull in case of many
> hostnames pointing to single IP).
I?d love t...
2016 Oct 20
2
logging TLS SNI hostname
...t;>> The goal is to be able to see which hostname client used like:
>>>>
>>>> May 30 08:21:19 xxx dovecot: pop3-login: Login: user=<abc>,
>>>> method=PLAIN, rip=1.1.1.1, lip=2.2.2.2, mpid=17135, TLS,
>>>> SNI=pop3.somehost.org, session=<hfS9Qwk03sBTBnrN>
>>> Dear dovecot team, would be possible to add such variable ^^^^^ ?
>>>
>>> That would be neat feature because server operator would know what
>>> hostname client uses to connect to server (which is really usefull in
>>> case of many hostnames poin...
2016 Oct 20
2
logging TLS SNI hostname
...e to see which hostname client used like:
>>>>>>
>>>>>> May 30 08:21:19 xxx dovecot: pop3-login: Login: user=<abc>,
>>>>>> method=PLAIN, rip=1.1.1.1, lip=2.2.2.2, mpid=17135, TLS,
>>>>>> SNI=pop3.somehost.org, session=<hfS9Qwk03sBTBnrN>
>>>>> Dear dovecot team, would be possible to add such variable ^^^^^ ?
>>>>>
>>>>> That would be neat feature because server operator would know what
>>>>> hostname client uses to connect to server (which is really usefull in
>>...
2016 Oct 18
0
logging TLS SNI hostname
...t;>
> >> The goal is to be able to see which hostname client used like:
> >>
> >> May 30 08:21:19 xxx dovecot: pop3-login: Login: user=<abc>,
> >> method=PLAIN, rip=1.1.1.1, lip=2.2.2.2, mpid=17135, TLS,
> >> SNI=pop3.somehost.org, session=<hfS9Qwk03sBTBnrN>
> >
> > Dear dovecot team, would be possible to add such variable ^^^^^ ?
> >
> > That would be neat feature because server operator would know what
> > hostname client uses to connect to server (which is really usefull in
> > case of many hostnames pointin...
2016 Oct 20
0
logging TLS SNI hostname
...s to be able to see which hostname client used like:
> >>>>
> >>>> May 30 08:21:19 xxx dovecot: pop3-login: Login: user=<abc>,
> >>>> method=PLAIN, rip=1.1.1.1, lip=2.2.2.2, mpid=17135, TLS,
> >>>> SNI=pop3.somehost.org, session=<hfS9Qwk03sBTBnrN>
> >>>
> >>> Dear dovecot team, would be possible to add such variable ^^^^^ ?
> >>>
> >>> That would be neat feature because server operator would know what
> >>> hostname client uses to connect to server (which is really usefull in...
2016 Oct 20
0
logging TLS SNI hostname
...me client used like:
> >>>>>>
> >>>>>> May 30 08:21:19 xxx dovecot: pop3-login: Login: user=<abc>,
> >>>>>> method=PLAIN, rip=1.1.1.1, lip=2.2.2.2, mpid=17135, TLS,
> >>>>>> SNI=pop3.somehost.org, session=<hfS9Qwk03sBTBnrN>
> >>>>>
> >>>>> Dear dovecot team, would be possible to add such variable ^^^^^ ?
> >>>>>
> >>>>> That would be neat feature because server operator would know what
> >>>>> hostname client uses to connec...