Just for info :
Mailing list : http://www.checkpoint.com/services/mailing.html
Newsgroup : http://news.checkpoint.com/nntp.html

If you can't have a web access, that's what they say on the mailling list page :

The address for the FireWall-1 mailing list address is
[EMAIL PROTECTED] To send a command to the mailing list, send
an e-mail to that address with the command in the body of the message (the
subject line can be left blank).

Best regards,
David

"Auteria Wally Winzer Jr." wrote:

> OFF-TOPIC: What's the Firewall-1 mailing list subscription name?
> I'd like to subscribe to that list.
>
> Thanks.
>
> - Wally Winzer Jr.
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> LEFEVRE David
> Sent: Friday, August 10, 2001 12:59 AM
> Cc: [EMAIL PROTECTED]
> Subject: Re: [ssh]: Subject emails
>
> Hello all,
>
> I agree ! I use this scheme for the Firewall-one mailling list ([FW1] in the
> subject), and it work perfectly.
> Why don't we use this simple trick ?
>
> Have a nice day,
> Bye
>
> J Grant wrote:
>
> > Hello
> >
> > I think it is better if i just add [ssh]: to every email i attempt to
> > send to this list, (along with changing the reply address to
> > [EMAIL PROTECTED], nearly made the same mistake of replying to myself with
> > this email!)
> >
> > I dont mean to create another long thread that is not SSH related but
> > does everyone else get 2 bounced emails every time they post to the
> > list?
> >
> > These are the 2 offending emails
> >
> > clearly the first will not be back soon so could they both be
> > temporarily be removed and they  can re subscribe when there email is
> > working again?
> >
> > --------------
> >
> > To: [EMAIL PROTECTED]
> > From: [EMAIL PROTECTED]
> > Date: Fri, 10 Aug 2001 3:49:40 +0100
> > Subject: [ssh]: Subject emails
> > Message-ID: <[EMAIL PROTECTED]>
> > X-Mozilla-Status: 8003
> > X-Mozilla-Status2: 00000000
> > X-UIDL: Y&Y!!EPk"!*W`"!9,P!!
> >
> > Von 17. Juli 2001 bis 16. Jaenner 2002 bin ich im
> > Elternkarenz und kann daher Ihre Mails nicht
> > persoenlich beantworten. Bitte wenden Sie sich in EDV-Angelegenheiten
> > an die zustaendigen Personen im ZID, siehe auch:
> >
> > http://zidweb.boku.ac.at/?id=p_girsch
> >
> > ====================================================
> >
> > >From 17th July 2001 to 16th of January 2002 I will be in
> > paternity leave  and can not reply until my return.
> > Concerning computer related problems please contact
> > my colleagues, you can find a list of responsibilities at:
> >
> > http://zidweb.boku.ac.at/?id=p_girsch
> >
> > -----------------------
> > To: [EMAIL PROTECTED]
> > Subject: Re: [ssh]: Subject emails
> > References: <[EMAIL PROTECTED]>
> > Content-Type: text/plain; charset=us-ascii
> > Content-Transfer-Encoding: 7bit
> > Sender: [EMAIL PROTECTED]
> > Precedence: bulk
> > X-Rcpt-To: <[EMAIL PROTECTED]>
> >
> > Our message was not delivered for the following reason:
> >
> > E-mail Account: blurzer is over the limit of 31457280 bytes.
> >
> > Automated Postmaster
> > -------------------------
> >
> > Regards
> >
> > JG
> >
> > Hypermedia Research Centre
> > Sanyo R&D Headquarters, TOKYO
> > http://www.sanyo.co.jp/R_and_D/3dm/
>
> --
> David LEFEVRE
> CARDIF - Architecture et Sécurité Opérationnelle
> [EMAIL PROTECTED] - Tél : 01 41 42 76 63
>      [EMAIL PROTECTED] - Tel : 01 41 42 24 22

--
David LEFEVRE
CARDIF - Architecture et Sécurité Opérationnelle
[EMAIL PROTECTED] - Tél : 01 41 42 76 63
     [EMAIL PROTECTED] - Tel : 01 41 42 24 22


**********************************************************************
L'intégrité de ce message n'étant pas assurée sur Internet,
CARDIF ne peut être tenu responsable de son contenu.
Si vous n'êtes pas destinataire de ce message confidentiel,
Merci de le détruire et d'avertir immédiatement l'expediteur.

The integrity of this message cannot be guaranteed on the
Internet. CARDIF can not therefore be considered responsible 
for the contents. 
If you are not the intended recipient of this confidential message,
then please delete it and notify immediately the sender.

**********************************************************************

Reply via email to