Re: exim-configuration--relaying mail
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
A long time ago, in a galaxy far, far way, someone said...
> I have my two machines setup. One Debian server, one Debian
> workstation. The server is called server.mynetwork.net and the
> workstation is called ws.onmynetwork.net. I have pointed my email
> client (balsa) on ws.onmynetwork.net at server.onmynetwork.net but for
> some reason exim is not relaying the mail. I realize it's probably
> something in my exim.conf but I can't seem to figure it out. Is this
> controlled with the local_domains option? If so here's what mine
> looks like:
>
> local_domains = localhost:server.onmynetwork.net
>
> Do I need to add ws.onmynetwork.net to that?
No.
You need to add ws.onmynetwork.net to "host_accept_relay". Even better:
add your private network scheme to "host_accept_relay". Let's assume that
you're using the 192.168.0 private network. Rather than adding every
workstation to "host_accept_relay":
host_accept_relay = localhost:192.168.0.1:192.168.0.2:192.168.0.3...
add the entire private network using CIDR (network/netmask-length)
notation, like this:
host_accept_relay = localhost:192.168.0.0/24
Using network/netmask (ie 192.168.0.0/255.255.255.0) notation might also
word:
host_accept_relay = localhost:192.168.0.0/255.255.255.0
> If so, how do I do that? The reason I need to send it to exim on the
> server is to rewrite the addresses.
If you're using balsa address rewriting probably isn't needed. But, in
any case, look for the section in exim.conf that starts like this:
######################################################################
# REWRITE CONFIGURATION #
######################################################################
Take a look at the sample exim.conf that has provided you with so much
help in the past for some examples.
However, I believe that address rewriting is only effective for locally
generated addresses (ie for programs that run /usr/lib/sendmail to send
outgoing email). At least, that's the case for Exim 3.13, the version
distributed with Debian 2.2. Therefore, re-writing will have to be done
on the local machine.
There is another alternative: upgrade Exim. The version in woody (the
latest-and-greatest, Exim 3.20) has the capabilities you seek, and
compiles very nicely on a potato system, provided you have the needed -dev
packages installed.
If you desire it, I compiled Exim 3.20 for potato over the weeked for my
own machines; I've put the .deb on the 'net under
ftp://tux.creighton.edu/pub/pbrutsch/ (sorry, no apt-get'table archive
yet). It has dependencies on the following packages:
libc6
libdb2
libgdbmg1
libident
libopenldap1
libpam0g
libpcre2
libpgsql2
cron
netbase
libssl096
With the exception of needing to compile and install libssl from woody
(very painless, btw: I put the .deb under
ftp://tux.creighton.edu/pub/pbrutsch/), every one of those packages are
the potato versions.
The necessity for SSL is to support the STARTTLS extension many mail
clients support. (The PostgreSQL client libraries and SSL libraries are
not included in the woody binary, hence the 1.1 version number)
> I realize I could set this up on the workstation but I plan on adding
> another one soon and would like to just maintain one exim.conf.
It's still possible: consider investigating a package called cfengine.
It will allow you to keep a central copy of a exim.conf, and have that
file automatically copied around on a regular (configurable) basis.
- --
- ----------------------------------------------------------------------
Phil Brutsche pbrutsch@tux.creighton.edu
GPG fingerprint: 9BF9 D84C 37D0 4FA7 1F2D 7E5E FD94 D264 50DE 1CFC
GPG key id: 50DE1CFC
GPG public key: http://tux.creighton.edu/~pbrutsch/gpg-public-key.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE6QEPh/ZTSZFDeHPwRApgIAJ9lIUqQSVtBje+LCAlmCypaZBqSWgCfV5J8
qUHIl7Wrw6NWYgcZUbPI3io=
=pmie
-----END PGP SIGNATURE-----
Reply to: