Ticket #824 (closed enhancement: fixed)

Opened 8 months ago

Last modified 4 weeks ago

IMAP SSL Traffic not counted

Reported by: BeNe Assigned to: raphael
Priority: major Milestone: ispCP ω 1.0.0 - RC5
Component: Backend (Engine) Version: ispCP ω 1.0.0 - DEV
Severity: Hard Keywords:
Cc: raphael

Description

When the Customer use IMAP-SSL & SMTP-SSL the Traffic is not counted in ispCP beacuse these Ports are not checked.--> http://www.isp-control.net/forum/imap-traffic-not-counted-t-1630.html

Attachments

Change History

(follow-up: ↓ 25 ) 10/28/2007 09:00:00 PM changed by raphael

  • priority changed from major to feature.
  • status changed from new to closed.
  • type changed from malfunction to enhancement.
  • resolution set to fixed.
  • milestone changed from ispCP ω 1.0.0 - RC4 to ispCP ω 1.0.0 - RC3.

Fixed in r890

Distros need to be updated before the changes are reflected.

11/07/2007 07:47:50 AM changed by BeNe

  • status changed from closed to reopened.
  • resolution deleted.

There is still no Traffic counted in the CustomerStatics.
No POP3/IMAP Traffic --> http://www.isp-control.net/forum/imap-traffic-not-counted-t-1630.html

11/18/2007 11:33:14 PM changed by raphael

can you try with the latest revision?

11/19/2007 05:47:25 PM changed by BeNe

Yes, i will test it!

11/19/2007 09:54:32 PM changed by BeNe

11/21/2007 11:30:54 PM changed by rats

  • owner set to raphael.
  • status changed from reopened to new.
  • milestone changed from ispCP ω 1.0.0 - RC3 to ispCP ω 1.0.0 - RC4.

02/17/2008 02:50:40 PM changed by rats

  • severity set to Hard.
  • milestone changed from ispCP ω 1.0.0 - RC4 to Working.

02/23/2008 05:45:05 PM changed by rats

  • priority changed from feature to major.
  • milestone changed from Working to ispCP ω 1.0.0 - RC4.

03/02/2008 12:22:31 AM changed by Cube

IMAP traffic is not counted because ispcp-vrl-traff looks for imaplogin in the logs, but at least Debian Etch logs it as couriertcpd, which is presumable a bug.

03/02/2008 12:43:07 AM changed by rats

I get imapd for imap Login on debian.

03/02/2008 12:57:49 AM changed by rats

  • status changed from new to closed.
  • resolution set to fixed.

I hope I got it in r1029

03/02/2008 01:15:48 AM changed by Cube

  • status changed from closed to reopened.
  • resolution deleted.

I'm not the only one with couriertcpd: http://www.isp-control.net/forum/imap-traffic-strange-things-t-1878.html

I now did a complete reinstall (with purge) of courier-imap and now it also logs as imapd. I now have a new config with LOGGEROPTS="-name=imapd". It seems there was a bug in Debian, but the configs were not updated with a normal apt-get update.

I also reinstalled courier-pop, now there's also the now option LOGGEROPTS="-name=pop3d", but it still logs as courierpop3login. I think is is an error in courier-pop's init-script, there $LOGGEROPTS is missing. Perhaps this will be changes also in the future.

So ispCP should look for imapd, pop3d, couriertcpd and courierpop3login.

03/02/2008 01:37:44 AM changed by Cube

...but the configs were not updated with a normal apt-get update.
I meant "apt-get upgrade".

03/02/2008 02:55:17 AM changed by breaki

imho apt asks you if you wanna get the new config files or take old one's if there was a change in them

(follow-up: ↓ 16 ) 03/02/2008 11:28:00 AM changed by anonymous

in the original /etc/courier/imapd (installed in Jan) there is the LOGGEROPTS=... but during installation of ispCP this file (and others) is overwritten and there the option is missing. So at least this is something we can fix...

There are some more differences from the Debian imapd file to the one delivered with ispCP... (and maybe we have to look in all theese files in /etc/courier)

