[ previous ] [ next ] [ threads ]
 
 From:  "Paul Rae" <PRae at aminocom dot com>
 To:  "Zadikem, Travis-taz" <tzadikem at picosecond dot com>, "Zadikem, Travis-taz" <tzadikem at picosecond dot com>, "Monowall \(E-mail\)" <m0n0wall at lists dot m0n0 dot ch>
 Subject:  RE: [m0n0wall] RE:RE: [m0n0wall] Ok, re-iped firewall and still no luck to new email server..FIXED
 Date:  Tue, 28 Dec 2004 17:47:12 -0500
umm yes, its to prevent poorly configured servers acting as open relays

	-----Original Message----- 
	From: Zadikem, Travis-taz [mailto:tzadikem at picosecond dot com] 
	Sent: Tue 28/12/2004 9:59 PM 
	To: Zadikem, Travis-taz; Monowall (E-mail) 
	Cc: 
	Subject: [m0n0wall] RE:RE: [m0n0wall] Ok, re-iped firewall and still no luck to new email
server..FIXED
	
	


	I fixed the problem.  Can you believe that my default build of sendmail on
	Red Hat ES only allows 127.0.0.1 to connect to it.  I added the following to
	sendmail.cf and it took care of my problem from other outside clients:
	O DaemonPortOptions=Port=smtp,Addr=64.207.38.4, Name=MTA
	
	Thanks for all to that tried to help
	-----Original Message-----
	From: Zadikem, Travis-taz
	Sent: Tuesday, December 28, 2004 1:52 PM
	To: Monowall (E-mail)
	Subject: [m0n0wall] Ok, re-iped firewall and still no luck to new email
	server
	
	
	Ok,
	  I re-iped my firewall to 64.207.38.5
	I also have the following aliases
	
	mail  64.207.38.4       
	web  64.207.38.2       
	webmail  64.207.38.2  Used for webmail  
	
	and the following Server NAT Rules:
	64.207.38.2  Exchange Mail     
	64.207.38.4  Web Mail (Scalix)     
	66.180.96.1    
	
	and Inbound Rules are now:
	WAN  TCP  25 (SMTP)  192.168.1.55
	(ext.: 64.207.38.2)  25 (SMTP)       
	WAN  TCP  110 (POP3)  192.168.1.55
	(ext.: 64.207.38.2)  110 (POP3)       
	WAN  TCP  443 (HTTPS)  192.168.1.55
	(ext.: 64.207.38.2)  443 (HTTPS)  Webmail on pspl-mail     
	WAN  TCP/UDP  143 (IMAP)  192.168.1.55
	(ext.: 64.207.38.2)  143 (IMAP)       
	WAN  TCP  25 (SMTP)  192.168.1.160
	(ext.: 64.207.38.4)  25 (SMTP)  Scalix SMTP NAT  
	
	but I still can not telnet to port 25 of the 64.207.38.4 (really 192.168.1.160), but can
	to 64.207.38.2 (really 192.168.1.55).  Any ideas? 
	
	Travis
	
	---------------------------------------------------------------------
	To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
	For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
	
	
	---------------------------------------------------------------------
	To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
	For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch