There's a really good reason why TMDA is designed to run on mail servers as opposed to running on your local mail client machine. You can reasonably expect the mail server to be running up and available close to 24x7 whereas a personal machine might not have a permanent network connection, and even if it did, might be switched off for long periods of time.
With TMDA running on the mail server, new messages are processed as they are recieved and confirmation messages (if any) are generated as close to the time of the original messages as possible. On the other hand if TMDA were to run on your mail client machine (for example as a plugin to outlook) confirmation messages would only be generated when the client checks for new mail. In a best case scenario the average turn around time for a confirmation message to be generated (assuming a 10 interval between POPs) would be about 5 minutes on average, whereas the worst case could range anywhere from overnight to several days depending on how often you login to check email. This is definitely not ideal for getting email delivered in a timely fashion, and is the root reason why TMDA is designed to run on a mail server rather than a clients local machine.
I can create custom addresses for all my needs with TMDA including:
dated addresses
sender specific addresses (which only let a unique from addresses through)
keyword addresses
Additionally since TMDA acts as my SMTP server for outgoing email I can tell it to automatically change any of my headers to one of these addresses. So for example I could send an email to somone in my blacklist rewrite my from/envelope/replyto address to be a dated address and the recipient will be allowed to respond to my mail for a set period of time after which the address expires, and the sender will no longer be able to contact me.
These generated address also work great for when SPAMers are spoofing an address on your whitelist. In this case just give the real email account holder (eg bob@guys.com) a sender tagged address (eg alice-sender-cryptographic_hash@dolls.com), and remove the senders email address from your whitelist. Now as long as Bob uses the alice-sender-xxx address Bob will be able to comunicate you.
Slashdot Mirror
There's a really good reason why TMDA is designed to run on mail servers as opposed to running on your local mail client machine. You can reasonably expect the mail server to be running up and available close to 24x7 whereas a personal machine might not have a permanent network connection, and even if it did, might be switched off for long periods of time.
With TMDA running on the mail server, new messages are processed as they are recieved and confirmation messages (if any) are generated as close to the time of the original messages as possible. On the other hand if TMDA were to run on your mail client machine (for example as a plugin to outlook) confirmation messages would only be generated when the client checks for new mail. In a best case scenario the average turn around time for a confirmation message to be generated (assuming a 10 interval between POPs) would be about 5 minutes on average, whereas the worst case could range anywhere from overnight to several days depending on how often you login to check email. This is definitely not ideal for getting email delivered in a timely fashion, and is the root reason why TMDA is designed to run on a mail server rather than a clients local machine.
mail from:
doesn't match any entry in my whitelist, so I wouldn't get this email.
I can create custom addresses for all my needs with TMDA including:
- dated addresses
- sender specific addresses (which only let a unique from addresses through)
- keyword addresses
Additionally since TMDA acts as my SMTP server for outgoing email I can tell it to automatically change any of my headers to one of these addresses. So for example I could send an email to somone in my blacklist rewrite my from/envelope/replyto address to be a dated address and the recipient will be allowed to respond to my mail for a set period of time after which the address expires, and the sender will no longer be able to contact me.These generated address also work great for when SPAMers are spoofing an address on your whitelist. In this case just give the real email account holder (eg bob@guys.com) a sender tagged address (eg alice-sender-cryptographic_hash@dolls.com), and remove the senders email address from your whitelist. Now as long as Bob uses the alice-sender-xxx address Bob will be able to comunicate you.
I've got to concur. TMDA is the best Challenge/Response system I've ever used, and what beats all is that it's open source.