9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Robert Raschke <rrplan9@tombob.com>
To: 9fans@cse.psu.edu
Subject: [9fans] how to deal with mail delivery problems
Date: Fri, 19 Nov 2004 15:20:56 +0000	[thread overview]
Message-ID: <7a1e45b3731ba65d720e75192cec523b@tombob.com> (raw)

Hi,

increasingly over the last couple of weeks, I am becoming a victim of
"we don't accept mail from that IP address, go away" mail servers.
This is due to vast swathes of IP addresses given out by ISPs being
blacklisted.

Now, the usual approach to fix this is to use the ISPs smtp server.
Unfortunately, these beasts (at least for my ISP, but I hear for
others as well) appear to be under constant attack and go up and down
like yo-yos.  This leaves you with quite an unreliable service.

Just as an example, if I send email directly from my Plan 9 box at
home to my work address, it takes under a second, but going via my
ISPs smtp server takes anywhere from 30 seconds to 3 days.

So, I can also pay for some other forwarding service, which hopefully
results in more stable conditions.

My question is this: Is it possible to come up with a mail
configuration that will first attempt to deliver directly, and only if
that fails will it attempt to use an external smtp server (and inform
me of that somehow)?

I am vaguely guessing that there is a problem here, in that I can't be
sure that any acceptance of a message by an external entity will
actually result in a reliable delivery of the message to the end
recipient. If that is the case, would I be best of by shopping for a
reliable smtp service and use that exclusively (even if it is on the
other side of the planet)?

Apologies for only being tangentially on topic for Plan 9.

Robby



             reply	other threads:[~2004-11-19 15:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-19 15:20 Robert Raschke [this message]
2004-11-19 15:47 ` Russ Cox
2004-11-22  8:55   ` Robert Raschke

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=7a1e45b3731ba65d720e75192cec523b@tombob.com \
    --to=rrplan9@tombob.com \
    --cc=9fans@cse.psu.edu \
    /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).