<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.mail.spam.tmda.devel">
    <title>gmane.mail.spam.tmda.devel</title>
    <link>http://permalink.gmane.org/gmane.mail.spam.tmda.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6862"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6861"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6860"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6858"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6857"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6856"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6855"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6854"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6853"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6852"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6851"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6850"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6849"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6848"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6847"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6846"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6845"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6844"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6843"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6842"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6862">
    <title>Re: Suggestions for 8BITMIME capability</title>
    <link>http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6862</link>
    <description>&lt;pre&gt;
I think, for tmda-ofmipd, the easiest and at the same time safest solution is to make it a command-line option, say -8, which decides whether or not 8BITMIME is advertised.  Since the owner of tmda-ofmipd is also the one specifying the host to which mail is relayed, he can know in advance whether or not it will accept any eight-bit mail he may send via tmda-ofmipd.  For this to work you will also need a config option in tmda-inject that will properly denote eight-bit mail using a command-line switch to sendmail (-B8BITMIME) or the equivalent SMTP parameter to MAIL From.  See RFC 6152.  While this does leave open the possibility of mail being designated 8BITMIME when it is in fact just 7BIT, in practice this probably isn't likely to be a problem.


For example, Alpine will use the SMTP's advertisement to (by default) decide whether to just send 8 or QP-encode.

Cheers,
Sabahattin

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technicall&lt;/pre&gt;</description>
    <dc:creator>Sabahattin Gucukoglu</dc:creator>
    <dc:date>2011-06-10T08:15:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6861">
    <title>Suggestions for 8BITMIME capability</title>
    <link>http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6861</link>
    <description>&lt;pre&gt;There was a request some time back to get the 8BITMIME capability added
to tmda-ofmipd:

http://sourceforge.net/mailarchive/message.php?msg_id=25325009

As I understand it, this requires possibly re-encoding messages to a
7-bit format when transmitting to a host that doesn't advertise 8BITMIME
support. However, there's an interesting case made for a different
approach here:

http://cr.yp.to/smtp/8bitmime.html

Since this requires virtually no effort to implement, it's appealing to me.

Does anyone have any thoughts what approach to take? Also, I'm wondering
what difference 8BITMIME makes in practice. My mailer seems to send 8
bits without this capability advertised, which makes testing tricky. If
I knew of use-cases that actually fail without 8BITMIME, that might
help.

-Kevin

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure&lt;/pre&gt;</description>
    <dc:creator>Kevin Goodsell</dc:creator>
    <dc:date>2011-06-10T05:10:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6860">
    <title>IPv6 support now in trunk</title>
    <link>http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6860</link>
    <description>&lt;pre&gt;I've just pushed several commits, mostly around adding IPv6 support
(plus adding tests, fixing some minor issues).

This primarily adds IPv6 support to tmda-ofmipd (though it also allows
using the tmda-cgi simple-server in IPv6 mode to test tmda-cgi). There
are several areas where IPv6 needed to be addressed:

* Options for the address/port the server listens on.
* Supporting IPv6 URL format for remote authentication (-R option).
* Recognizing ::1 as a loopback address allowing non-TLS authentication
  with --tls=localoptional.
* The ipauthmap file that allows selecting the remote authentication
  host based on the interface the client connected on.

This includes some functional changes:

* In addition to -p/--proxyport, there's a new -6/--ipv6proxyport option
  to specify on IPv6 address. These two options can appear multiple
  times, in any combination, to bind many address/port combinations.

* With the above options, the preferred syntax for binding all available
  addresses is now ":PORT" instead of "0&lt;/pre&gt;</description>
    <dc:creator>Kevin Goodsell</dc:creator>
    <dc:date>2011-05-21T17:16:59</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6858">
    <title>Re: Corrupted image files in tmda-cgi</title>
    <link>http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6858</link>
    <description>&lt;pre&gt;
I'm convinced (by doing some svnadmin dumps and examining the output)
that the images were corrupted in the repository. I don't know why I
didn't think to check the source tars (I guess I forgot they were
there), but this seems to have worked nicely. I've checked in the
repaired images and changed all the svn properties to omit
svn:keywords and svn:eol-style, and include svn:mime-type with the
value image/gif.

Thanks for the suggestion, Tim.

-Kevin

