<?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.imap.courier.general">
    <title>gmane.mail.imap.courier.general</title>
    <link>http://permalink.gmane.org/gmane.mail.imap.courier.general</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.imap.courier.general/34481"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.imap.courier.general/34480"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.imap.courier.general/34479"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.imap.courier.general/34478"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.imap.courier.general/34477"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.imap.courier.general/34476"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.imap.courier.general/34475"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.imap.courier.general/34474"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.imap.courier.general/34473"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.imap.courier.general/34472"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.imap.courier.general/34471"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.imap.courier.general/34470"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.imap.courier.general/34469"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.imap.courier.general/34468"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.imap.courier.general/34467"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.imap.courier.general/34466"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.imap.courier.general/34465"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.imap.courier.general/34464"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.imap.courier.general/34463"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.imap.courier.general/34462"/>
      </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.imap.courier.general/34481">
    <title>Re: E-Mails rejected due to MIME boundary too long</title>
    <link>http://permalink.gmane.org/gmane.mail.imap.courier.general/34481</link>
    <description>&lt;pre&gt;

Try:

     sprintf(p, "=_%-1.30s-%s-%s-%s", hostnamebuf,
        pidbuf, timebuf, cntbuf);

Also, a similar change to gpglib/gpg.c in newboundary():

sprintf(buffer, "=_%-1.30s-%u-%u-%04u",
hostnamebuf, (unsigned)getpid(),
(unsigned)t, ++counter);
return (buffer);


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
courier-users mailing list
courier-users&amp;lt; at &amp;gt;lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
&lt;/pre&gt;</description>
    <dc:creator>Sam Varshavchik</dc:creator>
    <dc:date>2012-05-18T17:06:45</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.imap.courier.general/34480">
    <title>Re: E-Mails rejected due to MIME boundary too long</title>
    <link>http://permalink.gmane.org/gmane.mail.imap.courier.general/34480</link>
    <description>&lt;pre&gt;Hello Sam,
first of all, sorry for the long delay. My admin was absent so I could
not try it out earlier.

On Tue, May 01, 2012 at 06:22:45PM -0400, Sam Varshavchik wrote:

I don't think this is possible on this machine, unfortuantely.


I rebuild with this fix and at first it seemed to work, some test
mails went through:
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=_static.213-239-213-133.clients.your-server.de-2710-1337109850-0001-2"

Now when I just wanted to do one final test, I got the same error message again:

                           UNDELIVERABLE MAIL

Your message to the following recipients cannot be delivered:

&amp;lt;kreutzm-guest&amp;lt; at &amp;gt;alioth.debian.org&amp;gt;:
    mail.alioth.debian.org [217.196.43.134]:
&amp;lt;&amp;lt;&amp;lt; 550 Broken MIME container (Long MIME Boundary)
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=_static.213-239-213-133.clients.your-server.de-11578-1337348775-0001-2"

Thanks for any further hints.

Gree&lt;/pre&gt;</description>
    <dc:creator>Helge Kreutzmann</dc:creator>
    <dc:date>2012-05-18T13:56:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.imap.courier.general/34479">
    <title>Re: build error on courier-authlib-0.64.0</title>
    <link>http://permalink.gmane.org/gmane.mail.imap.courier.general/34479</link>
    <description>&lt;pre&gt;


Install the source rpm, to get its spec file.

Modify the spec file, between "%setup" and "%configure -C --with-redhat",  
add a line:

autoreconf

Then try to build it using the modified spec file.

If this doesn't work, ask around on the CentOS lists. This should be a  
fairly common issue with packages built for CentOS; they should tell you  
what the real fix is.


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
courier-users mailing list
courier-users&amp;lt; at &amp;gt;lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
&lt;/pre&gt;</description>
    <dc:creator>Sam Varshavchik</dc:creator>
    <dc:date>2012-05-16T22:46:30</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.imap.courier.general/34478">
    <title>build error on courier-authlib-0.64.0</title>
    <link>http://permalink.gmane.org/gmane.mail.imap.courier.general/34478</link>
    <description>&lt;pre&gt;I downloaded the current tarball and tried to build the rpms on a CentOS
4 system.  I got these errors:

