1 (edited by pbf343 2015-09-02 23:49:13)

Topic: dovecot.log with rip=127.0.0.1

==== Required information ====
- iRedMail version (check /etc/iredmail-release):
- Linux/BSD distribution name and version:
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Web server (Apache or Nginx):
- Manage mail accounts with iRedAdmin-Pro?
- Related log if you're reporting an issue:
====

CentOS 6.6 with iRedAdmin-Pro mysql.

How, why or what would cause a user connection in the dovecot.log to represent the loopback (127.0.0.1) IP for RIP.  I think using the wedmail interface would result in such a scenario.  However, it is possible that others exist? 


Example:

Sep 02 07:03:48 imap-login: Info: Login: user=<bob@domain_name.tld>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=1726, secured, session=<QRT7nsEe2gB/AAAB>
Sep 02 07:03:48 imap-login: Info: Login: user=<bob@domain_name.tld>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=1728, secured, session=<R6P8nsEe3AB/AAAB>
Sep 02 07:03:49 imap-login: Info: Login: user=<bob@domain_name.tld>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=1740, secured, session=<wj8Mn8Ee3gB/AAAB>
Sep 02 07:03:49 imap-login: Info: Login: user=<bob@domain_name.tld>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=1743, secured, session=<1ogMn8Ee4AB/AAAB>
Sep 02 07:04:41 imap-login: Info: Login: user=<bob@domain_name.tld>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=1774, secured, session=<nZQlosEe8AB/AAAB>
Sep 02 07:04:49 imap-login: Info: Login: user=<bob@domain_name.tld>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=1777, secured, session=<jf2josEe8gB/AAAB>

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: dovecot.log with rip=127.0.0.1

pbf343 wrote:

How, why or what would cause a user connection in the dovecot.log to represent the loopback (127.0.0.1) IP for RIP.

Webmail, SOGo, and other applications running on localhost.