[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-developers] RE: ETRN and MS Exchange -for Taco
- Subject: RE: [cobalt-developers] RE: ETRN and MS Exchange -for Taco
- From: "Andy Brown" <andy.brown@xxxxxxxxxxxxx>
- Date: Fri Dec 14 03:27:49 2001
- List-id: Discussion Forum for developers on Sun Cobalt Networks products <cobalt-developers.list.cobalt.com>
> Taco,
>
> Hi Taco,
>
> Can you please let me have the howto for ETRN and SMTP please..
>
> Regards
>
> Jamie Rossi
>
> -----Original Message-----
> From: cobalt-developers-admin@xxxxxxxxxxxxxxx
> [mailto:cobalt-developers-admin@xxxxxxxxxxxxxxx] On Behalf Of
> Taco Scargo
> Sent: 07 December 2001 10:43
> To: cobalt-developers@xxxxxxxxxxxxxxx
> Subject: Re: [cobalt-developers] ETRN and MS Exchange
>
>
> Hi Jamie,
>
> > Does anyone know if a RAQ4 supports ETRN and if so how to set it up?
> ETRN is not supported by the RaQ4, you can however (by modifying files
> manually) enable ETRN, by adding the mailertable feature to
> the sendmail configuration.
>
> > I presume that the MX records show the exchange server as
> the primary
> > MX with the cobalt box being a lower priority MX record so
> it queues
> > mail.
> Not necessarily. You can use ETRN to mailservers that are not
> listed in the MX at all (e.g. on a private network). Sendmail
> uses a file named 'mailertable' to see how it should
> transport and queue mail.
>
> I will try to create a HOWTO and place it on
> http://pkg.cobalt.com either later today or on > Monday.
>
> With regards,
>
> Taco Scargo
> Sun Cobalt Product Manager, EMEA
Hi Jamie,
I'll post how I've implemented it here as Taco is a very busy guy, as
are all the sun/cobalt team these days.
Firstly your DNS records need to be put straight, in the example I give
yourdomain.com is the domain we are going to use for etrn and
mydomain.com is my servers/hosting that will queue when the other
machine isn't online.
In dns for yourdomain.com :
yourdomain.com Very High priority MX (value of 0) to
server.yourdomain.com
yourdomain.com high priority (value of 10) to mailserver.mydomain.com
server.yourdomain.com IN A 199.199.199.199
So, we've created the primary MX record here pointing to the entry
server.yourdomain.com and the secondary MX as the server that will queue
mail when server.yourdomain.com is offline.
Note that we've created an A record (forward lookup) entry for
server.yourdomain.com pointing to the static IP address of the server on
yourdomain (the one that is not always connected)
Now for the mailserver.mydomain.com configuration. In my case this is a
Raq3i, but the principles should be the same on any linux/Cobalt box.
I'll presume you already have an account in the Site Management for this
domain, if not create one, leaving switched OFF 'accept email for
domain'.
Now configure the email section on your Raq:
Control Panel > Email Server > Parameters
In the Relay for the following Hosts/Domains make sure you have the
entry in for yourdomain.com and also server.yourdomain.com
There should NOT be either of these or www.yourdomain.com in the
Host/Domain aliases box (as this will then try to deliver them to the
Raq rather than queue them)
Save changes, Save changes, and you can now leave your Raq interface.
Once DNS propagates then you should have a working setup. Simply set
your remote server to ETRN to the IP address of the
mailserver.mydomain.com and it should then push the mail down to the
box.
Pls read the previous post by Taco/myself regarding messages about 4hr
delivery timeouts, etc if you want to change them (This needs you to
telnet/ssh in)
I'll admit this took me a couple of goes to get right, so may be worth
doing so in a test environment first to make sure.
To check the queue on your Raq, telnet/ssh in and type in
mailq
And it will show anything waiting in the raq's queue, so you can
determine if there is a problem or not.
Also tailing the maillog file will show when the ETRN comes in. To do
that:
tail -f /var/log/maillog
And you should see something like:
Dec 14 09:28:21 host1 sendmail[5763]: NOQUEUE: Null connection from
server.yourdomain.com [199.99.99.99]
Which is the ETRN getting through.
Good luck! (And if anyone else has any comments, pls post as I'm not
saying this is 100% correct or efficient!)
Regards,
Andy Brown
andy@xxxxxxxxxxxxxxxxxxxxx
http://ineedlinux.info/