headers
Jason R. Mastaler | 5 Nov 2001 05:33
X-Face

TMDA 0.40 is released

TMDA 0.40 is released.  This release probably won't be very
interesting to you unless you are running Exim.

Download:
---------
gzipped tarball:
<URL:http://prdownloads.sf.net/tmda/tmda-0.40.tgz>

Linux source RPM:
<URL:http://prdownloads.sf.net/tmda/tmda-0.40-1.src.rpm>

RedHat Linux 7.x binary RPM:
<URL:http://prdownloads.sf.net/tmda/tmda-0.40-1.noarch.rpm>

=====================================================================

New in this release:

* Exim support!  TMDA now works on Exim as well as Postfix and qmail
  systems.  The documentation has been updated accordingly.

ChangeLogs follow:

=====================================================================

2001-11-04  Jason R. Mastaler  <jasonrm <at> nightshade.la.mastaler.com>

	* README: TMDA 0.40 is released.

2001-11-01  Jason R. Mastaler  <jasonrm <at> nightshade.la.mastaler.com>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Matt Armstrong | 5 Nov 2001 23:54

Re: thoughts on spam

Note: I've set the Mail-Followup-To: to tmda-users <at> libertine.org since
this is off topic for ding <at> gnus.org

Chris Shenton <chris <at> shenton.org> writes:

> This discussion has finally motivated me to try TMDA.  Just built
> and installed it but I'm having trouble figuring the best way to use
> it with all the mailing lists I'm already on.
>
> Naturally, the second I enabled it in .qmail[-default] it started
> pumping msgs to ~/.tmda/pending.  
>
> I don't see anything in my qmail logs which tells me the envelope
> sender; any suggestions how I can capture this?  For mailing lists,
> the From: is usually not what I want, since that just gets the
> originating human's address. Most the lists I'm on do not have a
> Reply-To: either.

Stick something like this in your .tmdarc:

    import time
    localtime = time.localtime(time.time())
    YYYYmm = time.strftime('%Y-%m',localtime)
    LOGFILE = os.path.expanduser("/home/matt/.tmda/log/tmdalog." + YYYYmm)

This'll give stuff like this in your ~/.tmda/log/tmdalog.2001-11 file:

    Date: Thu Nov  1 08:33:03 2001
    From: c379sb1 <at> caramail.com
      To: matt+bmi <at> lickey.com
(Continue reading)

Permalink | Reply | 3 comments |
headers
Jason R. Mastaler | 6 Nov 2001 00:20
X-Face

Re: thoughts on spam

Chris Shenton <chris <at> shenton.org> writes:

> This discussion has finally motivated me to try TMDA.  Just built
> and installed it but I'm having trouble figuring the best way to use
> it with all the mailing lists I'm already on.

Take a look at the "Client Configuration" section of the TMDA homepage
as this explains the different types of tagged addresses you can use.

For mailing lists, I'd use of one of:

- Keyword address (as Matt explained)

- Sender address (as explained in "Client Configuration")

- Whitelist the mailing list (e.g, owner-ding <at> gnus.org)

- Handle lists outside of TMDA (e.g, setup a ~/.qmail-list-default
  that contains ~/Mailbox.list or something.  Mail sent to
  chris-list-foo will bypass TMDA and be delivered to Mailbox.list)

> Naturally, the second I enabled it in .qmail[-default] it started
> pumping msgs to ~/.tmda/pending.

One way of testing TMDA before deploying it against all your incoming
mail would be to setup a ~/.qmail-tmda and .qmail-tmda-default and
test by sending messages to chris-tmda-*

> I don't see anything in my qmail logs which tells me the envelope
> sender; any suggestions how I can capture this?
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jason R. Mastaler | 6 Nov 2001 00:27
X-Face

Re: thoughts on spam

"Matt Armstrong" <matt+dated+1007592891.aaaadf <at> lickey.com> writes:

> Note: I've set the Mail-Followup-To: to tmda-users <at> libertine.org
> since this is off topic for ding <at> gnus.org

Praise Allah!

> Stick something like this in your .tmdarc:
> 
>     import time
>     localtime = time.localtime(time.time())
>     YYYYmm = time.strftime('%Y-%m',localtime)
>     LOGFILE = os.path.expanduser("/home/matt/.tmda/log/tmdalog." + YYYYmm)

