Hi - I must admit that I don't understand a whole lot about networks and am wondering
if someone who does could help me out with the configuration file for the James email
server. I have set up a small LAN that consists of both wireless and ethernet wired
computers, and am running the James email server on one of my computers. I am
connected to the internet via a DSL connection and have been assigned a static IP
address and my own domain name. The DSL modem is connected to a wireless base station
which is running a DHCP server which in turn assigns a set of local IP addresses to
each of the computers on my LAN. I have also configured the wireless base station to
use the DNS from my ISP.
Initially I ran into troubles when I tried to send out email from one of the computers
on my LAN, via my James server using my [EMAIL PROTECTED] and found that the
James server was not sending anything out, but was routing everything to the spam
folder, thinking my internally generated emails were being generated from an invalid
source. (Receiving emails works fine, when sent in to my James server) I tracked the
problem down to a section of the James.conf.xml file which has a mailet matcher for
preventing relaying and setting up the allowable LAN IP address from which mail can be
sent. - (shown here)
<!-- This matcher-mailet pair can prevent relaying... if you change this, you risk
making your mail server an open relay point for spammers .
NOTE 1: the order of matcher-mailets is important: it must come after valid local
recipients have been dealt with but before any attempt is made to delivery the mail
remotely.
NOTE 2: Add your own network, if you want to relay mail outwards -->
<mailet match="RemoteAddrNotInNetwork=127.0.0.1" class="ToProcessor">
<processor> spam </processor>
</mailet>
I tried changing the value of the matcher for the RemoteAddrNotInNetwork parameter to
equal one of the IP addresses assigned to one of my computers by my DHCP server and
that still resulted in the James server failing to send anything out, (that originated
from that computer) it just continued to route my mail to the spam folder. I thought
about it some and guessed that because I am using my ISP's DNS to resolve the >From
URL into a static IP address, I should use my static IP address as the value of the
RemoteAddrNotInNetwork parameter, and that worked! All my computers are now able to
send email out via my James server.
But this does not seem logical to me, and it seems that it now opens my James email
server to being an open relay point for spammers??? Like I mentioned before, I am new
to all this and having lots of fun ;-) trying to figure out how to set up a LAN with a
local James email server that can handle both internal emails and routing them in and
out via my DSL/ISP. I would have thought that I should set up this mailet/matcher to
reject any emails that does not originate from within my own LAN. Couldn't someone
else originate an email with a From URL that mimics one of
[EMAIL PROTECTED]? Am I wrong in my assumptions about how networks behave
and if not, then can someone help me get James configured right? Much appreciate any
pointers given....
One slightly confused Marc..... ;-)
----------------------------------------------------------------------------------------------------------------
Do you think the software industry will ever make software that is as easy and
reliable for a user to use
as the automobile industry makes a car easy and reliable for a user to drive?
----------------------------------------------------------------------------------------------------------------
A man said unto the universe - "Sir, I exist!"
"However," replied the universe "I do not see where that creates in me a sense of an
obligation."
- Stephen Crane
