From: Frank Carmickle <frankiec@braille.uwo.ca>
To: speakup@braille.uwo.ca
Subject: Re: Fetchmail/Sendmail problem
Date: Wed, 25 Jul 2001 04:24:49 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0107250419200.17508-100000@localhost> (raw)
In-Reply-To: <Pine.LNX.4.21.0107242102080.255-100000@C893988-a.stcla1.sfba.home.com>
Hi Mike
First thing that should be fixed is you getting a reasonable
nameserver. This should clear up the problems. You really don't want to
change much in the way of sendmail configuration because you don't want to
open yourself up as a relay for spam.
On Tue, 24 Jul 2001, Mike keithley wrote:
> This is probably off topic but the problem occurs getting mail from this
> list so I thought I'd ask the experts.
>
> I use fetchmail to get mail from shellworld.net (my ISP). Fetchmail
> negotiates with sendmail to get mail into my local mailbox. Sendmail seems to
> want to verify that the sender domain is valid and checks a route.
> the intermittent problem is this:
--
Frank Carmickle
phone: 412 761-9568
email: frankiec@dryrose.com
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
Mike keithley
` Frank Carmickle [this message]
` Mike keithley
` Mike keithley
Holmes, Steve
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=Pine.LNX.4.21.0107250419200.17508-100000@localhost \
--to=frankiec@braille.uwo.ca \
--cc=speakup@braille.uwo.ca \
/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).