On 01.05.2012 02:27, Chad M Stewart wrote: > On Apr 30, 2012, at 7:10 PM, Steve Fatula wrote: > >> I've found requiring them to forward as attachment not so simple for users >> though, esp. exchange users for some reason (I don't use exchange and never >> have, so, not sure why). In the end, they give up and don't bother. > > While I despise Outlook I had to use it for a over year. :( I have used it for multiple years while being on a project where they had Exchange as their core messaging infrastructure. The client is okay. It's not as powerful as Lotus Notes but one can work with it and it does not feel/look like being from another planet (like Lotus Notes does). I personally don't love Outlook but I don't hat it too. It's just software. It does it job.
> With those clients in mind I have set the defaults for the DSPAM > signature to go into the message body. Because finding the headers in > Outlook is extremely difficult to say the least, possible but very ugly. This is where an application/button would help very much. Only because it is difficult in the UI to find a certain information, does not mean it is equally hard in code. > Figure Outlook users can simply forward the message to the address and > then the signature should be present in the body. Being a user preference > they can easily change it if they desire. (Assuming I've given them an > interface to do so.) This is where I have a problem. Forwarding whole messages for retraining? This is a waste of system resources and of bandwidth. So you receive that 5MB document and presentation and it gets tagged as Spam. Now as a user I learned from my IT guy that I need to forward the message to another address so that the filter learns in the future that this is not Spam. So again I send 5 MB of date where in reality the system just needs a hand full of data to do the same. > Having the DSPAM signature only in the message headers could be problematic > for Exchange/Outlook users as the headers are difficult to get at and yeah > I'd probably give up too. :) For end users it is not convenient but for code (aka: a button) this does not need to be convenient. Once coded a Spam/Ham reporting button would always do the same and not complain that it had to parse each time the message to get the desired signature out of the header. > Thus my idea of a Outlook plugin which maybe the best solution for those > users. Just read the note from Stevan. Yeah the idea of supporting an > Outlook plugin, scares the tripe out of me. So maybe I can get the users > trained to simply forward the message to address@. You could get the users trained. Off course. Please! Don't use TEFT in your setup. Please use TOE or TUM. With TEFT you will pay a hefty price if the users don't train. > > -Chad > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Dspam-user mailing list > Dspam-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspam-user > -- Kind Regards from Switzerland, Stevan Bajić ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Dspam-user mailing list Dspam-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-user
