On Sun, 22 Feb 1998 08:58:15 EST, wrote:
> [EMAIL PROTECTED] (David Stern) writes:
> >
> > Recently I upgraded nmh on hamm from 0.17-1 to 0.22-1 and I just
> > discovered my smail header rewriting is broke, and I think the new nmh
> > is the culprit. smail remains on hold status in dselect. I've read
> > the bug reports (there are none), I've read /usr/doc/nmh/DIFFERENCES.gz,
> > but there is no mention of this.
> > [..]
> > Where can I get the nmh deb that works, 0.17-1 ?
>
> How is it broken? I'm trying to imagine what nmh is doing that could
> cause the header-rewriting to fail (unless nmh is trying to bypass
> smail completely). The only thing I can think is that nmh has started
> to append "@mailhostname" to your email address as it's going out. To
> test this, here's something you can do:
> [..]
I'd already done what you told me, and everything looks fine. Heres
the entry for this (original) post (this am):
--------------------------------------------------------------
Received FROM:[EMAIL PROTECTED] HOST:localhost [127.0.0.1]
PROTOCOL:esmtp PROGRAM:smail SIZE:1460 IDENT:kotsya
ID-METHOD:rfc1413
destination supports esmtp 8BITMIME PIPELINING
Delivered VIA:debian.novare.net
TO:debian-user@lists.debian.org
ORIG-TO:<debian-user@lists.debian.org> ROUTER:inet_hosts
TRANSPORT:smtprewriter
Completed.
---------------------------------------------------------------
Now here's a log entry for a similar post a week ago (Feb 16):
---------------------------------------------------------------
Received FROM:[EMAIL PROTECTED] HOST:localhost [127.0.0.1]
PROTOCOL:esmtp PROGRAM:smail SIZE:1556 IDENT:kotsya
ID-METHOD:rfc1413
destination supports esmtp 8BITMIME PIPELINING
Delivered VIA:debian.novare.net
TO:debian-user@lists.debian.org
ORIG-TO:<debian-user@lists.debian.org> ROUTER:inet_hosts
TRANSPORT:smtprewriter
Completed.
---------------------------------------------------------------
(so far as I can tell, the only difference is the number of bytes)
For some unknown reason my Sender: line is no longer being rewritten,
and most destinations will refuse my mail because it is not DNS
resolvable (as an aside I'd be interested to hear the basis for such
refusals). Those that don't refuse it will modify it, go figure.
So far, there's no indication why my headers aren't being rewritten.
If you (or anyone) have any more ideas, I'd sure appreciate hearing
them.
> I know, it's annoying to have to add a new line to frommap each time
> some program decides to pass your address along a slightly different
> way, but the whole smtprewriter thing is just a big giant hack anyway.
While I agree on technical grounds regarding smtprewriter transfer
method, I see no reason for nmh to break it. Why can't my mail
programs just get along?
Where do "old" .debs go? I need to get an nmh that doesn't break my
header rewriting, 0.17-1. I've searched everywhere I can think of and
they're not to be found.
--
David Stern
------------------------------------------------------------------
http://weber.u.washington.edu/~kotsya
[EMAIL PROTECTED]
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
