Re: make depend problems

On Tue, 31 Dec 2002 marc.bigler <at> day.com wrote:

> I am trying to compile the latest version of Cyrus IMAPD and have some
> problems already with the make depend, as you can see here in my output:
> 
> gmake[1]: Leaving directory `/opt/source/cyrus-imapd-2.1.11/imtest'
> ### Making depend in /opt/source/cyrus-imapd-2.1.11/perl
> gmake[1]: Entering directory `/opt/source/cyrus-imapd-2.1.11/perl'
> ### Making depend in /opt/source/cyrus-imapd-2.1.11/perl/sieve
> gmake[2]: Entering directory `/opt/source/cyrus-imapd-2.1.11/perl/sieve'
> gmake[2]: *** No rule to make target `depend'.  Stop.
> gmake[2]: Leaving directory `/opt/source/cyrus-imapd-2.1.11/perl/sieve'
> gmake[1]: *** [depend] Error 1
> gmake[1]: Leaving directory `/opt/source/cyrus-imapd-2.1.11/perl'
> gmake: *** [depend] Error 1
> 
> Does anyone have an idea what the problem could be ??? I am using standard
> GNU tools on Solaris 9.

Are you using the --disable-sieve configure option? It's broken and will
produce this error, but the attached patch (tested on Solaris 8 with GNU
tools) fixes the problem.

--
Simon Brady                             mailto:simon.brady <at> otago.ac.nz
ITS Technical Services
University of Otago, Dunedin, New Zealand

diff -ru cyrus-imapd-2.1.11.orig/configure.in cyrus-imapd-2.1.11/configure.in

Re: [Annoyed] Cyrus-imapd/sasl upgrade and lmtpd behaviour...

On Mon, 30 Dec 2002, Scott Smith wrote:

> What you probably want to do is add your MTA to the same group as Cyrus,
> at most.  [...]  Cyrus / SASL peeps, can you DOCUMENT this, since I
> personally know of several people that have had this problem, including
> myself when I upgraded from 1.5.x :)

Not wanting to sound patronising, but doc/install-configure.html already 
says this:

  * Edit /etc/group and add user "daemon" to the "mail" group. This 
    will permit sendmail to run the "deliver" (LMTP client) program to
    deliver mail to the IMAP server.

Mind you, it's under Sendmail 8.9.x - perhaps it need to be moved to an
outer scope?

--
Simon Brady                             mailto:simon.brady <at> otago.ac.nz
ITS Technical Services
University of Otago, Dunedin, New Zealand

Re: SASLAuthD keeps dying.

On 29 Dec 2002, Oliver Jones wrote:

> I think it is the TLS support of pam_ldap that is causing the core
> dump.  I ran saslauthd in a debugger and it seg faulted in
> libcrypto.so.2 which is part of openssl.
> 
> The interesting thing is that all my other pam related apps arn't
> dumping core or crashing and they are all using TLS to talk to the LDAP
> server via pam_ldap.  So it must be some interaction between pam, LDAP
> and saslauthd that is causing the issue.

This doesn't directly solve your problem, but have you considered dropping 
PAM and just using saslauthd's built-in ldap support? I'm running it in 
production (2.1.10) talking to ldap://localhost, and have tested it 
successfully with ldaps://remotehost. What does PAM-LDAP buy you that the 
native mechanism doesn't?

(Although as an aside, I strongly second Henrique's advice about checking
which libraries it's picking up: I sweated several hours over a different
saslauthd problem only to find that ldd told me the answer instantly.)

--
Simon Brady                             mailto:simon.brady <at> otago.ac.nz
ITS Technical Services
University of Otago, Dunedin, New Zealand

Re: someoone are using saslauthd+ldaps?

On Sat, 28 Dec 2002, Felix Cuello wrote:

>   Someone are using saslauthd + ldaps?, because my saslauthd works fine
>   with LDAP but not with LDAPS...

I can confirm that it works with SASL 2.1.10 / OpenLDAP 2.0.27 on 
Solaris 8. What sort of problems are you getting? Does ldaps in general 
work from the machine, e.g. can you do an ldapsearch to ldaps://host?

--
Simon Brady                             mailto:simon.brady <at> otago.ac.nz
ITS Technical Services
University of Otago, Dunedin, New Zealand

Re: [Annoyed] Cyrus-imapd/sasl upgrade and lmtpd behaviour...

huh...but I don't use Sendmail, so I never saw that :)

So yes maybe moving it to a different spot in the documentation and making
it a bit more generalized is a good idea, I agree.

Scott

--
scott <at> lackluster.net                     ``Chews?  I'll take charleston
http://storm.lackluster.net/~scott/     chews for SIXTEEN MILLIONS!!''

On Wed, 1 Jan 2003 simon.brady <at> otago.ac.nz wrote:

> On Mon, 30 Dec 2002, Scott Smith wrote:
>
> > What you probably want to do is add your MTA to the same group as Cyrus,
> > at most.  [...]  Cyrus / SASL peeps, can you DOCUMENT this, since I
> > personally know of several people that have had this problem, including
> > myself when I upgraded from 1.5.x :)
>
> Not wanting to sound patronising, but doc/install-configure.html already
> says this:
>
>   * Edit /etc/group and add user "daemon" to the "mail" group. This
>     will permit sendmail to run the "deliver" (LMTP client) program to
>     deliver mail to the IMAP server.
>
> Mind you, it's under Sendmail 8.9.x - perhaps it need to be moved to an
> outer scope?
>