------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
tmda-workers mailing list
tmda-workers&amp;lt; at &amp;gt;lists.sourceforge.net
https://lists.sour&lt;/pre&gt;</description>
    <dc:creator>Kevin Goodsell</dc:creator>
    <dc:date>2011-04-21T01:25:13</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6857">
    <title>Re: Corrupted image files in tmda-cgi</title>
    <link>http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6857</link>
    <description>&lt;pre&gt;

I ran md5 on all the .gif and .png files in tmda-cgi-0.13 and
tmda-cgi-0.16.4. 37 of them were different.
.......
display/icons/python.gif
display/icons/sound.gif
display/themes/Blue/button_templates/layout1_r1_c1.gif
display/themes/Blue/button_templates/layout1_r2_c1.gif
display/themes/Blue/button_templates/layout1_r3_c1.gif
display/themes/Blue/button_templates/layout1_r4_c1.gif
display/themes/Blue/button_templates/layout1_r5_c1.gif
display/themes/Blue/button_templates/layout1_r6_c1.gif
display/themes/Blue/button_templates/layout1_r7_c1.gif
display/themes/Blue/buttons/options_r1_c2.gif
display/themes/Blue/buttons/subnav_r1_c1.gif
display/themes/Blue/buttons/subnav_r1_c12.gif
display/themes/Blue/buttons/subnav_r1_c13.gif
display/themes/Blue/buttons/subnav_r1_c14.gif
display/themes/Blue/buttons/subnav_r1_c15.gif
display/themes/Blue/buttons/subnav_r1_c16.gif
display/themes/Blue/buttons/subnav_r1_c2.gif
display/themes/Blue/buttons/subnav_r1_c4.gif
display/themes/Blue/buttons/subnav_r1_c5.gif
display/themes/Bl&lt;/pre&gt;</description>
    <dc:creator>Tim Rice</dc:creator>
    <dc:date>2011-04-20T16:52:20</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6856">
    <title>Corrupted image files in tmda-cgi</title>
    <link>http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6856</link>
    <description>&lt;pre&gt;I've found many corrupted .gif files in tmda-cgi, mostly in
tmda-cgi/htdocs/display/ and various places in
tmda-cgi/display/themes/Blue. This *could* be because the files were
checked in with bad svn properties (especially svn:eol-style) which
would cause svn to rewrite the files on checkout (I think), in which
case the originals could still be in the repository. However, as a
test I fixed the properties on the files in tmda-cgi/display/icons and
this did not seem to make any difference for sound.gif, which is still
visibly distorted in those applications which don't simply fail to
open it.

(found on the Sourceforge web site) it appears the 0x0D bytes have all
been changed to 0x0A, so that suggests they were incorrectly processed
as text somewhere along the line, and had their "EOL" markers changed.

I'm concerned that the originals of some of these files may be lost.

The most pressing questions I have right now are:

* Is there a way to make Subversion give me the raw file, as it is in
the repository, wit&lt;/pre&gt;</description>
    <dc:creator>Kevin Goodsell</dc:creator>
    <dc:date>2011-04-20T02:43:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6855">
    <title>Re: Opinions for supported Python versions?</title>
    <link>http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6855</link>
    <description>&lt;pre&gt;Just a note, CentOS (RHEL) 5 is still at 2.4.3.  I don't know what RHEL
6 uses as I don't have any servers at that point since I primarily use
CentOS and they haven't gotten v 6 out yet.  I would anticipate
something in the 2.6 or 2.7 line though as the latest Fedora (14) is on
2.7.8

That being said, I too am thrilled to see development going forward
again on TMDA.  I may just have to backport the newer python to CentOS
so I can stay up to date.

-Andy-

On Tue, 2011-04-12 at 12:55 -0700, Tim Rice wrote:


------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
tmda-workers mailing li&lt;/pre&gt;</description>
    <dc:creator>Andrew Grimberg</dc:creator>
    <dc:date>2011-04-16T18:28:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6854">
    <title>Re: TMDA + Postfix/Procmail + TMDA-CGI</title>
    <link>http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6854</link>
    <description>&lt;pre&gt;On Wed, Apr 13, 2011 at 12:11 PM, Livia Santos
&amp;lt;liviasilvasantos&amp;lt; at &amp;gt;gmail.com&amp;gt; wrote:

