Re: requires explicit package name
Hi, Am Dienstag, den 09.02.2021, 19:11 +0100 schrieb Marcus Schopen: > Hi, > > on some older systems I see the following sa-update error since today > > > Possible unintended interpolation of @g in string at > /tmp/.spamassassin7185HJuhWPtmp/70_HS_header.cf, rule HS_HEADER_1506, > line 1. > Possible unintended interpolation of @mail in string at > /tmp/.spamassassin7185HJuhWPtmp/70_HS_header.cf, rule HS_HEADER_1509, > line 1. > Possible unintended interpolation of @leadstips in string at > /tmp/.spamassassin7185HJuhWPtmp/70_HS_header.cf, rule HS_HEADER_1500, > line 1. > Possible unintended interpolation of @amazonshoppings in string at > /tmp/.spamassassin7185HJuhWPtmp/70_HS_header.cf, rule HS_HEADER_1511, > line 1. > rules: failed to compile > Mail::SpamAssassin::Plugin::Check::_head_tests_0_6, skipping: > (Global symbol "@g" requires explicit package name at > /tmp/.spamassassin7185HJuhWPtmp/70_HS_header.cf, rule HS_HEADER_1506, > line 1. > Global symbol "@mail" requires explicit package name at > /tmp/.spamassassin7185HJuhWPtmp/70_HS_header.cf, rule HS_HEADER_1509, > line 1. > Global symbol "@leadstips" requires explicit package name at > /tmp/.spamassassin7185HJuhWPtmp/70_HS_header.cf, rule HS_HEADER_1500, > line 1. > Global symbol "@amazonshoppings" requires explicit package name at > /tmp/.spamassassin7185HJuhWPtmp/70_HS_header.cf, rule HS_HEADER_1511, > line 1.) > channel: lint check of update failed, channel failed > sa-update failed for unknown reasons > Sorry, these rules do not come from spamassassin.org. Ciao! Marcus
requires explicit package name
Hi, on some older systems I see the following sa-update error since today Possible unintended interpolation of @g in string at /tmp/.spamassassin7185HJuhWPtmp/70_HS_header.cf, rule HS_HEADER_1506, line 1. Possible unintended interpolation of @mail in string at /tmp/.spamassassin7185HJuhWPtmp/70_HS_header.cf, rule HS_HEADER_1509, line 1. Possible unintended interpolation of @leadstips in string at /tmp/.spamassassin7185HJuhWPtmp/70_HS_header.cf, rule HS_HEADER_1500, line 1. Possible unintended interpolation of @amazonshoppings in string at /tmp/.spamassassin7185HJuhWPtmp/70_HS_header.cf, rule HS_HEADER_1511, line 1. rules: failed to compile Mail::SpamAssassin::Plugin::Check::_head_tests_0_6, skipping: (Global symbol "@g" requires explicit package name at /tmp/.spamassassin7185HJuhWPtmp/70_HS_header.cf, rule HS_HEADER_1506, line 1. Global symbol "@mail" requires explicit package name at /tmp/.spamassassin7185HJuhWPtmp/70_HS_header.cf, rule HS_HEADER_1509, line 1. Global symbol "@leadstips" requires explicit package name at /tmp/.spamassassin7185HJuhWPtmp/70_HS_header.cf, rule HS_HEADER_1500, line 1. Global symbol "@amazonshoppings" requires explicit package name at /tmp/.spamassassin7185HJuhWPtmp/70_HS_header.cf, rule HS_HEADER_1511, line 1.) channel: lint check of update failed, channel failed sa-update failed for unknown reasons Ciao Marcus
Re: sa-update for versions 3.4.2 and older fail lint because of description on non-existent rule was Re: update fail
Am Donnerstag, den 16.07.2020, 17:43 -0400 schrieb Kevin A. McGrail: > Agreed. 1879851 is after I submitted the fix but doesn;t include the > fix. I will have to check again after the next rule publishing. > Sorry for the false alarm. Feedback: sa-update without errors now. Thanks a lot! Cheers m.
Re: sa-update for versions 3.4.2 and older fail lint because of description on non-existent rule was Re: update fail
Am Mittwoch, den 15.07.2020, 08:11 -0400 schrieb Kevin A. McGrail: > Just an update that this is fixed: > > https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7840 > > Should be a rule update published in the next 48 hours with the fix. > Feedback welcome because we are making fixes for older versions so > it's harder to gauge if it's fixed without user feedback. Which version should fix it? Same error with version 1879851. Ciao!
Re: update fail
Am Mittwoch, den 15.07.2020, 07:08 -0400 schrieb Kevin A. McGrail: > If it is still not working, what error are you getting, please? On 7/15/2020 6:59 AM, Marcus Schopen wrote: > > > Can you try now and lmk, please? I think the current ruleset is > > > 1879881 > > > has it fixed and is published. - config: warning: description exists for non-existent rule USER_IN_WELCOMELIST_TO Jul 15 13:10:33.621 [2458] dbg: diag: updates complete, exiting with code 4 Update failed, exiting with code 4 sa-update failed for unknown reasons - I will send you the complete output. Ciao!
Re: update fail
Am Mittwoch, den 15.07.2020, 12:59 +0200 schrieb Marcus Schopen: > The version for Ubuntu 16.04 LTS is Spamassassin 2.4.2. Sorry, Spamassassin 3.4.2-0ubuntu0.16.04.4 of course.
Re: update fail
Am Mittwoch, den 15.07.2020, 06:26 -0400 schrieb Kevin A. McGrail: > Yeah, that's just a lint warning. A fix was committed but I had to > work > out a merge complaint on the rule system publishing this morning. I > believe a Yes, but it prevents the signatures from being updated! > Can you try now and lmk, please? I think the current ruleset is > 1879881 > has it fixed and is published. > > However SA 3.4.3+ will still install updates with just a warning. > Can > you upgrade your SA or are you stuck at 3.4.2? The version for Ubuntu 16.04 LTS is Spamassassin 2.4.2. I don't want to update the whole server or build a backport on the fly. In this respect it would be good if the updates are also suitable for a still supported Ubuntu LTS. 1879817 is the current version and still fails. Ciao Marcus
Re: update fail
Am Dienstag, den 14.07.2020, 16:43 +0200 schrieb Benny Pedersen: > A. Schulze skrev den 2020-07-14 13:19: > > > I tried to place "meta USER_IN_ALLOWLIST_TO (USER_IN_WHITELIST_TO)" > > in > > $LOCAL_RULES_DIR/local.cf > > But that failed, too. > > sorry then, my rule ensure that USER_IN_ALLOWLIST_TO exists if > USER_IN_WHITELIST_TO exists aswell > > if none of them exists you still have problems where rules depend on > one > of them > > i use sa 3.4.4 where the problem is none existsing with sa-update > > > I had to place the line in $LOCAL_RULES_DIR/local.pre. To me it > > looks > > like sa-update read only files named $LOCAL_RULES_DIR/*.pre > > want to provide sa-update -D on this ? > > if you miss plugins, it could fail on lint Problem now "USER_IN_WELCOMELIST_TO" with spamassassin 3.4.2- 0ubuntu0.16.04.4 on Ubuntu 16.04 LTS: --- /etc/cron.hourly/spamassassin: config: warning: description exists for non-existent rule USER_IN_WELCOMELIST_TO channel: lint check of update failed, channel failed sa-update failed for unknown reasons --- So all Ubuntu 16.04 LTS and my be older Debian installations are affected. Ciao!
update fail
Hi, when updating by cron from channel updates.spamassassin.org I get the following error on multiple servers: --- config: warning: description exists for non-existent rule USER_IN_ALLOWLIST_TO channel: lint check of update failed, channel failed sa-update failed for unknown reasons --- The error occurred for the first time within the last hour. I'm not quite sure, but according to debug "Mail::SpamAssassin::Plugin::FreeMail" could be the problem. -- Jul 11 23:37:58.443 [17022] dbg: plugin: Mail::SpamAssassin::Plugin::FreeMail=HASH(0x2cab3c0) implements 'parse_config', priority 0 config: warning: description exists for non-existent rule USER_IN_ALLOWLIST_TO -- Ciao! Marcus
sa-update is broken on updates.spamassassin.org channel [was: Re: config: warning: description exists for non-existent rule EXCUSE_24]
Am Donnerstag, den 20.12.2018, 12:35 +0100 schrieb Marcus Schopen: > Hi, > > I get a warning, when updating the channel: > > -- > config: warning: description exists for non-existent rule EXCUSE_24 > > channel: lint check of update failed, channel failed > sa-update failed for unknown reasons > -- seems not to be a problem of the EXCUSE_24 rule, but a general problem with sa-update, as other users do have the same problem since today.
config: warning: description exists for non-existent rule EXCUSE_24
Hi, I get a warning, when updating the channel: -- config: warning: description exists for non-existent rule EXCUSE_24 channel: lint check of update failed, channel failed sa-update failed for unknown reasons -- Cheers Marcus
Re: trusted_networks and internal_networks confusion
Hi, Am Samstag, den 17.12.2016, 13:17 + schrieb RW: > On Fri, 16 Dec 2016 22:41:49 +0100 > Marcus Schopen wrote: > > > > The problem is, that smtp-out.myoffice.de is also a submission server > > for dialup clients. Headers from to to down: > > > > Received: from smtp-out.myoffice.de by MY_SERVER_IP > > Received: from dialup-client-IP by smtp-out.myoffice.de > > SpamAssassin usually deals with this problem by looking for > authentication in the header, but that's not recorded here. There is no auth hint in the header when using the submission server. Received: from [192.168.178.25] ([my dynamic IP]) by smtp-out.myoffice.de (Oracle Communications Messaging Server 7.0.5.37.0 64bit (built Jan 25 2016)) with ESMTPPA id <0OIA00E6KOQ65A80@smtp-out,myoffice> for i...@test.de; Fri, 16 Dec 2016 21:25:20 +0100 (CET) I think they manipulate the header or have a proxy, because the smtp host in my mailclient is smtp.myoffice.de (with a another IP) and not smtp-out.myoffice.de. But smtp-out.myoffice.de comes up as the first connecting host for the mail client. > I think your best option is to leave it in internal_networks and write > a custom rule to take some points off when it's submission. Good idea, something like if smtp-out.myoffice.de is the first trusted (header from down to top) 10 points off. How can I do that or what would you think? Ciao!
trusted_networks and internal_networks confusion
Hi, I have configuration problems with trusted_networks and internal_networks when forwarding my office mails to my private server, because one server in the trust chain is also a submission server. My current setup is simple (SA runs on my private server = MY_SERVER_IP): trusted_networks MY_SERVER_IP Forwarded mails via the office mail servers go this way, headers from to to down: Received: from smtp-out.myoffice.de by MY_SERVER_IP Received: from mx.myoffice.de by smtp-out.myoffice.de Received: from spamhost.de by mx.myoffice.de To get a trusty path I put mx.myoffice.de and smtp-out.myoffice.de to trusted_networks on my server: trusted_networks MY_SERVER_IP trusted_networks smtp-out.myoffice.de trusted_networks mx.myoffice.de The problem is, that smtp-out.myoffice.de is also a submission server for dialup clients. Headers from to to down: Received: from smtp-out.myoffice.de by MY_SERVER_IP Received: from dialup-client-IP by smtp-out.myoffice.de So if I set smtp-out.myoffice.de to trusted_networks without having internal_networks defined, internal_networks is set to trusted_networks which means dialup client IPs, that connect to smtp-out.myoffice.de will be checked against RBL/DUL lists by my SA and get blocked. I tried to remove the submission server from internal_networks to set trusted_networks and internal_networks, but in that case RBL checks seem not to run on the originate spamhost IP in case for forwarding: trusted_networks MY_SERVER_IP trusted_networks smtp-out.myoffice.de trusted_networks mx.myoffice.de internal_networks MY_SERVER_IP internal_networks mx.myoffice.de Any ideas? Ciao Marcus
Re: how to parse back through forwarding headers to find the true source IP
Hi, Am Donnerstag, den 08.12.2016, 16:25 + schrieb RW: > On Thu, 08 Dec 2016 16:54:26 +0100 > Marcus Schopen wrote: > > > Hi, > > > > some of my users forward external mails to my host. In some cases > > those forwarding hosts don't filter spam. How do I parse back through > > forwarding headers to find the true source IP and run dnsrbl checks on > > that IP. I don't want to reject those mails in case of spam, so that > > the forwarding host will become a backscatter, but just marking them. > > I tried to set the forwarding host IPs to trusted_networks, which > > helps with wrong dnswl.org checks, but RBL checks are disabled then. > > Any ideas how to handle that? > > You need to put them in internal networks for spamassassin to do > last-external checks. Thanks to all for helping! The forwarded mails go this way: Scammer -> 62.146.106.13[2-3] -> 62.146.106.2[1-6] -> MY_IP My current setup looks like this now: --- trusted_networks MY_IP # udag.de forwarding: forwarding servers connecting MY_IP trusted_networks 62.146.106.21 trusted_networks 62.146.106.22 trusted_networks 62.146.106.23 trusted_networks 62.146.106.24 trusted_networks 62.146.106.25 trusted_networks 62.146.106.26 # udag.de forwarding: original receiving servers trusted_networks 62.146.106.132 trusted_networks 62.146.106.133 --- I didn't set any internal_networks, because "If trusted_networks is set and internal_networks is not, the value of trusted_networks will be used for this parameter."[1], so in my understanding my internal_networks are equal to trusted_networks. After adding above rules to my SA config I checked some incoming mails and filtering seems to be correct. The forwarding servers 62.146.106.2[1-6] are not listed e.g. on SPAMCOP, INPS.de etc. so it must be the scammer's IP and DNSWL check doesn't come up with a RCVD_IN_DNSWL_LOW hit, which one gets if 62.146.106.2[1-6] hosts are checked directly: Dec 9 18:55:09 server mimedefang.pl[19467]: uB9Ht5SU012194: MDLOG,uB9Ht5SU012194,spam,22.67 BAYES_50 DIGEST_MULTIPLE DKIM_SIGNED FROM_EXCESS_BASE64 HTML_IMAGE_ONLY_24 HTML_MESSAGE MIME_HTML_ONLY PYZOR_CHECK RAZOR2_CF_RANGE_51_100 RAZOR2_CF_RANGE_E8_51_100 RAZOR2_CHECK RCVD_IN_BL_SPAMCOP_NET RCVD_IN_BRBL_LASTEXT RCVD_IN_DNSBL_INPS_DE RCVD_IN_SBL RCVD_IN_SBL_CSS RP_MATCHES_RCVD T_DKIM_INVALID URIBL_ABUSE_SURBL URIBL_BLACK URIBL_DBL_SPAM URIBL_SBL URIBL_SBL_A,62.146.106.23,,<mar...@mydomain.de>,Subject ... I checked another user, who's forwarding mails from ISP Strato to my host and there is a strange received header set by forwarder side. In this case mails go this way: Scammer -> 81.169.145.98 -> 81.169.146.14[4-9] -> MY_IP But receiving IP smtp.rzone.de[81.169.145.98] never comes up in the Received header. The header looks like this: - Received: from srv544.mailer-service.de ([62.138.228.44]) by smtp.rzone.de (RZmta 39.10 OK) with ESMTP id A02f69sB9H4Aw9o for <mar...@mydomain.de>; Fri, 9 Dec 2016 18:04:10 +0100 (CET) - How can SA parse for back to the original receiving host IP smtp.rzone.de[81.169.145.98], if they just come up with "smtp.rzone.de (RZmta 39.10 OK)". Would that nevertheless work or is it in this case only possible to put the outgoing servers 81.169.146.14[4-9] to my trusted_networks and does that make sense at all then? Ciao Marcus [1] https://spamassassin.apache.org/full/3.4.x/doc/Mail_SpamAssassin_Conf.html -- , [ Marcus Schopen ] | (0> | //\ | V_/_ D-33602 Bielefeld | `
how to parse back through forwarding headers to find the true source IP
Hi, some of my users forward external mails to my host. In some cases those forwarding hosts don't filter spam. How do I parse back through forwarding headers to find the true source IP and run dnsrbl checks on that IP. I don't want to reject those mails in case of spam, so that the forwarding host will become a backscatter, but just marking them. I tried to set the forwarding host IPs to trusted_networks, which helps with wrong dnswl.org checks, but RBL checks are disabled then. Any ideas how to handle that? Ciao Marcus
Re: return value of bl.spameatingmonkey.net
Hi, Am Dienstag, den 29.11.2016, 07:07 +0100 schrieb Axb: > On 11/29/2016 12:14 AM, Marcus Schopen wrote: > > Hi, > > > > what's the return value if an IP is listed on bl.spameatingmonkey.net? > > Seems to be 127.0.0.2. When is the return value 127.0.0.3? Can't find > > anything on their website. > > what about > http://spameatingmonkey.com/usage.html I've seen that page, but what does a return value of 127.0.0.3 mean? ~ $ host 2.0.0.127.bl.spameatingmonkey.net 2.0.0.127.bl.spameatingmonkey.net has address 127.0.0.3 2.0.0.127.bl.spameatingmonkey.net has address 127.0.0.2 Ciao! Marcus
return value of bl.spameatingmonkey.net
Hi, what's the return value if an IP is listed on bl.spameatingmonkey.net? Seems to be 127.0.0.2. When is the return value 127.0.0.3? Can't find anything on their website. Ciao Marcus -- "It's hard to be mad at someone who misses you while you're asleep." -Calvin
Re: spamassassin 3.4.1 on ubuntu precise systemd problems
Hi Matus, Am Sonntag, den 25.09.2016, 17:59 +0200 schrieb Matus UHLAR - fantomas: > On 25.09.16 14:18, Marcus Schopen wrote: > >I'm trying to build a spamassassin 3.4.1 backport on ubuntu precise, but > >have problems to handle systemd dependencies. Is it a good idea just to > >remove "dh-systemd" from control Build-Depends and remove > >"dh_systemd_enable --no-enable" from rules? Build is running through. > > you really should post this to ubuntu mailing list. This has nothing to do > with SA, it's purely issue of building on ubuntu. I know it's a little off topic, but I thought here is someone who's running that backport. Ciao! Marcus
spamassassin 3.4.1 on ubuntu precise systemd problems
Hi, I'm trying to build a spamassassin 3.4.1 backport on ubuntu precise, but have problems to handle systemd dependencies. Is it a good idea just to remove "dh-systemd" from control Build-Depends and remove "dh_systemd_enable --no-enable" from rules? Build is running through. Ciao Marcus
Re: Digest::SHA1 module is required by the Razor2 plugin
Hi, Am Montag, den 19.09.2016, 13:35 +0100 schrieb RW: > > > It's not a spamassassin problem, right. Question is, can I install a > > > SHA1 package without harming perl at other places? > > > > It should do any harm. > > That should have been: > > It shouldn't do any harm. Thanks. Build a backport and razor is running fine now. Is anyone using razor/pyzor/DCC and can give some efficiency report? Do they still make sense beside DNSBL and URIBL? Ciao Marcus
Re: Digest::SHA1 module is required by the Razor2 plugin
Am Montag, den 19.09.2016, 11:37 +0200 schrieb li...@rhsoft.net: > Am 19.09.2016 um 11:10 schrieb Marcus Schopen: > > I'd like to use razor on my private mailbox, but it seems to depend on > > Digest::SHA1, which is not part of Ubuntu 12.04 LTS or 14.04 TLS: > > > > The Digest::SHA1 module is required by the Razor2 plugin > > > > I found this bug report > > > > https://bugs.launchpad.net/ubuntu/+source/libdigest-sha1-perl/+bug/993648 > > > > where a package for precise is published (comment #9). > > > > What to do? Building an own package from > > just file a bugreport against Ubuntu spamassassin package and refer to > the above bugreport - someone needs to fix that mess in Ubuntu and i can > assure you Debian and Redhat systems don't have this problem > > in other words: this is a distribution mess and not SA related It's not a spamassassin problem, right. Question is, can I install a SHA1 package without harming perl at other places? Ciao Marcus
Digest::SHA1 module is required by the Razor2 plugin
Hi, I'd like to use razor on my private mailbox, but it seems to depend on Digest::SHA1, which is not part of Ubuntu 12.04 LTS or 14.04 TLS: The Digest::SHA1 module is required by the Razor2 plugin I found this bug report https://bugs.launchpad.net/ubuntu/+source/libdigest-sha1-perl/+bug/993648 where a package for precise is published (comment #9). What to do? Building an own package from https://launchpad.net/ubuntu/+source/libdigest-sha1-perl/2.13-2build2/ for 12.04 und 14.04 or would an install have side effects on perl? Btw: what's the efficiency of razor? Does it help? I used it years ago, but didn't follow it anymore. System: perl 5.14.2 (Ubuntu 12.04) 5.18.2 (Ubuntu 14.04) spamassassin 3.4.1-3 (backported) Ciao Marcus
Re: cron sa-update with multipe channels
Am Samstag, den 17.09.2016, 11:46 +0200 schrieb Axb: > On 09/17/2016 11:35 AM, Marcus Schopen wrote: > > Am Samstag, den 17.09.2016, 10:36 +0200 schrieb Axb: > >> On 09/17/2016 10:17 AM, Marcus Schopen wrote: > >>> Hi, > >>> > >>> is there a concept for updating from multiple channels > >>> in /etc/cron.daily/spamassassin so that sa-compile is called only if one > >>> channel got updates? > >> > >> > >> /etc/cron.daily/spamassassin is not part of the SA project. It's usually > >> something added by a distro maintainer > >> > >> just add conjobs for the "other" channels as per sa-update docs > >> > >> (http://spamassassin.apache.org/full/3.4.x/doc/sa-update.txt) > > > > Ah, understand. Thanks. > > > > If I use --channelfile to list all update servers in one file, I have a > > problem to mix servers with gpgkey and without. Do I need to use > > --channel for each server instead of --channelfile to be able to specify > > --gpgkey or --nogpg or how can I mix that? > > > > I've never used --channelfile so I can't tell. > > as different channels may require different update frequency, etc, I've > always chosen to us one cronjob per channel and/or server. > Makes it easier to track and debug. > > Maybe someone else can answer your question. Thanks! But then in sa-update-hock.d dir in my case mimedefang would be reloaded after each channel update instead of one recompile and one reload after all updates finished. Ciao!
Re: cron sa-update with multipe channels
Am Samstag, den 17.09.2016, 10:36 +0200 schrieb Axb: > On 09/17/2016 10:17 AM, Marcus Schopen wrote: > > Hi, > > > > is there a concept for updating from multiple channels > > in /etc/cron.daily/spamassassin so that sa-compile is called only if one > > channel got updates? > > > /etc/cron.daily/spamassassin is not part of the SA project. It's usually > something added by a distro maintainer > > just add conjobs for the "other" channels as per sa-update docs > > (http://spamassassin.apache.org/full/3.4.x/doc/sa-update.txt) Ah, understand. Thanks. If I use --channelfile to list all update servers in one file, I have a problem to mix servers with gpgkey and without. Do I need to use --channel for each server instead of --channelfile to be able to specify --gpgkey or --nogpg or how can I mix that? Ciao Marcus
cron sa-update with multipe channels
Hi, is there a concept for updating from multiple channels in /etc/cron.daily/spamassassin so that sa-compile is called only if one channel got updates? Ciao Marcus
Re: backport 3.4.0 Ubuntu 12.04 TLS
Hi Robert, Am Freitag, den 16.09.2016, 13:02 +0200 schrieb Robert Schetterer: > Am 16.09.2016 um 12:48 schrieb Marcus Schopen: > > Hi Patrick, > > > > Am Donnerstag, den 15.09.2016, 22:02 -0400 schrieb Patrick Domack: > >> Sounds like a lot of work for an old spamassassin version. > >> > >> https://launchpad.net/%7Epatrickdk/+archive/ubuntu/production/+sourcepub/5219815/+listing-archive-extra > > > > H ... do you think better backporting 3.4.1 from Xenial? Does it run > > on Ubuntu 12.04 LTS and 14.04 LTS? > > > > Ciao! > > > > > > tested and running with recompile debian way 3.4.1 from wily 15.04 does > run in 14.04 I just backported version 3.4.1-3 from Xenial, seems to be fine. Did you change any code or did you just backported it with dpkg-buildpackage? Ciao Marcus
Re: backport 3.4.0 Ubuntu 12.04 TLS
Hi Patrick, Am Donnerstag, den 15.09.2016, 22:02 -0400 schrieb Patrick Domack: > Sounds like a lot of work for an old spamassassin version. > > https://launchpad.net/%7Epatrickdk/+archive/ubuntu/production/+sourcepub/5219815/+listing-archive-extra H ... do you think better backporting 3.4.1 from Xenial? Does it run on Ubuntu 12.04 LTS and 14.04 LTS? Ciao!
backport 3.4.0 Ubuntu 12.04 TLS
Hi, I've backported 3.4.0 from Ubuntu 14.04 TLS for Ubuntu 12.04 LTS (perl 5.14.2), which comes with very old version 3.3.2 (can't upgrade the complete host right now). Before installing it: is there anything to be aware of, beside better wiping bayes database and starting fresh? [1] Ciao Marcus [1] http://svn.apache.org/repos/asf/spamassassin/branches/3.4/build/announcements/3.4.0.txt
sa-learn strip last Received: header for own MDA
Hi, still playing with sa-learn. If I feed sa-learn do I have to strip the last Received: header which is the Received header for my own MDA (imap-backend) before piping the message into sa-learn? Return-Path: spam...@whatever.com --- strip this header? -- Received: from mxrelay.mysendmail.com (mxrelay.mysendmail.com [xxx.xxx.xxx.xxx]) by imap-backend; Thu, 18 Sep 2014 22:25:35 +0200 Received: from emailstarget.com (emailstarget.com [5.196.112.99]) by mxrelay.mysendmail.com with ESMTP id s8IKPUkU005480 for t...@test123.com; Thu, 18 Sep 2014 22:25:33 +0200 To: t...@test123.com Subject: foo baar Message-ID: 2f56a1387b66e02d57493abba40bd...@emailstarget.com [...] Thanks Marcus
sa-learn from a remote imap folder
Hi, spamassassin and imap (cyrus) are running on different boxes. What is best practice to learn spam from a remote imap folder? Any good working scripts? I found these: https://wiki.apache.org/spamassassin/RemoteImapFolder https://gist.github.com/colinmollenhour/4127743 Ciao! Marcus
Re: sa-learn from a remote imap folder
Hi, Am Freitag, den 12.09.2014, 10:13 +0200 schrieb Axb: On 09/12/2014 10:05 AM, Marcus Schopen wrote: Hi, spamassassin and imap (cyrus) are running on different boxes. What is best practice to learn spam from a remote imap folder? Any good working scripts? I found these: https://wiki.apache.org/spamassassin/RemoteImapFolder https://gist.github.com/colinmollenhour/4127743 Imapsync or OfflineIMAP http://imapsync.lamiral.info/ http://offlineimap.org/ On the spamassassin box there is no imap server running to have an imap to imap sync. Therefore I think imapsync can't handle this. offlineimap seems to be interesting, because it seems to dump the mails to a local folder, which could eaten by sa-learn. there are tons more - Google sync imap Before start scripting mysself I was looking for a smart and stable script, which people use for long time without problems. Ciao Marcus
Re: sa-stats.pl problem on woody - looking for log analyser?
On Friday 26 November 2004 06:05, Marcus Schopen wrote:
Hi,
on debian/woody sa-stats.pl ends with following errors:
Error in option spec: top|T:25
Error in option spec: SCALAR(0x84ff7f4)
The getopt libs might be to old on woody. Are there any other programms to
get some nice statists of spam and ham? I'm using spamassassin 3.0.1 with a
sendmail/milter-spamc(0.25.321) combination (see www.milter.info).
I changed line 67 to
'top|T'= \$opt{'topusers'},
This will fix above error on Debian/woody. Strange, but works ...
Cheers,
M.
--
I have plenty of common sense, I just choose to ignore it.
--- Calvin