saslauthd performance anxiety

I've just upgraded to imapd 2.1.11, and while it's going fine so far I'm a
bit concerned about how it will cope under load when our students return.

The problem is that I'm using the saslauthd native LDAP mechanism, and the
directory it's binding to is quite slow (it's actually a slapd instance
running a shell backend which routes bind requests to different places
depending on the usercode - don't ask...). Because saslauthd makes
synchronous bind calls, it's doesn't take many concurrent requests to
exhaust the default pool of five instances.

Since it's hard to predict peak usage, I'm tempted to run the daemon with 
the -n0 option so it can spawn as required. However, a colleague has 
pointed out that if something blows up then spawn-on-demand could kill the 
server - with a fixed-size pool, auth requests would fail but the system 
would keep going.

Can anyone offer advice on tuning the saslauthd pool? Are there particular
options, either on the command line or in saslauthd.conf, which I should
be looking at?

Many thanks...
Simon

--
Simon Brady                             mailto:simon.brady <at> otago.ac.nz
ITS Technical Services
University of Otago, Dunedin, New Zealand

Re: saslauthd performance anxiety

On Wed, 1 Jan 2003 simon.brady <at> otago.ac.nz wrote:

> I've just upgraded to imapd 2.1.11, and while it's going fine so far I'm a
> bit concerned about how it will cope under load when our students return.
>
> The problem is that I'm using the saslauthd native LDAP mechanism, and the
> directory it's binding to is quite slow (it's actually a slapd instance
> running a shell backend which routes bind requests to different places
> depending on the usercode - don't ask...). Because saslauthd makes
> synchronous bind calls, it's doesn't take many concurrent requests to
> exhaust the default pool of five instances.
>
> Since it's hard to predict peak usage, I'm tempted to run the daemon with
> the -n0 option so it can spawn as required. However, a colleague has
> pointed out that if something blows up then spawn-on-demand could kill the
> server - with a fixed-size pool, auth requests would fail but the system
> would keep going.
>

How many concurrent authentications do you need?  You can use
testsaslauthd (in $cyrus-sasl/saslauthd) to verify the performance of
saslauthd.

> Can anyone offer advice on tuning the saslauthd pool? Are there particular
> options, either on the command line or in saslauthd.conf, which I should
> be looking at?
>

Try using 'ldap_auth_method: custom'.  It is up to three times faster

Re: Sendmail & Unix Hierarchy Sep

I believe this subject was treated in this thread:

Re: cyrus-2.2-cvs: virtualdomains and sendmail virtusertable (cyrusv2 as 
local mailer)

You can go to 
http://asg.web.cmu.edu/archive/index.php?mailbox=archive.info-cyrus
and do a search for "sendmail" and go to the last 25 messages to see the 
tail end of
the thread.

Maybe Christian would share with you his final (?) solution?

Mike.

>Ya this is definately a sendmail problem.  I was hoping someone on this list
>had run into it before because for the life of me I cant figure out which
>flag I need to remove or add to solve this.
>
>Thanks,
>Ilan
>
>On Tue, Dec 31, 2002 at 09:34:51AM -0600, Simon Loader wrote:
> > I havent messed with sendmail configs for a while (been using these new
> > fangled MTA`s of late). Check the flags for your mailer is passing the
> > full emial. Track down which line in the config the error is coming from
> > becuase it looks like this is a sendmail problem.
> >
> > --
> > Simon Loader

Re: make depend problems

>Are you using the --disable-sieve configure option? It's broken and will
>produce this error, but the attached patch (tested on Solaris 8 with GNU
>tools) fixes the problem.

Yes exactly I am using the --disable-sieve option, thanks for the patch !
In the mean time I've also found out that I just need to comment out the
depend:: part of the Makefile in the perl directory.

Regards
Marc

sieve notifyd method for sending sms doesn't work

I want to get the contrib notify_unix stuff to work. My goal is to send sms 
messages in case of important messages. This is my sieve file:

require ["fileinto","notify"];
if anyof (header :contains "subject" "test") {
        fileinto "INBOX.test
#tried       notify :method "zephyr"  :message "Important message";
#tried       notify :method "notify"  :message "Important message";
#tried       notify :method "daemon"  :message "Important message";
               notify :method "log"  :message "Important message";
}

This is my imap.conf
mailnotifier: log
sievenotifier: log

I get entries in my log like that:

Jan  1 03:27:30 horizon notifyd[15498]: do_notify using method 'log'
Jan  1 03:27:30 horizon notifyd[15498]: MAIL, , mt, INBOX.test,  "From: mt 
<mt <at> xx.do.main> Subject: test To: mt <at> xx.do.main "
Jan  1 03:27:30 horizon notifyd[15498]: do_notify using method 'unknown'

I have tried all methods I have found in the man pages and in the
mailarchives, but to no avail. The perl scripts are build and started. Please 
can someone point me to the correct direction? As my search of the archives 
revealed it is not only me who has some problems getting this type of
setup to work.