Gnus development mailing list
 help / color / mirror / Atom feed
From: David Abrahams <dave@boost-consulting.com>
Subject: Re: Gnus with Exim
Date: Wed, 08 Jun 2005 16:48:51 -0400	[thread overview]
Message-ID: <uzmu01sng.fsf@boost-consulting.com> (raw)
In-Reply-To: <jk44qc8ppvu.fsf@W003275.na.alarismed.com> (Steven E. Harris's message of "Wed, 08 Jun 2005 13:14:45 -0700")

"Steven E. Harris" <seh@panix.com> writes:

> David Abrahams <dave@boost-consulting.com> writes:
>
>> I'm just putting smart_route first at the moment.  I figure dnslookup
>> might work somewhere that my regular servers are unreachable.
>
> Sure, that's fine, so long as you don't mind "maintaining" the similar
> settings in more than one router.
>
>> Cool, I was thinking something like that might be possible
>
> I'm pretty sure the Debian people pushed or at least suggested this
> option to the exim maintainers; I had never noticed it until about a
> month ago.
>
>> Actually that's what I have running right now.  I was having bad
>> smtp response this morning so I decided to bite the bullet and set
>> everything up as best I could before hearing from you.
>
> Is the two-host route list working properly?

I don't know; I've never had to fall back, and I haven't gone outside
my ISP.  I guess I could switch the order and see what happens.  Or go
down the hill to a cafe.

>> [BTW, how do you make those nice callouts?]
>
> It's boxquote.el¹. I used the functions `boxquote-region' and
> `boxquote-title' where appropriate.

Ah, nice.

>> I was thinking that the ideal would be 
>>
>> ,----
>> | smart_route:
>> |   driver = manualroute
>> |   domains = ! +local_domains
>> |   transport = remote_smtp
>> |   .include /etc/exim_smarthost_route_list
>> `----
>>
>> with
>>
>> ,----[ /etc/exim_smarthost_route_list ]
>> | route_list = * smtp.rcn.com:smtp.boost-consulting.com
>> `----
>>
>> or
>>
>> ,----[ /etc/exim_smarthost_route_list ]
>> | route_list = * smtp.boost-consulting.com:smtp.rcn.com
>> `----
>>
>> depending on which server had succeeded the last time.  But I don't
>> know how to do that.  Parsing the log file?  That's a frightening
>> thought.
>
> Yow. I don't know how to do that either. You'd need some kind of hook
> function that ran upon success or failure when sending. Cursory
> reading of the exim manual suggests that perhaps with some chaining of
> transports one could write something to a file based on whether some
> other transport succeeded or failed, but for now it's beyond me. I
> think that's one to take to a dedicated exim mailing list.

Good idea.

> By the way, not this helps much, but the order of the hosts mentioned
> in the route_list can be randomized.²

I know.  But like you said, doesn't help much.

>> Fortunately I don't have that problem.
>
> Well, we'll leave that solution in the archives for some other unlucky
> person.
>
>
> Footnotes: 
> ¹ http://www.davep.org/emacs/boxquote.el
> ² http://www.exim.org/exim-html-4.50/doc/html/spec_20.html#SECT20.6

Do you have a footnote.el, too?
<does `M-x load-library footnote'>
Oh my gosh, you do!

What other tricks am I missing?  Too many to tell, I'm sure.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com



  reply	other threads:[~2005-06-08 20:48 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-03 13:30 Asynchronous Gnus? David Abrahams
2005-06-03 20:37 ` Gnus with Exim (was: Asynchronous Gnus?) David Abrahams
2005-06-03 22:28   ` Gnus with Exim Steven E. Harris
2005-06-04 13:47     ` David Abrahams
2005-06-04 15:29       ` Steven E. Harris
2005-06-06  2:05         ` David Abrahams
2005-06-06 17:04           ` Steven E. Harris
2005-06-06 18:31             ` David Abrahams
2005-06-06 19:59               ` Steven E. Harris
2005-06-06 20:43                 ` David Abrahams
2005-06-06 22:44                   ` Steven E. Harris
2005-06-06 23:08                     ` David Abrahams
2005-06-06 23:47                       ` Steven E. Harris
2005-06-07  1:36                         ` David Abrahams
2005-06-08 18:14                           ` Steven E. Harris
2005-06-08 19:45                             ` David Abrahams
2005-06-08 20:14                               ` Steven E. Harris
2005-06-08 20:48                                 ` David Abrahams [this message]
2005-06-08 21:20                                   ` Steven E. Harris
2005-06-23 18:49                                     ` David Abrahams
2005-06-24 17:14                                       ` Steven E. Harris
2005-06-24 18:09                                         ` David Abrahams
2005-06-25 15:33                                           ` Steven E. Harris
2005-07-19 11:05                                     ` func-menu David Abrahams
2005-07-19 14:01                                       ` func-menu J. David Boyd
2005-07-19 14:21                                       ` func-menu Ted Zlatanov
2005-07-19 14:35                                         ` func-menu David Abrahams
2005-07-19 15:20                                           ` func-menu Ted Zlatanov
2005-07-19 15:41                                             ` func-menu David Abrahams
2005-07-20  1:03                                               ` func-menu Danny Siu
2005-07-22 14:55                                                 ` func-menu David Abrahams

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=uzmu01sng.fsf@boost-consulting.com \
    --to=dave@boost-consulting.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).