[Alpine-info] return-receipt

Steven W. Orr steveo at syslang.net
Tue Jul 7 12:24:59 PDT 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/07/09 14:17, quoth Matt Ackeret:

> On Tue, 7 Jul 2009, andretta at apf.it wrote:

>> Many mail reader and webmail services manages the "return-receipt".

>> Personally I don't like it, but users think differently ... ;-)

>> I read FAQ and agree with considerations, but ... ;-)

>>

>> So I have watched mails and noticied that the return-receipt (at mailer level),

>> is implemnted using this additional header:

>>

>> Disposition-Notification-To: some at domain.tld

>>

>> There is a way to enable/disable this in AlPine with a simple manner like the

>> flag in Thunderbird & c. ?

>

> I honestly know *nothing* about the return-receipt functionality, but if it

> really is just a header value, it looks to me like you could just set this

> in the "Customized Headers" setup/configuration item.


That takes care of what you'd do to define a Role or possible default value
for *requesting* an RR. You'd have to write a Display Filter that would be
configured to either respond or ask to respond (or even not respond) to a
received header. Not a huge deal, but the Filter would want to keep a database
of messages that it already responded to so it wouldn't repeatedly send conf's
back every time you re-read the message. Not too hard to do in bash, but
frankly why bother? It either got delivered or it failed to be delivered. It
if failed then you are notified by DSN. If you really need to know *when* he
read his mail, it still won't tell you if he read it carefully or just deleted
it right away. If you really need to know that he got the message and really
did understand it then call him on the phone and talk to the poor guy. Or
else, in the body of your message, just say that you will assume that he
didn't read it until he writes back to confirm that he, as an individual, read
it and understands it.

The world is filled with important information that is diluted from misuse. A
C file might have thousands of warnings that prevent you from seeing the one
warning that you really needed to know about. An indicator light on your dash
is on and most of the time it means something that's not of any interest or
value to you. Getting notified of roughly when someone first may have seen a
message, but didn't pay any attention to it, is not only probably not giving
you anything of value, but is likely distracting you from reading things that
you would normally have time for, especially if you set RRR as a default.

Let me know if you read this rant. ;-)

- --
Time flies like the wind. Fruit flies like a banana. Stranger things have .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkpToQoACgkQRIVy4fC+NyRG2wCbB1GqK1Sr3V95RoQIsV+PTrjF
cXMAn0DkYYvHBz/HDpzHtU9xyQ6LuIgG
=/rye
-----END PGP SIGNATURE-----


More information about the Alpine-info mailing list