The following module was proposed for inclusion in the Module List:
modid: Net::Server::Mail::ESMTP::STARTTLS
DSLIP: RdpOp
description: STARTTLS for Net::Server::Mail::ESMTP
userid: DANMOORE (Dan Moore)
chapterid: 5 (Networking_Devices_IPC)
communities:
https://
Olivier Poitrey <[EMAIL PROTECTED]> writes:
> _brian_d_foy <[EMAIL PROTECTED]> writes:
>
>> sure you can. i suggest registering those names while we figure
>> out how to name the base class.
>
> Any idea ? I suggest Net::SMTP::Server::Base, not so bad is it ?
>
>> Net::SMTP::Server looks like it
_brian_d_foy <[EMAIL PROTECTED]> writes:
> sure you can. i suggest registering those names while we figure out
> how to name the base class.
Any idea ? I suggest Net::SMTP::Server::Base, not so bad is it ?
> Net::SMTP::Server looks like it hasn't been updated since 1999. you
> might be able to
In article <[EMAIL PROTECTED]>, Olivier Poitrey <[EMAIL PROTECTED]>
wrote:
> _brian_d_foy <[EMAIL PROTECTED]> writes:
> > do you need to rewrite Net::SMTP::Server or can you work with the
> > existing ones?
> >
> Net::Server::Mail::* are already written, and as I said in my first
> post, the cu
_brian_d_foy <[EMAIL PROTECTED]> writes:
> In article <[EMAIL PROTECTED]>, Olivier Poitrey
><[EMAIL PROTECTED]> wrote:
>
>> My class implements 3 protocols : SMTP, ESMTP and LMTP. ESMTP inherit
>> from SMTP and LMTP from ESMTP (as describe in RFCs). So isn't it a
>> problem to use 3 namespaces (N
In article <[EMAIL PROTECTED]>, Olivier Poitrey <[EMAIL PROTECTED]>
wrote:
> My class implements 3 protocols : SMTP, ESMTP and LMTP. ESMTP inherit
> from SMTP and LMTP from ESMTP (as describe in RFCs). So isn't it a
> problem to use 3 namespaces (Net::SMTP::Server, Net::ESMTP::Server and
> Net::L
_brian_d_foy <[EMAIL PROTECTED]> writes:
>> Is Mail::Server the right place for a network protocol class ?
>
> is this an application or a module?
No, it's just the server API.
> if you are writing an interface to the server side of a mail server,
> i think something like Net::ESMTP::Server is m
In article <[EMAIL PROTECTED]>, Olivier Poitrey <[EMAIL PROTECTED]>
wrote:
> _brian_d_foy <[EMAIL PROTECTED]> writes:
>
> >> > shouldn't this be Net::ESMTP and Net::LMTP then?
> >>
> >> Net::ESMTP and Net::LMTP are client-side protocols
> >> implementations. Net::Server::Mail::* are server-side
_brian_d_foy <[EMAIL PROTECTED]> writes:
>> > shouldn't this be Net::ESMTP and Net::LMTP then?
>>
>> Net::ESMTP and Net::LMTP are client-side protocols
>> implementations. Net::Server::Mail::* are server-side ones.
>
> ah, okay.
>
> i think this should be in Mail::* somewhere. perhaps Mail::Serv
In article <[EMAIL PROTECTED]>, Olivier Poitrey <[EMAIL PROTECTED]>
wrote:
> _brian_d_foy <[EMAIL PROTECTED]> writes:
>
> >> Other SMTPd implementations don't support useful ESMTP extensions
> >> and the LMTP protocol.
> >
> > shouldn't this be Net::ESMTP and Net::LMTP then?
>
> Net::E
_brian_d_foy <[EMAIL PROTECTED]> writes:
>> Other SMTPd implementations don't support useful ESMTP extensions
>> and the LMTP protocol.
>
> shouldn't this be Net::ESMTP and Net::LMTP then?
Net::ESMTP and Net::LMTP are client-side protocols
implementations. Net::Server::Mail::* are server
In article <[EMAIL PROTECTED]>, Perl Authors Upload Server
<[EMAIL PROTECTED]> wrote:
> The following module was proposed for inclusion in the Module List:
>
> modid: Net::Server::Mail
> The module Net::Server already exists, and Net::Server::Mail can
> easly be used with it (or
The following module was proposed for inclusion in the Module List:
modid: Net::Server::Mail
DSLIP: bmpOl
description: SMTP, ESMTP and LMTP protocol implementation
userid: RSOLIV (Olivier Poitrey)
chapterid: 16 (Server_and_Daemon_Utilities)
communities:
similar:
13 matches
Mail list logo