Am 18.08.2021 um 03:14 schrieb Robert Mueller: >> First, thanks for the patch. >> >> While the reuseport could cure (or hide if you will) the unbalancing you >> see it makes sense to get better understanding what exactly is going on. >> So far we haven't seen such weird behaviour ourself neither received >> reports about such uneven connections distribution amby MKl - Nginx Development
Hi Maxim, On Mar 3, 2015, at 4:50 PM, Maxim Dounin wrote: > Hello! > > On Tue, Mar 03, 2015 at 03:14:50PM +0100, Michael Kliewe wrote: > >> Hi again, >> >> On Mar 2, 2015, at 3:56 PM, Maxim Dounin wrote: >> >> I'm sorry, I don't really want to repeat my arguments, but as I >> said I don't have control over all nginx servers that are used. >by MKl - Nginx Development
Hi again, On Mar 2, 2015, at 3:56 PM, Maxim Dounin wrote: > Hello! > > On Mon, Mar 02, 2015 at 03:32:03PM +0100, Michael Kliewe wrote: > >> Hi Maxim, >> >> On Mar 2, 2015, at 3:14 PM, Maxim Dounin wrote: >> >>> Hello! >>> >>> On Mon, Mar 02, 2015 at 01:12:44PM +0100, Michael Kliewe >>> wrote: >>> >>>by MKl - Nginx Development
Hi Maxim, On Mar 2, 2015, at 3:14 PM, Maxim Dounin wrote: > Hello! > > On Mon, Mar 02, 2015 at 01:12:44PM +0100, Michael Kliewe wrote: > >> with your changes there is a problem: >> nginx now just sends the header if the connection is encrypted. >> If the connection is not encrypted, then there is no header sent >> to the auth script. >> In the auth sby MKl - Nginx Development
Hi Maxim, with your changes there is a problem: nginx now just sends the header if the connection is encrypted. If the connection is not encrypted, then there is no header sent to the auth script. In the auth script I cannot distinguish between "user did not use encryption" and "nginx doesn't have the feature" (because of mixed nginx versions). With the original version of theby MKl - Nginx Development
Hi Maxim, thank you very much, that helps a lot! Then we can use the unpatched nginx version again instead of self-compiling it every time ;-) Michael Am 25.02.2015 um 16:28 schrieb Maxim Dounin: > Hello! > > On Thu, Feb 05, 2015 at 04:00:28PM +0300, Maxim Dounin wrote: > >> Hello! >> >> On Wed, Feb 04, 2015 at 10:07:50PM +0100, Michael Kliewe wrote: >> >by MKl - Nginx Development
Hi Maxim, I would like to remind again this feature patch. It would help a lot to get this information about transport encryption into the auth script. It does not hurt the performance, and is a very tiny patch. You can rename the header name and values as you like. It would be very nice if you could please merge it into nginx. Thanks! Michael Am 01.08.2014 um 22:14 schrieb Michael Kliewe:by MKl - Nginx Development
Hi, Am 18.09.2014 um 19:59 schrieb Kunal Pariani: > Zimbra has a patch implementing this IMAP ID command > (http://www.rfc-base.org/txt/rfc-2971.txt). Would anyone from the > nginx team comment on if they would like this from us ? > > Thanks > -Kunal Please see the following patch, which Filipe implemented for me, but it has never been added to nginx ;-( http://mailman.nginxby MKl - Nginx Development
Hi, you can rename it as you wish, as long as the functionality gets into nginx ;-) Michael Am 01.08.2014 um 20:59 schrieb Maxim Dounin: > Hello! > > On Thu, Jul 31, 2014 at 04:32:16AM +0200, Michael Kliewe wrote: > >> Hi Maxim, >> >> this is very interesting to have in nginx, and it's a very easy patch. Any >> chance this gets into nginx? It helps a lot toby MKl - Nginx Development
Hi Maxim, this is very interesting to have in nginx, and it's a very easy patch. Any chance this gets into nginx? It helps a lot to migrate users to encrypted mail connections, allowing some users to still use unencrypted connections, and log in the auth script which user already uses encrypted connections. It would be great if you could add it to nginx. Thanks! Michael Am 19.06.2014 um 22by MKl - Nginx Development
Hi Maxim, On Mar 6, 2014, at 5:27 PM, Maxim Dounin wrote: > Hello! > > On Thu, Mar 06, 2014 at 10:59:29AM +0100, Filipe da Silva wrote: > >> # HG changeset patch >> # User Filipe da Silva <fdasilvayy@gmail.com> >> # Date 1394099468 -3600 >> # Thu Mar 06 10:51:08 2014 +0100 >> # Node ID 51fd90f96449c23af0076a19efbfdb1f88702125 >> # Pareby MKl - Nginx Development
Hello, I'm using the mail module of nginx to proxy and loadbalance IMAP+POP3 connections to backend servers. I do authentication via http authentication. Some Clients are sending IMAP ID commands to the server with information about their software and version. I would like to log that and maybe use that during authentication. It would be great if nginx would support that command, and if it hby MKl - Nginx Development
Maxim Dounin Wrote: ------------------------------------------------------- > Looks like the problem fixed by this changeset: > > http://trac.nginx.org/nginx/changeset/32fe021911c9/nginx > > Should work fine in nginx 1.5.1+. Hi Maxim, thanks for your answer! I will try this later. Will this also be merged into 1.4 or even 1.2 branch? Because it's a bugfix and not a neby MKl - Nginx Mailing List - English
Hello, to increase security of SSL I added some eliptic-curves-ciphers to the chain. For HTTPS it's working fine, but for the mail proxy it does not work, I only always get RC4-SHA instead of the ECDH ciphers. See configuration at the end of this message. I'm testing it with: openssl s_client -cipher 'ECDH:DH' -connect domain.de:443 openssl s_client -cipher 'ECDH:DH' -connect imap.domain.by MKl - Nginx Mailing List - English