I thought that draft_from couldn't be enabled in a .mh_profile so that the
installer could restrict its use. To preserve that capability, how about
just defaulting masquerade to be enabled instead of disabled?
In this day and age, isn't that an impossible mission? After all, we have
usespace (nmh or other) process doing smtp towars the smtp server. Any such
check should, imo, be on the server side. Nothing's stopping the user from
telnetting to port 25 and try to send the mail with whatever envelope he
It's always been that way. I think that we should retain the
original nmh capability, just change the default build configuration.
Speaking of ports, wny way to use other ports than 25? I'm occationally
sitting behind an intricate mess^Dh of ssh tunnels...
It looks like it's hard-coded ("smtp") in mts/smtp/smtp.c.
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
Nmh-workers mailing list