On 7/4/2013 8:01 PM, Wietse Venema wrote:
> gw1500:
>> It is not clear from the documentation if this is possible or how to do
>> it but I want to make authentication optional but if a user does
>> authenticate then I want to permit relaying. Can someone help?
> This is how permit_sasl_authenticate
On 7/4/2013 8:36 PM, Wietse Venema wrote:
> W T Riker:
>> On 7/4/2013 8:01 PM, Wietse Venema wrote:
>>> gw1500:
>>>> It is not clear from the documentation if this is possible or how to do
>>>> it but I want to make authentication optional but if a user do
On 7/5/2013 12:27 AM, b...@bitrate.net wrote:
> On Jul 4, 2013, at 20.44, W T Riker wrote:
>
>> On 7/4/2013 8:36 PM, Wietse Venema wrote:
>>> W T Riker:
>>>> On 7/4/2013 8:01 PM, Wietse Venema wrote:
>>>>> gw1500:
>>>>>> It is
On 7/4/2013 11:21 PM, Noel Jones wrote:
> On 7/4/2013 7:44 PM, W T Riker wrote:
>> On 7/4/2013 8:36 PM, Wietse Venema wrote:
>>> W T Riker:
>>>> On 7/4/2013 8:01 PM, Wietse Venema wrote:
>>>>> gw1500:
>>>>>> It is not clear from the
On 7/5/2013 9:51 AM, Larry Stone wrote:
> On Fri, 5 Jul 2013, W T Riker wrote:
>
>> Indeed this is using port 587. I did not realize that that in itself was
>> sufficient to prevent relaying from non-authenticated clients. Thanks.
>
> It doesn't. If 587 is configured t
Thanks. I fixed it.
On 7/5/2013 10:07 AM, Viktor Dukhovni wrote:
> On Fri, Jul 05, 2013 at 10:00:02AM -0400, W T Riker wrote:
>
>> Thanks for that explanation. I think I understand the way it works now
>> so I modified my restrictions a bit. Does this order p
On 7/5/2013 10:52 AM, Tom Hendrikx wrote:
> On 07/05/2013 04:07 PM, Viktor Dukhovni wrote:
>> On Fri, Jul 05, 2013 at 10:00:02AM -0400, W T Riker wrote:
>>
>>> Thanks for that explanation. I think I understand the way it works now
>>> so I modified my restriction
