Re: [Nmh-workers] rcvdist with non-default port

[David Levine]

Ken wrote:

> But my point is that combination should be fine (the email address there
> should be interpreted by rcvdist; instead it is being passed to post).

It's up to the user to get it right.  The rcvdist command line syntax is
ambiguous and seems to always have been.  If we want to fix that, great,
but see below about doing this after 1.7.1.

And the fact that rcvdist seems never to have passed switch arguments
to post tells me that not many users will have to figure out how to use
rcvdist to do what they want.

> It just seems like we're changing from one set of sub-optimal argument
> handling to another.

No, rcvdist right now is broken, not sub-optimal.

> In
> theory the changes to rcvdist should be relatively straightforward (just
> add every post switch that takes an argument to the option handling and
> add those switch arguments to the array that get passed to post; we do
> that everywhere else in places like whatnow and send).

That would be fine with me if implemented so that it's maintainable
across all nmh programs.  Because that's non-trivial, I think that it
should be done after 1.7.1.

David