$ rpmbuild -tb courier-authlib-0.64.0.tar.bz2
...
libtool: link: ar cru .libs/libauthpipe.a  authpipe.o authpipelib.o
libtool: link: ranlib .libs/libauthpipe.a
libtool: link: ( cd ".libs" &amp;amp;&amp;amp; rm -f "libauthpipe.la" &amp;amp;&amp;amp; ln -s
"../libauthpipe.la" "libauthpipe.la" )
libtool: link: gcc -I/usr/include/mysql -g -pipe -m32 -march=i386
-mtune=pentium4 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-fno-strict-aliasing -I/usr/include -O2 -g -pipe -m32 -march=i386
-mtune=pentium4 -Wall -I.. -I./.. -o authdaemontest authdaemontest.o 
./.libs/libcourierauthcommon.a
/home/bowieb/rpm/BUILD/courier-authlib-0.64.0/.libs/libcourierauth.a -ldl
libtool: link: cannot find the library `libltdl/libltdlc.la' or
unhandled argument `libltdl/libltdlc.la'
make[2]: *** [authdaemondprog] Error 1
make[2]: *** Waiting for unfinished jobs....
libtool: link: gcc -I/usr/include/mysql -g -pipe -m32 -march=i386
-mtune=pentium4 -D_GN&lt;/pre&gt;</description>
    <dc:creator>Bowie Bailey</dc:creator>
    <dc:date>2012-05-16T15:20:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.imap.courier.general/34477">
    <title>Re: Courier at Github</title>
    <link>http://permalink.gmane.org/gmane.mail.imap.courier.general/34477</link>
    <description>&lt;pre&gt;
Pull requests seem to be practical for occasional updates.  Doesn't
github provide for managing a project with several contribs, each one
maintained autonomously?

For example, if I were to add zdkimfilter, a link from README would
seem to be easier to operate than a stream of requests.  Am I missing
something?

&lt;/pre&gt;</description>
    <dc:creator>Alessandro Vesely</dc:creator>
    <dc:date>2012-05-14T16:42:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.imap.courier.general/34476">
    <title>Re: TLS on port 587?</title>
    <link>http://permalink.gmane.org/gmane.mail.imap.courier.general/34476</link>
    <description>&lt;pre&gt;

If STARTTLS is advertised on 25, it should also be advertised on 587. Check  
that you have STARTTTLS in the EHLO response on 25.

Either /usr/bin/couriertls, or $TLS_CERTFILE is missing.

If you use ${TLS_CERTFILE}.[ip address], you still need $TLS_CERTFILE  
symlinked to one of them.


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
courier-users mailing list
courier-users&amp;lt; at &amp;gt;lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
&lt;/pre&gt;</description>
    <dc:creator>Sam Varshavchik</dc:creator>
    <dc:date>2012-05-14T02:14:32</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.imap.courier.general/34475">
    <title>TLS on port 587?</title>
    <link>http://permalink.gmane.org/gmane.mail.imap.courier.general/34475</link>
    <description>&lt;pre&gt;I must be missing something in the docs.

How do I enable TLS (or SSL?) on port 587?


~ egrep -v "^(#|$)" /etc/courier/esmtpd
ESMTP_LOG_DIALOG=0
BOFHNOVRFY=1
PATH=/usr/bin:/bin:/usr/bin:/usr/local/bin
SHELL=/bin/sh
ULIMIT=16384
BOFHCHECKDNS=1
BOFHNOEXPN=1
NOADDMSGID=1
NOADDDATE=1
AUTH_REQUIRED=0
COURIERTLS=/usr/bin/couriertls
TLS_CERTFILE=/usr/lib/courier/esmtpd.pem
TLS_VERIFYPEER=NONE
MAILUSER=daemon
MAILGROUP=daemon
PORT=smtp
BLACKLISTS='-block=zen.spamhaus.org,BLOCK'
ACCESSFILE=${sysconfdir}/smtpaccess
MAXDAEMONS=400
MAXPERC=40
MAXPERIP=40
PIDFILE=/var/run/courier/esmtpd.pid
TCPDOPTS="-stderrlogger=/usr/sbin/courierlogger -noidentlookup -nodnslookup"
ESMTPAUTH="LOGIN PLAIN CRAM-MD5 CRAM-SHA1 CRAM-SHA256"
ESMTPAUTH_WEBADMIN="LOGIN CRAM-MD5 CRAM-SHA1 CRAM-SHA256"
ESMTPAUTH_TLS=""
ESMTPAUTH_TLS_WEBADMIN="PLAIN LOGIN CRAM-MD5 CRAM-SHA1 CRAM-SHA256"
ESMTPDSTART=YES

