RE: experience with borderware

[ha...@t-online.de]

>> 
>> Stefan Jakobs [mailto:stefan.jakobs@rus.uni-stuttgart.de]  said:
>> 
>> > What are good and what are bad recipients. Is a client of 
>> > borderware a good 
>> > recipient and all other bad? And is a bounce with an attached 
>> > SPAM-mail also 
>> > SPAM? If you ask them at borderware, they 'll answer that you 
>> > have to buy 
>> > their appliance to get an answer.
>> 
>> My guess is:
>> 
>> Good recipient:  validuser@example.com
>> 
>> Bad recipient:  nonexistentuser@example.com
>> 
>> Bounces with attached spam are considered spam by Borderware - it's in
>> their FAQ:
>> 
>>   http://bsn.borderware.com/faq.php
>>  
>> > > Do you run spamassassin against all outgoing mail?
>> > 
>> > Yes, I do. 
>> > 
>> > > What do you do with high-scoring spam?  If you're bouncing 
>> > that instead
>> > > of sending it to /dev/null that might be the problem.
>> > 
>> > Yes I bounce them, because I'm not allowed to change or 
>> > discard mails of data privacy reasons.
>> 
>> Bouncing emails is more of a data privacy concern than consigning them
>> to the bit bucket in the sky ever was, IMHO.  And if your backscattered
>> bounced spam / malware ends up infecting another person's PC or them
>> becoming victims of a phishing scam, to what extent are you responsible
>> (well, not you personally, but your organisation)?
>> 
>> Someone needs to get a clue somewhere.
>> 
The clueless people who consider discarding mails as the criminal offense of mail theft are
called parliament in this country, and possibly congress or House in others...:)

As a service provider, you can either quarantine the stuff, send out quarantine notices,
and sweep the q area after a week,
or you can ask customers to sign a document that they are willing to have their mail filtered.
There are probably more users who want no spam than the other way round

Wolfgang