That looks suspiciously like the first line of a Python traceback
message. With the whole message we would have a pretty good chance of
determining what the problem is, but one line doesn't help much. If
you can get the complete output from the CGI process that would help
diagnose the problem (but I don't know how this would be done with
Apache).

-Kevin

------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
tmda-workers mailing list
tmda-workers&amp;lt; at &amp;gt;lists.sourceforge.net
https://lists.sourceforge.net/lis&lt;/pre&gt;</description>
    <dc:creator>Kevin Goodsell</dc:creator>
    <dc:date>2011-04-14T02:29:20</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6853">
    <title>Re: TMDA + Postfix/Procmail + TMDA-CGI</title>
    <link>http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6853</link>
    <description>&lt;pre&gt;
"Not working" isn't much to go on.


Don't get your hopes up. tmda-cgi uses at least one old library
(whrandom) that's been removed since Python 2.5 (deprecated since 2.1).
That alone is easy enough to fix (just replace it with random), but it
indicates how out-dated the code is, and it's hard to say what else
might be broken.

I'm trying to update tmda-cgi at the moment (literally, was working on
it before I checked my mail and found this message), but I'm not
interested in using it myself, which means I'm not very interested in
maintaining it, and not very able to test it. In all likelihood it will
take more than I have to give to get it into a good, reasonably tested
and usable state.

That said, you can try the slightly updated version in Subversion. Not
much has changed in tmda-cgi itself, though. It's been slightly updated
to not depend on a local copy of the email library, and the
configuration script has been rewritten. Plus there's a simple testing
server that might help diagnose any problems you a&lt;/pre&gt;</description>
    <dc:creator>Kevin Goodsell</dc:creator>
    <dc:date>2011-04-13T18:56:12</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6852">
    <title>TMDA + Postfix/Procmail + TMDA-CGI</title>
    <link>http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6852</link>
    <description>&lt;pre&gt;Hi, 

I'm not familiar to mail servers, 
but I have to install TMDA on a 
already working Postfix server.

I read a lot of tutorials, but
 most of them explaining how to 
install TMDA to work with Maildrop. 

I need to make it work with procmail. 
So far I've installed TMDA 1.1.12 ok.  

I was told I need to create a file 
named ~/.procmailrc for each user 's home 
(although I dont't know its content yet... 
gonna find it somewhere...&amp;gt;D ).

Now I'm trying to install tmda-cgi 0.16.4 
but it's not working. 

Does anybody know if this version of tmda-cgi
 need a specific version of python? 

I'm using Python 2.6.

Thanks in advance.

Lívia.


------------------------------------------------------------------------------
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.&lt;/pre&gt;</description>
    <dc:creator>Lívia</dc:creator>
    <dc:date>2011-04-13T18:26:47</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6851">
    <title>Re: Opinions for supported Python versions?</title>
    <link>http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6851</link>
    <description>&lt;pre&gt;

Yes, Solaris 10 uses 2.4.6.
That said, I'm thrilled that someone is actually doing further
development work on TMDA and if it is a lot of extra work to support
2.4.x I'll build a newer version of python.



&lt;/pre&gt;</description>
    <dc:creator>Tim Rice</dc:creator>
    <dc:date>2011-04-12T19:55:00</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6850">
    <title>Re: Opinions for supported Python versions?</title>
    <link>http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6850</link>
    <description>&lt;pre&gt;I see no reason to support Python 2.4 and lower. I'd maintain 2.5
compatibility until it's prohibitive to the development process then
drop that as well. The few users that still rely on old versions of
Python still have the TMDA 1.1.x line available.

On Tue, Apr 12, 2011 at 2:55 PM, Kevin Goodsell
&amp;lt;kevingoodsell.lists&amp;lt; at &amp;gt;gmail.com&amp;gt; wrote:

------------------------------------------------------------------------------
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
_______________________________________________
tmda-workers mailing list
tmda-workers&amp;lt; at &amp;gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmda-workers

&lt;/pre&gt;</description>
    <dc:creator>Jason R. Mastaler</dc:creator>
    <dc:date>2011-04-12T19:49:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6849">
    <title>Opinions for supported Python versions?</title>
    <link>http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6849</link>
    <description>&lt;pre&gt;At this point I'm not sure it's exactly clear what Python versions are
