Re: Network mail

2006-09-11 Thread hackmiester (Hunter Fuller)


On 8 September 2006, at 11:45, Jerold McAllister wrote:


hackmiester (Hunter Fuller) writes:
I'm old school. Back in my day, we didn't have the Internet we  
have  today, and our UNIX boxes could mail over the network we had  
strung.  I don't care what mail app I use. I just want to be able  
to have two  boxes, boxbox and snowy, for example, and be able to  
'mail boxbox'  from snowy and vice versa. This has to be on a  
system-wide basis, so  people on my shell server can do it easily.  
Any ideas? A quick tutorial?

--
hackmiester (Hunter Fuller)


If you have some network connection between the two boxes (and any  
others)
Just follow the handbook and set up sendmail on each.   If you do  
not want
Email from anywhere else, then set it up to accept mail connections  
only

from those two boxen.
You don't need any of the other fancy stuff out there unless you  
see some

feature that you just gotta have.


So, as long as I set up sendmail and one host knows the other's name  
and can resolve it, it will Just Work™?



jerry

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions- 
[EMAIL PROTECTED]




--
hackmiester (Hunter Fuller)

svinx yknow when you go to a party, and everyones hooked up except  
one guy and one girl

svinx and so they look at each other like.. do we have to?
svinx intel  nvidia must be lookin at each other like that right now


Phone
Voice: +1 251 589 6348
Fax: Call the voice number and ask.

Email
General chat: [EMAIL PROTECTED]
Large attachments: [EMAIL PROTECTED]
SPS-related stuff: [EMAIL PROTECTED]

IM
AIM: hackmiester1337
Skype: hackmiester31337
YIM: hackm1ester
Gtalk: hackmiester
MSN: [EMAIL PROTECTED]
Xfire: hackmiester


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Network mail

2006-09-08 Thread hackmiester (Hunter Fuller)
I'm old school. Back in my day, we didn't have the Internet we have  
today, and our UNIX boxes could mail over the network we had strung.  
I don't care what mail app I use. I just want to be able to have two  
boxes, boxbox and snowy, for example, and be able to 'mail boxbox'  
from snowy and vice versa. This has to be on a system-wide basis, so  
people on my shell server can do it easily. Any ideas? A quick tutorial?

--
hackmiester (Hunter Fuller)

svinx yknow when you go to a party, and everyones hooked up except  
one guy and one girl

svinx and so they look at each other like.. do we have to?
svinx intel  nvidia must be lookin at each other like that right now


Phone
Voice: +1 251 589 6348
Fax: Call the voice number and ask.

Email
General chat: [EMAIL PROTECTED]
Large attachments: [EMAIL PROTECTED]
SPS-related stuff: [EMAIL PROTECTED]

IM
AIM: hackmiester1337
Skype: hackmiester31337
YIM: hackm1ester
Gtalk: hackmiester
MSN: [EMAIL PROTECTED]
Xfire: hackmiester


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Network mail

2006-09-08 Thread Jerold McAllister
hackmiester (Hunter Fuller) writes: 

I'm old school. Back in my day, we didn't have the Internet we have  
today, and our UNIX boxes could mail over the network we had strung.  I 
don't care what mail app I use. I just want to be able to have two  boxes, 
boxbox and snowy, for example, and be able to 'mail boxbox'  from snowy 
and vice versa. This has to be on a system-wide basis, so  people on my 
shell server can do it easily. Any ideas? A quick tutorial?

--
hackmiester (Hunter Fuller) 



If you have some network connection between the two boxes (and any others)
Just follow the handbook and set up sendmail on each.   If you do not want
Email from anywhere else, then set it up to accept mail connections only
from those two boxen. 


You don't need any of the other fancy stuff out there unless you see some
feature that you just gotta have. 


jerry

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Newbie:Home network mail forwarding

2004-04-23 Thread Alex de Kruijff
On Thu, Apr 22, 2004 at 07:00:48PM -0400, Peter Tokanel wrote:
 
 
 Alex de Kruijff wrote:
 
 On Wed, Apr 21, 2004 at 07:33:51PM -0400, Peter Tokanel wrote:
  
 
 Hi,
 
 I am new to unix but I have managed to setup a home network using  
 Free BSD. The
 FreeBSD box is a gateway/firewall/router for my Windows XP box and a 
 wireless access
 point. The XP box can access the web just great using the shared 
 connection.
 My problem is when email is used on the WindowsXP box , no messages can be
 sent out. I can receive email from my ISP's pop-server just fine. I am 
 not sure if I need
 to start some kind of mail daemon or what Is it my firewall 
 configuration
 I have included some of my setup files, hopefully someone can tell me 

 
 
 XP 192.168.1.0/24 - 192.168.1.0/24 gateway public_ip - internet
 
 It could be your firewall but it could also be you XP configuration.
 If you give me the output of 'ipfw sh' then i'll check if I can find
 anything that blocks sending mail.
 
  
 
 
 -- 
 Hi,
  Here is the output of 'ipfw sh'..I don't pretend to understand 
 what all these mean. The
 ipfw rules for the 'simple' case in rc.firewall were a starting point, 
 but then I added a few
 additional rules from various spots on the net attempting to fix various 
 problems. Any advice
 would be appreciated.

