Send inn-workers mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."
Today's Topics:
1. Re: nnrp conf (Edwardo Garcia)
2. RE: nnrp conf (Matt Seitz (matseitz))
----------------------------------------------------------------------
Message: 1
Date: Thu, 19 Mar 2015 22:00:17 +1000
From: Edwardo Garcia <[email protected]>
To: Noel Butler <[email protected]>
Cc: [email protected]
Subject: Re: nnrp conf
Message-ID:
<CANso6eEpcx3=FWhnLWYmuss6E=geojz4dy-hd1yhqxynwe9...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Halo,
On 3/18/15, Noel Butler <[email protected]> wrote:
>
>
> sounds peachy :)
What is peachy?
>
> On 18/03/2015 07:23, Julien ?LIE wrote:
>
>> Hi Edwardo,
>>
>>> I think as other say, be better for very clear example in add user:
>>> <EXAMPLE> This is still confuse, this what leed to my server be open to
>>> everyone, someway, it did not work this procedure because I try follow
>>> that at first.
>>
>> OK, I see where the confusion came. I then suggest the following new
>> wording. Would it suit both you and Noel?
>>
>> auth example.com {
>> hosts: "*.example.com, example.com"
>> default: "<EXAMPLE>"
>> }
>>
>> access full {
>> users: "<EXAMPLE>"
>> newsgroups: *
>> }
>>
>> Note that the above access realm could also be written without the
>> users: key, in which case it applies to any user identity (though in
>> this example, the user identity that will be assigned to all matching
>> connections is C<< <EXAMPLE> >>). It is however recommended to keep
>> an explicit users: key so as to better view to whom the access block
>> applies.
>>
>> As the only available auth realm only matches hosts in the "example.com"
>> domain, any connections from other hosts will be rejected immediately.
>
>
------------------------------
Message: 2
Date: Thu, 19 Mar 2015 15:42:10 +0000
From: "Matt Seitz (matseitz)" <[email protected]>
To: Edwardo Garcia <[email protected]>, Noel Butler
<[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: RE: nnrp conf
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="utf-8"
"Peachy" is an idiom meaning "very good : fine or excellent".
http://www.merriam-webster.com/dictionary/peachy
Matt Seitz
PROGRAM MANAGER.ENGINEERING RELEASE
[email protected]
Phone: +1 408 526 8974
Cisco Systems Limited
510 McCarthy Blvd.
MILPITAS
CALIFORNIA
95035
US
Cisco.com
Think before you print.
This email may contain confidential and privileged material for the sole use of
the intended recipient. Any review, use, distribution or disclosure by others
is strictly prohibited. If you are not the intended recipient (or authorized to
receive for the recipient), please contact the sender by reply email and delete
all copies of this message.
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/index.html
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Edwardo Garcia
Sent: Thursday, March 19, 2015 5:00
To: Noel Butler
Cc: [email protected]
Subject: Re: nnrp conf
Halo,
On 3/18/15, Noel Butler <[email protected]> wrote:
>
>
> sounds peachy :)
What is peachy?
>
> On 18/03/2015 07:23, Julien ?LIE wrote:
>
>> Hi Edwardo,
>>
>>> I think as other say, be better for very clear example in add user:
>>> <EXAMPLE> This is still confuse, this what leed to my server be open
>>> to everyone, someway, it did not work this procedure because I try
>>> follow that at first.
>>
>> OK, I see where the confusion came. I then suggest the following new
>> wording. Would it suit both you and Noel?
>>
>> auth example.com {
>> hosts: "*.example.com, example.com"
>> default: "<EXAMPLE>"
>> }
>>
>> access full {
>> users: "<EXAMPLE>"
>> newsgroups: *
>> }
>>
>> Note that the above access realm could also be written without the
>> users: key, in which case it applies to any user identity (though in
>> this example, the user identity that will be assigned to all matching
>> connections is C<< <EXAMPLE> >>). It is however recommended to keep
>> an explicit users: key so as to better view to whom the access block
>> applies.
>>
>> As the only available auth realm only matches hosts in the "example.com"
>> domain, any connections from other hosts will be rejected immediately.
>
>
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
------------------------------
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
End of inn-workers Digest, Vol 70, Issue 3
******************************************
