On 01/07/00 08:48 -0400, Russell Hoover typed:
>I've found out that my alternate ISP (Shore.Net, in Boston) is using a Mail
>Transfer Agent called "Exim" -- <http://www.us.exim.org> I went to its
>website, and, at least on a cursory look, couldn't find any mention of
>Delivery Status Notification.
Exim's an _excellent_ MTA :) However, I don't think it supports DSN (ref
RFC 1894). So, turn it off when using mutt on your shore.net account.
However, I don't see why mutt should bitch if sending a DSN request to a
non DSN aware MTA ... most other mailers simply say "ah, forget it" and go
right ahead.
>Exim isn't DSN-aware, I guess I'll have no choice but to continue running
>the mutt that's on that ISP with its 2 DSN variables forever disabled.
Any reason why you _need_ DSN? Try inserting these two headers in your
mutt (using my_hdr) - these work with several MTAs ...
Return-Receipt-To:[EMAIL PROTECTED]
X-Confirm-Reading-To:[EMAIL PROTECTED]
(the X-Confirm-Reading-To: was devised by David Harris, the author of
Pegasus Mail <you could call it the 'doze mailer that comes nearest to
mutt> and is recognized by several MUAs - use it if you want _read_
receipts)
hope this helps
--
Suresh Ramasubramanian + [EMAIL PROTECTED]
Love at first sight is one of the greatest labor-saving devices the
world has ever seen.