BTW Matt, the purpose of os.path.expanduser is to translate `~' into
/home/matt, so your use above is redundant.  Use either of:

LOGFILE = os.path.expanduser("~/.tmda/log/tmdalog." + YYYYmm)
LOGFILE = "/home/matt/.tmda/log/tmdalog." + YYYYmm

And Chris, if you don't need/want month-stamped logfiles, you can use
something as simple as:

LOGFILE = "/home/chris/tmda.log"

> I use the recently added "keyword" style addresses.

Recently added, as in post v0.37 which Chris seems to be using.  (I
really need to update that FreeBSD port one of these days).
_______________________________________________
(Continue reading)

Permalink | Reply | 2 comments |
headers
Chris Shenton | 6 Nov 2001 15:10
Gravatar

Re: thoughts on spam

"Jason R. Mastaler" <jason-dated-1005694044.979403 <at> mastaler.com> writes:

> LOGFILE = os.path.expanduser("~/.tmda/log/tmdalog." + YYYYmm)

OK, thanks.

> Recently added, as in post v0.37 which Chris seems to be using.  (I
> really need to update that FreeBSD port one of these days).

Yup, started with the port, since I didn't know any better :-(

Thanks.
_______________________________________________
tmda-users mailing list
http://libertine.org/lists/listinfo/tmda-users
Permalink | Reply | 1 comment |
headers
Jason R. Mastaler | 6 Nov 2001 18:10
X-Face

Re: thoughts on spam

Chris Shenton <chris <at> shenton.org> writes:

> Yup, started with the port, since I didn't know any better :-(

I've just submitted a PR to update the mail/tmda port to v0.40.
Attached is a copy since it often takes the port committers awhile to
get around to things.
Attachment (tmda-0.40-port.tgz): application/x-tar-gz, 1623 bytes
Permalink | Reply | 0 comments |
headers
Ron Bickers | 7 Nov 2001 17:49

Keyword address benefits

I'm trying to decide one the benefits of using keyword addresses vs. having
my own .qmail- files.

For starters, I don't see how rbickers-bogus.369acb <at> domain.dom is any better
than rbickers-bogus <at> domain.dom.  Is it?

I know using keyword addresses means I don't have to maintain a lot of
.qmail files, but one significant advantage of .qmail files is that I can
deliver to different mailboxes.  There has been recent discussion on having
an option for TMDA to deliver to different mailboxes, but I don't know
if/when that would be available.

Are there other benefits of keyword addresses over .qmail files?
_______________________

Ron Bickers
Logic Etc, Inc.

_______________________________________________
tmda-users mailing list
http://libertine.org/lists/listinfo/tmda-users
Permalink | Reply | 3 comments |
headers
Drew Raines | 9 Nov 2001 18:00
Picon

TMDA with maildrop (no SMTP)

I'm trying to invoke TMDA between maildrop and getmail.  I use qmail, but
just for outgoing SMTP, however, TMDA works great if I send messages
directly to my client through qmail-smtpd.

That's just for testing though.  My normal method of retrieving mail is
running getmail to POP messages off the departmental mail server, then
feeding them to maildrop for filtering and delivery.  For some reason this
fails.

I based my setup roughly on the TMDA documentation concerning other
MTAs/procmail:

   1. getmail retrieves messages, feeds them to maildrop
   2. .mailfilter logs the receiving of the message, then pipes it to
      tmda-filter.
   3. tmda-filter works its mojo, then (maybe) feeds the message to
      maildrop based on the following line.

	LOCAL_DELIVERY_AGENT = "/opt/bin/maildrop ~/.mailfilter-tmda" 

   4. .mailfilter-tmda filters mail based on my rules and makes the final
      delivery.

The problem occurs between 2 & 3.  maildrop logs reception of the message,
but for some reason doesn't pass it on to tmda-filter (or maybe it does,
and tmda-filter does something with it).  Whatever happens, the message is
not in ~/.tmda/pending and it's not in my inbox.

Is anyone using maildrop that has a working setup similar to what I'm
trying to do?
(Continue reading)

Permalink | Reply | 11 comments |
headers
Drew Raines | 9 Nov 2001 18:11
Picon

Re: TMDA with maildrop (no SMTP)

* drew <at> phg.mc.vanderbilt.edu (Drew Raines):
>
> That's just for testing though.  My normal method of retrieving mail is
> running getmail to POP messages off the departmental mail server, then
> feeding them to maildrop for filtering and delivery.  For some reason this
> fails.

Clarification:  The above doesn't fail by itself, only when I add in the
complexity of multiple pipes (with my TMDA setup).

--

-- 
Drew
_______________________________________________
tmda-users mailing list
http://libertine.org/lists/listinfo/tmda-users
Permalink | Reply | 0 comments |
headers
Matt Armstrong | 9 Nov 2001 18:31

Re: TMDA with maildrop (no SMTP)

drew <at> phg.mc.vanderbilt.edu (Drew Raines) writes:

> I'm trying to invoke TMDA between maildrop and getmail.  I use qmail, but
> just for outgoing SMTP, however, TMDA works great if I send messages
> directly to my client through qmail-smtpd.
>
> That's just for testing though.  My normal method of retrieving mail is
> running getmail to POP messages off the departmental mail server, then
> feeding them to maildrop for filtering and delivery.  For some reason this
> fails.
>
> I based my setup roughly on the TMDA documentation concerning other
> MTAs/procmail:
>
>    1. getmail retrieves messages, feeds them to maildrop

TMDA will not work out of the box this way, unless getmail sets the
same environment variables Qmail does when piping the message to a
command.  tmda-filter looks for SENDER, RECIPIENT and EXT environment
variables that hold the envelope sender, recipient, and any recipient
extension.

The other thing to consider here is that TMDA's "defer" option
probably won't work work.  TMDA exits with exit code 75, which causes
qmail/postfix/exim to defer the delivery and try again.  I wonder what
getmail does in such an instance.

I would recommend that you use fetchmail and not getmail.  Have
fetchmail send messages to your local smtp server, and then use
maildrop from a .qmail file.
(Continue reading)

Permalink | Reply | 9 comments |

Gmane