Hello Maxim,
Thank you for your answer. As you know, nginx does not send Auth command to
backend server, so there's no way for the backend to know if the sender
matches the authenticated account. I tried proxy_smtp_auth config but nginx
send mail COMMAND to my server but it can not understand :(
I have nginx setup to proxy file uploads. The file upload streams into
nginx, goes into my upstream, and then the upstream streams it to Amazon S3
(after some basic processing). In addition to proxying the upload, I also
want to proxy the download, with some caching on the nginx side.
It would be
Hello All,
Is it possible to configure NGINX to ignore the Content-Length header when used
as a reverse-proxy? Ideally for an individual location block while unaffecting
the rest of the configuration.
Currently, if the client sends a POST with Content-Length of 32767 then 32767
bytes makes it
Hello!
On Thu, May 20, 2021 at 03:25:48AM -0400, mbrother wrote:
> I am a fan of nginx and I really like nginx mail proxy module. I'm having a
> problem between the authenticated account and the sender when using this
> module. For better understanding, please see my test below:
>
> root@nginx:~
On Wed, 19 May 2021 07:55:24 +0530, Amila Gunathilaka wrote:
>
> Any update for my issue guys ?
Not if you are going to re-post THE ENTIRE ^%$&%&%! DIGEST
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello,
I am a fan of nginx and I really like nginx mail proxy module. I'm having a
problem between the authenticated account and the sender when using this
module. For better understanding, please see my test below:
root@nginx:~# telnet xx.xx.xx.xx 25
Trying xx.xx.xx.xx ...
Connected to xx.xx.
