IMAP SSL Traffic not counted

Fixed in r890

Distros need to be updated before the changes are reflected.

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

can you try with the latest revision?

Yes, i will test it!

No effect! --> http://www.isp-control.net/forum/imap-traffic-not-counted-t-1630-2.html#pid16354

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.

I get imapd for imap Login on debian.

I hope I got it in r1029

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.

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

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

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)

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

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

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.

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).

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.

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

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

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

fixed in r1033

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?

fixed in r1182

tbwWBW <a href="http://lyofchqqfskg.com/">lyofchqqfskg</a>, [url=http://oujlzvshacvb.com/]oujlzvshacvb[/url], [link=http://yogqoxhqunmf.com/]yogqoxhqunmf[/link], http://xffqjeghyvgx.com/