On ons 5 feb 2014 16:40:15, Viktor Dukhovni wrote:
> On Wed, Feb 05, 2014 at 10:01:15AM +0100, Patrik B?t wrote:
>
>> Maybe check that SASL give a respons, and if not just tmp fail it. or
>> someother check.
>
> The proposed patch is incorrect. Please reply on-list only.
>
>> --- ../../../postfix
On Wed, Feb 05, 2014 at 10:01:15AM +0100, Patrik B?t wrote:
> Maybe check that SASL give a respons, and if not just tmp fail it. or
> someother check.
The proposed patch is incorrect. Please reply on-list only.
> --- ../../../postfix-2.9.6/src/smtpd/smtpd_sasl_glue.c2011-12-18
> 19:03
On Wed, Feb 05, 2014 at 09:50:32AM +0100, Patrik B?t wrote:
> >> Hmm, Victor are you sure this works?
Setting restrictions to "permit_sasl_authenticated, defer" works
when clients don't attempt to authenticate. If a client attempts
to authenticate and fails, the client will not send the message.
On ons 5 feb 2014 09:50:32, Patrik Båt wrote:
> On ons 5 feb 2014 09:43:52, Patrik Båt wrote:
>> On ons 5 feb 2014 09:17:57, Patrik Båt wrote:
>>> On tis 4 feb 2014 15:42:04, Patrik Båt wrote:
On tis 4 feb 2014 15:36:34, Viktor Dukhovni wrote:
> On Tue, Feb 04, 2014 at 02:57:42PM +010
On ons 5 feb 2014 09:43:52, Patrik Båt wrote:
> On ons 5 feb 2014 09:17:57, Patrik Båt wrote:
>> On tis 4 feb 2014 15:42:04, Patrik Båt wrote:
>>> On tis 4 feb 2014 15:36:34, Viktor Dukhovni wrote:
On Tue, Feb 04, 2014 at 02:57:42PM +0100, Patrik B?t wrote:
> When saslauthd crashe
On ons 5 feb 2014 09:17:57, Patrik Båt wrote:
> On tis 4 feb 2014 15:42:04, Patrik Båt wrote:
>> On tis 4 feb 2014 15:36:34, Viktor Dukhovni wrote:
>>> On Tue, Feb 04, 2014 at 02:57:42PM +0100, Patrik B?t wrote:
>>>
When saslauthd crashes or beeing stopped, mails are bounced.
eg: 535 5
On tis 4 feb 2014 15:42:04, Patrik Båt wrote:
> On tis 4 feb 2014 15:36:34, Viktor Dukhovni wrote:
>> On Tue, Feb 04, 2014 at 02:57:42PM +0100, Patrik B?t wrote:
>>
>>> When saslauthd crashes or beeing stopped, mails are bounced.
>>> eg: 535 5.7.8 Error: authentication failed: generic failure
>>>
On tis 4 feb 2014 15:36:34, Viktor Dukhovni wrote:
> On Tue, Feb 04, 2014 at 02:57:42PM +0100, Patrik B?t wrote:
>
>> When saslauthd crashes or beeing stopped, mails are bounced.
>> eg: 535 5.7.8 Error: authentication failed: generic failure
>>
>> Can I somehow change it to just defer?
>
> If you
On Tue, Feb 04, 2014 at 02:57:42PM +0100, Patrik B?t wrote:
> When saslauthd crashes or beeing stopped, mails are bounced.
> eg: 535 5.7.8 Error: authentication failed: generic failure
>
> Can I somehow change it to just defer?
If you have a dedicated submission/relay service to which *all*
clie
On 04 Feb 2014, at 06:57 , Patrik Båt wrote:
> When saslauthd crashes or beeing stopped, mails are bounced.
Well, first off, why is saslauthd crashing? Fix that.
> eg: 535 5.7.8 Error: authentication failed: generic failure
Are you talking about SASL on submission? because that would not clas
On tis 4 feb 2014 15:13:03, LuKreme wrote:
>
> On 04 Feb 2014, at 06:57 , Patrik Båt wrote:
>
>> When saslauthd crashes or beeing stopped, mails are bounced.
>
> Well, first off, why is saslauthd crashing? Fix that.
saslauthd[33257]: DEBUG: auth_pam: pam_authenticate failed: Memory
buffer error
Am 04.02.2014 14:57, schrieb Patrik Båt:
> When saslauthd crashes or beeing stopped, mails are bounced.
> eg: 535 5.7.8 Error: authentication failed: generic failure
>
> Can I somehow change it to just defer?
that makes no sense
what do you do with that messages later?
how do you authenticate
Hello!
When saslauthd crashes or beeing stopped, mails are bounced.
eg: 535 5.7.8 Error: authentication failed: generic failure
Can I somehow change it to just defer?
// Patrik
signature.asc
Description: OpenPGP digital signature
13 matches
Mail list logo