supported, and I don't know off the top of my head if there's on
official requirement. I believe my releases have included dependencies
on Python 2.4, and some of my recent commits depend on Python 2.5
features.

Certainly supporting versions up to 2.7.x is desirable (and any future
2.x versions, though I *think* 2.7 is expected to be the last in the
Python 2 line), and supporting 3.x is impractical until some significant
work is put into converting the entire code base.

So the main question is the minimum supported version. Python 2.5 was
released in September of 2006, and is available in Debian's "oldstable"
release (Lenny) from February 2009. Since Debian has a reputation for
old software in its stable releases, something that's available as far
back as it's previous stable release seems more than reasonable.

Python 2.6 seems reasonably widespread at this point, and was released in
October 2008. It's also the default version in the c&lt;/pre&gt;</description>
    <dc:creator>Kevin Goodsell</dc:creator>
    <dc:date>2011-04-12T18:55:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6848">
    <title>Re: Security fixes for tmda-ofmipd now available</title>
    <link>http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6848</link>
    <description>&lt;pre&gt;On Sat, Apr 9, 2011 at 3:18 PM, Sabahattin Gucukoglu
&amp;lt;mail&amp;lt; at &amp;gt;sabahattin-gucukoglu.com&amp;gt; wrote:

Thanks for letting me know. I hit a site glitch while uploading this
package, but in the end it seemed to have worked. Apparently not. I've
re-uploaded it now, and it looks like it's finally working.

-Kevin

------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
tmda-workers mailing list
tmda-workers&amp;lt; at &amp;gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmda-workers

&lt;/pre&gt;</description>
    <dc:creator>Kevin Goodsell</dc:creator>
    <dc:date>2011-04-09T23:41:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6847">
    <title>Re: Security fixes for tmda-ofmipd now available</title>
    <link>http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6847</link>
    <description>&lt;pre&gt;On Sat, Apr 9, 2011 at 2:57 PM, Kevin Goodsell
&amp;lt;kevingoodsell.lists&amp;lt; at &amp;gt;gmail.com&amp;gt; wrote:

One thing I forgot to make clear in my message: these issues are
specific to the OpenSSL version of tmda-ofmipd that has been available
on the GitHub fork previously. The code was incorporated into the
Subversion repository recently, but no official releases have ever
included it. I have no particular reason to think that the TLSLite
version has either of these problems (though I can't say I trust its
security).

-Kevin

------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
tmda-workers mailing list
tmda-workers&amp;lt; at &amp;gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmda-workers

&lt;/pre&gt;</description>
    <dc:creator>Kevin Goodsell</dc:creator>
    <dc:date>2011-04-09T22:08:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6846">
    <title>Security fixes for tmda-ofmipd now available</title>
    <link>http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6846</link>
    <description>&lt;pre&gt;I've pushed two commits out to the Subversion repository as well as my
GitHub fork. On GitHub I've also tagged a new release (tag name
tmda-1.1.12-kg3 or debian-tmda-1.1.12-kg3-1 for the branch that
includes Debian packaging) and uploaded new .deb packages:

https://github.com/KevinGoodsell/tmda-fork

As indicated in the subject line, these changes are to address issues
that I consider security problems for tmda-ofmipd. Two separate issues
are addressed with these changes:

First, tmda-ofmipd allowed the use of SSL version 2, which is an
older, insecure version of the protocol. It also allowed weak 40-bit
and 56-bit ciphers. In all cases these were allowed because that is
the default for the OpenSSL library. One of the changes adds a new
--ciphers option to tmda-ofmipd, which allows the user to control
which ciphersuites are accepted by the server. The default set
excludes weak ciphers and SSL version 2 ciphers (though any user who
really needs to can easily re-enable them).

Second, tmda-ofmipd's error hand&lt;/pre&gt;</description>
    <dc:creator>Kevin Goodsell</dc:creator>
    <dc:date>2011-04-09T21:57:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6845">
    <title>Re: Latest updates: pythonlib, tmda-cgi</title>
    <link>http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6845</link>
    <description>&lt;pre&gt;That's great Kevin. If anyone wants to try out the new code, I put
links to tarballs of the trunk branch for tmda and tmda-cgi at the
bottom of the downloads page:
http://tmda.sourceforge.net/cgi-bin/moin.cgi/TmdaDownload

