Daniel Rose skrev, on 22-08-2007 07:52:
[...]
I've done redirects for a pilot group of users
gateway -----------> crap filter ------> exchange
| ^
---> postfix -> dspam -> postfix---|
[...]
Perhaps however it's a storm in a teacup. The worst case scenario is that
we either restore the db from a backup or just reset the training and
start again. This doesn't seem too serious really; have I missed the
point?
It's been such a long time ago that I'd forgotten why. My site has
always used Postfix latest with an LDAP backend for users and, like
Steve, we've always enforced lock-in SASL auth for all non-system users.
That's because they then can relay from anywhere to anywhere via their
account, but also because most of them are pubers/kids and I didn't want
them to be able to send messages as the rector or forge classmates' mail.
In the beginning I used the spam alias method, that's why it wasn't
possible to forge. I soon left that method, since it involved the users
thinking, and 95% of them aren't very good at that, which is why I
automated the whole dspam procedure, including automatic nag-nagging. If
you're using up-to-date Postfix you can enforce SASL auth and even make
it possible for unauthorized users to use Sendmail instead of smtp.
Best,
--Tonni
--
Tony Earnshaw
Email: tonni at hetnet dot nl