~ egrep -v "^(#|$)" /etc/courier/esmtpd-msa
BOFHCHECKDNS=1
NOADDMSGID=0
NOADDDATE=0
ESMTP_LOG_DIALOG=0
AUTH_REQUIRED=1
BLACKLISTS=""
ADDRESS=0
PO&lt;/pre&gt;</description>
    <dc:creator>Mark Constable</dc:creator>
    <dc:date>2012-05-13T23:36:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.imap.courier.general/34474">
    <title>Re: Courier at Github</title>
    <link>http://permalink.gmane.org/gmane.mail.imap.courier.general/34474</link>
    <description>&lt;pre&gt;
Thanks Sam. I hope it's not a waste of your time.

https://github.com/svarshavchik/courier-contrib

Folks, to play along just fork the above repo, add your stuff, commit/push
and then click on Pull Request on your Github page. Perhaps follow my simple
scripts example in README.md and add you scripts/programs in alphabetical
order and wrap the text to about 72 chars so it's easy to include in emails.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
courier-users mailing list
courier-users&amp;lt; at &amp;gt;lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

&lt;/pre&gt;</description>
    <dc:creator>Mark Constable</dc:creator>
    <dc:date>2012-05-13T13:59:12</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.imap.courier.general/34473">
    <title>Re: Courier at Github</title>
    <link>http://permalink.gmane.org/gmane.mail.imap.courier.general/34473</link>
    <description>&lt;pre&gt;

Yeah, right now things are comparably slow and steady; and a central  
subversion repo for the source code seems to be perfectly sufficient. But,  
who knows, if the pace picks up I'll certainly move the code to git; either  
github (probably), or Sourceforge's git server (maybe).


Well, I do have a link page that I maintain, that I'm pretty open as far as  
adding new links there.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
courier-users mailing list
courier-users&amp;lt; at &amp;gt;lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
&lt;/pre&gt;</description>
    <dc:creator>Sam Varshavchik</dc:creator>
    <dc:date>2012-05-12T15:02:47</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.imap.courier.general/34472">
    <title>Courier at Github</title>
    <link>http://permalink.gmane.org/gmane.mail.imap.courier.general/34472</link>
    <description>&lt;pre&gt;I was going to reply to the market share thread but this is a more specific
suggestion. How about an "official" Courier Github project that hosts all
the 3rd party utilities and nick nacks that no doubt a lot of us have
developed over the years. All in one well managed and highly visible place?

I'd love to see Mr Sam actually use Github as his primary source code repo
but I also suspect he is perfectly happy with the current repo system but
some central repo for the rest of us make our contributions could be very
useful. Maybe.

Anyone, of course, could set something up but unless it's "blessed" by Sam in
some way it's not going to fly.

What do folks think about this? Are there enough "3rd party" utilities lying
around on our hard drives, hidden from the rest of the world, to warrant a
central "official" meta repo for Courier?

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
th&lt;/pre&gt;</description>
    <dc:creator>Mark Constable</dc:creator>
    <dc:date>2012-05-12T14:46:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.imap.courier.general/34471">
    <title>Re: Courier "market share"</title>
    <link>http://permalink.gmane.org/gmane.mail.imap.courier.general/34471</link>
    <description>&lt;pre&gt;

No specific reason. Just the way the code turned out to be. But it's  
possible that &amp;lt;hostname&amp;gt; ESMTP was the standard greeting text, way back  
when, so that's what I went with.


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
courier-users mailing list
courier-users&amp;lt; at &amp;gt;lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
&lt;/pre&gt;</description>
    <dc:creator>Sam Varshavchik</dc:creator>
    <dc:date>2012-05-12T14:20:43</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.imap.courier.general/34470">
    <title>Re: Courier "market share"</title>
    <link>http://permalink.gmane.org/gmane.mail.imap.courier.general/34470</link>
    <description>&lt;pre&gt;
For a very very very skewed survey, since Courier is one of the MTA
packages that support SPF, its share among those who enable
reject-on-fail at the MAIL command (which excludes postfix, for
example) can be inferred from the attached file (5th to 8th place, I'd
say.)

