k...@munnari.oz.au said:
MX records apply only to delivery to destination mailboxes (the domain name
from an e-mail address is looked up to obtain its MX list, by the MTS doing
delivery of the message to that address), they shouldn't be used for any
other purpose at all.
Actually, I'd find
Actually, I'd find full MX'ing support a useful feature in nmh and most MUAs.
Today, there is no way to know that a mail has been delivered to the recipient
, or a designated box of his choosing. You always have to send via a outgoing
mail relay of some sort. :-(
An example, if you're in a
On Tue, 27 Jan 2009 21:57:50 +0100, Anders Eriksson said:
Unfortunately, today's broken internet infrastructure has removed this useful
feature from the mail system. If more MUAs implemented a Guaranteed Delivery
Service out of the box, maybe we can get proper connectivity reinstated?
wishful
Date:Sun, 25 Jan 2009 22:55:13 -0500
From:Ken Hornstein k...@cmf.nrl.navy.mil
Message-ID: 200901260355.n0q3te6l020...@hedwig.cmf.nrl.navy.mil
| People smarter than I can speak up, but I think nmh falls more in the
| category of a mail _user_ agent, and thus RFC
Ken Hornstein wrote:
I use mts:sendmail (this is the Debian package default and generally what
I recommend people use because (a) nmh's SMTP talking code doesn't get
the corner cases of the spec right and (b) Unix systems should have a
sendmail binary that can do this kind of thing anyhow).
So ... what MTS are you using? SMTP? Or sendmail? Does -snoop tell you
anything useful? I thought what I did only affected the SMTP MTS, but
hey, I've been wrong before.
I use mts:sendmail (this is the Debian package default and generally what
I recommend people use because (a) nmh's SMTP
Thus spake Ken Hornstein:
Comments welcome!
I don't have any comments on the changes beyond that I'm grateful that
someone is doing this. Thanks!
--
J.
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
I only took a quick glance, but I think there may be some issues
with freeaddrinfo() use. For example, in sbr/client.c client() a
NULL pointer can be passed to freeaddrinfo(). That doesn't work
on a lot of platforms. Second, it seems memory is being leaked
in that function if you get a result
Ken Hornstein wrote:
Okay, so I've committed my changes to nmh
Haven't investigated yet, but there's definitely a bug in there. When
I try to use this version of nmh it won't let me send any mail:
What now? w
-- Network Recipients --
pm215 at localhost
What now? s
send: message not
Haven't investigated yet, but there's definitely a bug in there. When
I try to use this version of nmh it won't let me send any mail:
What now? w
-- Network Recipients --
pm215 at localhost
What now? s
send: message not delivered to anyone
So ... what MTS are you using? SMTP? Or sendmail?
Ken Hornstein wrote:
So ... what MTS are you using? SMTP? Or sendmail? Does -snoop tell you
anything useful? I thought what I did only affected the SMTP MTS, but
hey, I've been wrong before.
I use mts:sendmail (this is the Debian package default and generally what
I recommend people use
Okay, so I've committed my changes to nmh (including a new file, pending-
release-notes!). Overview:
- All networking calls now converted to new APIs (getaddrinfo(),
sockaddr_storage, and the like).
- Everything supports IPv6 with the exception of the ftp client in
ftpsbr.c. Yeah,
12 matches
Mail list logo
