On Mon, Feb 24, 2003 at 10:25:16PM +, Brian M. Carlson wrote:
> On Fri, Feb 21, 2003 at 09:41:18AM +0100, Xavier Roche wrote:
> > > In this case, should the package just document what the use
> > > should do (it will be different for each MTA) or at least
> > > detect which MTA is installed and
On Mon, Feb 24, 2003 at 10:25:16PM +, Brian M. Carlson wrote:
> On Fri, Feb 21, 2003 at 09:41:18AM +0100, Xavier Roche wrote:
> > > In this case, should the package just document what the use
> > > should do (it will be different for each MTA) or at least
> > > detect which MTA is installed and
Hi,
On Tue, Feb 25, 2003 at 01:14:25PM +0100, Martin Baehr wrote:
> On Mon, Feb 24, 2003 at 03:37:25PM -0800, John H. Robinson, IV wrote:
> > to throw even more monkeywrenches in the gearbox, some people may have
> > compiled an MTA outside of the packaging system, and be using qmail/
> > sendmai
On Mon, Feb 24, 2003 at 03:37:25PM -0800, John H. Robinson, IV wrote:
> to throw even more monkeywrenches in the gearbox, some people may have
> compiled an MTA outside of the packaging system, and be using qmail/
> sendmail/postfix (the uspported MTA's) but not have it registered with
> apt/dpkg a
Hi,
On Tue, Feb 25, 2003 at 01:14:25PM +0100, Martin Baehr wrote:
> On Mon, Feb 24, 2003 at 03:37:25PM -0800, John H. Robinson, IV wrote:
> > to throw even more monkeywrenches in the gearbox, some people may have
> > compiled an MTA outside of the packaging system, and be using qmail/
> > sendmai
On Mon, Feb 24, 2003 at 03:37:25PM -0800, John H. Robinson, IV wrote:
> to throw even more monkeywrenches in the gearbox, some people may have
> compiled an MTA outside of the packaging system, and be using qmail/
> sendmail/postfix (the uspported MTA's) but not have it registered with
> apt/dpkg a
Hi, correct me if I am wrong...
On Mon, Feb 24, 2003 at 03:37:25PM -0800, John H. Robinson, IV wrote:
> Brian M. Carlson wrote:
> > On Fri, Feb 21, 2003 at 09:41:18AM +0100, Xavier Roche wrote:
> > > > In this case, should the package just document what the use
> > > > should do (it will be differ
Brian M. Carlson wrote:
> On Fri, Feb 21, 2003 at 09:41:18AM +0100, Xavier Roche wrote:
> > > In this case, should the package just document what the use
> > > should do (it will be different for each MTA) or at least
> > > detect which MTA is installed and copy an example config file
> >
> > Ensu
Hi, correct me if I am wrong...
On Mon, Feb 24, 2003 at 03:37:25PM -0800, John H. Robinson, IV wrote:
> Brian M. Carlson wrote:
> > On Fri, Feb 21, 2003 at 09:41:18AM +0100, Xavier Roche wrote:
> > > > In this case, should the package just document what the use
> > > > should do (it will be differ
On Fri, Feb 21, 2003 at 09:41:18AM +0100, Xavier Roche wrote:
> > In this case, should the package just document what the use
> > should do (it will be different for each MTA) or at least
> > detect which MTA is installed and copy an example config file
>
> Ensure that the depends: field in contro
Brian M. Carlson wrote:
> On Fri, Feb 21, 2003 at 09:41:18AM +0100, Xavier Roche wrote:
> > > In this case, should the package just document what the use
> > > should do (it will be different for each MTA) or at least
> > > detect which MTA is installed and copy an example config file
> >
> > Ensu
On Fri, Feb 21, 2003 at 09:41:18AM +0100, Xavier Roche wrote:
> > In this case, should the package just document what the use
> > should do (it will be different for each MTA) or at least
> > detect which MTA is installed and copy an example config file
>
> Ensure that the depends: field in contro
John Price (2003-02-21 01:54:24 -0600) :
> I'm considering packaging TPC from http://www.tpc.int, and it
> requires configuring the MTA to accept email to specific
> domain names. Needless to say, it's a fairly complicated
> mail server configuration.
>
> In this case, should the package just doc
> In this case, should the package just document what the use
> should do (it will be different for each MTA) or at least
> detect which MTA is installed and copy an example config file
Ensure that the depends: field in control has something like
Depends: (sendmail | qmail | postfix)
> in the cor
John Price <[EMAIL PROTECTED]> writes:
> I'm considering packaging TPC from http://www.tpc.int, and it
> requires configuring the MTA to accept email to specific
> domain names. Needless to say, it's a fairly complicated
> mail server configuration.
> In this case, should the package just documen
I'm considering packaging TPC from http://www.tpc.int, and it
requires configuring the MTA to accept email to specific
domain names. Needless to say, it's a fairly complicated
mail server configuration.
In this case, should the package just document what the use
should do (it will be different fo
John Price (2003-02-21 01:54:24 -0600) :
> I'm considering packaging TPC from http://www.tpc.int, and it
> requires configuring the MTA to accept email to specific
> domain names. Needless to say, it's a fairly complicated
> mail server configuration.
>
> In this case, should the package just doc
> In this case, should the package just document what the use
> should do (it will be different for each MTA) or at least
> detect which MTA is installed and copy an example config file
Ensure that the depends: field in control has something like
Depends: (sendmail | qmail | postfix)
> in the cor
John Price <[EMAIL PROTECTED]> writes:
> I'm considering packaging TPC from http://www.tpc.int, and it
> requires configuring the MTA to accept email to specific
> domain names. Needless to say, it's a fairly complicated
> mail server configuration.
> In this case, should the package just documen
I'm considering packaging TPC from http://www.tpc.int, and it
requires configuring the MTA to accept email to specific
domain names. Needless to say, it's a fairly complicated
mail server configuration.
In this case, should the package just document what the use
should do (it will be different fo
20 matches
Mail list logo