I drew two random ~30K-entries samples from a bunch of ~250K domain
names, and found that reject-on-fail can be detected in some 1.2% of
cases by this method (which is part of why the test is so skewed for
your purpose.)

I'd bet Sam did explain why Courier doesn't start sessions with an
identifiable greeting text, but am unable to quickly find any pointer.

&lt;/pre&gt;</description>
    <dc:creator>Alessandro Vesely</dc:creator>
    <dc:date>2012-05-12T09:14:12</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.imap.courier.general/34469">
    <title>Re: Rate limiting</title>
    <link>http://permalink.gmane.org/gmane.mail.imap.courier.general/34469</link>
    <description>&lt;pre&gt;
In addition to fail2ban, which I believe would work reasonably well, 
pythonfilter has a rate limiting module.  It currently limits by IP 
address, but changing just one line would allow you to rate limit users 
instead:
http://phantom.dragonsdawn.net/~gordon/courier-pythonfilter/courier-pythonfilter-1.7/filters/ratelimit.py
http://phantom.dragonsdawn.net/~gordon/courier-pythonfilter/

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
courier-users mailing list
courier-users&amp;lt; at &amp;gt;lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

&lt;/pre&gt;</description>
    <dc:creator>Gordon Messmer</dc:creator>
    <dc:date>2012-05-11T22:28:47</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.imap.courier.general/34468">
    <title>Courier "market share"</title>
    <link>http://permalink.gmane.org/gmane.mail.imap.courier.general/34468</link>
    <description>&lt;pre&gt;I went looking for some statistics on how Courier-MTA stacks up against
other MTA packages - something similar to Netcraft's web server survey.
I found nada.  I did find one page at
&amp;lt;http://shearer.org/MTA_Comparison&amp;gt; implying that Courier-MTA isn't
really a MTA at all, although this was from 2007.

Qmail still seems to be popular, in spite of its lack of modernization
and developer support, and its quirky license.  Courier, which is
well-maintained and supported, GPL licensed, and appears to have a wide
international user base, is seldom mentioned at all.

Does anyone have any stats, or reference to recent surveys, with some
figures?

