Mailman 3 October 2021 - Isbg

Training spamassassin on what is spam
by Daryl Rose 07 Dec '23

07 Dec '23

I am new to both spamassassin and ISBG. I've been reading the spamassissan docs and they have a command to train spamassassin on what is spam, but that only works if the SA and the mailbox are on the same server. I used ISBG because my mail is on a remote server. I was looking at the ISBG docs and see --learnspambox, so I was wondering if that is the option that is used to train SA on what is spam? Thanks Daryl

28 33

Marked SPAM not being moved to spam folder
by Daryl Rose 30 Nov '23

30 Nov '23

For the most part, I got ISBG working as expected, however, I am seeing some emails that was marked as SPAM not getting moved to the SPAM folder. The instructions that I found added this to the spamassassin config: > # Add *****SPAM***** to the Subject header of spam e-mails > # > rewrite_header Subject *****SPAM***** > report_contact isbg(a)SpamPi.net > report_hostname SpamPi.net > For the most part, this works. I see the spam marked and moved over to the spam folder, but occasionally, I see something marked *****SPAM***** in the inbox. Is there a reason why they don't get moved to the SPAM folder? Thanks Daryl

17 18

Version 2.1.0 is out!
by Louis-Philippe Véronneau 25 Oct '23

25 Oct '23

We just released version 2.1.0. Thanks a lot to all the people who contributed to the project since the last release! A large part of ISBG has be rewritten since the last release. This should fix a lot of the bugs people had. Here the changelog for this version: * Don't raise a error when learning a too big email spam (spamc return code 98). * Password is now stored as json data file. * Using standard cache xdg_cache_home to store information, usually $HOME/.cache/isbg/. If you have stored your password with and old releases you should re-store it and delete the old stored files, you should find the old ones as $HOME/.isbg. * We use cchardet and chardet if installed for better detect the mails encoding. * A more robust package, it can be used as a module and a script. * Using isbg/__main__ or python -m isbg to run as script. * python3 support. * Modularized. * Added a default --partialrun of 50. Use --partialrun=0 to retain the old behaviour. * Renamed sa_unwrap script to isbg_sa_unwrap, added command line options. Now it also depends of docopt. * Documentation: * Use sphinx and support to upload it to Read the docs. * Added development documentation. * Added manpages, built with sphinx. * Examples: added a crontab example in the bash_scripts directory. Note that you will need to save your passwords again since they are now being store as plaintext in a JSON file. You can find the signed release for 2.1.0 here: https://github.com/isbg/isbg/releases/tag/2.1.0 -- ,''`. : :' : Louis-Philippe Véronneau `. `'` pollo(a)debian.org / veronneau.org `-

3 2

Departing as a maintainer for ISBG :(
by Louis-Philippe Véronneau 21 Oct '23

21 Oct '23

Hi folks! I'm sad to announce I will no longer be able to contribute and maintain ISBG. I was working on ISBG for work, but I no longer work there and won't be using it anymore. I don't feel continuing to maintain ISBG while no longer using it myself it a great idea. Don't despair! Although I won't be working on ISBG myself, work hired someone to replace me and they will be taking over my regular duties and will thus continue to work on ISBG and maintain the ISBG package in Debian in my stead. I have given developer access on Gitlab to Taowa [1], a fellow Debian Developer and the person who's been hired to replace me at work. I trust Lukas Erlacher will continue to be of great help and will happily review Taowa's contributions until he's confident enough to grant him maintainer access :) ISBG is very cool and I learned a lot while working on it. I hope it continues to live on for a while :D [1] https://nm.debian.org/person/taowa/ -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ pollo(a)debian.org / veronneau.org ⠈⠳⣄

34 37

Newbie questions
by Daryl Rose 01 Oct '23

01 Oct '23

I just stood up ISBG and am in the process of configuring it. I've followed the documentation as well as some information found on a forum. I think that it's setup correctly, but it doesn't seem to actually be filtering spam. I have several email addresses setup. One of them I know for sure has spam in the inbox and I watch the log files when isbg runs. It see's the email, but flags it as "OK". I'm I missing something? Is there an option that I need to set? Here is the string that I'm using: isbg --verbose --imaphost <<Provider IMAP HOSTname>> --imapuser <<USER as you would logon in webmail>> --imapport <<YourISPKnows>> --partialrun 10 --spaminbox Spam --delete --expunge This is what I found on the forum. Second question.....I"m not sure about the "--spaminbox" setting. Am I supposed to create a "Spam" directory on the sever that I have setup, or is this the name of the spam folder on the email server? Most of the email addresses that I have use the name "Spam" for the spam folder, but a couple that I use have the folder named "Bulk Mail". If I run the "Bulk Mail" in the string, the command fails. I get the following error: ('select', 'Bulk Mail', 1) = ('NO', ['Mailbox does not exist.']) ('select', 'Bulk Mail', 1) returned ('NO', ['Mailbox does not exist.']) - aborting Any feedback is appreciated. Thank you. Daryl

20 21

Error message. Don't know how to proceed
by daniel＠kaesmayr.net 13 Sep '23

13 Sep '23

Hello, I have installed isbg on my ubuntu 18.04 server to do its magic. However I get an error message for my emails: <email.message.Message object at 0x7fa6efdb78d0> ('uid FETCH', ('2916', '(BODY.PEEK[])')) = ('OK', [('5 (UID 2916 BODY[] {42157}', "'Return-Path: XXXXXXXXX, ')']) ['spamassassin', '--exit-code'] error for mail 2916 NoneType: None Would anyone be able to point me towards a way to fix this? Thanks, Daniel

4 3

messages too large; --maxsize without effect
by Hendrik Friedel 13 Sep '23

13 Sep '23

8 8

Migrating to Gitlab
by Louis-Philippe Véronneau 13 Sep '23

13 Sep '23

Hey folks, I'd like to migrate to Gitlab. If you have an opinion on this, I'd like to hear it: https://github.com/isbg/isbg/issues/131 If on November 19th 2019 (in 2 months) we don't have a strong consensus on the issue tracker against moving to Gitlab, I'll initiate the move. Cheers! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ pollo(a)debian.org / veronneau.org ⠈⠳⣄

9 9

ISBG 2.3.0 is out!
by Louis-Philippe Véronneau 03 Mar '23

03 Mar '23

Hi! I just released a new version of ISBG, version 2.3.0. This version has a few fixes, but mainly marks the migration from Github to Gitlab. Cheers! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ pollo(a)debian.org / veronneau.org ⠈⠳⣄

25 26

ISBG 2.2.1 is out!
by Louis-Philippe Véronneau 27 Aug '22

27 Aug '22

Hi! I just released a new version of ISBG, version 2.2.1. For those of you asking "2.2.1, but where is 2.2.0 then?", PyPi was being an ass and kept me from uploading it: https://github.com/isbg/isbg/commit/e626d8d0628f691c041032c53f20d764b11d0079 2.2.0 fixes multiple bugs and deprecates the SecretyKeyring class, since it wasn't used and I had no plan to use it in the future. As a side note, I am now packaging isbg in Debian. This should make running isbg easier in the future: https://packages.debian.org/sid/isbg Thanks to the folks who reported issues and to Lukas Erlacher for reviewing my patches. Cheers! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ pollo(a)debian.org / veronneau.org ⠈⠳⣄

3 3