> -----Original Message----- > From: [email protected] [mailto:baruwa- > [email protected]] On Behalf Of Mikael Syska > Sent: 16 November 2011 13:04 > To: Baruwa users list > Subject: Re: [Baruwa] Bayes, MS Exchange & dumb users. > > Hi, > > On Wed, Nov 16, 2011 at 12:45 PM, Jason Ede > <[email protected]> wrote: > >> -----Original Message----- > >> From: [email protected] [mailto:baruwa- > >> [email protected]] On Behalf Of Andrew Colin Kissa > >> Sent: 16 November 2011 08:45 > >> To: Baruwa users list > >> Subject: Re: [Baruwa] Bayes, MS Exchange & dumb users. > >> > >> > >> On 16 Nov 2011, at 10:37 AM, Jason Ede wrote: > >> > >> > I think it'd be possible to add something to the ribbon or to the > >> > menus > >> something as mark as spam/not-spam and then it just sends the message > >> ID,spam/ham and an authentication token to Baruwa or a daemon > running > >> on the mail gateway... > >> > >> This would be cool too, it would require a component to be installed > >> in outlook i guess. > >> > > > > Yes, the component would need to be installed. I think using some basic > VB routines it should be possible to read the headers to pull out the > message ID and it's just a question of integrating it nicely. This way you'd > be > learning on the 'clean' message, not after exchange had mangled the > headers... > > I would go for Outlook 2010 only, we dont have any older installations. I > can't really remember how the older versions look like. > > But under one of the ribbons with 2 button "Report spam", "Report ham" > ... there should not really be more settings.
Yes, that is all you need... The other 'nice to have' option would be to be able to select a group of messages and right click and then have learn as ham/spam then. > > Authentication is another issue. We dont have account for every user, only > admins. So we need a nice and clean way for doing this. Maybe ip based or > some other sort that can only reports spam. Maybe a queue so an admin > first have to ackowlegde the incoming as also rightfully being spam. > > So ... lets say: 192.168.0.0/24 dont need acknowledgement from an admin, > while "130.0.0.0/24" are allowed to send to the queue but they need an > admin to acknowledge the mails before being processed. > Any feedback here ? > > I'm a .NET Dev, so it would take forever for me to do that part on the baruwa > webinterface, but maybe andrew or some other could implement this that > knows python/django. > I was thinking that assuming outlook is on a domain for now then you could just push out settings via the GPO for authentication... For standalone installs then you'd need to manually enter values. I think if it works on outlook 2010 then it should probably work on 2007 as well? On the baruwa side then we'd need a way of passing username/password along with message ID and learn operation (probably via https) and then all we'd need to return would be a success/fail value. > > > >> > > >> > In an exchange environment the authentication details could be > >> > pushed > >> using group policy or the user could just put in their own account > >> details... I figure it could work in a similar manner to the release > >> from the quarantine email? > >> > >> Maybe NTLM or SPNEGO, I am planning to work on some exchange > >> integration features, but i do need some one to provide me with a > >> licensed exchange & active directory KVM instance, i intend on > >> putting out an appeal for sponsors soon. > >> > >> -- > >> Baruwa - www.baruwa.org > >> > >> _______________________________________________ > >> Keep Baruwa FREE - http://pledgie.com/campaigns/12056 > > _______________________________________________ > > Keep Baruwa FREE - http://pledgie.com/campaigns/12056 > > > _______________________________________________ > Keep Baruwa FREE - http://pledgie.com/campaigns/12056 _______________________________________________ Keep Baruwa FREE - http://pledgie.com/campaigns/12056
