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
ma
Hello!
On Wed, Jan 17, 2018 at 07:33:43AM -0500, anish10dec wrote:
[...]
> > > Is there a way to check for First IP Address in http_x_forwarded_for for
> > > blocking the request ?
> >
> > If you really want to, you can do so using the
> > geoip_proxy_recursive directive and configuring the g
Hello!
On Tue, Jan 16, 2018 at 12:23:31PM -0800, Luis E. Muñoz wrote:
[...]
> Proxying and authentication works as advertised, no issues. However,
> I've been unable to locate any piece of documentation indicating how to
> produce a suitable access log message (ie, a log tying the mail client
Thanks ... We need the Client IP on Server B as well for analytics .
Tried by enabling the Geo IP module on Server A which looks after remote
address field and successfully blocks the request.
But the problem here is that it is even blocking the requests coming from
our Internal Private IP Segme
Maxim Dounin Wrote:
---
> Hello!
>
> On Thu, Jan 11, 2018 at 07:17:20AM -0500, anish10dec wrote:
>
> > GeoIP module is able to block request on basis of remote address
> which is IP
> > of the remote device or user but not on basis of X-Forwarde
