[EMAIL PROTECTED] (David Stern) writes: > Hi, > > 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. > > My isp has become irate. This is causing a lot of grief for a lot of > people, and I hope the nmh package maintainer will please be far more > considerate in the future. Since my mail will bounce from just about > anywhere but the debian list, I can't very well send this to the nmh > package maintainer right now, but you can trust that I will when this > is fixed. > > 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: Take your net connection down, and if you're using diald do a "force down" to keep it down. Then, send a message with nmh to any address. Now, do a: tail /var/log/smail/logfile and look at the second-to-last entry - it should start with "Received FROM:" and then give the name as handed to it by nmh. For example, suppose that nmh is now sending From: lines that look like "[EMAIL PROTECTED]" - You can then add the following to your /etc/smail/maps/frommap: [EMAIL PROTECTED] [EMAIL PROTECTED] 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. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