I couldn't find exacly what the problem is. It looks oke for me. If you
like to go on with this one you could try doing:
1. ipfw z
2. Try sending your mail
3. ipfw sh (and look where the packed gets blocked)
4. If you sloved the problem skip to the end
5. Add log to the rule and do 1-3. Then check /etc/security and look for
the rigth packets and see what happens.

What I like to do is offer you an alternative framework. I'll be in a
better position to help you this way.

For this first put these lines in your /etc/rc.conf. This will load the
firewall rules from that file.
firewall_enable=YES
firewall_type=/etc/firewall.conf

Then put these rules in your /etc/firewall.conf:
# Select NIC (1 = internal 2 = external)
add 00010 skipto 1  ip from any to any via rl0
add 00020 skipto 2  ip from any to any via vl0
add 00030 allow ip from any to any via lo0
add 0 deny  ip from any to any

 A packet send from the XP box to the internet passes these rule twice
 because it goes through two NICs.

# Internal NIC
19997 allow ip from 192.168.1.0/24 to any
19997 allow ip from any to 192.168.1.0/24
19998 reject log ip from any to any in
1 deny log ip from any to any out

 reject = deny + it tells the sender that no such service exist. That
 is smart for _you own_ computer.

## External NIC - Anti spoofing
#add 20200 skipto 20300  ip from 192.168.1.0/24 to any in
#add 20210 rejectip from any to 10.0.0.0/8 out
#add 20220 rejectip from any to 172.0.0.0/12   out
#add 20230 rejectip from any to 192.168.0.0/16 out
#add 20240 deny  ip from 10.0.0.0/8 to any in
#add 20250 deny  ip from 172.0.0.0/12   to any in
#add 20260 deny  ip from 192.168.0.0/16 to any in

 Afther everything works you can place your anti spoofing rules here
 and keep those packets from going into natd. Rules 200,240-260 can
 block you out and are optional.

# External NIC - Natd
20520 skipto 20600 ip from me to any
20530 divert 8668 ip from any to any
20540 allow ip from me to any
20550 allow ip from any to 192.168.31.0/24

 This acts like a stateful firewall (like below) for the lan.

# External NIC - Stateful firewall
29800 allow tcp from me to any keep-state setup
29810 allow udp from me to any keep-state
29820 allow ip  from me to any keep-state

 This allows packets out and responce back in.

# External NIC - deny or reject everyting else
29998 deny log ip from any to any in
2 reject log ip from any to any out

-- 
Alex

Articles based on solutions that I use:
http://www.kruijff.org/alex/index.php?dir=docs/FreeBSD/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Newbie:Home network mail forwarding

2004-04-22 Thread Alex de Kruijff
On Wed, Apr 21, 2004 at 07:33:51PM -0400, Peter Tokanel wrote:
 Hi,
 
  I am new to unix but I have managed to setup a home network using  
 Free BSD. The
 FreeBSD box is a gateway/firewall/router for my Windows XP box and a 
 wireless access
 point. The XP box can access the web just great using the shared connection.
  My problem is when email is used on the WindowsXP box , no messages can be
 sent out. I can receive email from my ISP's pop-server just fine. I am 
 not sure if I need
 to start some kind of mail daemon or what Is it my firewall 
 configuration
  I have included some of my setup files, hopefully someone can tell me 

XP 192.168.1.0/24 - 192.168.1.0/24 gateway public_ip - internet

It could be your firewall but it could also be you XP configuration.
If you give me the output of 'ipfw sh' then i'll check if I can find
anything that blocks sending mail.

-- 
Alex

Articles based on solutions that I use:
http://www.kruijff.org/alex/index.php?dir=docs/FreeBSD/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Newbie:Home network mail forwarding

2004-04-21 Thread Peter Tokanel
Hi,

 I am new to unix but I have managed to setup a home network using  
Free BSD. The
FreeBSD box is a gateway/firewall/router for my Windows XP box and a 
wireless access
point. The XP box can access the web just great using the shared connection.
 My problem is when email is used on the WindowsXP box , no messages can be
sent out. I can receive email from my ISP's pop-server just fine. I am 
not sure if I need
to start some kind of mail daemon or what Is it my firewall 
configuration
 I have included some of my setup files, hopefully someone can tell me 
what I am doing
wrong. Thanks in advance..
___
rc.conf
hostname=.SNOOPY
network_interfaces=vr0 rl0 lo0
ifconfig_vr0=DHCP
ifconfig_rl0=inet 192.168.1.1  netmask 255.255.255.0
linux_enable=YES
moused_enable=YES
moused_port=/dev/psm0
moused_type=auto
usbd_enable=YES
#defaultrouter=`ifconfig vr0 |grep inet |awk '{print $6}'`
gateway_enable=YES

