<?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://blog.gmane.org/gmane.mail.imap.courier.general">
    <title>gmane.mail.imap.courier.general</title>
    <link>http://blog.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://comments.gmane.org/gmane.mail.imap.courier.general/34485"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.imap.courier.general/34482"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.imap.courier.general/34478"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.imap.courier.general/34475"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.imap.courier.general/34472"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.imap.courier.general/34468"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.imap.courier.general/34467"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.imap.courier.general/34463"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.imap.courier.general/34458"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.imap.courier.general/34455"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.imap.courier.general/34452"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.imap.courier.general/34451"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.imap.courier.general/34450"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.imap.courier.general/34448"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.imap.courier.general/34442"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.imap.courier.general/34439"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.imap.courier.general/34413"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.imap.courier.general/34411"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.imap.courier.general/34410"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.imap.courier.general/34407"/>
      </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://comments.gmane.org/gmane.mail.imap.courier.general/34485">
    <title>Can not use my Intranet Server to relay mails...</title>
    <link>http://comments.gmane.org/gmane.mail.imap.courier.general/34485</link>
    <description>&lt;pre&gt;Hello *,

I have a Server Cluster which is configured as Cloud  for  currently  50
users (testing)

Any of the storage servers can send mails to &amp;lt;mail.tamay-dogan.net&amp;gt;  and
use it as relay...

I can ecven use the storage servers as relay which looks like

Workstation - storage000.tdcloud.net - mail.tamay-dogan.net - Recipient

BUT, if I use

Workstation - samba.intranet1.tamay-dogan.net - mail.t-d.net - Recipient

my &amp;lt;mail.tamay-dogan.net&amp;gt; tell me "relaying denied"...  This  is  grmpf,
since the Courier-installations are 1:1 copies, speak,  the  setups  are
100% identic.

Any hints what could happen to my network?

Note 1: I have local copies of both setups  &amp;lt;samba&amp;gt; and &amp;lt;storage000&amp;gt; and
        used 'diff -Nurp samba/ storage000/' to see the  difference, but
        appart the server names and IP adresses, there is NO  difference
        and &amp;lt;mail&amp;gt; is configured to accept mail from any machines in  my
        network...

Note 2: Mail send like
            samba.intranet1.tamay-dogan.net - mail.t-d.net - Reci&lt;/pre&gt;</description>
    <dc:creator>Michelle Konzack</dc:creator>
    <dc:date>2012-05-25T13:05:51</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.imap.courier.general/34482">
    <title>Courier-IMAP disconnecting at successful login</title>
    <link>http://comments.gmane.org/gmane.mail.imap.courier.general/34482</link>
    <description>&lt;pre&gt;Hi,

I'm happily using courier on dynds Webserver, but trying to setup 
another one recently, I've run into trouble.
I'm autheticating via authdaemond via mysql (plain) and everything works 
fine, I can logon, send &amp;amp; receive mail etc. until after an (seemingly 
undefined) uptime the server disconnects after a successful login. All I 
get is

    # telnet localhost 143
    Trying ::1...
    Connected to localhost.
    Escape character is '^]'.
    * OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE
    THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL
    ACL2=UNION STARTTLS] Courier-IMAP ready. Copyright 1998-2011 Double
    Precision, Inc.  See COPYING for distribution information.
    0 LOGIN %user %wrongpass
    0 NO Login failed.
    1 LOGIN %user %pass
    Connection closed by foreign host.

