public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jim Kingdon <kingdon@redhat.com>
To: rosalia@lanl.gov
Cc: overseers@sourceware.cygnus.com
Subject: Re: important people (!) unable to use sourceware
Date: Thu, 09 Mar 2000 16:13:00 -0000	[thread overview]
Message-ID: <200003100013.TAA04899@devserv.devel.redhat.com> (raw)
Message-ID: <20000309161300.VO2iyBWLfiXxKOCGJJXvqK7AxO8tHkdlwoDcgBR5Evs@z> (raw)
In-Reply-To: <87vh2vafvt.fsf@portacipria.lanl.gov>

It sounds like you are mostly talking about the DUL
( http://mail-abuse.org/dul/ ) which basically says "we don't accept
mail directly from a dial-up".  This is a separate issue (in terms of
what it lists) from the other blocking lists (RBL, ORBS, or RSS).
Last I looked the DUL blocks a *lot* of spam so I'm sure that if we
turned it off we'd get lots of complaints from the spammed ones.  It
isn't like ORBS where we could probably do without it and not miss it
much.

> I would propose that a "requirement" on the system be that people be
> able to travel and hook up their laptops to major ISPs and still use
> our system.

You just need some mail server which you can authenticate yourself to
(or which otherwise will accept mail from you).  Sometimes this will
be the "major ISP" that you dial into, sometimes it will be your home
ISP/company (using POP-before-SMTP usually, although it could be
something more exotic like smtpauth).  Or, as has been suggested, use
an SSH tunnel to a machine where you can send the mail.

No one has a really nice solution to the problem of sending email
while on the road.  But just counting on being able to send from your
laptop to the destination mail server is becoming less possible (for
example, more and more dialup ISPs are blocking port 25 outbound,
which would foil this kind of usage quite aside from anything which
sourceware is doing).

  parent reply	other threads:[~2000-03-09 16:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-30  6:08 Mark Galassi
2000-03-09 15:27 ` Mark Galassi
2000-12-30  6:08 ` Jason Molenda
2000-03-09 18:31   ` Jason Molenda
2000-12-30  6:08   ` Bart Veer
2000-03-10  3:35     ` Bart Veer
2000-12-30  6:08   ` Chris Faylor
2000-03-09 20:13     ` Chris Faylor
2000-12-30  6:08 ` Jim Kingdon [this message]
2000-03-09 16:13   ` Jim Kingdon
2000-12-30  6:08   ` Bob Manson
2000-03-09 19:35     ` Bob Manson
2000-12-30  6:08 ` Gerald Pfeifer
2000-03-09 15:45   ` Gerald Pfeifer
2000-12-30  6:08   ` Bob Manson
2000-03-09 19:25     ` Bob Manson
2000-12-30  6:08     ` Jason Molenda
2000-03-09 23:32       ` Jason Molenda
2000-12-30  6:08       ` Chris Faylor
2000-03-10  9:27         ` Chris Faylor
2000-12-30  6:08       ` Jim Kingdon
2000-03-10  7:32         ` Jim Kingdon
2000-12-30  6:08       ` Bob Manson
2000-03-10 14:40         ` Bob Manson

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=200003100013.TAA04899@devserv.devel.redhat.com \
    --to=kingdon@redhat.com \
    --cc=overseers@sourceware.cygnus.com \
    --cc=rosalia@lanl.gov \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).