Hi all,
my apologies for jumping into the thread so late.
Paul Cockings wrote:
> [snip]
>> No. Barracuda normally sends quarantine messages to end users and they can
>> then say if a mail is ham/spam by pressing a link inside the mail. The link
>> has the username/password already encoded in the url (it's not the normal
>> http://username:passw...@host/uri/ thing. It's more or less a hash that is
>> already encoded in the url that automatically authenticates/validates the
>> user). Pressing that link then triggers Barracuda to release the message
>> from quarantine and learn. That's it. Retraining HAM as SPAM is still done
>> by the admin.
>>
>>
>>
>>
> Arhhh, this sound interesting too. This sounds like something that
> could be added to dspam without much core change- right?
>
> Do you know how/when the quarantine messages are triggered?
> - per message?, per x number of message in quarantine?, time based?
>
Even though a WebService Interface (SOAP) would be most convenient for
.NET-based addins to outlook or the like, you have yet another option:
use a "RESTful" interface to submit the results (ok, this is not exactly
REST, but no need for SOAP either)
Best of all, since the operation can be completed with a simple GET
request, the option to send e-mails with encoded links is still open.
So, the solution would look like this:
----------------------
*Train to Spam*
http://www.domain.tld/dspam/remote/spam?user=u...@domain1.tld&signatureID=100001,4b54909b399539992375514&key=DEADBEEFCAFEB00F
***Train to Ham*
http://www.domain.tld/dspam/remote/ham?user=u...@domain1.tld&retrain=innocent&signatureID=100001,4b54909b399539992375514&key=DEADBEEFCAFEB00F
* Outlook add-in (w/Button): make a GET request to the URL
- the "key" is an SHA1 of the user's username & password
* Thunderbird extension: likewise
* From a link in an e-mail
http://www.domain.tld/dspam/remote/spam?user=u...@domain1.tld&signatureID=100001,4b54909b399539992375514&auth=DEADBEEFCAFEB00F123456789
(where the key is an HMAC keyed with the server's timestamp modulo
2h or so)
* Manually
(since the "key" is not present, we need to authenticate the user)
Send an HTTP 401 response, read username and password from the user.
-----------------
All of this is trivially implemented in PHP on whatever webserver is
available.
It can be "overlaid" over DSPAM's url hierarchy as needed (since it
would be optional) using mod_rewrite or a simple alias. No need to even
include the logic for this into the main dspam executable.
Regards,
J.L.
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
Dspam-devel mailing list
Dspam-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspam-devel
