-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 5, 2009, at 6:03 AM, Ian Eiloart wrote:
I've added a note to the docs about Exim's callout features. They
allow Exim to determine not only whether the list exists, but
whether the list will accept mail from the current sender - before
ac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 4, 2009, at 7:29 PM, Patrick Ben Koetter wrote:
* Barry Warsaw :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 05, 2009, at 12:58 AM, Patrick Ben Koetter wrote:
Thanks. Minor bug fix in the docco, though. Destination syntax for
lm
--On 5 January 2009 10:09:53 + Simon Fraser wrote:
On Fri, 2009-01-02 at 12:06 -0500, Barry Warsaw wrote:
Finally, I would like to get input from MTA experts on this list as to
the best way to integrate the various MTAs with Mailman's LMTP
server. Specifically, I'm looking at fixing an
On Fri, 2009-01-02 at 12:06 -0500, Barry Warsaw wrote:
> Finally, I would like to get input from MTA experts on this list as to
> the best way to integrate the various MTAs with Mailman's LMTP
> server. Specifically, I'm looking at fixing and improving bin/
> genaliases for each of the MTAs.
Hi,
William's internship has finished here, so I think I'd better pick up this
thread - if that's OK with you, William. I'll mail you off list about your
two questions.
I've added a note to the docs about Exim's callout features. They allow
Exim to determine not only whether the list exists
* Barry Warsaw :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Jan 05, 2009, at 12:58 AM, Patrick Ben Koetter wrote:
>
> >Thanks. Minor bug fix in the docco, though. Destination syntax for lmtp
> >targets in the transport table requires a fourth parameter: service type.
>
> I'm not su
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 05, 2009, at 12:58 AM, Patrick Ben Koetter wrote:
>Thanks. Minor bug fix in the docco, though. Destination syntax for lmtp
>targets in the transport table requires a fourth parameter: service type.
I'm not sure it requires it; I saw that in th
* Barry Warsaw :
> On Jan 04, 2009, at 12:00 AM, Patrick Ben Koetter wrote:
>
> >* Barry Warsaw :
>
> >> Thanks Patrick. I think there's one other configuration variable that
> >> needs to be set. Please see the comment on the wiki page. I believe I
> >> have this working now.
> >
> >Yes. I'v
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 04, 2009, at 12:00 AM, Patrick Ben Koetter wrote:
>* Barry Warsaw :
>> Thanks Patrick. I think there's one other configuration variable that
>> needs to be set. Please see the comment on the wiki page. I believe I
>> have this working now.
* Barry Warsaw :
>> * Barry Warsaw :
>>> Finally, I would like to get input from MTA experts on this list as to
>>> the best way to integrate the various MTAs with Mailman's LMTP server.
>>> Specifically, I'm looking at fixing and improving bin/genaliases for each
>>> of the MTAs. I've looked at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 2, 2009, at 5:44 PM, Patrick Ben Koetter wrote:
* Barry Warsaw :
Finally, I would like to get input from MTA experts on this list as
to
the best way to integrate the various MTAs with Mailman's LMTP
server.
Specifically, I'm looking at fi
* Barry Warsaw :
> Finally, I would like to get input from MTA experts on this list as to
> the best way to integrate the various MTAs with Mailman's LMTP server.
> Specifically, I'm looking at fixing and improving bin/genaliases for each
> of the MTAs. I've looked at Postfix's documentation,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi William,
The Mailman 3 branch is nearly ready for the next alpha release. I've
been working on some major structural changes that should make
development go much faster.
First, I've converted the installation infrastructure over to
zc.bui
13 matches
Mail list logo
