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 public IPv4 addresses were showing up in the log. thank you, and sorry to all whom I may have wasted your time. On Tue, Feb 28, 2023 at 9:48 PM Grant Taylor via Courier-imap < courier-imap@lists.sourceforge.net> wrote: > 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 login to courier-imapd > > The thing that I don't understand is why you aren't already seeing the > public IP address of the remote client trying to log in. > > Both Courier servers that I'm running do show the remote IP address of > clients. > > Is there a chance that the IP that you're seeing is your server logging > into itself? Possibly via a webmail interface running on the same system? > > > can I add additional text to that line to include the remote ip address? > > I think that you should already be seeing the remote IP address of clients. > > So if you're not seeing remote IP addresses of clients, I'd take that as > an indication that something is wrong. > > > > -- > Grant. . . . > unix || die > > > _______________________________________________ > Courier-imap mailing list > Courier-imap@lists.sourceforge.net > Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap >
_______________________________________________ Courier-imap mailing list Courier-imap@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
