[Vmail-discuss] Exim as Secondary MX

[Jose de Paula Eufrasio Junior]

--=-I+dRJq+/T4PqeDvLZtRF
Content-Type: multipart/mixed; boundary="=-/qmXNo9Ye1eePb6uE9qa"


--=-/qmXNo9Ye1eePb6uE9qa
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, 2003-06-11 at 12:37, Pat Crean wrote:
> On Wednesday 11 June 2003 11:04, Jose de Paula Eufrasio Junior wrote:
> > Hello.
> >
> > I was thinking in changing some MX here to use the vmail machine as
> > secondary.
> >
> > What should I do? Just put the domains that I want in the relay_domains
> > and not in the localdomains?
> >
> > Any help is welcome ! :)
> >
> > []s
> > coredump
>=20
>=20
> The easiest way to handle it is to set "relay_domains_include_local_mx =
=3D yes". =20
> That way you just have to create a low priority mx record pointing to you=
r=20
> vmail machine and everything else happens automagically.  You do open=20
> yourself up to a potential spam attack in that a spammer could,=20
> theoretically, set up a dns server containing an mx record pointing to yo=
u=20
> and then use you as an open relay.  Not too big a problem, though as most=
=20
> spammers aren't going to go to that extreme when there are so many open=20
> relays available in china....

Sorry, I don't made myself clear enough. It's not a secondary MX. It's a
relay. That's the full history:

We have one First Class server, and it's SMTP server suc*s, no AV, bad
spam prevention, a whole list of problems.

To remedy that, we're trying to pass the mails (smtp) by the vmail
machine, where exim + vmail + amavis will do the cleaning...

so, what I need is that the vmail machine receives the mail for the
first class machine and redirect them, after all routing thru exim, to
the final smtp.

The First Class is a separate domain, and the vmail machine handles
multople domains too (of course).

I think that now I pictured the scneario right :)

[]s
core

--=20
Jos=E9 de Paula Eufr=E1sio J=FAnior
Analista de Sistema | CPD
ProInternet do Brasil

--=-/qmXNo9Ye1eePb6uE9qa
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: base64

LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KVmVyc2lvbjogR251UEcgdjEuMC43IChHTlUv
TGludXgpCgppRDhEQlFBKzUxQml1dXgraEFmZlpmc1JBcWliQUo5UUJyZUpwRWF0ODJCQmx0SmpO
dTAzWFlsSTR3Q2VQSkx0CnFBVWRyL0RaYnNnTWNrZFRJY0VVdVU4PQo9OUZsSQotLS0tLUVORCBQ
R1AgU0lHTkFUVVJFLS0tLS0K

--=-/qmXNo9Ye1eePb6uE9qa--

--=-I+dRJq+/T4PqeDvLZtRF
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQA+51CJuux+hAffZfsRAvkMAJ9UXdWlJupIQnYqJZgcTEAfO5M4xgCfbTgD
udESpmDAi58VCQMjOzRspsc=
=nwGv
-----END PGP SIGNATURE-----

--=-I+dRJq+/T4PqeDvLZtRF--