Re: help with dated addresses being held

Vincent Danen <[email protected]>
Newsgroups gmane.mail.spam.tmda.user
Message-ID <[email protected]>
* [2008-02-04 13:14:10 -0700] Stephen Warren wrote:

>On Mon, February 4, 2008 10:53 am, Vincent Danen wrote:
>> I've been using tmda for a while, but never really noticed until now
>> that when I send a dated message out, a confirmation is always asked.
>> My incoming log shows this:
>>
>> Actn: CONFIRM (from * confirm)
>
>you have an explicit rule in your incoming filter:
>
>from * confirm
>
>As such, this forces all messages to go through the confirmation process.
>
>I'm assuming that's the last line of your filter. You should remove this
>rule, and set ACTION_INCOMING to confirm:
>
>http://wiki.tmda.net/ConfigurationVariables#ACTION_INCOMING
>
>The processing of dated/keyword/... addresses is performed *after* your
>incoming filter, so that you can add overrides to e.g. block mail from a
>known blacklisted sender, even if sent to an otherwise valid e.g. dated
>address.

Hmmmm.... ok, but then why in contrib/dot-tmda/filters/incoming is there
the following:

#####################
# default disposition
#####################

# Mail that didn't match one of the rules above will be challenged.

from * confirm


Is this no longer valid?  If so, that should probably be fixed in the
tarball.

Ok, so if I remove "from * confirm", then the filters will get run and
if there are no matches to any filters, ACTION_INCOMING will be used as
the "default disposition", which should be 'confirm' anyways, correct?

I'll give that a try.  Thanks.

-- 
Vincent Danen @ http://linsec.ca/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.