mail.log is full of

    May 21 23:33:48 %host imapd: Connection, ip=[::ffff:%IP]
    May 21 23:39:09 %host imapd: Connection, ip=[::ffff:%IP]
    May 21 23:39:09 %host imapd: Connection, ip=[::ffff:%IP]&lt;/pre&gt;</description>
    <dc:creator>xt&lt; at &gt;padimail.de</dc:creator>
    <dc:date>2012-05-24T09:44:57</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.imap.courier.general/34478">
    <title>build error on courier-authlib-0.64.0</title>
    <link>http://comments.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://comments.gmane.org/gmane.mail.imap.courier.general/34475">
    <title>TLS on port 587?</title>
    <link>http://comments.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://comments.gmane.org/gmane.mail.imap.courier.general/34472">
    <title>Courier at Github</title>
    <link>http://comments.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://comments.gmane.org/gmane.mail.imap.courier.general/34468">
    <title>Courier "market share"</title>
    <link>http://comments.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://comments.gmane.org/gmane.mail.imap.courier.general/34467">
    <title>Inconsistency between esmtpd.cnf and mkesmtpdcertscript</title>
    <link>http://comments.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://comments.gmane.org/gmane.mail.imap.courier.general/34463">
    <title>new "longer" TLS keys needed,</title>
    <link>http://comments.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://comments.gmane.org/gmane.mail.imap.courier.general/34458">
    <title>Rate limiting</title>
    <link>http://comments.gmane.org/gmane.mail.imap.courier.general/34458</link>
    <description>&lt;pre&gt;The first link in Google for this search suggests rate limiting is possible but
where is the actual info about how to enable and control it?

site:courier-mta.org rate limit

Rate limiting is implemented in the main scheduler, and applies to any transport mechanism, not just ESMTP

------------------------------------------------------------------------------
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-07T10:57:37</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.imap.courier.general/34455">
    <title>New releases of courier and courier-authlib packages</title>
    <link>http://comments.gmane.org/gmane.mail.imap.courier.general/34455</link>
    <description>&lt;pre&gt;Courier release 0.68.1

Courier-authlib release 0.64.0

Download: http://www.courier-mta.org/download.php

Changes:

• Updated courier-authlib RPM script adds support for systemd, and a fix for  
the PAM module. It's needed for certain PAM modules, like pam_krb5.

• Do not accept email addresses that begin with '&amp;lt; at &amp;gt;".

• Fix decoding of attachment filenames in some locales.

• Additional configuration options for servers with multiple IP addresses.

• Servers with very long hostnames can result in overly long MIME boundary  
delimiters. Truncate the hostname portion of it. This fix was broken in the  
tarball versioned 0.68.0; quickly pulled, and replaced with 0.68.1.

------------------------------------------------------------------------------
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.&lt;/pre&gt;</description>
    <dc:creator>Sam Varshavchik</dc:creator>
    <dc:date>2012-05-05T20:45:25</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.imap.courier.general/34452">
    <title>Vacation notices</title>
    <link>http://comments.gmane.org/gmane.mail.imap.courier.general/34452</link>
    <description>&lt;pre&gt;Been asked to build a client app to set vacation notices.

Is there any framework in courier that is available to accept this or
authenticate users before dropping a maildrop recipe into their
homedir?

Harry.

------------------------------------------------------------------------------
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>Harry Duncan</dc:creator>
    <dc:date>2012-05-01T22:20:47</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.imap.courier.general/34451">
    <title>E-Mails rejected due to MIME boundary too long</title>
    <link>http://comments.gmane.org/gmane.mail.imap.courier.general/34451</link>
    <description>&lt;pre&gt;Hello,
System:
mutt, talking to local courier (0.65.0) for transmission (outgoing);
an earlier version als exhibited the problem. System used to be Debian
oldstable, now Debian stable.

Symptom:
Outgoing e-mails do not reach certain recipients, instead of
delivery I recieve an e-mail with the following message:

                           UNDELIVERABLE MAIL

Your message to the following recipients cannot be delivered:

&amp;lt;xxx&amp;lt; at &amp;gt;lists.alioth.debian.org&amp;gt;:
    lists.alioth.debian.org [217.196.43.134]:
&amp;lt;&amp;lt;&amp;lt; 550 Broken MIME container (Long MIME Boundary)

According to the Debian bug log [1], first message, this is because
 The rule is:
 "Encapsulation boundaries may be no longer than 70 characters, not
 counting the blank line and leading hyphens."

In our installation the boundaries of e-mails after they left our
system are (most of the time[2]) 71 characters long.

