Charlie/Darrell
Thanks a lot for both of these suggestions. I'm now going to spend a bit of
time reading through the HOWTO's and looking at the checkrules templates,
but things look promising. I'm not really worried about the possibility of
personation because if any user in the company is that
on 14/8/01 5:44 pm, Charlie Brady at [EMAIL PROTECTED] wrote:
Have a look in
/etc/e-smith/templates/var/spool/smtpd/etc/smtpd_check_rules/
at 30InternalOnly. That will show you how to use a property of an account
Is the visibility property used elsewhere? An easy solution for me would
Check this link. I think this is what you are looking for.
http://www.linux.made-to-order.net/article.php?sid=103
D.J. Schmidt
Information Services Manager
Excel Industries, Inc.
P.O. Box 7000, 200 S. Ridge Rd.
Hesston, KS 67062
Ph: 620.327.1228 Fax:
On Tue, 14 Aug 2001, D.J. Schmidt wrote:
Check this link. I think this is what you are looking for.
http://www.linux.made-to-order.net/article.php?sid=103
No, that won't help. That has to do with incoming external mail, not with
the ability to send outgoing mail.
Attempting to limit the
On Tue, 14 Aug 2001, Richard Bruce wrote:
I agree entirely, but some people at the top are paranoid and can't be
dissuaded from their views. If it's any consolation the users concerned
won't have web access either (I've forced proxy authentication thanks to
information previously posted by
Charlie Brady [EMAIL PROTECTED] said:
Have a look in
/etc/e-smith/templates/var/spool/smtpd/etc/smtpd_check_rules/
Agreed. What you want can be set up via custom smtp_check_rules
entries. Start with this HowTo:
http://netsourced.com/servers/docs/smtp-restrict-howto.html
Here is
On Tue, 14 Aug 2001, Darrell May wrote:
If you really need to implement a complete solution you could look into
adding 'authenticated' SMTP support where the user needs to login to send.
The design of the e-smith server makes authenticated SMTP difficult. The
SMTP daemon (in this case,
Charlie Brady [EMAIL PROTECTED] said:
The design of the e-smith server makes authenticated SMTP difficult. The
SMTP daemon (in this case, obtuse smtpd) runs in a chroot jail which
does not contain the password database. It makes the password
database safe from theft (and cracking) via a
are you going to block that? ;-)
Scott
-Original Message-
From: Charlie Brady [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 14, 2001 1:54 PM
To: Darrell May
Cc: [EMAIL PROTECTED]
Subject: Re: [e-smith-devinfo] Restricting External Email
On Tue, 14 Aug 2001, Darrell May wrote
On Tue, Aug 14, 2001 at 03:01:34PM -0400, Charlie Brady [EMAIL PROTECTED] wrote:
[...]
Remember to do it all reliably and securely.
Also ensure that the usernames/passwords are not made available in the
clear (or you compromise local security by sniffing SMTP connections),
and/or use another
On Wed, 15 Aug 2001, Gordon Rowell wrote:
On Tue, Aug 14, 2001 at 03:01:34PM -0400, Charlie Brady [EMAIL PROTECTED] wrote:
[...]
Remember to do it all reliably and securely.
Also ensure that the usernames/passwords are not made available in the
clear (or you compromise local security by
11 matches
Mail list logo
