POP-before-SMTP w/Exim and Courier IMAP/POP?
I've looked at the "drac" package, but the documentation leaves a bit to be desired. Has anyone found a good tool for doing POP (or IMAP) before SMTP to allow relaying in Exim? I'd rather not roll my own, but I guess I could... Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! <[EMAIL PROTECTED]> | http://jeremy.zawodny.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Problem with ifconfig???
Hello: I have this strange problem. When i issue ifconfig the output for eth0 is the following: eth0 Link encap:Ethernet HWaddr 00:07:95:0F:79:F9 inet addr:64.86.241.90 Bcast:64.86.241.95 Mask:255.255.255.248 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:184422998 errors:0 dropped:4876 overruns:0 frame:0 TX packets:228525471 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:5 Base address:0xd000 as you see packets count are ok but bytes count??? Any idea. In /proc/net/dev is the same thing.. Thanx Salu2 Andres -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SQUID LOG
On Fri, Oct 04, 2002 at 08:53:26AM +0200, ?ngel Carrasco wrote: > Yeah, but this option runs good, but sarg only sends a list de users. > But I need a list the webs visited by user. unless you're using proxy authentication, squid does not log by user, it logs by client IP address. if you enable squid proxy authentication, or if the client IP address can be traced to a specific user (e.g. you have static IP addresses for each client on your LAN, or dhcp assigns the same IP to the same MAC address each time) then you can track each request back to a notional user - i say notional because sometimes people use someone else's workstation. users with a bit of a clue can even wait until they know another user has switched off their workstation and then assign the same IP address to their own workstation - browsing the web with all logging being recorded against the IP address belonging to the other user. similarly, password security is sloppy in many offices (because most users absolutely refuse to believe that securing their password is at all important), with people sharing logins/passwords or writing their password on sticky notes and attaching it to their monitor. even if you manage to solve all the problems noted above(*), and write/modify a script to email reports to your boss, your boss will receive reports that are many megabytes in size. almost certainly he will not bother to read them. even if he does bother, it sounds like he will not bother learning how to interpret what he is reading, so there is no point. (*) the easiest way is to just lie and pretend that these issues are not a problem. this is what most log analyser programs do. the fact is that both web and proxy logs are useful only for telling you how much load the server is under. anything else is just guesswork, which is OK if you understand that it's guesswork, but dangerous if you believe that it's "the truth". craig -- craig sanders <[EMAIL PROTECTED]> Fabricati Diem, PVNC. -- motto of the Ankh-Morpork City Watch -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
LSB and Debian, Commercial perspective
Hi all, Was reading an article on News.com http://news.com.com/2100-1001-961296.html?tag=fd_top_5 -- Four new versions of Linux have been certified to comply with guidelines set down by the Linux Standard Base, a group trying to make it easier for software to run on different companies' versions of the Unix clone. Red Hat 8, SuSE 8.1, SCO Group OpenLinux 3.1.1 and MandrakeSoft 9 ProSuite all comply with the LSB's guidelines, according to the Free Standards Group, which oversees the LSB certification process. - What are your thoughts on this? Since everyone on this group is presumably running Debian Linux for a server/commercial perspective, our views would probably differ from the home/desktop users. To the home user, I can't see this making any huge difference. But on the commercial side, I can see this having serious long-term consequences. IMHO, I think Debian should join the group (and as many standards groups as possible), if not just for the compatibility, but also for the appearance of co-operating. I'd hate if more and more companies certify their software and drivers for those 4 distros, and leave Debian out "because it's not part of any standard". I know that kind of answer is bogus and not really a reason to not support Debian, but I'm sure that's what we'll be hearing from the vendors later on as an excuse not to support Debian "officially". Since many times we need "official" vendor support for company purchases and such (however useless it may end up being), what do you guys think of all this? I would really hate if we were forced to go an "only Redhat" or "only Mandrake" path just because vendors start supporting only the "standardized" distros. (Oh, and just in case Debian actually already complies with the LSB, why on earth is it not mentioned in the article, or other prominent places? If that _IS_ the case I think Debian seriously needs to do better PR work, otherwise vendors are going to drop support and/or ignore Debian, calling it "the distro no one heard of"). Sincerely, Jason Lim Zentek International Co. Ltd. http://www.zentek-international.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: how to use web based change LDAP password?
axacheng wrote: > how about "Poppass" or others? > this does work but i have turned it off for security reasons. mfg.ds.ar IOhannes > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: how to use web based change LDAP password?
axacheng wrote: how about "Poppass" or others? this does work but i have turned it off for security reasons. mfg.ds.ar IOhannes
POP-before-SMTP w/Exim and Courier IMAP/POP?
I've looked at the "drac" package, but the documentation leaves a bit to be desired. Has anyone found a good tool for doing POP (or IMAP) before SMTP to allow relaying in Exim? I'd rather not roll my own, but I guess I could... Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! <[EMAIL PROTECTED]> | http://jeremy.zawodny.com/
Problem with ifconfig???
Hello: I have this strange problem. When i issue ifconfig the output for eth0 is the following: eth0 Link encap:Ethernet HWaddr 00:07:95:0F:79:F9 inet addr:64.86.241.90 Bcast:64.86.241.95 Mask:255.255.255.248 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:184422998 errors:0 dropped:4876 overruns:0 frame:0 TX packets:228525471 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:5 Base address:0xd000 as you see packets count are ok but bytes count??? Any idea. In /proc/net/dev is the same thing.. Thanx Salu2 Andres
Re: SQUID LOG
On Fri, Oct 04, 2002 at 08:53:26AM +0200, ?ngel Carrasco wrote: > Yeah, but this option runs good, but sarg only sends a list de users. > But I need a list the webs visited by user. unless you're using proxy authentication, squid does not log by user, it logs by client IP address. if you enable squid proxy authentication, or if the client IP address can be traced to a specific user (e.g. you have static IP addresses for each client on your LAN, or dhcp assigns the same IP to the same MAC address each time) then you can track each request back to a notional user - i say notional because sometimes people use someone else's workstation. users with a bit of a clue can even wait until they know another user has switched off their workstation and then assign the same IP address to their own workstation - browsing the web with all logging being recorded against the IP address belonging to the other user. similarly, password security is sloppy in many offices (because most users absolutely refuse to believe that securing their password is at all important), with people sharing logins/passwords or writing their password on sticky notes and attaching it to their monitor. even if you manage to solve all the problems noted above(*), and write/modify a script to email reports to your boss, your boss will receive reports that are many megabytes in size. almost certainly he will not bother to read them. even if he does bother, it sounds like he will not bother learning how to interpret what he is reading, so there is no point. (*) the easiest way is to just lie and pretend that these issues are not a problem. this is what most log analyser programs do. the fact is that both web and proxy logs are useful only for telling you how much load the server is under. anything else is just guesswork, which is OK if you understand that it's guesswork, but dangerous if you believe that it's "the truth". craig -- craig sanders <[EMAIL PROTECTED]> Fabricati Diem, PVNC. -- motto of the Ankh-Morpork City Watch
