You can subscribe to this list here.
2009 |
Jan
(7) |
Feb
(1) |
Mar
(1) |
Apr
(16) |
May
(6) |
Jun
(4) |
Jul
(2) |
Aug
(9) |
Sep
|
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2010 |
Jan
(1) |
Feb
(1) |
Mar
(12) |
Apr
(10) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(1) |
Nov
|
Dec
(1) |
2011 |
Jan
|
Feb
(22) |
Mar
(26) |
Apr
(26) |
May
(5) |
Jun
(4) |
Jul
(1) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
(9) |
Dec
(1) |
2012 |
Jan
(2) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
(3) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(4) |
2017 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
(7) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Jonathan K. <ji...@ka...> - 2023-01-12 15:15:39
|
Well, I wish i'd bothered to check recent messages on this mailing list before spending about 12 hours yesterday porting version 1.1.2 of TMDA to Python 3. It would have saved me a lot of time. I've uploaded my port to https://github.com/jikamens/tmda . It's certainly not fully tested since I only use a subset of TMDA's functionality, but it's working at least for what I use it for. I welcome additional patches. I've also included a simple CGI script written in Perl that you can use as a front-end to tmda-pending to allow you to whitelist and blacklist senders and delete messages through a web server running on the same machine as TMDA. It's in contrib/simple-tmda.cgi <https://github.com/jikamens/tmda/blob/main/contrib/simple-tmda.cgi>. Feedback / bug reports / pull requests are welcome, of course. Regards, Jonathan Kamens |
From: Chris C. <cc...@al...> - 2022-06-03 03:41:15
|
I wish I could help - but all I gotta say is: Hardcore! I never made use of tmda-cgi since I use alpine (previously pine) to consume email. Chris On Thu, 2 Jun 2022, Hippo Man wrote: > > However, it turns out that the Cédric Dufour version runs under Python 3. > > I decided to take the plunge and try it, and I very easily got it to work!!! > > ... but unfortunately, I still have to deal with tmda-cgi. I found several versions > of it on line and tried each of them, but none work in conjunction with this > Python 3 version of TMDA. > > And it would be major piece of work to convert any of the existing tmda-cgi > releases to Python 3, and therefore, I believe I will have to write my own > replacement for tmda-cgi in order to accomplish this. > > I already have been using a command-line utility that I wrote a number of > years ago (in the Ruby language) to go through my pending emails and > either release, blacklist, whitelist, or delete them via invocations of > "tmda-pending". > > But I want a web-based app for doing this, and so I guess I will have to use > my command-line code as a starting point in order to write my own > web-based tmda-cgi-like utility. > > Or perhaps is there already some sort of alternative web-based front end to > tmda? I haven't been able to find such a thing, but perhaps I am missing > something. > > Thanks in advance for any thoughts or suggestions. > > -- > hip...@gm... > Take a hippopotamus to lunch today. > > > On Thu, Jun 2, 2022 at 1:44 AM Hippo Man <hip...@gm...> wrote: > > I really tried to get TMDA working with python3 but eventually I gave up > and decided to just stick with python2. Admittedly, my python skills are > poor, and I didn't want to spend more hours trying to get it to work. > > Hopefully you'll make better progress than I did! > > Chris > > > Thank you! > > And yes, I understand, I spent way, *way* too much time trying to convert > the original Python 2 TMDA code to Python 3. It ended up being a big > mess, and I finally gave up. > > However, it turns out that the Cédric Dufour version runs under Python 3. > I decided to take the plunge and try it, and I very easily got it to work!!! > ... as follows: > > % cd [work directory] > > % git clone https://github.com/cedric-dufour/tmda.git > > % cd tmda > > % sudo python3 setup.py install > > This installs the Python 3 TMDA executables into /usr/local/bin , and they > all work for me! It turns out that the "debian" subdirectory that I was > asking about in my previous message is totally irrelevant. The only > purpose of that subdirectory is for facilitating the creation of a debian > APT package for TMDA. There is no need to do that, since the steps I > outlined above will perform a full TMDA installation on your own linux > machine. > > After performing those steps, I only had to make one tiny change to my > existing TMDA configuration: > > Near the top of /etc/tmdarc is the following line of code: > os.makedirs(LOGDIR, 0755) > > That simply needs to be changed to this: > os.makedirs(LOGDIR, 0o755) > > (i.e., put a lower-case letter "o" between the zero and the seven) > > Some of my own scripts had to be changed, because I had the original > Python 2 TMDA code in /usr/local/tmda/bin, and I had to change a small > number of references to that directory into /usr/local/bin. But to be clear, > those changes are in my own code which *calls* TMDA executables ... > not in any of the Python 3 TMDA code itself. > > One caveat is that I do not use TMDA for challenge-response these > days, and I have never used it for tagging ... only for whitelisting, for > blacklisting, and for putting unfamiliar messages into the Pending queue > so I can inspect them via the TMDA-cgi web software and decide what > to do with them. Therefore, I don't know if you would encounter > challenge-response or tagging issues. However, given how well the > Python 3 version is working for me, I am optimistic that those functions > would also probably work. > > If you or anyone else want to try this Python 3 version of TMDA, and > if problems are encountered, I'm glad to offer whatever help I can here > in this mailing list. > -- > hip...@gm... > Take a hippopotamus to lunch today. > > > > On Wed, 1 Jun 2022, Hippo Man wrote: > > I have done a "git clone" of the python3 version of TMDA from here: > > https://github.com/cedric-dufour/tmda.git > > > > And I have done a "python3 setup.py install". > > > > I see that it created a TMDA directory tree under /opt/local/share/tmda > > > > In the cloned git directory, there is also a "debian" subdirectory, and since > > I am running under Debian-11, I want to install that debian-specific code. > > However, this debian code was not installed anywhere after my run of > > "python3 setup.py install", and I could not find any instructions for how > > to install that debian code. > > > > Futhermore, in the documentation that came with this TMDA version, > > there are a few references to http://wiki.tmda.net, but that web site > > no longer exists. > > > > Is there any place where I could find instructions for how to do a full, > > complete TMDA install of this python3 version on my Debian host? > > > > Thanks in advance for any pointers and help! > > > > -- > > hip...@gm... > > Take a hippopotamus to lunch today. > > > > > > On Wed, Jun 1, 2022 at 10:14 AM Hippo Man <hip...@gm...> wrote: > > Thank you very much. > > > > And I'm glad to see that this mailing list is actually still alive! > > > > Also, I went to your github site, and see that there are links there for two > > Python3 forks. TMDA is the only Python2 code on my server, and I very > > much want to get rid of Python2 completely. I'm going to check out both of > > those Python3 TMDA forks, and I'm happy that they exist. > > > > -- > > hip...@gm... > > Take a hippopotamus to lunch today. > > > > > > On Wed, Jun 1, 2022 at 1:17 AM Chris Caputo <cc...@al...> wrote: > > Nice work! > > > > BTW, I maintain https://github.com/ccaputo/TMDAretro in case anyone has > > trouble installing TMDA these days. > > > > Chris > > > > On Tue, 31 May 2022, Hippo Man wrote: > > > I figured out the answer to my question. > > > > > > In case anyone might come to this mailing list some > > > day and wants to know how I solved my problem, here > > > is how I did so ... > > > > > > I can implement item #2 in my list below by means of > > > an "incoming" filter. I created a "holdlist" file to contain > > > match patterns for the set of addresses that I want to > > > automatically put into a pending state, and I put the > > > following rule into my incoming filter ... > > > > > > from-file ~/.tmda/lists/holdlist hold > > > > > > Now, I have succcessfully implemented all three items > > > in my list. > > > -- > > > hip...@gm... > > > Take a hippopotamus to lunch today. > > > > > > > > > On Mon, May 30, 2022 at 7:51 PM Hippo Man <hip...@gm...> wrote: > > > I've been using TMDA for something like 15 years, and I am still > > > getting lots of benefit from it and am still very happy with it. > > > > > > If there is anyone who is actually reading this email list these days, > > > I have a question about the use of TMDA. > > > > > > My question is this: I want to set up the following filtering rules ... > > > > > > (1) If the sender's email address is on a very small list (less than a > > > dozen entries), I'd like the sender to be blacklisted. > > > > > > (2) if the sender's email address is on a very small list (less than a > > > dozen entries), I'd like the email to be held in the pending queue. > > > > > > (3) If any email arrives whose sender address is not in either of those > > > two small lists, I'd like it to be delivered. > > > > > > If all I had to deal with were item 1 and item 3, I could set ACTION_INCOMING > > > to "ok" and simply put the unwanted sender addresses into a blacklist file. > > > > > > However, I don't know how to also handle item 2 along with items 1 and 3. > > > Is what I want to do even possible with TMDA? > > > > > > If anyone is actually reading this email list and can answer my question, > > > I will be greatly appreciative! > > > > > > -- > > > hip...@gm... > > > Take a hippopotamus to lunch today. > > > |
From: Hippo M. <hip...@gm...> - 2022-06-03 02:12:33
|
> However, it turns out that the Cédric Dufour version runs under Python 3. > I decided to take the plunge and try it, and I very easily got it to work!!! ... but unfortunately, I still have to deal with tmda-cgi. I found several versions of it on line and tried each of them, but none work in conjunction with this Python 3 version of TMDA. And it would be major piece of work to convert any of the existing tmda-cgi releases to Python 3, and therefore, I believe I will have to write my own replacement for tmda-cgi in order to accomplish this. I already have been using a command-line utility that I wrote a number of years ago (in the Ruby language) to go through my pending emails and either release, blacklist, whitelist, or delete them via invocations of "tmda-pending". But I want a web-based app for doing this, and so I guess I will have to use my command-line code as a starting point in order to write my own web-based tmda-cgi-like utility. Or perhaps is there already some sort of alternative web-based front end to tmda? I haven't been able to find such a thing, but perhaps I am missing something. Thanks in advance for any thoughts or suggestions. -- hip...@gm... Take a hippopotamus to lunch today. On Thu, Jun 2, 2022 at 1:44 AM Hippo Man <hip...@gm...> wrote: > > I really tried to get TMDA working with python3 but eventually I gave up >> and decided to just stick with python2. Admittedly, my python skills are >> poor, and I didn't want to spend more hours trying to get it to work. >> >> Hopefully you'll make better progress than I did! >> >> Chris >> > > Thank you! > > And yes, I understand, I spent way, *way* too much time trying to convert > the original Python 2 TMDA code to Python 3. It ended up being a big > mess, and I finally gave up. > > However, it turns out that the Cédric Dufour version runs under Python 3. > I decided to take the plunge and try it, and I very easily got it to > work!!! > ... as follows: > > % cd [work directory] > > % git clone https://github.com/cedric-dufour/tmda.git > > % cd tmda > > % sudo python3 setup.py install > > This installs the Python 3 TMDA executables into /usr/local/bin , and they > all work for me! It turns out that the "debian" subdirectory that I was > asking about in my previous message is totally irrelevant. The only > purpose of that subdirectory is for facilitating the creation of a debian > APT package for TMDA. There is no need to do that, since the steps I > outlined above will perform a full TMDA installation on your own linux > machine. > > After performing those steps, I only had to make one tiny change to my > existing TMDA configuration: > > Near the top of /etc/tmdarc is the following line of code: > os.makedirs(LOGDIR, 0755) > > That simply needs to be changed to this: > os.makedirs(LOGDIR, 0o755) > > (*i.e.*, put a lower-case letter "o" between the zero and the seven) > > Some of my own scripts had to be changed, because I had the original > Python 2 TMDA code in /usr/local/tmda/bin, and I had to change a small > number of references to that directory into /usr/local/bin. But to be > clear, > those changes are in my own code which *calls* TMDA executables ... > not in any of the Python 3 TMDA code itself. > > One caveat is that I do not use TMDA for challenge-response these > days, and I have never used it for tagging ... only for whitelisting, for > blacklisting, and for putting unfamiliar messages into the Pending queue > so I can inspect them via the TMDA-cgi web software and decide what > to do with them. Therefore, I don't know if you would encounter > challenge-response or tagging issues. However, given how well the > Python 3 version is working for me, I am optimistic that those functions > would also probably work. > > If you or anyone else want to try this Python 3 version of TMDA, and > if problems are encountered, I'm glad to offer whatever help I can here > in this mailing list. > <https://github.com/cedric-dufour/tmda.git> > -- > hip...@gm... > Take a hippopotamus to lunch today. > > > >> >> On Wed, 1 Jun 2022, Hippo Man wrote: >> > I have done a "git clone" of the python3 version of TMDA from here: >> > https://github.com/cedric-dufour/tmda.git >> > >> > And I have done a "python3 setup.py install". >> > >> > I see that it created a TMDA directory tree under /opt/local/share/tmda >> > >> > In the cloned git directory, there is also a "debian" subdirectory, and >> since >> > I am running under Debian-11, I want to install that debian-specific >> code. >> > However, this debian code was not installed anywhere after my run of >> > "python3 setup.py install", and I could not find any instructions for >> how >> > to install that debian code. >> > >> > Futhermore, in the documentation that came with this TMDA version, >> > there are a few references to http://wiki.tmda.net, but that web site >> > no longer exists. >> > >> > Is there any place where I could find instructions for how to do a full, >> > complete TMDA install of this python3 version on my Debian host? >> > >> > Thanks in advance for any pointers and help! >> > >> > -- >> > hip...@gm... >> > Take a hippopotamus to lunch today. >> > >> > >> > On Wed, Jun 1, 2022 at 10:14 AM Hippo Man <hip...@gm...> wrote: >> > Thank you very much. >> > >> > And I'm glad to see that this mailing list is actually still alive! >> > >> > Also, I went to your github site, and see that there are links there >> for two >> > Python3 forks. TMDA is the only Python2 code on my server, and I very >> > much want to get rid of Python2 completely. I'm going to check out both >> of >> > those Python3 TMDA forks, and I'm happy that they exist. >> > >> > -- >> > hip...@gm... >> > Take a hippopotamus to lunch today. >> > >> > >> > On Wed, Jun 1, 2022 at 1:17 AM Chris Caputo <cc...@al...> wrote: >> > Nice work! >> > >> > BTW, I maintain https://github.com/ccaputo/TMDAretro in case >> anyone has >> > trouble installing TMDA these days. >> > >> > Chris >> > >> > On Tue, 31 May 2022, Hippo Man wrote: >> > > I figured out the answer to my question. >> > > >> > > In case anyone might come to this mailing list some >> > > day and wants to know how I solved my problem, here >> > > is how I did so ... >> > > >> > > I can implement item #2 in my list below by means of >> > > an "incoming" filter. I created a "holdlist" file to contain >> > > match patterns for the set of addresses that I want to >> > > automatically put into a pending state, and I put the >> > > following rule into my incoming filter ... >> > > >> > > from-file ~/.tmda/lists/holdlist hold >> > > >> > > Now, I have succcessfully implemented all three items >> > > in my list. >> > > -- >> > > hip...@gm... >> > > Take a hippopotamus to lunch today. >> > > >> > > >> > > On Mon, May 30, 2022 at 7:51 PM Hippo Man <hip...@gm...> >> wrote: >> > > I've been using TMDA for something like 15 years, and I >> am still >> > > getting lots of benefit from it and am still very happy with it. >> > > >> > > If there is anyone who is actually reading this email list >> these days, >> > > I have a question about the use of TMDA. >> > > >> > > My question is this: I want to set up the following filtering >> rules ... >> > > >> > > (1) If the sender's email address is on a very small list (less >> than a >> > > dozen entries), I'd like the sender to be blacklisted. >> > > >> > > (2) if the sender's email address is on a very small list (less >> than a >> > > dozen entries), I'd like the email to be held in the pending >> queue. >> > > >> > > (3) If any email arrives whose sender address is not in either >> of those >> > > two small lists, I'd like it to be delivered. >> > > >> > > If all I had to deal with were item 1 and item 3, I could set >> ACTION_INCOMING >> > > to "ok" and simply put the unwanted sender addresses into a >> blacklist file. >> > > >> > > However, I don't know how to also handle item 2 along with >> items 1 and 3. >> > > Is what I want to do even possible with TMDA? >> > > >> > > If anyone is actually reading this email list and can answer my >> question, >> > > I will be greatly appreciative! >> > > >> > > -- >> > > hip...@gm... >> > > Take a hippopotamus to lunch today. > > |
From: Hippo M. <hip...@gm...> - 2022-06-02 05:44:42
|
> I really tried to get TMDA working with python3 but eventually I gave up > and decided to just stick with python2. Admittedly, my python skills are > poor, and I didn't want to spend more hours trying to get it to work. > > Hopefully you'll make better progress than I did! > > Chris > Thank you! And yes, I understand, I spent way, *way* too much time trying to convert the original Python 2 TMDA code to Python 3. It ended up being a big mess, and I finally gave up. However, it turns out that the Cédric Dufour version runs under Python 3. I decided to take the plunge and try it, and I very easily got it to work!!! ... as follows: % cd [work directory] % git clone https://github.com/cedric-dufour/tmda.git % cd tmda % sudo python3 setup.py install This installs the Python 3 TMDA executables into /usr/local/bin , and they all work for me! It turns out that the "debian" subdirectory that I was asking about in my previous message is totally irrelevant. The only purpose of that subdirectory is for facilitating the creation of a debian APT package for TMDA. There is no need to do that, since the steps I outlined above will perform a full TMDA installation on your own linux machine. After performing those steps, I only had to make one tiny change to my existing TMDA configuration: Near the top of /etc/tmdarc is the following line of code: os.makedirs(LOGDIR, 0755) That simply needs to be changed to this: os.makedirs(LOGDIR, 0o755) (*i.e.*, put a lower-case letter "o" between the zero and the seven) Some of my own scripts had to be changed, because I had the original Python 2 TMDA code in /usr/local/tmda/bin, and I had to change a small number of references to that directory into /usr/local/bin. But to be clear, those changes are in my own code which *calls* TMDA executables ... not in any of the Python 3 TMDA code itself. One caveat is that I do not use TMDA for challenge-response these days, and I have never used it for tagging ... only for whitelisting, for blacklisting, and for putting unfamiliar messages into the Pending queue so I can inspect them via the TMDA-cgi web software and decide what to do with them. Therefore, I don't know if you would encounter challenge-response or tagging issues. However, given how well the Python 3 version is working for me, I am optimistic that those functions would also probably work. If you or anyone else want to try this Python 3 version of TMDA, and if problems are encountered, I'm glad to offer whatever help I can here in this mailing list. <https://github.com/cedric-dufour/tmda.git> -- hip...@gm... Take a hippopotamus to lunch today. > > On Wed, 1 Jun 2022, Hippo Man wrote: > > I have done a "git clone" of the python3 version of TMDA from here: > > https://github.com/cedric-dufour/tmda.git > > > > And I have done a "python3 setup.py install". > > > > I see that it created a TMDA directory tree under /opt/local/share/tmda > > > > In the cloned git directory, there is also a "debian" subdirectory, and > since > > I am running under Debian-11, I want to install that debian-specific > code. > > However, this debian code was not installed anywhere after my run of > > "python3 setup.py install", and I could not find any instructions for how > > to install that debian code. > > > > Futhermore, in the documentation that came with this TMDA version, > > there are a few references to http://wiki.tmda.net, but that web site > > no longer exists. > > > > Is there any place where I could find instructions for how to do a full, > > complete TMDA install of this python3 version on my Debian host? > > > > Thanks in advance for any pointers and help! > > > > -- > > hip...@gm... > > Take a hippopotamus to lunch today. > > > > > > On Wed, Jun 1, 2022 at 10:14 AM Hippo Man <hip...@gm...> wrote: > > Thank you very much. > > > > And I'm glad to see that this mailing list is actually still alive! > > > > Also, I went to your github site, and see that there are links there for > two > > Python3 forks. TMDA is the only Python2 code on my server, and I very > > much want to get rid of Python2 completely. I'm going to check out both > of > > those Python3 TMDA forks, and I'm happy that they exist. > > > > -- > > hip...@gm... > > Take a hippopotamus to lunch today. > > > > > > On Wed, Jun 1, 2022 at 1:17 AM Chris Caputo <cc...@al...> wrote: > > Nice work! > > > > BTW, I maintain https://github.com/ccaputo/TMDAretro in case > anyone has > > trouble installing TMDA these days. > > > > Chris > > > > On Tue, 31 May 2022, Hippo Man wrote: > > > I figured out the answer to my question. > > > > > > In case anyone might come to this mailing list some > > > day and wants to know how I solved my problem, here > > > is how I did so ... > > > > > > I can implement item #2 in my list below by means of > > > an "incoming" filter. I created a "holdlist" file to contain > > > match patterns for the set of addresses that I want to > > > automatically put into a pending state, and I put the > > > following rule into my incoming filter ... > > > > > > from-file ~/.tmda/lists/holdlist hold > > > > > > Now, I have succcessfully implemented all three items > > > in my list. > > > -- > > > hip...@gm... > > > Take a hippopotamus to lunch today. > > > > > > > > > On Mon, May 30, 2022 at 7:51 PM Hippo Man <hip...@gm...> > wrote: > > > I've been using TMDA for something like 15 years, and I am > still > > > getting lots of benefit from it and am still very happy with it. > > > > > > If there is anyone who is actually reading this email list these > days, > > > I have a question about the use of TMDA. > > > > > > My question is this: I want to set up the following filtering > rules ... > > > > > > (1) If the sender's email address is on a very small list (less > than a > > > dozen entries), I'd like the sender to be blacklisted. > > > > > > (2) if the sender's email address is on a very small list (less > than a > > > dozen entries), I'd like the email to be held in the pending > queue. > > > > > > (3) If any email arrives whose sender address is not in either > of those > > > two small lists, I'd like it to be delivered. > > > > > > If all I had to deal with were item 1 and item 3, I could set > ACTION_INCOMING > > > to "ok" and simply put the unwanted sender addresses into a > blacklist file. > > > > > > However, I don't know how to also handle item 2 along with items > 1 and 3. > > > Is what I want to do even possible with TMDA? > > > > > > If anyone is actually reading this email list and can answer my > question, > > > I will be greatly appreciative! > > > > > > -- > > > hip...@gm... > > > Take a hippopotamus to lunch today. |
From: Chris C. <cc...@al...> - 2022-06-02 02:42:31
|
I really tried to get TMDA working with python3 but eventually I gave up and decided to just stick with python2. Admittedly, my python skills are poor, and I didn't want to spend more hours trying to get it to work. Hopefully you'll make better progress than I did! Chris On Wed, 1 Jun 2022, Hippo Man wrote: > I have done a "git clone" of the python3 version of TMDA from here: > https://github.com/cedric-dufour/tmda.git > > And I have done a "python3 setup.py install". > > I see that it created a TMDA directory tree under /opt/local/share/tmda > > In the cloned git directory, there is also a "debian" subdirectory, and since > I am running under Debian-11, I want to install that debian-specific code. > However, this debian code was not installed anywhere after my run of > "python3 setup.py install", and I could not find any instructions for how > to install that debian code. > > Futhermore, in the documentation that came with this TMDA version, > there are a few references to http://wiki.tmda.net, but that web site > no longer exists. > > Is there any place where I could find instructions for how to do a full, > complete TMDA install of this python3 version on my Debian host? > > Thanks in advance for any pointers and help! > > -- > hip...@gm... > Take a hippopotamus to lunch today. > > > On Wed, Jun 1, 2022 at 10:14 AM Hippo Man <hip...@gm...> wrote: > Thank you very much. > > And I'm glad to see that this mailing list is actually still alive! > > Also, I went to your github site, and see that there are links there for two > Python3 forks. TMDA is the only Python2 code on my server, and I very > much want to get rid of Python2 completely. I'm going to check out both of > those Python3 TMDA forks, and I'm happy that they exist. > > -- > hip...@gm... > Take a hippopotamus to lunch today. > > > On Wed, Jun 1, 2022 at 1:17 AM Chris Caputo <cc...@al...> wrote: > Nice work! > > BTW, I maintain https://github.com/ccaputo/TMDAretro in case anyone has > trouble installing TMDA these days. > > Chris > > On Tue, 31 May 2022, Hippo Man wrote: > > I figured out the answer to my question. > > > > In case anyone might come to this mailing list some > > day and wants to know how I solved my problem, here > > is how I did so ... > > > > I can implement item #2 in my list below by means of > > an "incoming" filter. I created a "holdlist" file to contain > > match patterns for the set of addresses that I want to > > automatically put into a pending state, and I put the > > following rule into my incoming filter ... > > > > from-file ~/.tmda/lists/holdlist hold > > > > Now, I have succcessfully implemented all three items > > in my list. > > -- > > hip...@gm... > > Take a hippopotamus to lunch today. > > > > > > On Mon, May 30, 2022 at 7:51 PM Hippo Man <hip...@gm...> wrote: > > I've been using TMDA for something like 15 years, and I am still > > getting lots of benefit from it and am still very happy with it. > > > > If there is anyone who is actually reading this email list these days, > > I have a question about the use of TMDA. > > > > My question is this: I want to set up the following filtering rules ... > > > > (1) If the sender's email address is on a very small list (less than a > > dozen entries), I'd like the sender to be blacklisted. > > > > (2) if the sender's email address is on a very small list (less than a > > dozen entries), I'd like the email to be held in the pending queue. > > > > (3) If any email arrives whose sender address is not in either of those > > two small lists, I'd like it to be delivered. > > > > If all I had to deal with were item 1 and item 3, I could set ACTION_INCOMING > > to "ok" and simply put the unwanted sender addresses into a blacklist file. > > > > However, I don't know how to also handle item 2 along with items 1 and 3. > > Is what I want to do even possible with TMDA? > > > > If anyone is actually reading this email list and can answer my question, > > I will be greatly appreciative! > > > > -- > > hip...@gm... > > Take a hippopotamus to lunch today. |
From: Hippo M. <hip...@gm...> - 2022-06-02 02:32:06
|
I have done a "git clone" of the python3 version of TMDA from here: https://github.com/cedric-dufour/tmda.git And I have done a "python3 setup.py install". I see that it created a TMDA directory tree under /opt/local/share/tmda In the cloned git directory, there is also a "debian" subdirectory, and since I am running under Debian-11, I want to install that debian-specific code. However, this debian code was not installed anywhere after my run of "python3 setup.py install", and I could not find any instructions for how to install that debian code. Futhermore, in the documentation that came with this TMDA version, there are a few references to http://wiki.tmda.net, but that web site no longer exists. Is there any place where I could find instructions for how to do a full, complete TMDA install of this python3 version on my Debian host? Thanks in advance for any pointers and help! -- hip...@gm... Take a hippopotamus to lunch today. On Wed, Jun 1, 2022 at 10:14 AM Hippo Man <hip...@gm...> wrote: > Thank you very much. > > And I'm glad to see that this mailing list is actually still alive! > > Also, I went to your github site, and see that there are links there for > two > Python3 forks. TMDA is the only Python2 code on my server, and I very > much want to get rid of Python2 completely. I'm going to check out both of > those Python3 TMDA forks, and I'm happy that they exist. > > -- > hip...@gm... > Take a hippopotamus to lunch today. > > > On Wed, Jun 1, 2022 at 1:17 AM Chris Caputo <cc...@al...> wrote: > >> Nice work! >> >> BTW, I maintain https://github.com/ccaputo/TMDAretro in case anyone has >> trouble installing TMDA these days. >> >> Chris >> >> On Tue, 31 May 2022, Hippo Man wrote: >> > I figured out the answer to my question. >> > >> > In case anyone might come to this mailing list some >> > day and wants to know how I solved my problem, here >> > is how I did so ... >> > >> > I can implement item #2 in my list below by means of >> > an "incoming" filter. I created a "holdlist" file to contain >> > match patterns for the set of addresses that I want to >> > automatically put into a pending state, and I put the >> > following rule into my incoming filter ... >> > >> > from-file ~/.tmda/lists/holdlist hold >> > >> > Now, I have succcessfully implemented all three items >> > in my list. >> > -- >> > hip...@gm... >> > Take a hippopotamus to lunch today. >> > >> > >> > On Mon, May 30, 2022 at 7:51 PM Hippo Man <hip...@gm...> wrote: >> > I've been using TMDA for something like 15 years, and I am still >> > getting lots of benefit from it and am still very happy with it. >> > >> > If there is anyone who is actually reading this email list these days, >> > I have a question about the use of TMDA. >> > >> > My question is this: I want to set up the following filtering rules ... >> > >> > (1) If the sender's email address is on a very small list (less than a >> > dozen entries), I'd like the sender to be blacklisted. >> > >> > (2) if the sender's email address is on a very small list (less than a >> > dozen entries), I'd like the email to be held in the pending queue. >> > >> > (3) If any email arrives whose sender address is not in either of those >> > two small lists, I'd like it to be delivered. >> > >> > If all I had to deal with were item 1 and item 3, I could set >> ACTION_INCOMING >> > to "ok" and simply put the unwanted sender addresses into a blacklist >> file. >> > >> > However, I don't know how to also handle item 2 along with items 1 and >> 3. >> > Is what I want to do even possible with TMDA? >> > >> > If anyone is actually reading this email list and can answer my >> question, >> > I will be greatly appreciative! >> > >> > -- >> > hip...@gm... >> > Take a hippopotamus to lunch today. > > |
From: Hippo M. <hip...@gm...> - 2022-06-01 14:15:00
|
Thank you very much. And I'm glad to see that this mailing list is actually still alive! Also, I went to your github site, and see that there are links there for two Python3 forks. TMDA is the only Python2 code on my server, and I very much want to get rid of Python2 completely. I'm going to check out both of those Python3 TMDA forks, and I'm happy that they exist. -- hip...@gm... Take a hippopotamus to lunch today. On Wed, Jun 1, 2022 at 1:17 AM Chris Caputo <cc...@al...> wrote: > Nice work! > > BTW, I maintain https://github.com/ccaputo/TMDAretro in case anyone has > trouble installing TMDA these days. > > Chris > > On Tue, 31 May 2022, Hippo Man wrote: > > I figured out the answer to my question. > > > > In case anyone might come to this mailing list some > > day and wants to know how I solved my problem, here > > is how I did so ... > > > > I can implement item #2 in my list below by means of > > an "incoming" filter. I created a "holdlist" file to contain > > match patterns for the set of addresses that I want to > > automatically put into a pending state, and I put the > > following rule into my incoming filter ... > > > > from-file ~/.tmda/lists/holdlist hold > > > > Now, I have succcessfully implemented all three items > > in my list. > > -- > > hip...@gm... > > Take a hippopotamus to lunch today. > > > > > > On Mon, May 30, 2022 at 7:51 PM Hippo Man <hip...@gm...> wrote: > > I've been using TMDA for something like 15 years, and I am still > > getting lots of benefit from it and am still very happy with it. > > > > If there is anyone who is actually reading this email list these days, > > I have a question about the use of TMDA. > > > > My question is this: I want to set up the following filtering rules ... > > > > (1) If the sender's email address is on a very small list (less than a > > dozen entries), I'd like the sender to be blacklisted. > > > > (2) if the sender's email address is on a very small list (less than a > > dozen entries), I'd like the email to be held in the pending queue. > > > > (3) If any email arrives whose sender address is not in either of those > > two small lists, I'd like it to be delivered. > > > > If all I had to deal with were item 1 and item 3, I could set > ACTION_INCOMING > > to "ok" and simply put the unwanted sender addresses into a blacklist > file. > > > > However, I don't know how to also handle item 2 along with items 1 and 3. > > Is what I want to do even possible with TMDA? > > > > If anyone is actually reading this email list and can answer my question, > > I will be greatly appreciative! > > > > -- > > hip...@gm... > > Take a hippopotamus to lunch today. |
From: Chris C. <cc...@al...> - 2022-06-01 05:43:49
|
Nice work! BTW, I maintain https://github.com/ccaputo/TMDAretro in case anyone has trouble installing TMDA these days. Chris On Tue, 31 May 2022, Hippo Man wrote: > I figured out the answer to my question. > > In case anyone might come to this mailing list some > day and wants to know how I solved my problem, here > is how I did so ... > > I can implement item #2 in my list below by means of > an "incoming" filter. I created a "holdlist" file to contain > match patterns for the set of addresses that I want to > automatically put into a pending state, and I put the > following rule into my incoming filter ... > > from-file ~/.tmda/lists/holdlist hold > > Now, I have succcessfully implemented all three items > in my list. > -- > hip...@gm... > Take a hippopotamus to lunch today. > > > On Mon, May 30, 2022 at 7:51 PM Hippo Man <hip...@gm...> wrote: > I've been using TMDA for something like 15 years, and I am still > getting lots of benefit from it and am still very happy with it. > > If there is anyone who is actually reading this email list these days, > I have a question about the use of TMDA. > > My question is this: I want to set up the following filtering rules ... > > (1) If the sender's email address is on a very small list (less than a > dozen entries), I'd like the sender to be blacklisted. > > (2) if the sender's email address is on a very small list (less than a > dozen entries), I'd like the email to be held in the pending queue. > > (3) If any email arrives whose sender address is not in either of those > two small lists, I'd like it to be delivered. > > If all I had to deal with were item 1 and item 3, I could set ACTION_INCOMING > to "ok" and simply put the unwanted sender addresses into a blacklist file. > > However, I don't know how to also handle item 2 along with items 1 and 3. > Is what I want to do even possible with TMDA? > > If anyone is actually reading this email list and can answer my question, > I will be greatly appreciative! > > -- > hip...@gm... > Take a hippopotamus to lunch today. |
From: Hippo M. <hip...@gm...> - 2022-05-31 21:59:54
|
I figured out the answer to my question. In case anyone might come to this mailing list some day and wants to know how I solved my problem, here is how I did so ... I can implement item #2 in my list below by means of an "incoming" filter. I created a "holdlist" file to contain match patterns for the set of addresses that I want to automatically put into a pending state, and I put the following rule into my incoming filter ... from-file ~/.tmda/lists/holdlist hold Now, I have succcessfully implemented all three items in my list. -- hip...@gm... Take a hippopotamus to lunch today. On Mon, May 30, 2022 at 7:51 PM Hippo Man <hip...@gm...> wrote: > I've been using TMDA for something like 15 years, and I am still > getting lots of benefit from it and am still very happy with it. > > If there is anyone who is actually reading this email list these days, > I have a question about the use of TMDA. > > My question is this: I want to set up the following filtering rules ... > > (1) If the sender's email address is on a very small list (less than a > dozen entries), I'd like the sender to be blacklisted. > > (2) if the sender's email address is on a very small list (less than a > dozen entries), I'd like the email to be held in the pending queue. > > (3) If any email arrives whose sender address is not in either of those > two small lists, I'd like it to be delivered. > > If all I had to deal with were item 1 and item 3, I could set > ACTION_INCOMING > to "ok" and simply put the unwanted sender addresses into a blacklist file. > > However, I don't know how to also handle item 2 along with items 1 and 3. > Is what I want to do even possible with TMDA? > > If anyone is actually reading this email list and can answer my question, > I will be greatly appreciative! > > -- > hip...@gm... > Take a hippopotamus to lunch today. > |
From: Hippo M. <hip...@gm...> - 2022-05-30 23:51:56
|
I've been using TMDA for something like 15 years, and I am still getting lots of benefit from it and am still very happy with it. If there is anyone who is actually reading this email list these days, I have a question about the use of TMDA. My question is this: I want to set up the following filtering rules ... (1) If the sender's email address is on a very small list (less than a dozen entries), I'd like the sender to be blacklisted. (2) if the sender's email address is on a very small list (less than a dozen entries), I'd like the email to be held in the pending queue. (3) If any email arrives whose sender address is not in either of those two small lists, I'd like it to be delivered. If all I had to deal with were item 1 and item 3, I could set ACTION_INCOMING to "ok" and simply put the unwanted sender addresses into a blacklist file. However, I don't know how to also handle item 2 along with items 1 and 3. Is what I want to do even possible with TMDA? If anyone is actually reading this email list and can answer my question, I will be greatly appreciative! -- hip...@gm... Take a hippopotamus to lunch today. |
From: Chris C. <cc...@al...> - 2019-06-04 06:43:11
|
I need TMDA to continue working under Python 2.7, so I created TMDAretro. It is available at: https://github.com/ccaputo/TMDAretro Also, it is on PyPI, so the following is an easy way to test it out: pip2 install --upgrade --user TMDAretro Feedback and fixes most welcome. Long live TMDA! Enjoy, Chris |
From: Chloe <sta...@ol...> - 2017-01-13 05:10:16
|
The server configuration says to edit ~/.tmda/config and create ~/.tmda/crypt_key. But how do you do this when using virtual mailboxes? http://tmda.sourceforge.net/cgi-bin/moin.cgi/ServerConfiguration *main.cf* - Postfix virtual_mailbox_domains = domain1 oliveyou.net domain2 domain3 virtual_mailbox_base = /var/mail/vhosts virtual_mailbox_maps = hash:/etc/postfix/vmailbox virtual_minimum_uid = 497 virtual_uid_maps = static:497 virtual_gid_maps = static:510 virtual_alias_maps = hash:/etc/postfix/virtual http://superuser.com/questions/1165815/how-do-you-configure-tmda-for-virtual-email-addresses-if-the-configuration-refer |
From: David O. <dav...@me...> - 2016-12-01 22:53:34
|
Thanks Guys, I used TMDA from about 2,000 to around 2003, when it became impractical for me to run a home mail server. I loved it, and it kept spam to near zero. Paul, I may take you up on the PR offer, but I am experimenting with some wild things right now, to see how they work. If what I am trying works out, I'll be back here to post. It's great to know there is still an active group. I look forward to following your comments. David Overman On Dec 01, 2016, at 02:31 PM, Michael Allan <mi...@ze...> wrote: I still use it. It seems to work perfectly for challenge/response. It's the main reason I still run my own mail server. -- Michael Allan Toronto, +1 416 699 9528 http://reluk.ca/ ------------------------------------------------------------------------------ _______________________________________________ tmda-users mailing list tmd...@li... https://lists.sourceforge.net/lists/listinfo/tmda-users |
From: Michael A. <mi...@ze...> - 2016-12-01 20:31:02
|
I still use it. It seems to work perfectly for challenge/response. It's the main reason I still run my own mail server. -- Michael Allan Toronto, +1 416 699 9528 http://reluk.ca/ |
From: Paul J. <pj...@pl...> - 2016-12-01 13:57:32
|
I did a bit of forward porting (to python 3.4, current at the time) and got permission from the author to rename it 'TMDAng'. Besides the forward-port, I also made it a full pypi package to make it easier to install. I use it for challenge-response via email. I'm happy to take PRs to fix whatever. --pj On 11/30/2016 11:31 PM, David Overman wrote: > Greetings, > > I see that there is a github-fork. Guess challenge response is dead, > by looking around on the internet. > I am getting almost the same functionality with ezmlm. Just configured > the list as a plain old email address. > subscribe is a pain though. i.e. " me-...@my..." > <mailto:me-...@my...%22> I would like to get tmda going > again with > vpopmail,on a qmail toaster. > > Recently ASK, Active Spam Killer, has been deprecated. This is similar > software, which can be found on sourceforge. I have a copy of the > documentaion, if anyone needs it. The link no longer works at the SF > page, or you can get your own copy by using waybackmachine. > > Is anyone still using TMDA, or tmda-cgi. do the updated versions work? > I am trying to follow, what I can piece together. > > thanks, > David > > > ------------------------------------------------------------------------------ > > > _______________________________________________ > tmda-users mailing list > tmd...@li... > https://lists.sourceforge.net/lists/listinfo/tmda-users |
From: David O. <dav...@me...> - 2016-12-01 04:31:16
|
Greetings, I see that there is a github-fork. Guess challenge response is dead, by looking around on the internet. I am getting almost the same functionality with ezmlm. Just configured the list as a plain old email address. subscribe is a pain though. i.e. " me-...@my..." I would like to get tmda going again with vpopmail,on a qmail toaster. Recently ASK, Active Spam Killer, has been deprecated. This is similar software, which can be found on sourceforge. I have a copy of the documentaion, if anyone needs it. The link no longer works at the SF page, or you can get your own copy by using waybackmachine. Is anyone still using TMDA, or tmda-cgi. do the updated versions work? I am trying to follow, what I can piece together. thanks, David |
From: David O. <dav...@me...> - 2016-11-06 20:30:57
|
I installed tmda on qmail/ The confirmation/acceptance emails go out, but the message is never delivered. qmail/courier-imap/vpopmail/debian jessie |
From: Paul J. <pj...@pl...> - 2016-11-06 13:54:44
|
This kind of issue is why I launched the TMDAng project. On November 5, 2016 10:47:21 PM EDT, David Overman <dav...@me...> wrote: >GitHub Says read INSTALL. INSTALL says got to website or wiki. >half of links are broken at website and at wiki. > >qmail-debian > > > > >------------------------------------------------------------------------ > >------------------------------------------------------------------------------ >Developer Access Program for Intel Xeon Phi Processors >Access to Intel Xeon Phi processor-based developer platforms. >With one year of Intel Parallel Studio XE. >Training and support from Colfax. >Order your platform today. http://sdm.link/xeonphi > >------------------------------------------------------------------------ > >_______________________________________________ >tmda-users mailing list >tmd...@li... >https://lists.sourceforge.net/lists/listinfo/tmda-users -- Sent from my Android device with K-9 Mail. Please excuse my brevity. |
From: David O. <dav...@me...> - 2016-11-06 02:47:40
|
GitHub Says read INSTALL. INSTALL says got to website or wiki. half of links are broken at website and at wiki. qmail-debian |
From: Anne M. H. <ha...@tx...> - 2015-06-11 23:41:36
|
I'm not getting notices of pending email via cron. I suspect it has to do with a zero length .pendingcache. This is for a new use where I mostly cloned my environment. His cron job executes 05 9,11,13,15,17,18 * * * /bin/sh $HOME/.tmda/tmda.sh 2> /dev/null There are 4 messages in .tmda/pending: 1434053133.26415.msg 1434056996.28754.msg 1434057706.29361.msg 1434064527.33804.msg 1434065391.36130.msg $HOME/.tmda/tmda.sh contains: $TMDA_BINDIR/tmda-pending -Cbs > /tmp/$$ if test -s /tmp/$$; then mail -s 'TMDA Pending Summary' me...@co... < /tmp/$$ fi #rm /tmp/$$ However /tmp/$$ is always zero length, and he never receives a "TMDA Pending Summary" via email. My tmda, however, works great. Any advice greatly appreciated. |
From: Kevin G. <kev...@om...> - 2014-10-21 03:19:10
|
On 10/20/2014 08:42 AM, Ron Stordahl wrote: <snip> > In order to send emails with a header that replaces > base@mydomain everywhere with alias@mydomain when sending an e-mail > to joe@joesdomain I am using this TMDA outgoing filter: > > to joe@joesdomain tag from explicit=alias@mydomain Return-Path explicit=alias@mydomain X-Primary-Address alias@mydomain > <snip> > > I also want to perform an action much like: > > # Add outgoing message recipients to whitelist to joe@joesdomain tag > envelope bare from bare=append > > > That format however is for the 'bare' format. I have not been able > to figure out how to include that ability within my 'explicit=' > filter so as to simultaneously adding 'joe' to my whitelist while > replacing base@mydomain with alias@mydomain. > If I understand you correctly, you want "joe" to only see the "alias" address. In that case, whitelisting is probably not a good idea. Once joe is in your whitelist, future messages to joe will likely use your default "base" address. This depends on your filter configuration, but typically that's what the whitelist means: "This person checks out, and is permitted to see and use my real address." I think the more practical solution is to adjust your incoming filters to handle joe the way you want. If the whitelisting idea was to prevent challenges, just add an incoming filter rule to accept mail from joe's address. You could also create a list of people like joe, who only get to see the "alias" address, and use a "from-file" incoming filter and a "to-file" outgoing filter pointing to your list, so you can avoid having to write the addresses in both filter files. -Kevin |
From: Ron S. <ron...@ya...> - 2014-10-20 15:42:13
|
Using qMail I can create any number of aliases off the base address, for example with a base address of base@mydomain I can create alias@mydomain. In order to send emails with a header that replaces base@mydomain everywhere with alias@mydomain when sending an e-mail to joe@joesdomain I am using this TMDA outgoing filter: to joe@joesdomain tag from explicit=alias@mydomain Return-Path explicit=alias@mydomain X-Primary-Address alias@mydomain Using this filter I can send an email to joe from any e-mail client configured for base@mydomain and the e-mail header will be translated such that all references to base@mydomain will be replaced by alias@mydomain, thus completely hiding my 'base' address. I also want to perform an action much like: # Add outgoing message recipients to whitelist to joe@joesdomain tag envelope bare from bare=append That format however is for the 'bare' format. I have not been able to figure out how to include that ability within my 'explicit=' filter so as to simultaneously adding 'joe' to my whitelist while replacing base@mydomain with alias@mydomain. A little help is needed.... Thanks Ron Stordahl |
From: Ron S. <ron...@ya...> - 2014-08-14 17:05:27
|
I am testing TMDA as offered by a service provider. My only access to settings is via TMDA-cgi. Today I encountered a user whose system uses Bounce Address Tag Validation. In brief this means that his e-mail server prefixes the "Return-Path:" address with something like: prvs-29596b788= and changes this perhaps daily. As a result if that correspondent's address had been validated yesterday, today it might have changed the prefix and will require validation again..and again... A solution, requiring effort, is to manually white list, replacing the BATV string with a '*'. If the validation was based instead on the "From:" address this BATV issue would not occur, but I suppose other issues might arise, which probably would explain why "Return-Path:" was used. Ron Stordahl Bounce Address Tag Validation - Wikipedia, the free encyclopedia In computing, Bounce Address Tag Validation (BATV) is a method, defined in an Internet Draft, for determining whether the bounce address specified in an E-mail message is valid. It is designed to reject backscatter, that is, bounce messages to forged return addresses. View on en.wikipedia.org Preview by Yahoo |
From: Ron S. <ron...@ya...> - 2014-08-11 02:45:16
|
Thanks for the response Toby. I have some concerns: Will TMDA continue into the future, or fade away due to as you said.."I fear it (tmda)may eventually die, unless someone puts in the effort of porting it to a modern python version..." That would be a shame! If one of the developers reads this I hope he will comment about that possibility. I made reference to a system called 'Traveler' http://www.vsta.org/spam/Traveler.html which takes a different approach..assigning a separate email address to be used by each correspondent. You suggest that perhaps this could be implemented through tmda-ofmipd. I had never heard of tmda-ofmipd, but I searched for it and have to admit I don't understand it. Does it run on the server? It would seem to be useful only if this were true as I want to be able to be able to use email clients on various machines including smart phones taking advantage of tmda. I am able to use TMDA only via an e-mail provider who provides it, my control is only through tmda-cgi. For now that will be my only means of using TMDA, perhaps this will be sufficient. For now I am only experimenting with TMDA. Should I decide this is what I want I then have to start the tedious job of making the change. Lots of address changes for my correspondents, mailing lists and web sites. Perhaps this Fall I will find the time. Ron Stordahl Traveler, a Spam-resistant E-mail System Overview Traveler is an E-mail system in use by me, Andy Valencia, handling E-mail for my personal domains as well as my operating system projects, vsta.org and forthos.org. View on www.vsta.org Preview by Yahoo On Sunday, August 10, 2014 1:31 PM, Toby Cubitt <to...@dr...> wrote: On Sun, Aug 10, 2014 at 10:55:20AM -0700, Ron Stordahl wrote: > By experimenting I found that if I post the keyword address into > Lists\Revoked and click Save, that keyword is revoked. However simply > removing it from that screen and clicking Save will 'unrevoke' it. > This is satisfactory, wish it had been documented, maybe it was, but I > couldn't find it. Yes, that's the method I was advocating. I can't remember whether I read about it somewhere, or just figured it out. > I am under the impression that TMDA isn't much used. I think it's still used, but is essentially no longer developed or maintained. I fear it may eventually die, unless someone puts in the effort of porting it to a modern python version... But for now, it works fine and is pretty feature-complete. > I don't think the objections regarding challenge-response are very > significant. All in all it seems like a pretty good system. Indeed. > It does fall down with respect to mailing lists. Perhaps at the time > of the design of TMDA, mailing lists were not refusing postings from > unmatching e-mail addresses, No, mailing lists have been doing this since time immemorial! > i.e. other than one you registered with. Since I know of no way for > the mail server to substitute the keyword address for my real address > when posting i can't see how one can successfully use TMDA with > mailing lists other than to use your 'standard' address. And even then > mailing lists can use multiple sending addresses depending upon the > function they are performing. So as a result I have found with a ham > radio list, 'topband' that even though it typically sends with address > 'top...@ma...' at other times it replaces bounces > with something else, which would result in a challenge. The solution > is to whitelist 'topband*@mailman.qth.net' to cover these variations. You should read this: http://www.arda.homeunix.net/tmda-mailing-lists-howto/ There are various good solutions for using TMDA with mailing lists (though most of them require using tmda-ofmipd). > All in all I think I can use TMDA. It looks like I am the only person > to post to the TMDA mailing list in 2014! And it's likely to stay that way for the rest of 2014 :) > Incidentally are you familiar with this > http://www.vsta.org/spam/Traveler.html. I hadn't seen it before. > It is a different concept which automatically assigns a unique e-mail > address to everyone in your address book. The author seems willing to > share the code. I think you can configure TMDA to work this way if you want, by configuring tmda-ofmipd to use a sender-address for all outgoing mail. That sounds better to me than the Traveler system, as also get all the other TMDA features (like automated challenges to new correspondents who aren't already on your list). However, I don't use TMDA like this, so you'd have to experiment for yourself / read the TMDA documentation on tmda.net (which is surprisingly good). TMDA really is an amazingly flexible system. It's a shame it's unmaintained. > I don't think the spam problem has been solved, but perhaps it has been > controlled to the point that most users are satisfied with the > filtering method. I use filtering *together with* TMDA. Indeed, you should probably always use TMDA in combination with a filter if you want to be a good net citizen. The reason is that spam is often forged to come from a valid email address. Challenging obvious spam just sends a challenge to the unwitting victim whose address has been used by the spammer, and who never emailed you in the first place. Which as bad as spamming them. You can configure TMDA not to challenge mails that are above a given spam score. That way obvious spam to your address doesn't generate further "challenge-spam". Addresses on your whitelist/keyword/dated etc. still always get through unchallenged (which accounts for most mail anyway). And mail from new correspondents that doesn't look like obvious spam gets challenged. You can set the spam score threshold as low or high as you want. A higher threshold means means you risk fewer false positives but generate more challenge spam, and vice versa. HTH, Toby > On Sunday, August 10, 2014 9:26 AM, Toby Cubitt <tob...@dr...> wrote: > > > > Hi Ron, > > I believe the canonical way is simply to create a "revoked" list, and > configure TMDA to challenge all addresses on that list. Then simply add > the keyword address you want to revoke to the "revoked" list. > > If I remember right (it's a long time since I've needed to do this), to > create a new address list file in TMDA-cgi, you simple add a rule that > refers to the new list to your incoming filter. TMDA-cgi will then create > the file for you, and you can start adding addresses to it in the usual > way. > > Hope that helps, > > Toby > > > On Sat, Aug 09, 2014 at 05:55:06PM -0700, Ron Stordahl wrote: > > I am testing TMDA offered by a e-mail provider. My interface to it is via the TMDA cgi. > > > > I have created a 'keyword' address and tested it, it works. > > > > But how to I revoke it? I can't find anything in the TMDA cgi screens which permit me to do so. > > > > Ron > > > ------------------------------------------------------------------------------ > > > _______________________________________________ > > tmda-users mailing list > > tmd...@li... > > https://lists.sourceforge.net/lists/listinfo/tmda-users > > -- Dr T. S. Cubitt Royal Society University Research Fellow Fellow of Churchill College, Cambridge Centre for Quantum Information DAMTP, University of Cambridge email: ts...@ca... web: www.dr-qubit.org |
From: Toby C. <to...@dr...> - 2014-08-10 18:58:53
|
Hi Ron, I believe the canonical way is simply to create a "revoked" list, and configure TMDA to challenge all addresses on that list. Then simply add the keyword address you want to revoke to the "revoked" list. If I remember right (it's a long time since I've needed to do this), to create a new address list file in TMDA-cgi, you simple add a rule that refers to the new list to your incoming filter. TMDA-cgi will then create the file for you, and you can start adding addresses to it in the usual way. Hope that helps, Toby On Sat, Aug 09, 2014 at 05:55:06PM -0700, Ron Stordahl wrote: > I am testing TMDA offered by a e-mail provider. My interface to it is via the TMDA cgi. > > I have created a 'keyword' address and tested it, it works. > > But how to I revoke it? I can't find anything in the TMDA cgi screens which permit me to do so. > > Ron > ------------------------------------------------------------------------------ > _______________________________________________ > tmda-users mailing list > tmd...@li... > https://lists.sourceforge.net/lists/listinfo/tmda-users -- Dr T. S. Cubitt Royal Society University Research Fellow Fellow of Churchill College, Cambridge Centre for Quantum Information Department of Applied Mathematics and Theoretical Physics University of Cambridge email: ts...@ca... web: www.dr-qubit.org |