Ken Hornstein <email@example.com> writes:
I had written this long note about how there was NO way that that the
local-mailbox entry would affect that, but I am glad I double checked ...
because I would have been wrong. It totally does! From
/* If there's a Local-Mailbox profile component, try to extract
the username from it. But don't try very hard, this assumes
the very simple User Name <firstname.lastname@example.org> form.
Note that post(8) uses context_foil(), so it won't see the profile
If it finds a username in local-mailbox profile component, then it copies
that over to username and that's returned by getusername() which is
eventually used to construct the default maildrop name. It looks like
that was changed in commit af586ebe59b7, which was back in ... 2012.
Whoops. So yeah, your Local-Mailbox profile entry made it look in
a maildrop file named /var/mail/martin.m. That one is on us!
Obviously this was an unintended consequence of this change; I
understand why it was done, so the mh-format functions would work
correctly with a Local-Mailbox profile component, but I think we'd all
be in agreement that the default maildrop name should be based on the
local Unix username and NOT what the user places in their Local-Mailbox
profile entry. I think the correct change should be what we did to
LocalName(); add an argument that indicates if you want something that
could come out of a config file or ONLY the Unix username. Thoughts?
Wow! I am so glad I read all the rest of the messages in
this thread. It makes me feel less clueless.
For now, I will consider this problem solved and move on
to creating new ones^H^h^H did I say that?
Anyway, thanks, everyone.
Martin McCormick WB5AGZ