it'd be interesting to have the sendmail process hupped and watch maillog as
that occurs. If telnet to port 25 of localhost works, all I can expect is
that either dest port 25 is blocked going out, or the servers dns is not
able to look up mx records. BTW you said you had sendmail_enable="YES" in
rc.conf. There are several sendmail lines in /etc/defaults/rc.conf..
Bri
----- Original Message -----
From: "Jack L. Stone" <[EMAIL PROTECTED]>
To: "Matthew Emmerton" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Monday, January 06, 2003 6:31 PM
Subject: Re: Redirecting root's email
> At 08:13 PM 1.6.2003 -0500, Matthew Emmerton wrote:
> >[ dah! Don't top-post! ]
> >> >
> >> > I'm not a big Sendmail expert or anything, but do you even
> >> > have the MTA
> >> > process running? Can you successfully telnet localhost.visimation.com
> >> > port 25? What sendmail related lines do you have in /etc/rc.conf?
> >> > --
> >> > Toomas Aas | [EMAIL PROTECTED] |
> >> > http://www.raad.tartu.ee/~toomas/
> >> > * All wiyht. Rho sritched
> >> > mg kegboawd awound?
> >> >
> >> Yes, I have the Sendmail Process running. Telnet to port 25 of
> >> localhost.visimation.com gives this:
> >> Forcefield# telnet localhost.visimation.com 25
> >> Trying 127.0.0.1
> >> Connected to locahost.visimation.com.
> >> Escape character is '^]'.
> >> 220 forcefield.visimation.com ESMTP Sendmail 8.12.6/8.12.6; Mon, 6 Jan
> >> 2003 16:50:15 -0800 (PST)
> >>
> >> I really wish I could get this working. It seems like such a simple
> >> thing, and my installation was pretty much straight-out-of-the-box from
> >> the Standard installation.
> >
> >Usually to redirect root's email, you edit /etc/mail/aliases to have an
> >entry that looks like this:
> >
> >root: matt
> >
> >and then run 'newalises' for it to take effect. If you want to redirect
> >root's email to a non-local mailbox, then you have to make an entry in
> >/etc/mail/virtusertable, like this:
> >
> >root [EMAIL PROTECTED]
> >
> >and then 'cd /etc/mail' and 'make' which will do the trick.
> >
> >--
> >Matt Emmerton
> >
>
> Well, not to be left out of the party, here's the way I've done for as
long
> as I can remember:
>
> <snip/> (# are from from the aliases file)
> # Pretty much everything else in this file points to "root", so
> # you would do well in either reading roots mailbox or forwarding
> # roots email from here.
>
> root: sageame # On this server
> sageame: [EMAIL PROTECTED] # Another domain on another server
>
> # In the above example, I first send root to a normal user account (may be
> redundant).
> # I also put include files which contain outside and inside accounts
>
> # Test include file list
> sendtest::include:/etc/mail/sendtest # a test file
>
> </snip>
>
> Then run # newaliases -- should work
>
> I suggest you try the above "sendtest" used as follows below which runs on
> the console verbose and you can see what it the mail system is doing and
> perhaps see the problem:
>
> # mail -v -s test sendtest < /dev/null
>
> where include is a list from /etc/aliases
> ...
> sendtest :include:/etc/sendtest
>
> where sendtest (aliases include)
> root # On this server
> [EMAIL PROTECTED] # On another server on my network
> [EMAIL PROTECTED] # A outside network
>
> Best regards,
> Jack L. Stone,
> Administrator
>
> SageOne Net
> http://www.sage-one.net
> [EMAIL PROTECTED]
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-questions" in the body of the message
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
