On Wed, Jan 29, 2003 at 08:13:41PM -0700, Jason R. Mastaler wrote:
>Well, you could set an alias an your Postfix system so that it will
>work no matter where you are sending the message from.
So what are you saying, I would set up the following in /etc/aliases:
mark: [EMAIL PROTECTED]
Wouldn't that forward all email to [EMAIL PROTECTED] to the sender
address?
>I don't know what to tell you, as the problem seems easily solved to
>me using plain extension addresses.
You don't have to tell me anything. If I really want this I can code.
FWIW, I don't like your solution, even though it's trivially easy
to implement. Your solution means that whatever word you choose as
your extension address is effectively a password. What do you do when
you want to copy yourself on something, Bcc? What if you slip up and
accidentally include it on a public email?
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.
But this is all just my $.02. If I want it bad enough, I'll submit
a patch.
>It wouldn't be too difficult to verify your X-TMDA-Fingerprint before
>the message hit TMDA and allow the message directly through if it
>checked out.
That would work, too. I recall that there was some python code to verify
the X-TMDA-Fingerprint posted to one or the other of the lists. I guess
I would just pipe the headers to that code and if the script returned 0,
then deliver it (skipping TMDA), if not send it to TMDA... yeah that
should work... or am I missing something?
Cheers,
- Mark
_________________________________________________
tmda-workers mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-workers
