Mark Jeftovic wrote: > Stephen, thanks for your reply on this.... > > Stephen Warren wrote: > >>> and no matter what if I reply to that address it keeps generating >>> another challenge request. >> >> Most likely, something is screwing up the environment variables that are >> set (i.e. not setting them) what TMDA processes the response to the >> challenge. Thus, it sees to mail as being to [EMAIL PROTECTED] >> instead of [EMAIL PROTECTED] >> > > Would you know which environment variables I need to be concerned about > here? So far I'm trying to set RECIPIENT and DESTINATION to the correct > values but it is still issuing an additional confirmation request....
I don't know off the top of my head, and it's different for each MTA (mail server software). You should verify that the script you're calling TMDA from (which I assume is called from your MTA as the local delivery agent) is not deleting or destroying any environment variables that the MTA sets - I believe that should be enough for everything to work. >>> 2) I can't seem to get tmda to issue "dated" type challenges. >> >> I don't think they exist. >> >> The option for dated addresses only applies to messages sent by an >> end-user throught TMDA for outbound processing. > > Sorry I don't follow you here. Under the existing system I have been > using for years, all the challenges come from myprivacy-dated-......@ > with a 24 hour lifespan, I'm trying to duplicate that. > > And the http://www.tmda.net/config-client.html page seems to indicate > this is still an option. The config-client.html web page isn't talking about challenge messages, but messages that the end user send out through TMDA - these are two completely unrelated things, with different message processing. I'm sure this is well covered in the documentation somewhere, but here's a quick recap of the message processing TMDA does: Inbound: Looks at the message, processes it according to the inbound configuration, which is typically: /etc/tmdarc ~/.tmda/config ~/.tmda/filters/incoming If the filter specifically says what to do with the message, TMDA does that. Otherwise, the default action is applied (as defined by the config file(s) or TMDA default) If "what to do with the message" is "challenge", then TMDA sends a new email back to the mail sender's original sender, *from* the destination users's address, with "-confirm-some_extra_stuff" added to the *from* email address. If the original sending user then replies to this confirmation email address, the original sent email is then delivered to the original recipient user. None of the above processing uses the outgoing filter in any fashion. Outbound: When the TMDA user (the person who has TMDA enabled on their email account) sends out email, they have the option of having their outbound email processed by TMDA, typically according to these configuration files: /etc/tmdarc ~/.tmda/config ~/.tmda/filters/outgoing In this case, the filter can specify to rewrite various addresses (such as "From" header, SMTP envelope sender etc.) to be so-called tagged addresses, which can be tagged as dated/sender/keyword if desired. TMDA could also completely replace addresses with some other hard-coded addresses. Note again: This processing isn't used when TMDA internally generates challenge messages - this processing is only applied to end-user generated outbound email, and only if the end user configures their email client to send outbound email through TMDA somehow (replacing the sendmail binary, point at a different sendmail binary, or use the tmda-ofmipd daemon)
signature.asc
Description: OpenPGP digital signature
_____________________________________________ tmda-users mailing list ([email protected]) http://tmda.net/lists/listinfo/tmda-users
