On Fri, Jun 03, 2022 at 03:58:04PM +0200, Matus UHLAR - fantomas
wrote:
> > On Fri, Jun 03, 2022 at 11:09:08AM +0200, Matus UHLAR - fantomas wrote:
> > > this will unpack the tarball in local directory.
> > > I use standard debian packages, there's SASL related patch but it doesn't
> > > seem to
On June 3, 2022 3:20:31 PM UTC, Viktor Dukhovni
wrote:
>On Fri, Jun 03, 2022 at 09:27:15AM -0400, Viktor Dukhovni wrote:
>> On Fri, Jun 03, 2022 at 11:09:08AM +0200, Matus UHLAR - fantomas wrote:
>>
>> > >Also can you "apt-get source postfix", and post a link to the tarball?
>> >
>> > this w
On Fri, Jun 03, 2022 at 09:27:15AM -0400, Viktor Dukhovni wrote:
> On Fri, Jun 03, 2022 at 11:09:08AM +0200, Matus UHLAR - fantomas wrote:
>
> > >Also can you "apt-get source postfix", and post a link to the tarball?
> >
> > this will unpack the tarball in local directory.
> > I use standard debi
On Fri, Jun 03, 2022 at 09:27:15AM -0400, Viktor Dukhovni wrote:
> The only thing to decide is whether the upstream mechanism behind
> "cyrus_sasl_config_path" should continue to use the simple
> sasl_set_path() API:
>
> https://github.com/cyrusimap/cyrus-sasl/blob/master/include/sasl.h
Corr
On Fri, Jun 03, 2022 at 11:09:08AM +0200, Matus UHLAR - fantomas wrote:
this will unpack the tarball in local directory.
I use standard debian packages, there's SASL related patch but it doesn't
seem to affect this issue
https://sources.debian.org/patches/postfix/3.5.6-1/
https://sources.debian.
On Fri, Jun 03, 2022 at 11:09:08AM +0200, Matus UHLAR - fantomas wrote:
> >Also can you "apt-get source postfix", and post a link to the tarball?
>
> this will unpack the tarball in local directory.
> I use standard debian packages, there's SASL related patch but it doesn't
> seem to affect this
On 02.06.22 08:38, raf wrote:
>No. Perhaps in the past, but no longer. I grepped for
>/etc/postfix/sasl in every file on a debian11 system
>and it didn't appear in libsasl2 or anywhere
>interesting.
On Thu, Jun 02, 2022 at 03:45:01PM +0200, Matus UHLAR - fantomas wrote:
maybe it uses e.g. path
On Thu, Jun 02, 2022 at 03:45:01PM +0200, Matus UHLAR - fantomas wrote:
> On 02.06.22 08:38, raf wrote:
> >No. Perhaps in the past, but no longer. I grepped for
> >/etc/postfix/sasl in every file on a debian11 system
> >and it didn't appear in libsasl2 or anywhere
> >interesting.
>
> maybe it use
On 30/05/22 2:48 pm, raf wrote:
> > If set
> > +empty (the default value) the search path is the one compiled into the
> > +Cyrus SASL library.
>
> I don't think that's entirely correct. On Debian, for
> example, the default value of cyrus_sasl_config_path is
> empty, and /etc/postfix/sasl is th
On 2/06/22 10:38 am, raf wrote:
No. Perhaps in the past, but no longer. I grepped for
/etc/postfix/sasl in every file on a debian11 system
and it didn't appear in libsasl2 or anywhere
interesting. It did appear in things like saslfinger
and apparmor rules and the postfix package file list
and aug
On Wed, Jun 01, 2022 at 10:44:51PM +, Scott Kitterman wrote:
> >No. Perhaps in the past, but no longer. I grepped for
> >/etc/postfix/sasl in every file on a debian11 system
> >and it didn't appear in libsasl2 or anywhere
> >interesting. It did appear in things like saslfinger
> >and apparmor
On Wed, Jun 01, 2022 at 12:03:43AM -0400, Viktor Dukhovni
wrote:
> On Wed, Jun 01, 2022 at 01:35:56PM +1000, raf wrote:
>
> > > So what did they do?
> > >
> > > > $ postconf -d cyrus_sasl_config_path
> > > > cyrus_sasl_config_path =
> > > > $ postconf cyrus_sasl_config_path
> > > > cyr
On June 1, 2022 10:38:55 PM UTC, raf wrote:
>On Wed, Jun 01, 2022 at 03:56:02PM +1200, Peter wrote:
>
>> On 30/05/22 2:48 pm, raf wrote:
>> > > If set
>> > > +empty (the default value) the search path is the one compiled into the
>> > > +Cyrus SASL library.
>> >
>> > I don't think that's en
On Wed, Jun 01, 2022 at 03:56:02PM +1200, Peter wrote:
> On 30/05/22 2:48 pm, raf wrote:
> > > If set
> > > +empty (the default value) the search path is the one compiled into the
> > > +Cyrus SASL library.
> >
> > I don't think that's entirely correct. On Debian, for
> > example, the default
On Wed, Jun 01, 2022 at 01:35:56PM +1000, raf wrote:
> > So what did they do?
> >
> > > $ postconf -d cyrus_sasl_config_path
> > > cyrus_sasl_config_path =
> > > $ postconf cyrus_sasl_config_path
> > > cyrus_sasl_config_path =
> > > $ dpkg-query -S /etc/postfix/sasl
> > > postfix: /et
On 30/05/22 2:48 pm, raf wrote:
If set
+empty (the default value) the search path is the one compiled into the
+Cyrus SASL library.
I don't think that's entirely correct. On Debian, for
example, the default value of cyrus_sasl_config_path is
empty, and /etc/postfix/sasl is the directory that
On Mon, May 30, 2022 at 12:15:19AM -0400, Viktor Dukhovni
wrote:
> On Mon, May 30, 2022 at 12:48:46PM +1000, raf wrote:
>
> > I don't think that's entirely correct. On Debian, for
> > example, the default value of cyrus_sasl_config_path is
> > empty, and /etc/postfix/sasl is the directory that
On Mon, May 30, 2022 at 12:48:46PM +1000, raf wrote:
> I don't think that's entirely correct. On Debian, for
> example, the default value of cyrus_sasl_config_path is
> empty, and /etc/postfix/sasl is the directory that is
> used.
Well, how exactly does that happen? I don't see any patches to Po
On Sun, May 29, 2022 at 11:25:44AM -0400, Viktor Dukhovni
wrote:
> On Sat, May 28, 2022 at 10:32:56PM -0400, Viktor Dukhovni wrote:
>
> > > This might be irrelevant, but the SASL readme mentions
> > > that on some systems Postfix is modified to look for
> > > the Cyrus SASL config in /etc/postf
On Sat, May 28, 2022 at 10:32:56PM -0400, Viktor Dukhovni wrote:
> > This might be irrelevant, but the SASL readme mentions
> > that on some systems Postfix is modified to look for
> > the Cyrus SASL config in /etc/postfix/sasl or
> > /var/lib/sasl2. On Debian, it's in /etc/postfix/sasl.
> > Perha
20 matches
Mail list logo