I've been trying forever to get the Mailman list server developers
(&amp;lt;http://www.gnu.org/software/mailman&amp;gt;) to include a courier-to-mailman
list insertion script for courier which I wrote _years_ ago.  It finally
made it to the contrib collection (along with qmail-to-mailman) but
unlike the qmail script it has never been properly integrated into
configure.in so as to be properl&lt;/pre&gt;</description>
    <dc:creator>Lindsay Haisley</dc:creator>
    <dc:date>2012-05-11T19:37:40</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.imap.courier.general/34467">
    <title>Inconsistency between esmtpd.cnf and mkesmtpdcertscript</title>
    <link>http://permalink.gmane.org/gmane.mail.imap.courier.general/34467</link>
    <description>&lt;pre&gt;Hello,

there is an inconsistency in esmtpd.cnf.openssl.in which is fixed by the attached
patch.

All other .cnf files and all mkcert scripts are using .rand as extension for
the "RANDFILE".

Regards
Racke

&lt;/pre&gt;</description>
    <dc:creator>Stefan Hornburg (Racke</dc:creator>
    <dc:date>2012-05-09T10:39:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.imap.courier.general/34466">
    <title>Re: Rate limiting</title>
    <link>http://permalink.gmane.org/gmane.mail.imap.courier.general/34466</link>
    <description>&lt;pre&gt;

Backscatter tracks recipient addresses.


A newmsg line records each new message received via smtp:

May  6 04:07:03 shorty courierd: newmsg,id=00000000000A03CA. 
000000004FA63127.00000588: dns; lists.sourceforge.net (lists.sourceforge.net  
[::ffff:216.34.181.88])

This tracks only messages that have been succesfully received. Gives you the  
IP address of the connecting SMTP client. You can count how many were  
received from a given IP address, and go from there.

And, again, a filter module gets access to the control file of each message,  
which has a complete dossier of what the message is all about; which IP  
address it came from, more importantly if it was from the authenticated  
sender, the authenticated identity.

The info is all there, all that's needed is the code to keep track of it all.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has change&lt;/pre&gt;</description>
    <dc:creator>Sam Varshavchik</dc:creator>
    <dc:date>2012-05-08T23:39:23</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.imap.courier.general/34465">
    <title>Re: Rate limiting</title>
    <link>http://permalink.gmane.org/gmane.mail.imap.courier.general/34465</link>
    <description>&lt;pre&gt;
I'm not sure how fail2ban could work with outgoing mail as it would need
to track all connection IPs and watch for the number of delivered per user
and then if that rate hits a limit then decide which was the originating
IP and do an iptables block. I know it's pretty good at doing this with
logfiles that contain the incoming IP per line but in this case the IP
is going to be way back in the logfile, and that's assuming that the
logfile hasn't been rotated.

My brief episode with Plesk and postfix showed they used something called
policyd for this purpose, http://policyd.org/content/features

"This policy daemon is designed mostly for large scale mail hosting
environments. The main goal is to implement as many spam combating
and email compliance features as possible while at the same time
maintaining the portability, stability and performance required for
mission critical email hosting of today."

So Sam, would it be possible to use, say, the BACKSCATTER facility to have
an idea what message-id was associat&lt;/pre&gt;</description>
    <dc:creator>Mark Constable</dc:creator>
    <dc:date>2012-05-08T23:21:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.imap.courier.general/34464">
    <title>Re: new "longer" TLS keys needed,</title>
    <link>http://permalink.gmane.org/gmane.mail.imap.courier.general/34464</link>
    <description>&lt;pre&gt;

With gnutls, use:

certtool -p --dsa --sec-param normal --outfile privkey.pem
certtool -s --load-privkey privkey.pem --outfile cert.pem

Concatenate privkey.pem and cert.pem together.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
courier-users mailing list
courier-users&amp;lt; at &amp;gt;lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
&lt;/pre&gt;</description>
    <dc:creator>Sam Varshavchik</dc:creator>
    <dc:date>2012-05-08T22:16:47</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.imap.courier.general/34463">
    <title>new "longer" TLS keys needed,</title>
    <link>http://permalink.gmane.org/gmane.mail.imap.courier.general/34463</link>
    <description>&lt;pre&gt;Hi all,

just today (glad to see others using STARTTLS) I got a bounce back:

 &amp;gt;&amp;gt;&amp;gt; STARTTLS
  &amp;lt;&amp;lt;&amp;lt; 500 The Diffie-Hellman prime sent by the server is not acceptable 
(not long enough).

My self signed keys are due to coincidentally expire in a week or so. 
Unfortunately, due to very severe head/eye injury, it's tough to RTFM 
:-) "oops" is my best thought on that subject...

Anyone care to assist with the appropriate command lines to help me roll 
new keys this weekend?

Thanks kindly,
Andy
p.s. Mr. Sam, thanks for a decade of first class software!

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
courier-users mailing li&lt;/pre&gt;</description>
    <dc:creator>Andrew Burnette</dc:creator>
    <dc:date>2012-05-08T20:46:14</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.imap.courier.general/34462">
    <title>Re: Rate limiting</title>
    <link>http://permalink.gmane.org/gmane.mail.imap.courier.general/34462</link>
    <description>&lt;pre&gt;
...



I use fail2ban (http://www.fail2ban.org/) for that purpose.
You can set your log line regexps, and it works!


&lt;/pre&gt;</description>
    <dc:creator>Dino Ciuffetti</dc:creator>
    <dc:date>2012-05-08T10:09:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.imap.courier.general/34461">
    <title>Re: Rate limiting</title>
    <link>http://permalink.gmane.org/gmane.mail.imap.courier.general/34461</link>
    <description>&lt;pre&gt;

It's not the scenario for these knobs. These knobs are there mostly to set  
the maximum upper limits to keep one from blowing away all the RAM and  
network bandwidth. That the kind of "rate limiting" this is.


There's nothing there that can be readily used for something like this. I  
suppose one can hack up a perlfilter script that counts messages from each  
authenticated user.


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
courier-users mailing list
courier-users&amp;lt; at &amp;gt;lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
&lt;/pre&gt;</description>
    <dc:creator>Sam Varshavchik</dc:creator>
    <dc:date>2012-05-08T00:52:58</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.mail.imap.courier.general">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.mail.imap.courier.general</link>
  </textinput>
</rdf:RDF>