(in reply to: ↑ 15 ) 03/02/2008 11:52:18 AM changed by joximu

Replying to anonymous: ... that was me... :-) (was not logged in)

(follow-up: ↓ 18 ) 03/02/2008 11:54:23 AM changed by rats

Do we need to shipper (old) courier config files with ispCP installation? Are there any changes to the courier files delivered with the distributions?

(in reply to: ↑ 17 ; follow-up: ↓ 20 ) 03/02/2008 01:00:38 PM changed by rats

Replying to rats:

Are there any changes to the courier files delivered with the distributions?

The only thing we have to change is authmodulelist="authpam" to authmodulelist="authuserdb"

mybe some day we can use pam, too.

03/02/2008 05:52:18 PM changed by Cube

I did not notice the config is overwritten by ispCP. So this was not a Debian bug, only the init-script is wrong. So it would be better to not overwrite the config-file, but to change the default file like it's already done with logrotate's apache-config. Then it will be enough to look for imapd, courierpop3login and pop3d (to be future-proof and perhaps for other distros).

(in reply to: ↑ 18 ) 03/02/2008 05:57:14 PM changed by Cube

Replying to rats:

Replying to rats: The only thing we have to change is authmodulelist="authpam" to authmodulelist="authuserdb"

BTW: authmodulelist is in authdaemonrc, so we don't need to touch imapd and pop3d at all.

03/02/2008 07:10:49 PM changed by rats

I tried it; It won't work, because authmodulelist="authpam" is in authdaemonrc. Maybe I made something wrong, please test.

03/03/2008 01:52:18 PM changed by joximu

Hi

I took the original /etc/courier - and just replaced

authmodulelist="authpam" with authmodulelist="authuserdb" in /etc/courier/authdaemonrc (as Cube stated above in c20 :-)

and at least imapd-ssl and normal pop3 is working (it's our company internal mailserver :-)

Now: the pop3-traffic is logged with "courierpop3login:" the others seem to take what's in the conf-file (LOGGEROPTS) - this exception is (as Cube mentioned in c19) - based on the different startup-scripts for the 4 different services...

I recommend: only change authdaemonrc (pam->userdb) and try to get the traffic with the 4 keywords (imapd, imapd-ssl, pop3d-ssl, courierpop3login) if this fit's for all distros. Otherwise change the init-script for courier-pop3d to also use the LOGGEROPTS... (maybe debian could do this also... :-)

/J

03/03/2008 01:55:33 PM changed by rats

okay, as I said. I'll try it tonight and if okay; I'll fix and close this ticket.

03/04/2008 11:47:48 PM changed by rats

  • status changed from reopened to closed.
  • resolution set to fixed.

fixed in r1033

(in reply to: ↑ 1 ) 05/16/2008 12:47:51 AM changed by zttom <tom@zitro.de>

  • status changed from closed to reopened.
  • resolution deleted.

Your coding is wrong. It has to be following because you dont know the order of the output of 'iptables -nvL'.

$smtp_in += $bytes if ($port == 25);

$smtp_in += $bytes if ($port == 587);

$pop3_in += $bytes if ($port == 110);

$pop3_in += $bytes if ($port == 995);

$imap_in += $bytes if ($port == 143);

$imap_in += $bytes if ($port == 993);

$http_in += $bytes if ($port == 80);

$http_in += $bytes if ($port == 443);

With your coding you are overwriting the value of the variable and as example not adding the pops traffic to the pop traffic. Sorry for my bad english. For a germany explanation please write a mail. By the way: Isn't the default port of smtps 465 and not 587?

05/16/2008 11:05:05 PM changed by zothos

  • milestone changed from ispCP ω 1.0.0 - RC4 to ispCP ω 1.0.0 - RC5.

05/29/2008 09:04:54 PM changed by zothos

  • status changed from reopened to closed.
  • resolution set to fixed.

fixed in r1182

06/11/2008 12:04:37 AM changed by aguylticsyl


Add/Change #824 (IMAP SSL Traffic not counted)




Action