[AMaViS-user] amavis-stats-0.1.19 no data in domain.com
Hi Group, New bie here I have installed the amavis-stats-0.1.19 on my Linux server with Amavisd-new 2.3.3 . But I am not able to see the domain-wise graphs / stats. -- The /usr/local/var/lib/amavis-stats/amavis-stats.* are getting updated properly. /usr/local/var/lib/amavis-stats/domain.com/amavis-stats.count 0 bytes /usr/local/var/lib/amavis-stats/domain.com/amavis-stats.seen 0 bytes /usr/local/var/lib/amavis-stats/domain.com/amavis-stats.state 58 bytes [EMAIL PROTECTED] #cat domain.com/amavis-stats.state pos: 12378614 lastupdate: 1134474900 LC_TIME: C spamsess: - Please forgive if I have missed any earlier posts. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37alloc_id865op=click ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
Re: [AMaViS-user] Errors in the log
Gary, Keyname Type Cardinality Field PRIMARY PRIMARY 0id id UNIQUE0id users_idx_email INDEX None email PRIMARY and INDEX keys should not both be set for column `id` Using SERIAL PRIMARY KEY appears to have created a new problem. It looks like it creates two indexes. Reverting back to: INT UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY solves the newly introduced problem, at least I think it does, as now I get: Keyname Type Cardinality Field PRIMARY PRIMARY 0 id users_idx_email INDEXNoneemail Thanks for pointing it out. You are right. The reason is probably because SERIAL stands for BIGINT UNSIGNED NOT NULL AUTO_INCREMENT UNIQUE, the culprit being the UNIQUE, which creates an index on its own, and since the 'id' is already a primary key with an implicit index, the 'id' field now has two indices. It is a waste of resources, although is not harmful. I modified the README.sql to reflect this: http://www.ijs.si/software/amavisd/README.sql.txt Mark --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
Re: [AMaViS-user] Errors in the log
Heute (13.12.2005/15:50 Uhr) schrieb Mark Martinec ([EMAIL PROTECTED]), Gary, Keyname Type Cardinality Field PRIMARY PRIMARY 0id id UNIQUE0id users_idx_email INDEX None email PRIMARY and INDEX keys should not both be set for column `id` Using SERIAL PRIMARY KEY appears to have created a new problem. It looks like it creates two indexes. Reverting back to: INT UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY solves the newly introduced problem, at least I think it does, as now I get: Keyname Type Cardinality Field PRIMARY PRIMARY 0 id users_idx_email INDEXNoneemail Thanks for pointing it out. You are right. The reason is probably because SERIAL stands for BIGINT UNSIGNED NOT NULL AUTO_INCREMENT UNIQUE, However, it stands correctly in the old README.sql --snip -- MySQL notes: -- the attribute SERIAL was introduced with MySQL 4.1.0; -- with earlier versions one can use INT UNSIGNED NOT NULL AUTO_INCREMENT --snap the culprit being the UNIQUE, which creates an index on its own, and since the 'id' is already a primary key with an implicit index, the 'id' field now has two indices. It is a waste of resources, although is not harmful. I modified the README.sql to reflect this: http://www.ijs.si/software/amavisd/README.sql.txt Mark -- Viele Grüße, Kind regards, Jim Knuth [EMAIL PROTECTED] ICQ #277289867 - VoIP: +49 (0) 322 212 044 67 Key ID: 0x1F78066F -- Zufalls-Zitat -- Ein Vorteil von Gruppensex ist, dass man ein Nickerchen machen kann wenn man will (allen Woody) -- Der Text hat nichts mit dem Empfänger der Mail zu tun -- Virus free. Checked by NOD32 Version 1.1320 Build 6438 12.12.2005 --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37alloc_id865op=click ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
[AMaViS-user] TIMING step update_cache randomly becomes VERY slow.
Hello, I've got several postfix/amavis filtering types of installs setup. On my most recent one, I've hit a snag that I haven't yet been able to figure out. This particular server handles about 70k messages per day, which is generally fine. Anyhow, things will churn along fine for days and then all of a sudden I'll get a backlog in my active postfix queue (meaning things are still churning, but it can't process messages as quickly as it's getting them in). Looking at the TIMING log entries that amavisd-new creates, I get things like this: update_cache: 17135 (67%) So, 17 seconds for the update_cache step. Can anyone elaborate on what exactly that is? /var/amavis is currently on a ramdisk, (freebsd 6.0) so it shouldn't be disk IO related. Also, is this related to the $enable_global_cache setting? If so, what exactly does this cache do? Thanks, --falz --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37alloc_id865op=click ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
Re: [AMaViS-user] TIMING step update_cache randomly becomes VERY slow.
falz, I've got several postfix/amavis filtering types of installs setup. On my most recent one, I've hit a snag that I haven't yet been able to figure out. This particular server handles about 70k messages per day, which is generally fine. Anyhow, things will churn along fine for days and then all of a sudden I'll get a backlog in my active postfix queue (meaning things are still churning, but it can't process messages as quickly as it's getting them in). Looking at the TIMING log entries that amavisd-new creates, I get things like this: update_cache: 17135 (67%) Looks like a problem with berkeley db (libdb). What version of libdb are you using - it is logged during startup like: amavis[xxx]: Creating db in /var/amavis/db/; BerkeleyDB 0.27, libdb 4.3 The last time this was reported it turned out it was with an old version of libdb. If this is also true in your case, try with a more recent version form ports, e.g. databases/db42 or databases/db43 or databases/db44. See also that the databases/p5-BerkeleyDB is reasonably recent. So, 17 seconds for the update_cache step. Can anyone elaborate on what exactly that is? It is not normal. Possibly a contention, but more likely a bug in bdb. During update_cache step a MD5 digest of a message body, along with results of virus and spam checks, are written to a database. /var/amavis is currently on a ramdisk, (freebsd 6.0) so it shouldn't be disk IO related. Also, is this related to the $enable_global_cache setting? If so, what exactly does this cache do? Yes, it is related. Setting $enable_global_cache to 0 will disable bdb-based cache, which can be used as a stop-gap measure until the problem is fixed. Using a cache of recent mail checks can quicken checking messages that have the same content and are sent as separate messages, e.g. some types of spam or viruses, and some types of mailing list traffic. Turning it off looses some benefit, but is not too bad. Mark --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
Re: [AMaViS-user] TIMING step update_cache randomly becomes VERY slow.
Mark Martinec wrote: using - it is logged during startup like: amavis[xxx]: Creating db in /var/amavis/db/; BerkeleyDB 0.27, libdb 4.3 The last time this was reported it turned out it was with an old version of libdb. If this is also true in your case, try with a more recent version form ports, e.g. databases/db42 or databases/db43 or databases/db44. See also that the databases/p5-BerkeleyDB is reasonably recent. On a somewhat related note - what is the proper db to use for the lastest Amavis with FreeBSD? -- Best regards, Chris There is no such thing as a dirty capitalist, only a capitalist. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
Re: [AMaViS-user] TIMING step update_cache randomly becomes VERY slow.
Chris, Is there some sort of compile time arg to use? Just I removed my older db port, and installed 4.3 - recompliled Postfix to use it, then rebuilt Amavis. Seems Ami still calls in db3 You may need to reinstall Perl module BerkeleyDB after upgrading libdb. No changes and no reinstall on amavisd-new are needed. On FreeBSD one puts a line like: WITH_BDB_VER=43 into /etc/make.conf, which influences later ports installs. I don't know what is needed on Linux for a clean upgrade of libdb. Perhaps you have multiple versions present on the system, causing confusion. Mark --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
Re: [AMaViS-user] TIMING step update_cache randomly becomes VERY slow.
Mark Martinec wrote: Chris, Is there some sort of compile time arg to use? Just I removed my older db port, and installed 4.3 - recompliled Postfix to use it, then rebuilt Amavis. Seems Ami still calls in db3 You may need to reinstall Perl module BerkeleyDB after upgrading libdb. No changes and no reinstall on amavisd-new are needed. On FreeBSD one puts a line like: WITH_BDB_VER=43 into /etc/make.conf, which influences later ports installs. I don't know what is needed on Linux for a clean upgrade of libdb. Perhaps you have multiple versions present on the system, causing confusion. Mark This worked well. I'm now gliding along on 4.3 - this also may explain why Amavis crashed on Sunday, possibly do to the fact that Amivis was using the default type that installs with BerkeleyDB (3.3 I think?) -- Best regards, Chris The label new and/or improved means the price went up. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
[AMaViS-user] slow processing after upgrade to 2.3.3
On my FreeBSD 5.4 server, I have upgraded to v2.3.3 from 2.2.x and the CPU now has no idle time with less than 400 messages in the queue. Messages are taking several minutes to process. I dug around and realize that my amavisd.conf file is drastically different than the new default file installed by the port package system. The new default does not even have ClamAV setup for uncommenting like the old. Is this contributing to my problem? And where can I find a doc to set this up properly with Postfix, SpamAssassin and ClamAV? -- Robert --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
Re: [AMaViS-user] amavisd-release troubles
Replying to my own post. I still do not have the inet method working. It still gives the errors below. I got amavisd-release to work by switching to the unixsocket method. Still interested in the inet method. john john wrote: I'm running amavisd-new 2.3.3 on FreeBSD 5.4 I'm trying to release a quarantined file. I'm trying to use amavisd-release. I added this entry to not require a auth_id. $auth_required_release = 0; I'm using INET as the connection method. I'm entering the file name exactly as in the log message. Dec 13 11:25:23 mg-p1 amavis[45356]: (45356-07) Blocked SPAM, [24.248.74.254] [24.248.74.254] [EMAIL PROTECTED] - [EMAIL PROTECTED], quarantine: spam-1pID0wOJvRSl.gz, Message-ID: [EMAIL PROTECTED], mail_id: 1pID0wOJvRSl, Hits: 20.596, 11736 ms Commands I've used: amavisd-release spam-1pID0wOJvRSl.gz amavisd-release /var/virusmails/spam-1pID0wOJvRSl.gz amavisd-release - spam-1pID0wOJvRSl.gz I get the following in my log file. Dec 13 20:32:10 mg-p1 amavis[48786]: (48786-01) SMTP: 500 5.5.2 Error: bad syntax; PENALIZE: request=release\r\n Dec 13 20:32:15 mg-p1 amavis[48786]: (48786-01) SMTP: 500 5.5.2 Error: bad syntax; PENALIZE: quar_type=Z\r\n Dec 13 20:32:20 mg-p1 amavis[48786]: (48786-01) SMTP: 500 5.5.2 Error: bad syntax; PENALIZE: mail_id=1pID0wOJvRSl\r\n Dec 13 20:32:25 mg-p1 amavis[48786]: (48786-01) SMTP: 500 5.5.2 Error: bad syntax; PENALIZE: mail_file=spam-1pID0wOJvRSl.gz\r\n Dec 13 20:32:30 mg-p1 amavis[48786]: (48786-01) SMTP: 500 5.5.2 Error: bad syntax; PENALIZE: \r\n Any help with this? The release script is v1.1 John --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/ --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
[AMaViS-user] deliver tagged spam locally for one gateway domain?
Greetings: I have a postfix-amavisd-spamassassin box setup and running OK so far. I have domains that get mail locally via virtual_users, and the box is a gateway for a couple domains. Total of less than 100 users. My postfix setup is mostly like the configuration at the end of the amavisd's postfix readme. I will be happy to post if it is of any help. I need to be able to segregate the tagged spam from at least one of my gateway domains from the rest of the spam. Ideally, I need to deliver the tagged spam to a local mailbox for the gateway domain, and pass the non-tagged spam on to their exchange server. as in: localdeliverdomainOne - localspam1mailbox localdeliverdomainTwo - localspam2mailbox gatewaydomainOneSpam - localspam3mailbox gatewaydomainOneHam - exchange server Is this possible? I figured I could use procmail or similar to divy out the local spam as desired, but I don't know how to intercept the spam destined for the exchange box (via its corresponding postfix transport). I saw the recent thread on not scanning particular users and hoped something along those lines might help, but I don't see how to do it if it's possible. Thanks very much for the time to help, Scott --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
Re: [AMaViS-user] deliver tagged spam locally for one gateway domain?
techlist06 wrote:
Greetings:
I have a postfix-amavisd-spamassassin box setup and running OK so far. I
have domains that get mail locally via virtual_users, and the box is a
gateway for a couple domains. Total of less than 100 users.
I need to be able to segregate the tagged spam from at least one of my
gateway domains from the rest of the spam. Ideally, I need to deliver the
tagged spam to a local mailbox for the gateway domain, and pass the
non-tagged spam on to their exchange server.
The way you have worded this last sentence makes it a little
confusing. I'm not sure what you mean by 'non-tagged spam'.
as in:
localdeliverdomainOne - localspam1mailbox
localdeliverdomainTwo - localspam2mailbox
gatewaydomainOneSpam - localspam3mailbox
gatewaydomainOneHam - exchange server
Is this possible? I figured I could use procmail or similar to divy out the
local spam as desired, but I don't know how to intercept the spam destined
for the exchange box (via its corresponding postfix transport).
If I understand you correctly, you want to quarantine spam to three different
mailboxes, based on the recipient domain. You can use
@spam_quarantine_to_maps to accomplish this. This assumes you are
using the default 'local' quarantine method:
$spam_quarantine_to = 'spam-quarantine'; # default local quarantine
@spam_quarantine_to_maps = (
{ '.example.com' = '[EMAIL PROTECTED]',
'.example2.com' = '[EMAIL PROTECTED]',
'.example3.com' = '[EMAIL PROTECTED]',
},
$spam_quarantine_to, # catchall
);
Spam that scores at or above $sa_kill_level_deflt will be sent to these
mailboxes.
Yes procmail could be used on the local domains. Also take a look at:
http://www.ijs.si/software/amavisd/amavisd-new-docs.html#addrext
discussed in this thread:
http://marc.theaimsgroup.com/?l=amavis-userm=11320138374w=2
The thread does not exactly pertain to what you want, but does
illustrate how 'plus addressing' might be used.
Another recent thread also discussed what I believe is the same issue:
http://marc.theaimsgroup.com/?l=amavis-userm=113242039910897w=2
Gary V
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
