Ken wrote:
> 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
Ken Hornstein 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
> sbr/mts.c:getuserinfo():
>
> /* If there's a Local-Mailbox pro
Ken wrote:
> 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!
Whoops, on me.
> I think the correct change should be what we did
> The proper fix was to remove the local-mailbox
>declaration I had unwittingly copied from the system that does
>send internet mail to the ones that don't and on the one that
>does, I now set the $MAILDROP environment variable and, so far,
>all is peace and bliss now.
I had written this lon
Martin wrote:
> The proper fix was to remove the local-mailbox
> declaration I had unwittingly copied from the system that does
> send internet mail to the ones that don't
I don't think that Local-Mailbox should affect inc, see Ralph's
excerpts from the man pages and sources.
> and on the
Thank you to everybody who responded both on and off the
list. The problem is correctly solved and here is what
happened.
This is a good example of how long an incomplete
configuration can work perfectly until 0 Day when the right set
of circumstances make it glaringly obvious th
