Get a list of currently active IMAP connections?

[Narcis Garcia]

Hi Paul, with your command syntax I get no account/IP on Debian GNU/Linux:

$ ps -axww | grep imap
19024 ?        S      0:00 dovecot/imap
19696 ?        S      0:00 dovecot/imap
20515 ?        S      0:04 dovecot/imap
22247 pts/4    S+     0:00 grep imap
24720 ?        S      0:03 dovecot/imap
24991 ?        S      0:00 dovecot/imap
25446 ?        S      0:03 dovecot/imap
25447 ?        S      0:04 dovecot/imap
25475 ?        S      0:03 dovecot/imap
31778 ?        S      6:10 dovecot/imap-login



Narcis Garcia

__________
I'm using this dedicated address because personal addresses aren't 
masked enough at this mail public archive. Public archive administrator 
should fix this against automated addresses collectors.
El 19/8/22 a les 8:22, Paul Kudla (SCOM.CA Internet Services Inc.) ha 
escrit:
> 
> I use ps : (greping by imap & idle)
> 
> # ps -axww | grep imap | grep IDLE
> 
> thant and split() in python
> 
> 
> 
>   8606  -  S         0:08.78 imap: [keith at elirpa.com 54.242.98.60 IDLE] 
> (imap)
> 12234  -  I         0:01.00 imap: [reception at clancyca.com 72.143.119.178 
> IDLE] (imap)
> 20668  -  S         0:02.01 imap: [paul at scom.ca 216.58.25.131 IDLE] (imap)
> 23219  -  I         0:00.33 imap: [clancy at clancyca.com 72.143.119.178 
> IDLE] (imap)
> 26761  -  S         0:00.52 imap: [ed.hanna at ekst.ca 204.237.91.165 IDLE] 
> (imap)
> 26785  -  I         0:00.87 imap: [ed at scom.ca 204.237.91.165 IDLE] (imap)
> 26787  -  I         0:00.80 imap: [ed.hanna at dssmgmt.com 204.237.91.165 
> IDLE] (imap)
> 27378  -  S         0:00.42 imap: [ed at scom.ca 204.237.91.165 IDLE] (imap)
> 31404  -  S         0:03.90 imap: [paul at scom.ca 216.58.25.131 IDLE] (imap)
> 32494  -  S         0:00.13 imap: [installers at tomkudla.ca 167.94.196.10 
> IDLE] (imap)
> 32497  -  S         0:00.13 imap: [installers at tomkudla.ca 167.94.196.10 
> IDLE] (imap)
> 33809  -  I         0:00.28 imap: [clancy at clancyca.com 72.143.119.178 
> IDLE] (imap)
> 36321  -  I         0:00.21 imap: [clancy at clancyca.com 72.143.119.178 
> IDLE] (imap)
> 39188  -  I         0:00.39 imap: [clancy at clancyca.com 72.143.119.178 
> IDLE] (imap)
> 42706  -  S         0:00.45 imap: [ed at scom.ca 204.237.91.165 IDLE] (imap)
> 46356  -  S         0:02.98 imap: [rcooke at tnky.ca 198.91.141.141 IDLE] 
> (imap)
> 46422  -  S         0:01.32 imap: [rcooke at tnky.ca 198.91.141.141 IDLE] 
> (imap)
> 46424  -  S         0:01.27 imap: [rcooke at tnky.ca 198.91.141.141 IDLE] 
> (imap)
> 50756  -  S         0:01.36 imap: [rcooke at tnky.ca 198.91.141.141 IDLE] 
> (imap)
> 58656  -  I         0:00.07 imap: [ditchburn at clancyca.com 216.58.50.30 
> IDLE] (imap)
> 63886  -  S         0:00.70 imap: [rcooke at tnky.ca 198.91.141.141 IDLE] 
> (imap)
> 68246  -  I         0:00.08 imap: [li at clancyca.com 72.143.119.178 IDLE] 
> (imap)
> 74719  -  I         0:00.03 imap: [dan at elirpa.com 142.183.30.44 IDLE] 
> (imap)
> 76580  -  I         0:00.02 imap: [info at willsagriquipandfencing.ca 
> 173.32.244.194 IDLE] (imap)
> 76584  -  I         0:00.02 imap: [howard at willsagriquipandfencing.ca 
> 173.32.244.194 IDLE] (imap)
> 77567  -  S         0:00.04 imap: [rcooke at tnky.ca 198.91.141.141 IDLE] 
> (imap)
> 77569  -  I         0:00.03 imap: [rcooke at tnky.ca 198.91.141.141 IDLE] 
> (imap)
> 
> 
> 
> 
> 
> 
> Happy Friday !!!
> Thanks - paul
> 
> Paul Kudla
> 
> 
> Scom.ca Internet Services <http://www.scom.ca>
> 004-1009 Byron Street South
> Whitby, Ontario - Canada
> L1N 4S3
> 
> Toronto 416.642.7266
> Main 1.866.411.7266
> Fax 1.888.892.7266
> Email paul at scom.ca
> 
> On 8/18/2022 6:28 PM, J Doe wrote:
>>
>> On 2022-08-16 16:46, Antonio Leding wrote:
>>> At the risk of being pedestrian, I just use something like |sudo 
>>> netstat -an | grep ‘:[ IMAP_PORT ]’|
>>>
>>> I’m pretty sure you thought of this but still, thought I would toss 
>>> it out…
>>>
>>
>> Hi Antonio and Jaroslaw,
>>
>> I don't think the second solution is pedestrian; I think it's cool 
>> that people have come up with different solutions for the same problem!
>>
>> I am thinking that this may not be the solution that Jaroslaw is 
>> looking for, as this also requires spawning a process to run netstat 
>> and then capturing the results.  The socket approach avoids an 
>> additional process.
>>
>> - J
>>