Mark Horn <[EMAIL PROTECTED]> writes:
> So what are you saying, I would set up the following in
> /etc/aliases:
>
> mark: [EMAIL PROTECTED]
No, I thought you meant something like:
inbox: [EMAIL PROTECTED]
as I thought you were implying that the extension addresses were
harder to remember than regular ones or something.
> You don't have to tell me anything. If I really want this I can
> code.
:-)
> FWIW, I don't like your solution
You don't say?
> Your solution means that whatever word you choose as your extension
> address is effectively a password.
Sure, but only you know that password.
> What do you do when you want to copy yourself on something, Bcc?
Right. No more difficult in your MUA than adding a Cc.
> What if you slip up and accidentally include it on a public email?
Then change your extension address. FWIW, I've never done this, and
I've been using this methodology for 5 years or so now.
> What I'm suggesting doesn't force me to keep something secret that
> isn't already secret. And it's also something that I'm not going to
> accidentally disclose. It seems to me a natural extension of how
> TMDA is used.
True. It's just one of those cost-benefit arguments. I don't know if I
see the justification for the expense of using technology to solve
something that is so simple to solve with a slight change of practice.
> But this is all just my $.02. If I want it bad enough, I'll submit
> a patch.
I guess I'm not clear on what the patch would do? Or, put another way,
how you would attempt to solve this using TMDA?
_________________________________________________
tmda-workers mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-workers