If I save the e-mail in mutt instead of sending, a shorter, completely
different boundary is in the file; if I look at the boundary after I
recieved it &lt;/pre&gt;</description>
    <dc:creator>Helge Kreutzmann</dc:creator>
    <dc:date>2012-05-01T13:45:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.imap.courier.general/34450">
    <title>SPF deployment survey</title>
    <link>http://comments.gmane.org/gmane.mail.imap.courier.general/34450</link>
    <description>&lt;pre&gt;All,
as you may know, an IETF working group is reviewing the SPF spec.
The evaluation of current deployment is nearly completed, but thus far
only analyzes published SPF records.  Please contribute to a better
understanding by completing the survey:

  https://www.surveymonkey.com/s/SPF-deployment-survey

It will only take three minutes (ten questions on a single page).

Please help reaching all mail admins by forwarding this prompt to
specialized mailing lists and mail admins you are in touch with,
worldwide.  Thank you in advance!

The program for moving SPF to Standard Track currently includes:

* deprecate the Resource Record Type 99,
* fix some nits, and
* push toward resolving the incompatibility issue with Sender-ID.

&lt;/pre&gt;</description>
    <dc:creator>Alessandro Vesely</dc:creator>
    <dc:date>2012-04-27T06:06:35</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.imap.courier.general/34448">
    <title>(no subject)</title>
    <link>http://comments.gmane.org/gmane.mail.imap.courier.general/34448</link>
    <description>&lt;pre&gt;Download: http://www.courier-mta.org/download.php

Changes:

• A minor change to use the authenticated client's identify to enable  
virtual configuration settings, rather than a message's return address. This  
change affects domain-based virtual configuration settings only; no changes  
to the IP-address based virtual configuration settings. This requires  
authenticated IDs to take the form of "user&amp;lt; at &amp;gt;domain".



------------------------------------------------------------------------------
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-04-26T00:37:05</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.imap.courier.general/34442">
    <title>Courier 20120423</title>
    <link>http://comments.gmane.org/gmane.mail.imap.courier.general/34442</link>
    <description>&lt;pre&gt;Download: http://www.courier-mta.org/download.php

* Couple of fixes.

* Fixes pipelining which broke in 20120422 as a result of the virtual host  
config changes. An additional configuration step gets added. You now need  
to create a 0-length "vhost.ip-address" file in addition to everything  
else, in order to enable virtual configuration for this ip-address. This  
needs to be done explicitly, in order to avoid breaking pipelining.

* Also this also adds a alternative, slightly limited, form of virtual  
configuration based on a message's return address. Creating a  
"vhost.domain" configuration file enables virtual configuration for  
messages with "&amp;lt; at &amp;gt;domain" return address. The courier(8) man page is updated  
with more information and details.
------------------------------------------------------------------------------
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 incl&lt;/pre&gt;</description>
    <dc:creator>Sam Varshavchik</dc:creator>
    <dc:date>2012-04-24T12:23:00</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.imap.courier.general/34439">
    <title>PHP Admin for Courier?</title>
    <link>http://comments.gmane.org/gmane.mail.imap.courier.general/34439</link>
    <description>&lt;pre&gt;Now that vhosts work I am re-enthused to get some kind of PHP
based admin panel working for Courier. Something that could run
on any modern LAMP server, with an AJAX interface for speed and
highly theme-able for vhost branding.

Would anyone still be using a (hopefully updated) version of
Quica by any chance?

Or, would anyone know of *any* other PHP frontend for Courier?

------------------------------------------------------------------------------
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-04-24T06:54:13</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.imap.courier.general/34413">
    <title>Bug#669688: courier-authlib: does not call pam_end</title>
    <link>http://comments.gmane.org/gmane.mail.imap.courier.general/34413</link>
    <description>&lt;pre&gt;Hello,

I received a Debian bug report from Russ Albery on Courier's authlib.
Maybe someone can shed a light on this, as I have very little understanding
of PAM internals and authlib.

