From kirebrow at yahoo.com Sun Aug 9 03:33:35 2015 From: kirebrow at yahoo.com (Erik M. Brown) Date: Sat, 8 Aug 2015 21:33:35 -0400 Subject: [spambayes-dev] Fwd: Message with no Package: tag cannot be processed! (Trying to contact Debian's SpamBayes package maintainer) In-Reply-To: References:

<20150702153744.GB22885@geta> <20150702211655.GC4449@hugo6390.home> Message-ID: <002301d0d243$697ce920$3c76bb60$@yahoo.com> Skip, I was wondering if you can help me. I've been using SpamBayes for YEARS and on my current rig, the "show spam clues for current message" is broken. I am running the following: SpamBayes 1.1b2 (March 6, 2010) Office Professional Plus 2010 If you would like any further details, I would be more than happy to help. I want this feature back so bad...lol! Thank you! Take care, Erik -----Original Message----- From: spambayes-dev [mailto:spambayes-dev-bounces+kirebrow=yahoo.com at python.org] On Behalf Of Skip Montanaro Sent: Thursday, July 02, 2015 5:57 PM To: Hugo Lefeuvre Cc: spambayes-dev at python.org Subject: Re: [spambayes-dev] Fwd: Message with no Package: tag cannot be processed! (Trying to contact Debian's SpamBayes package maintainer) Adding spambayes-dev back in. Hopefully the conversation will be smoother now that we have a working email address for you. Rather than respond point-by-point, I'm just going to quote on part of your note: Skip> I'm not sure I've seen any bug reports, and like I said, I had no Skip> idea it was included in any Linux distributions. Do you have Skip> specific bugs to report? Hugo> Spambayes bugs can be found here[3]. Some bugs like #374496 or Hugo> #296322 have been forwarded, but were never answered, some other Hugo> bugs like Hugo> #315866 or #376114 weren't forwarded and won't be forwarded Hugo> because upstream isn't responding anymore. These bugs aren't Hugo> really important, but the problem is actually that their number is growing. I will poke around the SF bug tracker. I haven't used it for ages. The most recent source is on GitHub: https://github.com/smontanaro/spambayes Going forward, I would prefer bugs to be reported there. Note, however, I am not going to go out and hunt down bug reports. If they are forwarded and I can handle them, that's fine. It's not my job to figure out all the other places people might be reporting bugs. I don't have a bunch of time to devote to this, but a couple other SpamBayes developers indicated they still use it (alas, they will have all gotten bounces to their replies). Perhaps we can clean up some of the obvious problems and push out a new release. One of the primary reasons releases stopped was that we lost the last person available to make Windows releases. I've created a couple other source releases since then, but was hesitant to get too far in front of the Windows version, since from where I sat (watching the spambayes at python.org mailing list), most users seemed to be on Windows. Skip On Thu, Jul 2, 2015 at 4:16 PM, Hugo Lefeuvre wrote: > Hi Skip, > >> > Please forward to Hugo, your SpamBayes package maintainer. If he >> > can't be bothered to contact me using a valid email address, I >> > can't be bothered to jump through a bunch of hoops to get my reply back to him. >> > >> > I am the last developer standing of SpamBayes. I got an email a few >> > days ago from Hugo (hugo6390 at users.sf.net), who says he is the >> > package manager for SpamBayes on Debian. My reply bounced with SF.net issues. >> > I'm not a Debian user or developer, and do not plan to jump through >> > a bunch of hoops to file a bug report. Please have Hugo contact me >> > at skip.montanaro at gmail.com from a valid email address. > > Please, excuse me for the trouble. > > The only way I found to contact you was Sourceforge's contact form > and, for an obscure reason, Sourceforge has decided to specify an > internal (and apparently non-working) adress in the From field. That's > quite embarrassing. > >> > Thanks for the note, Hugo. I've cc'd spambayes-dev to my reply. >> > Others there (assuming there still are others) might have some suggestions. >> > >> > SpamBayes has been dormant for quite some time, as you observed. >> > I'm not sure what you mean by "dead" though. I'm not sure what's to >> > be done about that. There are a few people who try to answer >> > questions about it on the main list (spambayes at python.org), but >> > most of those questions come from users of the Windows version. > > With 'dead', I was actually meaning that the project isn't active > anymore, despite of the fact that the official version of the project > is still an alpha/b?ta pre-release. I was also meaning that > spambayes's upstream isn't providing patches anymore, though more and > more bugs are being discovered. > >> > I no longer use it myself anymore, except on the mail.python.org site. >> > That instance hasn't been updated in quite awhile either. >> > >> > I'm not sure what an official "declare the end of the Spambayes >> > project" would mean. Do you want to take it over? Assuming you've >> > been maintaining it for Debian (I had no idea any Linux distros >> > included it), I don't think it would be a big deal to get you added >> > as an official maintainer. > > I'm not a really good Python developer, so I don't intend to take the > project over, and, that's actually the problem. More and more bugs are > appearing, and I'm not able to fix them alone. > > So, I wanted to ask you if you could say me clearly if the project is > abandonned, or just in pause. With 'official', I was meaning: Can I > still wait some help from spambayes's Upstream ? Or, is 1.1b1 > definitely spambayes's last official version ? > > As far as I know, spambayes is also available in freeBSD[0], Ubuntu[1] > and Fedora[2] (but the package seems to be orphaned). > >> > I'm not sure I've seen any bug reports, and like I said, I had no >> > idea it was included in any Linux distributions. Do you have >> > specific bugs to report? > > Spambayes bugs can be found here[3]. Some bugs like #374496 or #296322 > have been forwarded, but were never answered, some other bugs like > #315866 or #376114 weren't forwarded and won't be forwarded because > upstream isn't responding anymore. These bugs aren't really important, > but the problem is actually that their number is growing. > > Moreover, it may be really problematic if a Release Critical/Security > bug appears on this package. I wouldn't be able to fix it; It could > lead to spambayes's removal. > > All in all, could you say me if I can still expect some help from > spambayes's Upstream to fix bugs ? > > Best Regards, > Hugo > > [0] > http://portsmon.freebsd.org/portoverview.py?category=mail&portname=py- > spambayes [1] https://launchpad.net/ubuntu/+source/spambayes > [2] https://admin.fedoraproject.org/pkgdb/package/spambayes/ > [3] https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=spambayes > > -- > Hugo Lefeuvre (hugo6390) | www.hugo6390.org > 4096/ ACB7 B67F 197F 9B32 1533 431C AC90 AC3E C524 065E _______________________________________________ spambayes-dev mailing list spambayes-dev at python.org https://mail.python.org/mailman/listinfo/spambayes-dev