On Wed, Mar 01, 2023 at 03:31:55PM -0700, Grant Taylor via Courier-imap wrote:
> On 3/1/23 11:31 AM, Doug McIntyre wrote:
> > The problem that I assumed was the issue (but apparently not), is
> > that when Courier IMAP is setup behind a load balancer/proxy such as
> > HAProxy without using the
On 3/1/23 11:31 AM, Doug McIntyre wrote:
The problem that I assumed was the issue (but apparently not), is
that when Courier IMAP is setup behind a load balancer/proxy such as
HAProxy without using the proxy protocol extension, the IP address
that Courier IMAP sees is the IP address of the
On 3/1/23 10:35 AM, Steve Charmer wrote:
Aha Grant, you were correct !
:-)
during testing and watching the logs, I had a webmail interface open, so
the code in the webmail script residing on the same server as the
courier installation was showing the server's public ip address.
That makes
On Tue, Feb 28, 2023 at 08:05:02PM -0500, Sam Varshavchik wrote:
> Doug McIntyre writes:
>
> > On Tue, Feb 28, 2023 at 06:22:12PM -0500, Sam Varshavchik wrote:
> >
> > > That's because there is nothing that the server can do to determine the
> > > client's real IP address. When NAT is used, as is
Aha Grant, you were correct !
during testing and watching the logs, I had a webmail interface open, so
the code in the webmail script residing on the same server as the courier
installation was showing the server's public ip address.
today, we tested imapd-ssl from a smartphone, and the expected
On 2/28/23 11:34 AM, Steve Charmer wrote:
hello,
Hi,
I want to add additional information to these lines.
The ip address is the public IPv4 of my server.
That seems both odd and somewhat unexpected to me.
I want to be able to add the public IPv4 address of the remote client
trying to
On 2/28/23 4:22 PM, Sam Varshavchik wrote:
That's because there is nothing that the server can do to determine the
client's real IP address. When NAT is used, as is apparently the case is
here, as far as the server knows that's the IP address where the
connection is coming from, and that's the
Doug McIntyre writes:
On Tue, Feb 28, 2023 at 06:22:12PM -0500, Sam Varshavchik wrote:
> That's because there is nothing that the server can do to determine the
> client's real IP address. When NAT is used, as is apparently the case is
> here, as far as the server knows that's the IP address
On Tue, Feb 28, 2023 at 06:22:12PM -0500, Sam Varshavchik wrote:
> Steve Charmer writes:
>
> > Feb 28 12:20:04 diggy-ocn-drop imapd-ssl: LOGOUT,
> > user=mailto:m...@mydomain.co>m...@mydomain.co,
> > ip=[:::104.xxx.xxx.xxx],
> > headers=0, body=0, rcvd=77, sent=330, time=0, starttls=1
Steve Charmer writes:
Feb 28 12:20:04 diggy-ocn-drop imapd-ssl: LOGOUT,
user=mailto:m...@mydomain.co>m...@mydomain.co, ip=[:::104.xxx.xxx.xxx],
headers=0, body=0, rcvd=77, sent=330, time=0, starttls=1
I want to add additional information to these lines.
The ip address is the public
10 matches
Mail list logo