Thanks
        Racke

--snip--
Package: courier-authlib
Version: 0.63.0-4
Severity: normal

Note that I don't use Courier myself.  I found this bug while
investigating a problem reported against libpam-krb5.

authpam.c makes for rather surreal reading.  There's a large comment
that explains a complex and thorough philosophy for how the PAM code
is supposed to work, but then all the code that implements that is
removed with #if 0 and the actual code does something much simpler.

Unfortunately, while the comment and the other code was written by
someone who understands PAM library issues and complexity, the code
that's actually run never calls pam_end.  This means that any external
resources allocated by the PAM module, such as the Kerberos ticket
cache created by pam-krb5, are never released.

The #if 0 code does the right thin&lt;/pre&gt;</description>
    <dc:creator>Stefan Hornburg (Racke</dc:creator>
    <dc:date>2012-04-23T07:50:03</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.imap.courier.general/34411">
    <title>Courier 20120422</title>
    <link>http://comments.gmane.org/gmane.mail.imap.courier.general/34411</link>
    <description>&lt;pre&gt;Let's try this again.

This is a development build of Courier packages.

Download: http://www.courier-mta.org/download.php

==Changes

* Put back sysinit scripts into the RPM package, so it can be built on RHEL  
and Cent-OS without systemd.

* Do not allow an email address that begins with &amp;lt; at &amp;gt;

* Sqwebmail used an incorrect encoding when showing attachments' names, in  
some circumstances.

* Replace '''SOURCE_ADDRESS''' and '''SOURCE_ADDRESS_IPV6''' variables with  
ipout and ip6out configuration files, which offer more functionality. The  
outgoing IP address may be specified based on the IP address the sending  
client connected to, to relay the message. A complete description in a new  
section in the courier(8) man page.
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2_________________&lt;/pre&gt;</description>
    <dc:creator>Sam Varshavchik</dc:creator>
    <dc:date>2012-04-22T21:47:54</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.imap.courier.general/34410">
    <title>Courier 20120422</title>
    <link>http://comments.gmane.org/gmane.mail.imap.courier.general/34410</link>
    <description>&lt;pre&gt;------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2_______________________________________________
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-04-22T18:11:42</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.imap.courier.general/34407">
    <title>Courier + Dspam + Clamav</title>
    <link>http://comments.gmane.org/gmane.mail.imap.courier.general/34407</link>
    <description>&lt;pre&gt;All the tutorials I seem to Google about Dspam involve postfix
so would anyone happen to know of any step by step howto for
integrating Dspam with Courier?

Ideally on Debian or Archlinux but any OS would do.

------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
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-04-21T05:48:37</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.imap.courier.general/34385">
    <title>Multiple SSL certs on multiple IPs</title>
    <link>http://comments.gmane.org/gmane.mail.imap.courier.general/34385</link>
    <description>&lt;pre&gt;I know how to do this with courier-imap and it works great but
I've been playing with postfix and found that this config below
actually provides a virtually branded set of headers for the
recipient, passing both SPF and eyeball tests.

Is there any way that courier-mta can do the same thing?


/etc/postfix/master.cf

12.34.56.78:smtps inet n - - - - smtpd
 -o myhostname=domain1.com
 -o smtpd_tls_wrappermode=yes
 -o smtpd_client_restrictions=permit_sasl_authenticated,reject
 -o milter_macro_daemon_name=ORIGINATING
 -o smtpd_tls_cert_file=/etc/postfix/domain1.com.crt
 -o smtpd_tls_key_file=/etc/postfix/domain1.com.key
 -o smtpd_tls_CAfile=/etc/postfix/domain1.com.ca

12.34.56.78- unix - n n - - smtp
 -o smtp_bind_address=12.34.56.78
 -o smtp_bind_address6=
 -o smtp_address_preference=ipv4

------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. T&lt;/pre&gt;</description>
    <dc:creator>Mark Constable</dc:creator>
    <dc:date>2012-04-16T14:46:45</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>

