Re: [courier-users] LOGGEROPT and esmtpd
Hanno Böck writes: Hello, I'd like to separate log files from the various esmtpds (25, 465, 587), so I can see which one gets used how often by my users. However, I currently don't see any easy way to do so. The pop3d and imapd config files and start scripts have a variable LOGGEROPTS in their configfile that gets passed to courierlogger. However, the esmtpd startup script seems a bit different and doesn't call the logger directly. Is there a reason why LOGGEROPTS is not available for esmtpd? Sam, could this be changed for the next version? courierlogger captures error messages from its managed process, and sends them to syslog. The entire emstp server talks to syslog directly, that's why it's different. This is not something that can be changed trivially, since big chunks of code are also used when sendmail gets invoked from the command line, where standard error is already serving its traditional role, and logging should, truly, go to syslog. pgpSy3QfKwV6t.pgp Description: PGP signature -- Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] ltdl error building Courier-authlib rpm
Bowie Bailey writes: I added the above between the %setup and %configure lines. It seemed to go ok until it hit autoconf. Here's the last bit of output: libtoolize: linking file `libltdl/ltdl.c' libtoolize: linking file `libltdl/ltdl.h' libtoolize: linking file `libltdl/slist.c' libtoolize: Remember to add `LT_CONFIG_LTDL_DIR([libltdl])' to `configure.in'. libtoolize: Consider using `AC_CONFIG_AUX_DIR([libltdl/config])' in configure.in. libtoolize: Consider using `AC_CONFIG_MACRO_DIR([libltdl/m4])' in configure.in. libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. + aclocal + autoheader + automake + autoconf configure.in:24: error: possibly undefined macro: AC_PROG_SYSCONFTOOL If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. error: Bad exit status from /var/tmp/rpm-tmp.WVdhQW (%prep) Do you think this is worth pursuing, or should I just give up and run the upgrade the old system? Install http://www.courier-mta.org/download.html#sysconftool Am I likely to have any issues with an upgrade from Courier 0.69.0 and Authlib 0.65.0 to the current releases? It's up to you. courier-authlib upgrade shouldn't be an issue. Updating to the current version of Courier only adds a new configuration setting related to encryption, and a monthly script to generate a new set of DH parameters. This should be taken care of automatically if you follow the typical upgrade process – either build the RPMs, or run make install-configure, and manually install the cron entry. But there's a possibility that even the current version might balk for the same reason – libtool library mismatch. You might end up being in the same boat again. Updating to the current version does have certain advantages. The default, out of the box, encryption settings are stronger. Which is always a good thing. pgptmJi1cGW7k.pgp Description: PGP signature -- Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] LOGGEROPT and esmtpd
Hello, I'd like to separate log files from the various esmtpds (25, 465, 587), so I can see which one gets used how often by my users. However, I currently don't see any easy way to do so. The pop3d and imapd config files and start scripts have a variable LOGGEROPTS in their configfile that gets passed to courierlogger. However, the esmtpd startup script seems a bit different and doesn't call the logger directly. Is there a reason why LOGGEROPTS is not available for esmtpd? Sam, could this be changed for the next version? cu, -- Hanno Böck http://hboeck.de/ mail/jabber: ha...@hboeck.de GPG: BBB51E42 signature.asc Description: PGP signature -- Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] ltdl error building Courier-authlib rpm
On 4/4/2014 6:23 PM, Sam Varshavchik wrote: > Bowie Bailey writes: > >> Anyone have any ideas? >> >> If the line in the spec file reads: >> >> PATH=/usr/bin:$PATH %configure -C --with-redhat --without-authsqlite >> --without-authmysql --with-ltdl-lib=/usr/lib >> or >> PATH=/usr/bin:$PATH %configure -C --with-redhat --without-authsqlite >> --without-authmysql >> >> Then I get the error: >> configure: error: invalid ltdl library directory: `/usr/lib' >> >> If it reads: >> PATH=/usr/bin:$PATH %configure -C --with-redhat --without-authsqlite >> --without-authmysql --with-ltdl-lib=/usr/lib64 >> >> Then I get the error: >> configure: error: invalid ltdl library directory: `/usr/lib64' >> >> I think all of the libtool and ltdl packages are installed. >> libtool-ltdl-2.2.6-15.5.el6.x86_64 >> libtool-2.2.6-15.5.el6.x86_64 >> libtool-ltdl-devel-2.2.6-15.5.el6.x86_64 >> >> This is for installing courier-authlib-0.65.0 on CentOS 6.5 x86_64. >> (0.66.1 builds fine, but I would prefer to build this one first so I can >> copy over my old config and then do the upgrade on the new system.) >> >> Any suggestions, ideas, or wild guesses appreciated... :) > Try adding before %configure > > libtoolize -f > aclocal > autoheader > automake > autoconf I added the above between the %setup and %configure lines. It seemed to go ok until it hit autoconf. Here's the last bit of output: libtoolize: linking file `libltdl/ltdl.c' libtoolize: linking file `libltdl/ltdl.h' libtoolize: linking file `libltdl/slist.c' libtoolize: Remember to add `LT_CONFIG_LTDL_DIR([libltdl])' to `configure.in'. libtoolize: Consider using `AC_CONFIG_AUX_DIR([libltdl/config])' in configure.in. libtoolize: Consider using `AC_CONFIG_MACRO_DIR([libltdl/m4])' in configure.in. libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. + aclocal + autoheader + automake + autoconf configure.in:24: error: possibly undefined macro: AC_PROG_SYSCONFTOOL If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. error: Bad exit status from /var/tmp/rpm-tmp.WVdhQW (%prep) Do you think this is worth pursuing, or should I just give up and run the upgrade the old system? Am I likely to have any issues with an upgrade from Courier 0.69.0 and Authlib 0.65.0 to the current releases? -- Bowie -- Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees_APR ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Logging help
Just to wrap this one up I'm not getting the auth details in the logs, and I'm pretty sure that is because this is our oldest running mta which is in the process of being upgraded, once the new NAS comes in this week we'll begin the migration, and all should be good in the world. On Fri, Apr 4, 2014 at 3:13 PM, Manuel Schneider < manuel.schnei...@wikimedia.ch> wrote: > > I still wonder: If you didn't give RELAYCLIENT privileges to this > external IP address, how can it relay mails through your server? We found in the backups of a site linked to the domain which had full auth info in a php file, smtp username and password, we assumed this file got lifted in a cms hack, but it turns out that it didn't. Definitely is something worth looking into if you're experiencing something similar. On Sat, Apr 5, 2014 at 7:41 AM, Bernd Plagge wrote: > > in the mail queue files - should be in /var/lib/courier/msgq > > can't verify it right now because the mail queue is empty. > BTW, you check your mail queue with the 'mailq' command. > > Yes, this was the path to success. First off, mailq was the exim mail binary on the path installed by debian on this old machine, had to create a symbolic link between /usr/bin/mailq and /usr/lib/courier/bin/mailq Otherwise, running mailq gives the impression of empty mailqueue! Using that I could find the message Queue ID for a likely message Pretty much taken from : http://www.courier-mta.org/queue.html - i found the message id in /usr/lib/courier/var/msgs by running find -type f -print0 | xargs -r0 grep -F and was able to find the AUTH info in the message headers in there, which turned out to be a mother who returned from maternity leave and changed her email password to her newly born son's firstname, which was rather easily guessable. So, thanks everybody for your input, got there in the end, and lots of new things on my todo list for the new server for this client. Lisa. -- Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees_APR___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
