Re: [courier-users] RBL answers
David Niklas writes: On Fri, 24 Mar 2017 16:41:35 -0400 Sam Varshavchik wrote: > > I think they're smart enough to understand how DNS works. I don't need > to tell them that. > > I can't quite put my finger on why exactly I believe that this would be > a waste of energy, trying to fight it. Call it a sixth sense, of sorts, > of me being involved in this industry for a while. If I brought the matter before them referencing this thread would you mind? (Not that I don't have better things to do but it's worth a try...) Feel free. This is a public mailing list. I always thought that it was quite silly for anyone on a public mailing list, that's probably archived and searchable in a bunch of places, to have some kind of an issue with their public scribblings being forwarded all over the place. pgpZLSQjf6heo.pgp Description: PGP signature -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] RBL answers
On Fri, 24 Mar 2017 16:41:35 -0400 Sam Varshavchik wrote: > David Niklas writes: > > > On 03/10/2017(Fri) 15:35 > > > That's the other thing that the blacklists definitely don't want: > > > excessi ve queries. Making two queries instead of one will put extra > > > load on the blacklists, and slow down your mail delivery. > > Well isn't that what they want, two quires instead of one? > > No. From the looks of it, they want either an A or a TXT query. > > > > That's why I think that getting rid of ANY is counter-productive. > > > But, it 's their call to make, so we'll go with that. > > Why not tell them that courier has a valid use case for the ANY > > query? > > I think they're smart enough to understand how DNS works. I don't need > to tell them that. > > I can't quite put my finger on why exactly I believe that this would be > a waste of energy, trying to fight it. Call it a sixth sense, of sorts, > of me being involved in this industry for a while. If I brought the matter before them referencing this thread would you mind? (Not that I don't have better things to do but it's worth a try...) Thanks, David -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] courier-authlib: exported symbols
Markus Wanner writes: Sam, On 03/31/2017 12:26 AM, Sam Varshavchik wrote: > libcourierauthcommon is not solely an externally-linked library. It's > also linked to by other .so-s in the package. These symbols correspond > to internal APIs. Am I correct to assume that libcourierauthcommon is an internal library and not part of the public API of courier-auth, i.e. users of courier-auth shouldn't ever directly link to it? No, I said "solely". Apps do link to libcourierauthcommon. Do libauthpam.so and libauthcustom.so exposed a public API? No, these ones are internal modules only. pgpdR2ErGZ9h6.pgp Description: PGP signature -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] courier-authlib: exported symbols
Hello Alessandro, On 03/31/2017 10:49 AM, Alessandro Vesely wrote: > I, for one, run my own pipeauth > > ldd /etc/courier/authlib/authProg > linux-vdso.so.1 => (0x7fffb59bc000) > libcourierauthsasl.so => > /usr/local/lib/courier-authlib/libcourierauthsasl.so (0x7ff1e44cd000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7ff1e414) > libcourierauthcommon.so => > /usr/local/lib/courier-authlib/libcourierauthcommon.so (0x7ff1e3f37000) > libcourierauth.so => /usr/local/lib/courier-authlib/libcourierauth.so > (0x7ff1e3d2a000) > /lib64/ld-linux-x86-64.so.2 (0x7ff1e46d) > libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 > (0x7ff1e3a23000) > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7ff1e37a1000) > libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 > (0x7ff1e358b000) > libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 > (0x7ff1e3354000) The interesting question here would be whether you're linking against libcourierauthsasl (and using its symbols only) or if your authProg depends on libcourierauthcommon, directly. (Indirectly, via libcourierauthsasl, libcourierauthcommon will always be linked in either case.) (Other than that I note that you're not using Debian packages, in the first place, so you wouldn't be affected. I still appreciate your inputs. Maybe there are Debian users doing or wanting to do the same.) Kind Regards Markus Wanner signature.asc Description: OpenPGP digital signature -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] courier-authlib: exported symbols
Hi Markus, On Fri 31/Mar/2017 09:36:27 +0200 Markus Wanner wrote: > On 03/31/2017 12:26 AM, Sam Varshavchik wrote: >> libcourierauthcommon is not solely an externally-linked library. It's >> also linked to by other .so-s in the package. These symbols correspond >> to internal APIs. > > Am I correct to assume that libcourierauthcommon is an internal library > and not part of the public API of courier-auth, i.e. users of > courier-auth shouldn't ever directly link to it? > > Do libauthpam.so and libauthcustom.so exposed a public API? I, for one, run my own pipeauth ldd /etc/courier/authlib/authProg linux-vdso.so.1 => (0x7fffb59bc000) libcourierauthsasl.so => /usr/local/lib/courier-authlib/libcourierauthsasl.so (0x7ff1e44cd000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7ff1e414) libcourierauthcommon.so => /usr/local/lib/courier-authlib/libcourierauthcommon.so (0x7ff1e3f37000) libcourierauth.so => /usr/local/lib/courier-authlib/libcourierauth.so (0x7ff1e3d2a000) /lib64/ld-linux-x86-64.so.2 (0x7ff1e46d) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x7ff1e3a23000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7ff1e37a1000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7ff1e358b000) libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 (0x7ff1e3354000) API recently changed, so my authProg is now portable, but I haven't autoconfed it yet. Ale signature.asc Description: OpenPGP digital signature -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Build 20170309 of Courier packages
On Fri 31/Mar/2017 00:28:49 +0200 Sam Varshavchik wrote: > Alessandro Vesely writes: > >> authpgsqllib.cpp:14:22: fatal error: libpq-fe.h: No such file or directory >> #include >> ^ >> compilation terminated. >> Makefile:1352: recipe for target 'authpgsqllib.lo' failed >> >> I reckon anyone having PostgreSQL should experience this error. The include >> file /usr/include/postgresql/libpq-fe.h cannot be found without a proper -I, >> which is in CFLAGS but not CXXFLAGS. The last authpgsqllib.c I have is in >> courier-authlib-0.66.4.20160106 and named .cpp thereafter. > > Ok, that was something else, that fell out of the C++ rewrite. Made another > fix > to configure.ac, which should fix this one too. Build 20170330 is there now. 20170330 compiles nicely Thanks Ale -- signature.asc Description: OpenPGP digital signature -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] courier-authlib: exported symbols
Sam, On 03/31/2017 12:26 AM, Sam Varshavchik wrote: > libcourierauthcommon is not solely an externally-linked library. It's > also linked to by other .so-s in the package. These symbols correspond > to internal APIs. Am I correct to assume that libcourierauthcommon is an internal library and not part of the public API of courier-auth, i.e. users of courier-auth shouldn't ever directly link to it? Do libauthpam.so and libauthcustom.so exposed a public API? Kind Regards Markus Wanner signature.asc Description: OpenPGP digital signature -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
