Tom Strickland <[EMAIL PROTECTED]> wrote:
>
> Hmmm - sounds great for my home machine, but not so great for the
> charity. The idea is to set up a minimum administration system so that
> an administrator is only needed to check the logs periodically and
> patch the system. Backup, user admin, mail - nearly everything else
> needs to be admin'd by the secretary. This is one area where Win NT
> still manages to do a little better, but I'm not letting that back on
> our server.
> If we're delivering our mail as coming from ourcharity.org.uk and it's
> being relayed through our ISP's SMTP server (BT), wouldn't it get
> blocked at some point by spam filters?
>
> Thanks,
I was originally not going to send this to the entire list until I
realized that someone may know of other differences than I have
thought of.
(also, see the other email I sent in reply to your clarification of the
above question ;-)
Well, actually from the admin maintenance point of view there's really
very little difference between a smart smtp server and one that *uses*
a smart smtp server. (actually, I can think of none at all, but I
thought I'd cover my bottom ;-)
On the admin side:
1 - You may want to set up sudo scripts to perform tasks like adding users
and so forth.
2 - Think about who you really want to handle bounce messages (ok, I suppose
this is more of a problem for smart smtp servers, but not much more,
as people would be getting bounce messages anyway, its just that the
ADMIN can get them too if you are the smart smtp server)
3 - Same goes for other admin email - I assume you all are training the
secretary which ones can be filed and which need 'professional help' ?
4 - What part of backup is going to be admin'd by the secretary? I'd think you'd
set it up so that they just have to change tapes? (And perhaps add
or remove items from the 'things to back up' list)
5 - Same for user admin - I assume you just mean being able to add and remove users?
I've never needed this, but I suggest sudo (e.g. to allow the secretary to
run 'useradd' or 'adduser') (You may not want this on your firewall!)
6 - Again, same for mail admin. Are you thinking just for adding and removing
mail users? Or do you have a mailing list (or more)? An awful lot
can be done with scripts (shell, perl, awk, sed, whatever ;-) that you
allow certain folks (i.e. the secretary) to run using sudo.
But in any case, consider whether you want your mail server to also be your
firewall (I actually am beginning to think that I hope its not ;-), and
whether the accounts need to actually be ON the mail machine (so the mail
'lands' there) or on the user's machines (so that the mail 'pauses' on
your mail machine but 'lands' on each user's machine - this is probably
NOT what you want, but I thought i'd mention it anyway).
Well, I'm really starting to wander now, I'll shut up ;-)
rc
Rusty E. Carruth Email: [EMAIL PROTECTED] or [EMAIL PROTECTED]
Voice: (480) 345-3621 SnailMail: Schlumberger ATE ___
FAX: (480) 345-8793 7855 S. River Parkway, Suite 116 \e/
Ham: N7IKQ @ 146.82+,pl 162.2 Tempe, AZ 85284-1825 V
ICBM: 33 20' 44"N 111 53' 47"W http://tuxedo.org/~esr/ecsl/index.html
