On 17 Jan 2018, at 4:38, Maxim Dounin wrote:
>> On Tue, Jan 16, 2018 at 12:23:31PM -0800, Luis E. Muñoz wrote:
>> ⋮
>> Given how I've not seen any mention to logging in the various
>> documents
>> that describe SMTP/IMAP/POP proxying, [⋯]

> The error_log directive as available in the core module works for
> mail module, too. If needed, you can set a specific error log in
> mail{} or server{} contexts. See http://nginx.org/r/error_log for
> details.
>
> There is no access log support for mail. Instead, basic mail
> session events are logged to the error log at the "info" level.

Thank you very much for your response. Indeed, the error_log directive
produces suitable logging that include both ends of the proxied
connection.

Best regards

Luis Muñoz
Director, Registry Operations
____________________________

http://www.uniregistry.link/
2161 San Joaquin Hills Road
Newport Beach, CA 92660

Office +1 949 706 2300 x 4242
lem@uniregistry.link
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx