Ken Hornstein k...@pobox.com writes:
So for this bounced email, was the email sent to localhost or your ISP?
My ISP.
Then to me that sounds like your ISP's problem. You could look at the
headers of your bounce message and see which host it's complaining about.
Well, maybe you could 'look at
Norm wrote:
Well, maybe you could 'look at the headers... and see which
host..,', but I can't. So I'm forwarding a typical bounce, in the
hope that you'll do it.
--- Forwarded Message
Date: Wed, 23 May 2012 05:50:36 -0700 (PDT)
From: mailer-dae...@jad.dad.org (Mail Delivery System)
On Wed, 23 May 2012 21:46:21 +0100, Tethys said:
Yes, but I'm also lying. It turns out that what I was seeing was
a bug in xterm and show does display the message correctly in a
terminal. However, exmh doesn't :-(
What release of exmh and nmh are you on, and what font are you using for
the
Hi David,
Date: Wed, 23 May 2012 05:50:36 -0700 (PDT)
From: mailer-dae...@jad.dad.org (Mail Delivery System)
Subject: Undelivered Mail Returned to Sender
To: n...@dad.org
Message-Id: 20120523125036.e2663124...@jad.dad.org
This is the mail system at host jad.dad.org.
That bounce
Ralph wrote:
Is his local SMTP server on jad not involved with passing it onto
his ISP's smarthost then?
I don't think so, based on my possibly faded recollection
of the earlier discussion.
I read it as the other party, mail.eipye.com, rejected it
when jad tried to hand it over so the
On Wed, 23 May 2012 10:50:11 -0700, n...@dad.org said:
After I sent the attached Email, last February, Ken Hornstein solved the
dilemma it posed by telling me about the -server localhost option to send.
Until a few weeks ago, everything was fine. Then I started getting the same:
Received:
Ken Hornstein k...@pobox.com writes:
Well, maybe you could 'look at the headers... and see which host..,', but I
can't. So I'm forwarding a typical bounce, in the hope that you'll do it.
As others have mentioned ... you're submitting your email to the localhost
MTA, instead of your ISP smarthost.
Hi Ken,
That's what I do now. I only use 'send -server localhost', for
messages addressed to plain 'norm' and nobody else. If I
inadvertently attempt to use plain 'send' to send a message
addressed to plain 'norm', I get an error message. All this had
worked well, from February, sending
