Re: identify MUA connecting?
On Tue, 29 Jul 2014 00:49:37 +0200 Reindl Harald wrote: Am 28.07.2014 22:40, schrieb Peter Chiochetti: Am 2014-07-28 um 21:15 schrieb Reindl Harald: Am 28.07.2014 20:57, schrieb Rick Romero: Am 28.07.2014 19:58, schrieb Juan Pablo: The reason I am wanting to do this is I would like to know if people are getting their email on personal devices instead of work secured / standardized phones IMHO, client certificates would work work well here. I think Dovecot supports it yes, but you accept them or not that's a different story than log the MUA information Yes, it is a means to stop people from using insecure devices. a client certificate hadrly makes a device secure if the device is compromised your cert is gone So possibly a useful hint the OP may be interested in! Might well be that its the reason for learning which MUA was used? well, what client is used is impossible there is no user-agent like HTTP and even for HTTP the header is not mandatory and rqeuire it will break your web-app for anybody who cares for privacy while gain nothing Not in general: cyrus/imaps[9143]: client id: name Thunderbird version 24.6.0 I guess, dovecot simply must learn it. --Frank Elsner
Re: identify MUA connecting?
Am 29-07-2014 09:08, schrieb Frank Elsner: On Tue, 29 Jul 2014 00:49:37 +0200 Reindl Harald wrote: Am 28.07.2014 22:40, schrieb Peter Chiochetti: Am 2014-07-28 um 21:15 schrieb Reindl Harald: Am 28.07.2014 20:57, schrieb Rick Romero: Am 28.07.2014 19:58, schrieb Juan Pablo: The reason I am wanting to do this is I would like to know if people are getting their email on personal devices instead of work secured / standardized phones IMHO, client certificates would work work well here. I think Dovecot supports it yes, but you accept them or not that's a different story than log the MUA information Yes, it is a means to stop people from using insecure devices. a client certificate hadrly makes a device secure if the device is compromised your cert is gone So possibly a useful hint the OP may be interested in! Might well be that its the reason for learning which MUA was used? well, what client is used is impossible there is no user-agent like HTTP and even for HTTP the header is not mandatory and rqeuire it will break your web-app for anybody who cares for privacy while gain nothing Not in general: cyrus/imaps[9143]: client id: name Thunderbird version 24.6.0 I guess, dovecot simply must learn it. But this depend on if some Mailheader (X-mailer, User-Agent (k9), ...) are set. I'm sure this could be logged with sieve. I haven't seen a option on http://wiki2.dovecot.org/Variables for normal dovecot log, maybe there is one. Cheers Aleks
Re: identify MUA connecting?
29.07.2014 09:08, Frank Elsner: Not in general: cyrus/imaps[9143]: client id: name Thunderbird version 24.6.0 I guess, dovecot simply must learn it. Dovecot already knows about the ID fields a client sends. It just doesn't log them by default. This default, of course, can be changed - by setting imap_id_log appropriately. For example imap_id_log = * will log all ID info a client sends. Obviously, if a client doesn't send ID info, there's nothing dovecot can do about it, though. -- Regards mks
Re: identify MUA connecting?
On 28. jul. 2014 19.59.07 Juan Pablo juanpabl...@openmailbox.org wrote: Hello I am using dovecot 1.2.15 on ubuntu. dovecot -n is more usefull for more help ignore this maillist of unsupported version here is what settings i have in pluging section mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_group_events = no mail_log_fields = uid box msgid size Sent with AquaMail for Android http://www.aqua-mail.com
Re: identify MUA connecting?
Am 28.07.2014 19:58, schrieb Juan Pablo: Hello I am using dovecot 1.2.15 on ubuntu. Is it possible to somehow log the MUA information that is connecting to Dovecot? The reason I am wanting to do this is I would like to know if people are getting their email on personal devices instead of work secured / standardized phones from where should that information come? dovecot has IP, auth-method, username, passwword, TLS that is logged - there is no more information available grep the logs and analyze IP's reslove the PTR's and you get some useful informations signature.asc Description: OpenPGP digital signature
Re: identify MUA connecting?
On 2014-07-28 18:14, Reindl Harald wrote: from where should that information come? That is what I was not sure. I did not know what information was possible available. I was thinking or hoping something same as http logs dovecot has IP, auth-method, username, passwword, TLS that is logged - there is no more information available I see unfortunate but thank you for this information grep the logs and analyze IP's reslove the PTR's and you get some useful informations not of use as their business device can be used from home where also their personal device may be
Re: identify MUA connecting?
On 07/28/2014 05:58 PM, Juan Pablo wrote: Hello I am using dovecot 1.2.15 on ubuntu. UPGRADE! Dovecot 2.x is no longer supported. Is it possible to somehow log the MUA information that is connecting to Dovecot? In the Dovecot v2.0 tree there was the following commit: changeset: 9123:edcafb3efbbf branch: HEAD user:Timo Sirainen t...@iki.fi date:Thu Apr 16 19:14:23 2009 -0400 summary: Added imap_idle_notify_interval setting. Some time later in the v2.1 tree there was fix: changeset: 14197:32ffa616f249 user:Timo Sirainen t...@iki.fi date:Sat Feb 25 07:29:15 2012 +0200 summary: imap-login: imap_id_* settings were ignored pre-login. So, if you would use Dovecot v2.1.x you would be able to log some information about the connected client. BUT not all mail clients are supporting RFC2971 [http://tools.ietf.org/html/rfc2971]. The settings for this feature are configured in conf.d/20-imap.conf: * imap_id_log * imap_id_send The reason I am wanting to do this is I would like to know if people are getting their email on personal devices instead of work secured / standardized phones. That depends on the used software, see above Regards, Pascal -- The trapper recommends today: beeffeed.1420...@localdomain.org
Re: identify MUA connecting?
On 07/28/2014 06:38 PM, Pascal Volk wrote: In the Dovecot v2.0 tree there was the following commit: changeset: 9123:edcafb3efbbf branch: HEAD user:Timo Sirainen t...@iki.fi date:Thu Apr 16 19:14:23 2009 -0400 summary: Added imap_idle_notify_interval setting. … Oops, that was the wrong one. :-) Bad grep-voodoo, sorry. So you will need Dovecot v2.1.1 at least. Regards, Pascal -- The trapper recommends today: beeffeed.1420...@localdomain.org
Re: identify MUA connecting?
Quoting Reindl Harald h.rei...@thelounge.net: Am 28.07.2014 19:58, schrieb Juan Pablo: Hello I am using dovecot 1.2.15 on ubuntu. Is it possible to somehow log the MUA information that is connecting to Dovecot? The reason I am wanting to do this is I would like to know if people are getting their email on personal devices instead of work secured / standardized phones from where should that information come? dovecot has IP, auth-method, username, passwword, TLS that is logged - there is no more information available grep the logs and analyze IP'sreslove the PTR's and you get some useful informations IMHO, client certificates would work work well here. I think Dovecot supports it. Rick
Re: identify MUA connecting?
Am 28.07.2014 20:57, schrieb Rick Romero: Quoting Reindl Harald h.rei...@thelounge.net: Am 28.07.2014 19:58, schrieb Juan Pablo: Hello I am using dovecot 1.2.15 on ubuntu. Is it possible to somehow log the MUA information that is connecting to Dovecot? The reason I am wanting to do this is I would like to know if people are getting their email on personal devices instead of work secured / standardized phones from where should that information come? dovecot has IP, auth-method, username, passwword, TLS that is logged - there is no more information available grep the logs and analyze IP'sreslove the PTR's and you get some useful informations IMHO, client certificates would work work well here. I think Dovecot supports it yes, but you accept them or not that's a different story than log the MUA information signature.asc Description: OpenPGP digital signature
Re: identify MUA connecting?
Am 2014-07-28 um 21:15 schrieb Reindl Harald: Am 28.07.2014 20:57, schrieb Rick Romero: Am 28.07.2014 19:58, schrieb Juan Pablo: The reason I am wanting to do this is I would like to know if people are getting their email on personal devices instead of work secured / standardized phones IMHO, client certificates would work work well here. I think Dovecot supports it yes, but you accept them or not that's a different story than log the MUA information Yes, it is a means to stop people from using insecure devices. So possibly a useful hint the OP may be interested in! Might well be that its the reason for learning which MUA was used? -- peter
Re: identify MUA connecting?
Am 28.07.2014 22:40, schrieb Peter Chiochetti: Am 2014-07-28 um 21:15 schrieb Reindl Harald: Am 28.07.2014 20:57, schrieb Rick Romero: Am 28.07.2014 19:58, schrieb Juan Pablo: The reason I am wanting to do this is I would like to know if people are getting their email on personal devices instead of work secured / standardized phones IMHO, client certificates would work work well here. I think Dovecot supports it yes, but you accept them or not that's a different story than log the MUA information Yes, it is a means to stop people from using insecure devices. a client certificate hadrly makes a device secure if the device is compromised your cert is gone So possibly a useful hint the OP may be interested in! Might well be that its the reason for learning which MUA was used? well, what client is used is impossible there is no user-agent like HTTP and even for HTTP the header is not mandatory and rqeuire it will break your web-app for anybody who cares for privacy while gain nothing signature.asc Description: OpenPGP digital signature
Re: identify MUA connecting?
Juan Pablo juanpabl...@openmailbox.org writes:
That is what I was not sure. I did not know what information was
possible available. I was thinking or hoping something same as http logs
My dovecot 2 installation logs this information. E.g.
Jul 26 07:13:02 server dovecot: imap(user): ID sent: name=iPad
Mail, version=11D201, os=iOS, os-version=7.1.1 (11D201)
Jul 26 07:13:38 server dovecot: imap-login: ID sent:
name=com.google.android.email, os=android, os-version=4.4.4;
KTU84P, vendor=LGE, x-android-device-model=Nexus 4,
x-android-mobile-net-operator=Koodo, AGUID=...: user=,
rip={client-ip}, lip={server-ip}, TLS,
session=BH7SSxn/CQBFrJG2
If you want this info, upgrade, as a later poster suggests.
Joseph Tam jtam.h...@gmail.com
