Release 0.8.4
This commit is contained in:
@@ -5,8 +5,11 @@ wrapper (Milter.py) that handles attachments, did lots of testing, packaged
|
|||||||
it with distutils, and generally transformed it from a quick hack to a
|
it with distutils, and generally transformed it from a quick hack to a
|
||||||
real, usable Python extension.
|
real, usable Python extension.
|
||||||
|
|
||||||
Other contributors:
|
Other contributors (in random order):
|
||||||
|
|
||||||
|
Dave MacQuigg
|
||||||
|
for noticing that smfi_insheader wasn't supported, and creating
|
||||||
|
a template to help first time pymilter users create their own milter.
|
||||||
Terence Way
|
Terence Way
|
||||||
for providing a Python port of SPF
|
for providing a Python port of SPF
|
||||||
Scott Kitterman
|
Scott Kitterman
|
||||||
|
|||||||
+1
-1
@@ -16,7 +16,7 @@ from milter import ACCEPT,CONTINUE,REJECT,DISCARD,TEMPFAIL, \
|
|||||||
try: from milter import QUARANTINE
|
try: from milter import QUARANTINE
|
||||||
except: pass
|
except: pass
|
||||||
|
|
||||||
__version__ = '0.8.3'
|
__version__ = '0.8.4'
|
||||||
|
|
||||||
_seq_lock = thread.allocate_lock()
|
_seq_lock = thread.allocate_lock()
|
||||||
_seq = 0
|
_seq = 0
|
||||||
|
|||||||
@@ -1,6 +1,9 @@
|
|||||||
Train honeypot with auto-whitelisted mail as ham. This should result in
|
Send DSN for permerror before processing extended result. An additional
|
||||||
a totally self training auto screener. Rescind whitelist for banned
|
DSN may be sent based on extended result.
|
||||||
extensions, in case sender is infected.
|
|
||||||
|
Rescind whitelist for banned extensions, in case sender is infected.
|
||||||
|
|
||||||
|
Train honeypot on error only.
|
||||||
|
|
||||||
Find rfc2822 policy for MFROM quoting.
|
Find rfc2822 policy for MFROM quoting.
|
||||||
|
|
||||||
|
|||||||
+6
-4
@@ -1,5 +1,5 @@
|
|||||||
%define name milter
|
%define name milter
|
||||||
%define version 0.8.3
|
%define version 0.8.4
|
||||||
%define release 1.RH7
|
%define release 1.RH7
|
||||||
# what version of RH are we building for?
|
# what version of RH are we building for?
|
||||||
%define redhat9 0
|
%define redhat9 0
|
||||||
@@ -169,10 +169,12 @@ rm -rf $RPM_BUILD_ROOT
|
|||||||
/usr/share/sendmail-cf/hack/rhsbl.m4
|
/usr/share/sendmail-cf/hack/rhsbl.m4
|
||||||
|
|
||||||
%changelog
|
%changelog
|
||||||
* Fri Oct 20 2005 Stuart Gathman <stuart@bmsi.com> 0.8.4-1
|
* Thu Oct 20 2005 Stuart Gathman <stuart@bmsi.com> 0.8.4-1
|
||||||
- Fix SPF policy via sendmail access map (case insensitive keys).
|
- Fix SPF policy via sendmail access map (case insensitive keys).
|
||||||
- Auto whitelist senders
|
- Auto whitelist senders, train screener on whitelisted messages
|
||||||
* Thu Oct 12 2005 Stuart Gathman <stuart@bmsi.com> 0.8.3-1
|
- Optional idx parameter to addheader to invoke smfi_insheader
|
||||||
|
- Activate progress when SMFIR_PROGRESS defined
|
||||||
|
* Wed Oct 12 2005 Stuart Gathman <stuart@bmsi.com> 0.8.3-1
|
||||||
- Keep screened honeypot mail, but optionally discard honeypot only mail.
|
- Keep screened honeypot mail, but optionally discard honeypot only mail.
|
||||||
- spf_accept_fail option for braindead SPF senders (treats fail like softfail)
|
- spf_accept_fail option for braindead SPF senders (treats fail like softfail)
|
||||||
- Consider SMTP AUTH connections internal.
|
- Consider SMTP AUTH connections internal.
|
||||||
|
|||||||
+1
-1
@@ -18,7 +18,7 @@ sent via an authorized SMTP server, but may still be legitimate. Since there
|
|||||||
is no positive confirmation that the message is really from you, we have
|
is no positive confirmation that the message is really from you, we have
|
||||||
to give it extra scrutiny - including verifying that the sender really
|
to give it extra scrutiny - including verifying that the sender really
|
||||||
exists by sending you this DSN. We will remember this sender and not
|
exists by sending you this DSN. We will remember this sender and not
|
||||||
bother you again for while. You can avoid this message entirely for
|
bother you again for a while. You can avoid this message entirely for
|
||||||
legitimate mail by using an authorized SMTP server. Contact your mail
|
legitimate mail by using an authorized SMTP server. Contact your mail
|
||||||
administrator and ask how to configure your email client to use an
|
administrator and ask how to configure your email client to use an
|
||||||
authorized server.
|
authorized server.
|
||||||
|
|||||||
Reference in New Issue
Block a user