firewall_enable=YES
firewall_type=simple
firewall_quiet=NO
natd_enable=YES
natd_interface=vr0
natd_flags=-f /etc/natd.conf
tcp_drop_synfin=YES

# Enable ip6fw.
#ipv6_firewall_enable=YES
#ipv6_firewall_type=type# see rc.firewall6 for what goes here
#ipv6_firewall_quiet=NO
# Setup caching only name server
named_enable=YES
# This file now contains just the overrides from /etc/defaults/rc.conf.
# Please make all changes to this file, not to /etc/defaults/rc.conf.
# Enable network daemons for user convenience.
# Created: Sat Apr 17 09:50:48 2004
linux_enable=YES

# This file now contains just the overrides from /etc/defaults/rc.conf.
# Please make all changes to this file, not to /etc/defaults/rc.conf.
# Enable network daemons for user convenience.
# Created: Sat Apr 17 12:58:28 2004
# -- sysinstall generated deltas -- # Sat Apr 17 12:58:28 2004
inetd_enable=YES
___
rc.firewall using natd  the simple define

#!/bin/sh -
# Copyright (c) 1996  Poul-Henning Kamp
# All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
# 1. Redistributions of source code must retain the above copyright
#notice, this list of conditions and the following disclaimer.
# 2. Redistributions in binary form must reproduce the above copyright
#notice, this list of conditions and the following disclaimer in the
#documentation and/or other materials provided with the distribution.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
# ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
# FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
# OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
# OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
# SUCH DAMAGE.
#
# $FreeBSD: src/etc/rc.firewall,v 1.47 2003/11/02 07:31:44 ru Exp $
#
#
# Setup system for firewall service.
#
# Suck in the configuration variables.
if [ -z ${source_rc_confs_defined} ]; then
   if [ -r /etc/defaults/rc.conf ]; then
   . /etc/defaults/rc.conf
   source_rc_confs
   elif [ -r /etc/rc.conf ]; then
   . /etc/rc.conf
   fi
fi

# Define the firewall type in /etc/rc.conf.  Valid values are:
#   open - will allow anyone in
#   client   - will try to protect just this machine
#   simple   - will try to protect a whole network
#   closed   - totally disables IP services except via lo0 interface
#   UNKNOWN  - disables the loading of firewall rules.
#   filename - will load the rules in the given filename (full path 
required)
#
# For ``client'' and ``simple'' the entries below should be customized
# appropriately.



setup_loopback () {
   
   # Only in rare cases do you want to change these rules
   #
   ${fwcmd} add 100 pass all from any to any via lo0
   ${fwcmd} add 200 deny all from any to 127.0.0.0/8
   ${fwcmd} add 300 deny ip from 127.0.0.0/8 to any
}
if [ -n ${1} ]; then
   firewall_type=${1}
fi

# Flush out the list before we begin.
#
${fwcmd} -f flush

# Network Address Translation.  All packets are passed to natd(8)
# before they encounter your remaining rules.  The firewall rules
# will then be run again on each packet after translation by natd
# starting at the rule number following the divert rule.
#
# For ``simple'' firewall type the divert rule should be put to a
# different place to not interfere with address-checking rules.
#
case ${firewall_type} in
[Oo][Pp][Ee][Nn]|[Cc][Ll][Ii][Ee][Nn][Tt])
   case 

Re: Newbie:Home network mail forwarding

2004-04-21 Thread Kevin D. Kinsey, DaleCo, S.P.
Peter Tokanel wrote:

Hi,

 I am new to unix but I have managed to setup a home network using  
Free BSD. The
FreeBSD box is a gateway/firewall/router for my Windows XP box and a 
wireless access
point. The XP box can access the web just great using the shared 
connection.
 My problem is when email is used on the WindowsXP box , no messages 
can be
sent out. I can receive email from my ISP's pop-server just fine. I am 
not sure if I need
to start some kind of mail daemon or what Is it my firewall 
configuration
 I have included some of my setup files, hopefully someone can tell me 
what I am doing
wrong. Thanks in advance..


I'm not a Unix developer, and *don't* play one on TV.
I do run a firewall, though.  My $0.02 :
If you're using the default /etc/rc.firewall in simple
configuration, you don't have a firewall rule to allow
outbound connections to an SMTP server (Tcp port
25).
Try issuing the following as the superuser on your
FBSD box:
$ipfw add 00023 allow tcp from me to any 25 setup

 and then see what happens from the Windows
machine.  Please note that 00023 is an arbitrary
choice of rule numbers; you will want this rule fairly
close to the top.  You might do ipfw show and decide
where the rule should fit before deciding what number
to assign... ?
HTH,

Kevin Kinsey
DaleCo, S.P.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]