So it seems like we can already use this style of request to train
email..... (i'm thinking that forwarding via SMTP is not always best)
*Train to Spam*
http://www.domain.tld/dspam/dspam?template=history&history_page=1&user=u...@domain1.tld&retrain=spam&signatureID=100001,4b54909b399539992375514
***Train to Ham*
http://www.domain.tld/dspam/dspam?template=history&history_page=1&user=u...@domain1.tld&retrain=innocent&signatureID=100001,4b54909b399539992375514
So if a made the request sending the usr/pass, then I could train like this?
Does this cut it as a webservice or should the design be changed if we
wanted to develop this idea?
I also thought about a small 'relay service' that runs on the exchange
server (or other server inside a network), so users inside a corporate
network that would be firewalled off from making such requests would be
able to send the retraining request to the relay and the relay passes to
dspam.
------------------------------------------------------------------------------
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
