Sorry, I was wrong: 1.0 still has not fixed the long address problem.
When one sends a subscribe request to a mailinglist managed by
ezmlm/qmail, one receives a confirmation request which is to be sent
to a long, but completely rfc822 compliant address. For example:
[EMAIL PROTECTED]
This address appears in the reply-to field of the confirmation
request, but when I do repl, my header looks like
To: mw-longaddress-sc.918697841.mmpkjcijamdlnnfehpgk-mw=wierdlmpc.msci.m
[EMAIL PROTECTED]
which is cut at the wrong place.
Again, I can fix the address manually, or set up some parameters in
mh_profile, but the point is that this default behavior does not
conform to rfc822, and many of the subscribers to a mailinglist I
manage happen to use mh(-e), and they were puzzled.
If any of you want to experiment with this, you can try to send a
message (any message) to
[EMAIL PROTECTED]
and then just use repl to reply to the confirmation request. (No need
to actually send the reply.)
Thx
Mate---
Mate Wierdl | Dept. of Math. Sciences | University of Memphis
