Well the current status is that I *think* the mail is fixed, but I'm not
too sure about the ISDN dial-on-demand....

I'll check the logs in the morning to see what is happenning over night.

On Wed, 10 Jan 2001, Benjamin Scott wrote:
>   You want your system to be the primary MX for your domain. 

Check.

> You want your ISP's mailhost to be a secondary MX.  

Check.

> Your ISP's mailhost should be configured
> to accept mail for your domain. 

Check.

>   Now your ISP's mailhost will accept and queue mail for your system when it
> is down.  It will retry however often it is configured to do so, so mail
> should eventually get through, regardless.  To speed things up, you can send
> an ETRN command to your ISP's mailhost.  That will tell their MTA to retry
> your domain's mail queue immediately.

That's the plan.

>   To do so, you can use fetchmail, something like this:
> 
> fetchmail --protocol ETRN --smtphost your-domain.com mailhost.your-isp.com

Actually I made a quick script to issue ETRN manually and tossed it into
cron.hourly.  That *should* prompt the dial-on-demand where fetchmail
would probably time out before the connection is established unless I
made fetchmail's timeout fairly high... 

>   Hope this helps,

Actually it did, but more as a confirmation than as instructions... 

As for the dial-on-demand, I added the demand option to /etc/ppp/options
and specified a bogus IP pair for the local and remote then added the
option to accept any IP pair the RAS assigns.  Since it dialled out fine
on it's own before, I hope it will dial OK still.  I nix'd the ping -i
300 that I had running with /etc/ppp/ip-up.local

I'll post the results after work tomorrow, including if it worked and if
not, what it did...

Thanks,

Brian
---------------------------------------------------------------
|  [EMAIL PROTECTED]                Spam me and DIE!       |
|                 http://www.datasquire.net                   |
|                 Co-Founder & Co-Owner of                    |
|              Data Squire Internet Services                  |
---------------------------------------------------------------


**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************

Reply via email to