Weblogs for rak
#4
Posted by rak on Wed 2 Feb 2011 at 18:56
For WineHQ use this(taken from winehq web):
wget -O - http://www.lamaresh.net/apt/key.gpg | apt-key add -
For Multimedia use this(taken from multimedia web):
Use the keyring download from the web page.
www.debian-multimedia.org
wget -O - http://www.lamaresh.net/apt/key.gpg | apt-key add -
For Multimedia use this(taken from multimedia web):
Use the keyring download from the web page.
www.debian-multimedia.org
[0 Comments
| Add Comment
|
]
]
#3
Posted by rak on Tue 4 Aug 2009 at 21:07
Ok, GLD is not exactly what you might call a spam filter but the fact is that it filters almost 75% of the spam before it gets to the spam filter, like DSPAM or the more classic spamassassin. It also filters virus in most cases again before they reach the server delivery agent or your Antivirus software, which saves lots of CPU, RAM and HHD.
GLD use 2 Tables in a MySQL Data Base Whitelist and Greylist, and is the last one that brings most of its blocking capabilities to GLD when you are running an open mail site like I do.
Grey list DB simply stores little information about incoming mails, most important origin IP Address, Sender and Receiver plus some other info so far of no concern, the fact is that in a very short time a busy site can generate half a million registries or more depending on the traffic the site handles.
With that in mind your MySQL tables grew quiet a bit in a year or so. And this some times leads to Table Crashes, that will manifest with users complaining about receiving more and more spam and your system going slower and slower both of which you don't wont to happen.
Regularly chopping the Table could reduce the problem but greylist would have to be retrained every time you do so, which is not necessary bad.
But in any case the first step is to recover the corrupted tables.
I found 2 options really simple, first and most user friendly phpmyadmin, using this web tool you select the Data Base and check the table to then select the Repair Table from the drop down menu.
Other option is logged into MySQL connected to the DB, execute the command:
GLD use 2 Tables in a MySQL Data Base Whitelist and Greylist, and is the last one that brings most of its blocking capabilities to GLD when you are running an open mail site like I do.
Grey list DB simply stores little information about incoming mails, most important origin IP Address, Sender and Receiver plus some other info so far of no concern, the fact is that in a very short time a busy site can generate half a million registries or more depending on the traffic the site handles.
With that in mind your MySQL tables grew quiet a bit in a year or so. And this some times leads to Table Crashes, that will manifest with users complaining about receiving more and more spam and your system going slower and slower both of which you don't wont to happen.
Regularly chopping the Table could reduce the problem but greylist would have to be retrained every time you do so, which is not necessary bad.
But in any case the first step is to recover the corrupted tables.
I found 2 options really simple, first and most user friendly phpmyadmin, using this web tool you select the Data Base and check the table to then select the Repair Table from the drop down menu.
Other option is logged into MySQL connected to the DB, execute the command:
repair table greylist
[0 Comments
| Add Comment
|
]
]
#2
Posted by rak on Tue 2 Jun 2009 at 06:16
Last Saturday there was a power lost in the city, may home systems all crashed but suffer almost no damage, I was happy that we finish a mayor upgrade in the electrical systems where I work, and that a larger UPS was install recently by a co-worker.
To my disappointment when I try to get my mail from home, the mail system was down.
>.<
To my disappointment when I try to get my mail from home, the mail system was down.
>.<
This entry has been truncated read the full entry.
[0 Comments
| Add Comment
|
]
]
#1
Posted by rak on Sat 4 Mar 2006 at 02:01
Recently I had to reinstall my home router, this was and old woody dist-upgrade to sarge with a 2.4.27 kernel. I've a privet network 192... for a couple of Windows and lynux boxs.
The machine crash and I only backup some config files and the data partition.
After installing a brand new sarge with update package and the precompile kernel 2.6.8. I began to notice that there where some troubles connecting to some www sites, from the windows boxs. Especially sites like www.mininova.org or www.astalavista.com couldnt be access at all, or the connection would take long and hang. Some times the page would half load, and making a reload of the page it could eventually load most of it.
At the same time if I try to load that same page with lynx from the router it would load fast and without any problem.
The iptables configuration is simple and work fine untill the upgrade:
bane:~# iptables -L -t nat
Chain PREROUTING (policy ACCEPT)
target prot opt source destination
DNAT tcp -- anywhere isp.provider.com tcp dpts:6881:6999 to:192.168.0.3:6881-6999
DNAT tcp -- anywhere isp.provider.com tcp dpts:10000:60000 to:192.168.0.3:10000-60000
DNAT udp -- anywhere isp.provider.com udp dpt:4672 to:192.168.0.3:4672
DNAT tcp -- anywhere isp.provider.com tcp dpt:4662 to:192.168.0.3:4662
Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
MASQUERADE all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
I google arround but found nothing about it, some references about net.ipv4, in kernel 2.6, but the config wos ok.
Did any one els here something similar to this problem or have any idea what could be wrong.
The machine crash and I only backup some config files and the data partition.
After installing a brand new sarge with update package and the precompile kernel 2.6.8. I began to notice that there where some troubles connecting to some www sites, from the windows boxs. Especially sites like www.mininova.org or www.astalavista.com couldnt be access at all, or the connection would take long and hang. Some times the page would half load, and making a reload of the page it could eventually load most of it.
At the same time if I try to load that same page with lynx from the router it would load fast and without any problem.
The iptables configuration is simple and work fine untill the upgrade:
bane:~# iptables -L -t nat
Chain PREROUTING (policy ACCEPT)
target prot opt source destination
DNAT tcp -- anywhere isp.provider.com tcp dpts:6881:6999 to:192.168.0.3:6881-6999
DNAT tcp -- anywhere isp.provider.com tcp dpts:10000:60000 to:192.168.0.3:10000-60000
DNAT udp -- anywhere isp.provider.com udp dpt:4672 to:192.168.0.3:4672
DNAT tcp -- anywhere isp.provider.com tcp dpt:4662 to:192.168.0.3:4662
Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
MASQUERADE all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
I google arround but found nothing about it, some references about net.ipv4, in kernel 2.6, but the config wos ok.
Did any one els here something similar to this problem or have any idea what could be wrong.