On Sat, Apr 2, 2011 at 2:25 PM, Kevin Goodsell
&amp;lt;kevingoodsell.lists&amp;lt; at &amp;gt;gmail.com&amp;gt; wrote:

------------------------------------------------------------------------------
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
_______________________________________________
tmda-workers mailing list
tmda-workers&amp;lt; at &amp;gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmda-workers

&lt;/pre&gt;</description>
    <dc:creator>Jason R. Mastaler</dc:creator>
    <dc:date>2011-04-02T19:57:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6844">
    <title>Latest updates: pythonlib, tmda-cgi</title>
    <link>http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6844</link>
    <description>&lt;pre&gt;I just pushed a few more changes:

* Remove pythonlib
* Some cleanup and minor fixes for tmda-cgi
* A simple web server for testing tmda-cgi
* A mostly new configure script for tmda-cgi, to support the web server

Most of the actual work here was just to make tmda-cgi testable for
me, without having to install and configure a web server.

One thing I am unable to test is the tmda/contrib/tmda.spec script for
RPM building. This had to be updated for the pythonlib removal, but as
a Debian user I don't have experience building RPMs and I'm not sure
exactly how this is supposed to be used. If anyone can test this and
notify the tmda-workers list of any problems, that would be
appreciated.

Next I plan to do some additional updates to tmda-cgi, mostly to
remove deprecated items.

I'm also keeping a github branch synchronized with the Subversion trunk here:

https://github.com/KevinGoodsell/tmda-fork/tree/svn-trunk

-Kevin

------------------------------------------------------------------------------
Create and p&lt;/pre&gt;</description>
    <dc:creator>Kevin Goodsell</dc:creator>
    <dc:date>2011-04-02T18:25:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6843">
    <title>Re: DB APPEND variables</title>
    <link>http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6843</link>
    <description>&lt;pre&gt;On Wed, Mar 30, 2011 at 7:34 AM, David Grimberg
&amp;lt;sentinel&amp;lt; at &amp;gt;bardicgrove.org&amp;gt; wrote:

OK, I've added it to the list of things to look at.

-Kevin

------------------------------------------------------------------------------
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
_______________________________________________
tmda-workers mailing list
tmda-workers&amp;lt; at &amp;gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmda-workers

&lt;/pre&gt;</description>
    <dc:creator>Kevin Goodsell</dc:creator>
    <dc:date>2011-03-30T16:47:34</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6842">
    <title>Re: Mail rejected for tmda-cvs email address</title>
    <link>http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6842</link>
    <description>&lt;pre&gt;Ok thanks. That's a mailing list that's no longer active.

On Fri, Mar 18, 2011 at 10:23 AM, Kevin Goodsell
&amp;lt;kevingoodsell.lists&amp;lt; at &amp;gt;gmail.com&amp;gt; wrote:

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
tmda-workers mailing list
tmda-workers&amp;lt; at &amp;gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmda-workers

&lt;/pre&gt;</description>
    <dc:creator>Jason R. Mastaler</dc:creator>
    <dc:date>2011-03-18T18:26:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6841">
    <title>Mail rejected for tmda-cvs email address</title>
    <link>http://permalink.gmane.org/gmane.mail.spam.tmda.devel/6841</link>
    <description>&lt;pre&gt;I'm getting email errors from sourceforge because the email
notifications for checkins are going to an address that appears to no
longer be valid:

   Delay reason: SMTP error from remote mail server after RCPT
TO:&amp;lt;tmda-cvs&amp;lt; at &amp;gt;tmda.net&amp;gt;:
   host a.mx.tmda.net [66.135.48.124]: 450 4.1.1 &amp;lt;tmda-cvs&amp;lt; at &amp;gt;tmda.net&amp;gt;:
   Recipient address rejected: User unknown in local recipient table

For the moment I've removed the hook that sends checkin notifications.
It can of course be restored if the address is fixed.

-Kevin

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
tmda-workers mailing list
tmda-workers&amp;lt; at &amp;gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmda-workers

&lt;/pre&gt;</description>
    <dc:creator>Kevin Goodsell</dc:creator>
    <dc:date>2011-03-18T17:23:54</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.mail.spam.tmda.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.mail.spam.tmda.devel</link>
  </textinput>
</rdf:RDF>
