Commit graph

21 commits

Author SHA1 Message Date
schmonz
31bad3ac19 Some of the Python bytecode contains absolute paths. After
installation, the affected files are recompiled the first time
tmda-ofmipd runs with sufficient permissions. Force the recompile
during post-install to ensure the package tools record the right
checksums.
2004-06-13 10:59:31 +00:00
schmonz
70f369d4b9 Always pass "-b" on the command line, in case the default behavior changes. 2004-06-10 16:33:40 +00:00
schmonz
fa18bda451 Update to 1.0.3. From the changelog:
* Fixed a small bug in the auto-response rate limiting code that
  choked on extremely long addresses.
  (http://mla.libertine.org/tmda-users/2004-01/msg00375.html)

* Fixed a small bug in the X-Primary-Address header handling code that
  was triggered by a broken MTA.
  (http://mla.libertine.org/tmda-users/2004-01/msg00100.html)

* Fixed a bug in TMDAINJECT that caused Message-ID and Date headers to
  differ when sending to multiple recipients.

* Fixed a bug that would cause pending message release to fail under
  certain MTAs (particularily Exim) if the envelope sender was null <>.

pkgsrc changes:
* Add rc.d script for tmda-ofmipd.
* Create "tofmipd" user for tmda-ofmipd.
* Require Python 2.2 or higher, as needed by tmda-ofmipd.
* Use subst.mk to honor PKG_SYSCONFDIR.
* Set PKG_SYSCONFSUBDIR, as TMDA potentially has several config files.
* Update MASTER_SITES.
* Use shell globs to simplify some definitions.
* Remove MESSAGE, as TMDA provides its own upgrade instructions.
* Pass one file at a time to install(1) for the benefit of some of our
    differently-abled platforms.
2004-06-06 05:08:34 +00:00
snj
64b64af3bb Convert to buildlink3. 2004-04-18 04:41:12 +00:00
kim
09a8377976 Upgrade to the 1.0 release. 2004-01-28 00:12:53 +00:00
recht
215a6b647e Add USE_BUILDLINK2.
This should fix hubertf's bulk build.
2003-09-27 08:22:29 +00:00
kim
324c1d74c6 Works with more Python versions. 2003-09-26 00:20:32 +00:00
kim
65611f025c Update to tmda-0.84
See share/doc/tmda/UPGRADE for important notes, or view the notes from
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/~checkout~/tmda/tmda/UPGRADE
before upgrading.  There are too many changes to list here.
2003-09-23 01:57:18 +00:00
grant
0155927c43 s/netbsd.org/NetBSD.org/ 2003-07-17 21:41:05 +00:00
kim
a5b52a648c Upgrade to tmda-0.65:
What's new?

* New feature: A new header called ``X-Primary-Address'' is now
  supported in order to reduce the amount of thinking and planning
  ahead you need to do when sending mail to a new correspondent who
  may or may not use a challenge/response system like
  TMDA. Essentially, this header allows a sender to specify the
  address he prefers be whitelisted once he confirms his first
  message.

  For more information, see the following URLs:

  <URL:http://tmda.net/config-vars.html#PRIMARY_ADDRESS_MATCH>
  <URL:http://tmda.net/faq.cgi?req=show&file=faq04.005.htp>

* New feature. You can customize the header lines displayed by
  tmda-pending in interactive mode by setting SUMMARY_HEADERS. See
  <URL:http://tmda.net/config-vars.html#SUMMARY_HEADERS> for more
  information.

* New version of Josh Huber's tmda.el.

* Bugfixes.

Here are the new additions to UPGRADE:

* If you are using customized templates, you should replace
  %(envelope_sender)s with %(confirm_append_address)s in your
  confirm_request.txt. This is to support the new
  <URL:http://tmda.net/config-vars.html#PRIMARY_ADDRESS_MATCH>
  feature.

* When doing program deliveries to procmail, you should no longer be
  using the ``-f'' option. e.g,

  DELIVERY = "|/usr/bin/procmail -f $SENDER ~/.procmailrc-tmda"

  becomes

  DELIVERY = "|/usr/bin/procmail ~/.procmailrc-tmda"

* contrib/sample.tmdarc has been renamed contrib/sample.config.
2002-12-12 04:38:30 +00:00
kim
4deadf0dc7 Upgrade to tmda-0.64:
* New feature. TEMPLATE_DIR_MATCH_SENDER provides a way to further
  specialize the template selection process. When enabled, TMDA looks
  for templates in a subdirectory of TEMPLATE_DIR that matches the
  sender address, and then increasingly general portions of the domain
  part of the address. For more information and an example, see
  <URL:http://tmda.net/config-vars.html#TEMPLATE_DIR_MATCH_SENDER>

* tmda-pending now allows messages to be specified on standard input
  instead of the command line by using `-' instead of a message
  list. See ``tmda-pending -h'' for an example. Thanks to Michael
  S. Fischer for the patch.

Only accept Python 2.2, as the PLIST is incorrect for 2.1 (due to one
file failing to compile).
2002-11-14 04:25:31 +00:00
schmonz
284f11ca73 Update to 0.63. From the changelog:
* Python version 2.1 or greater is now required.  Upgrade at
  <URL:http://www.python.org/download/>

* When sending an auto response, a new configuration variable
  (AUTORESPONSE_INCLUDE_SENDER_COPY) is used to control whether a copy
  of the sender's message is included or not.  For available options,
  <URL:http://tmda.net/config-vars.html#AUTORESPONSE_INCLUDE_SENDER_COPY>

  If you are using customized templates, you should remove the last
  few lines in each template which include the sender's copy.  For
  example, in confirm_request.txt:

  --- Enclosed is a copy of your message.

  %(original_message)s

  Otherwise, you'll include two copies of the sender's message.

* When sending confirmation requests, Reply-To is now set from the
  confirm_request.txt template.  This is to allow the option to not
  include the confirmation address in a Reply-To header.

  If you use a customized confirm_request.txt, you'll need to add the
  following line to the top (header section) of your template:

  Reply-To: %(confirm_accept_address)s
2002-11-11 05:28:07 +00:00
jlam
e44bf515dc Strip the ".buildlink" from the names of the python application and
extension Makefile fragments, because they really don't have anything to
do with the buildlink[12] frameworks.  Change all the Makefiles that use
application.buildlink.mk and extension.buildlink.mk to use application.mk
and extension.mk instead.
2002-09-21 23:46:45 +00:00
schmonz
67c50710c1 Update to 0.61. From the changelog:
* New -A option for tmda-ofmipd to allow authentication against
  checkpassword compatible programs such as checkpassword-pam
  (http://checkpasswd-pam.sourceforge.net/).

* New -C option for tmda-ofmipd to set a limit on the number of
  simultaneous connections.  Default is 20.

* tmda-ofmipd general bugfixes and security improvements.

* New config variable, `X_TMDA_IN_SUBJECT' which turns on parsing of
  the Subject header for X-TMDA override actions.  See description in
  Defaults.py for more information.

* New config variable, `ADDED_HEADERS_SERVER' which allows you to add
  arbitrary headers to all server-sent (i.e, tmda-filter) messages.

* Josh Huber's tmda.el, an elisp module for integrating TMDA with Gnus
  and Message mode, has been added to the contrib directory.  This is
  super-cool, Jason sez check it out!

* Major improvements to the filter file language, courtesy of Tim,
  including:

   - The addition of "macro" definition and expansion.
   - The addition of variable interpolation.
   - A new argument, `-optional', for all rules that access files.
   - Support for nested filter files with the 'include' statement.

   For more information on these new features, see the updated TMDA
   Filter Specification (http://tmda.net/config-filter.html).

* Logging capability for client-side message (i.e, those sent with
  tmda-sendmail).  Set LOGFILE_OUTGOING in your config to enable this.

* New version of tmda.el.

* Fixed a bug which prevented the `from/to-mailman' filter sources
  from working.
2002-08-31 23:08:40 +00:00
schmonz
971f79e06c Update to 0.58.
Changes to the package itself:

- Update MASTER_SITES and HOMEPAGE.
- Change iterator variables to something other than "file" to
  placate pkglint.

From the changelog:

* 'keyword' addresses now use an identifying string like 'dated' and
  'sender' addresses do.  'keyword' by default, and customizable via
  TAGS_KEYWORD.  This means you'll need to generate new addresses
  using `tmda-address', as your old ones will no longer work.

  If you want your old keyword addresses to be accepted until you can
  transition to the new format, you can add entries for them in your
  FILTER_INCOMING.  e.g,

  to jason-promos.8d06eu@mastaler.com ok
  to jason-stupid_promo.289j76@mastaler.com ok

* RECIPIENT_DELIMITER is no longer allowed to be part of the keyword
  in a keyword address.  `?' will be substituted for it when a new
  keyword address is created.

* The format for a confirmation request address is now:

  RECIPIENT-confirm-TIMESTAMP.PID.HMAC, instead of
  RECIPIENT-confirm-accept.TIMESTAMP.PID.HMAC

  The new format is detailed in CRYPTO.  Because of this change, it's
  recommended that you run tmda-pending to make sure your queue is
  free of legitimate messages, since the old confirmation addresses
  will no longer work.

  If you are unable to do this and need temporary backward
  compatibility with the old format, there is a patch against 0.56
  available at:
  <URL:http://mla.libertine.org/tmda-users/200206/msg00193.html>

* Confirmed messages are now reinjected to the original envelope
  recipient address (RECIPIENT) rather than to:
  RECIPIENT-confirm-done.TIMESTAMP.PID.HMAC

  See CRYPTO for more details.

* TMDA now sends outgoing mail by handing it off to an SMTP server
  instead of the /usr/sbin/sendmail program.  By default it will use
  the standard SMTP port (25) on the local host.  You can modify this
  by setting the "SMTPHOST" variable in your tmdarc.  See
  TMDA/Defaults.py for further information.

* tmdarc variable SENDMAIL has been renamed SENDMAIL_PROGRAM, but is
  irrelevant unless OUTGOINGMAIL = "sendmail".

* tmdarc variable PURGED_HEADERS now lists "Bcc:" and "Resent-Bcc" by
  default.  If you define this variable in your tmdarc, be sure to add
  these two headers.

* CRYPT_KEY should be removed from ~/.tmdarc or ~/.tmda/config.  Your
  secret key is now read from CRYPT_KEY_FILE, which defaults to
  ~/.tmda/crypt_key.  To make this conversion, move your existing
  CRYPT_KEY to ~/.tmda/crypt_key, but without the double-quotes.  e.g,

  if CRYPT_KEY = "df7a18a8d95f02ff94bf6463a8ec214cf20cb9e8"

  ~/.tmda/crypt_key should contain:
  df7a18a8d95f02ff94bf6463a8ec214cf20cb9e8

* ~/.tmdarc and ~/.tmda/config are no longer checked for file
  permissions.  Instead, make sure ~/.tmda/crypt_key is chmod 400 or
  600 (or 640 if ALLOW_MODE_640 = 1).

* An exception is no longer be raised if ~/.tmdarc or ~/.tmda/config
  is missing.  However, a ~/.tmda/crypt_key file is required.

* tmda-keygen now outputs an unquoted key instead of a CRYPT_KEY line.

* Template variables dated_cookie_address and sender_cookie_address
  were replaced with dated_recipient_address and
  sender_recipient_address, which are based on the RECIPIENT address.
2002-07-23 20:05:47 +00:00
schmonz
14f19c69ad Update to 0.55. Changes:
* Tighter integration of the local delivery code.  An external LDA
  like procmail is now required only if you are running Sendmail.
  Further, if you are driving TMDA with procmail, you no longer need
  to maintain a second procmailrc (e.g, ~/.procmailrc-tmda) for final
  delivery.

* Improvements to the mailing list filter file sources.

* Bugfixes.
2002-05-14 14:38:56 +00:00
schmonz
c3f709d021 Update to 0.54. Changes:
* New ``--terse-summary'' option to tmda-pending which can be used as
  an alternative to ``--summary''.  See ``tmda-pending -h'' for more.

* New tmdarc options PENDING_DELETE_APPEND and PENDING_RELEASE_APPEND
  which define filenames to which the sender address will be appended
  when a message is deleted or released by tmda-pending.  This can be
  used for example to update your white/blacklist from tmda-pending.

* In addition to ~/.tmdarc, ~/.tmda/config is now a valid location for
  your TMDA configuration file.

* Performance improvements.

* Bugfixes.
2002-05-12 15:01:59 +00:00
schmonz
d18a282084 Update to 0.52:
* Fix a bug in tmda-pending that would result in delivered messages
  being skipped during batch/delete (-bd) runs.
2002-04-23 19:26:33 +00:00
schmonz
bc4f128588 Update to 0.51. From the changelog:
* Messages in the pending directory are no longer deleted after they
  are confirmed (or released) and delivered.  Now they are simply
  noted in the DELIVERED_CACHE file.

* BOUNCE_TEXT_ALREADY_CONFIRMED has been deprecated.

* The confirm_accept.txt template has been modified.  The message body
  of the notification is no longer hardcoded, but rather stored in
  %(confirm_accept_text)s, which comes from one of the following
  tmdarc variables depending on context:

  CONFIRM_ACCEPT_TEXT_INITIAL
  CONFIRM_ACCEPT_TEXT_ALREADY_CONFIRMED
  CONFIRM_ACCEPT_TEXT_ALREADY_RELEASED

* Custom templates are now referred to by a template directory rather
  than individually.  Any templates found in this directory will be
  used, otherwise the default templates will be used.  You can specify
  a custom template directory in one of two ways:

  A TEMPLATE_DIR setting in your tmdarc.  This replaces use of
  CONFIRM_ACCEPT_TEMPLATE and CONFIRM_REQUEST_TEMPLATE.

  tmda-filter's -t option, which replaces both -A and -R.

* The 'unquoted' and 'parens' options to MESSAGE_FROM_STYLE have been
  deprecated.  'angles' now double-quotes the fullname only when
  necessary.
2002-04-07 06:56:34 +00:00
wiz
87b88e46c4 Update to 0.48, provided by Amitai Schlair in pkg/15783.
Changes:
* TMDA has acquired the ability to handle local mail delivery itself.
  It can now do safe and reliable delivery to qmail-style Maildirs and
  mboxrd-format mboxes, as well as program (pipe) delivery, and
  forward to a different e-mail address.
* Added an -autodbm argument to the 'from-file' and 'to-file' filter
  sources to match the existing -autocdb capability.  -autodbm
  automatically maintains a DBM file for the specified TMDA list file.
  No more rebuilding your DBM files by hand, cron, or scripting.
* Added the ability to use 'from*' rules in outgoing filters.
  See the TMDA Filter Specification for details.
* Lots of internal reorganization.
2002-03-14 17:24:18 +00:00
drochner
92ecbe5a01 import of tmda-0.46, a Python-based SPAM reduction system, submitted by
Amitai Schlair per PR pkg/15075
2002-02-14 13:00:25 +00:00