> > We are locking for "dothack" patch in order to be able to create logins
> > with dots...
> >
> The alternate separator patch is incorporated into 2.1, which provides the
> same functionality.
Yes, yes, but 2.1 requires the new SASL and all those problems. Since the
'final answer' is "stick w
> > > We are locking for "dothack" patch in order to be able to create
logins
> > > with dots...
> > >
> > The alternate separator patch is incorporated into 2.1, which provides
the
> > same functionality.
>
> Yes, yes, but 2.1 requires the new SASL and all those problems. Since the
> 'final answ
> We are locking for "dothack" patch in order to be able to create logins
> with dots...
>
The alternate separator patch is incorporated into 2.1, which provides the
same functionality.
I'm currently running smoothly 4 cyrus-imap servers and
when trying to add 3 more I got the _funky_ Death by 11
when telnetting 143 (see logs below).
The old servers are under mandrake 7.1 with
- cyrus-imapd-2.0.7
- cyrus-sasl-1.5.24
- openldap-1.2.7
- pam-ldap or sasl_ldap_mysql.patch
The new s
Vernon,
Maybe your first 128 MB memory modules are defective?
If they are the same in both test you reported (that is you added
256 MB to get 384 MB) and your hardware allowd try making
another test without them installed.
On 25 Jan 2002 at 12:14, Vernon A.. Fort wrote about "Signaled to De
Hi:
I recently upgraded/installed:
- Cyrus SASL 2 Libraries
- Cyrus IMAP 2.1.1
- OpenLDAP 2.0.21
All were configured with Kerberos version 1.2.3 DES.
Messages from syslog are:
imapd[12221]: unable to dlopen /usr/lib/sasl2/libdigestmd5.so.2:
/usr/lib/sasl2/libdigestmd5.
Hello all,
I have a problem for which has consumed me. The master process is reporting the
following:
Jan 25 09:58:33 mail master[8412]: process 18150 exited, signaled to death by
11
What I have done:
1. Re-compiled both cyrus-sasl and cyrus-imap using db3
Rob Siemborski wrote:
> On Fri, 25 Jan 2002, Olaf Zaplinski wrote:
>
>
>>Can someone tell me what's going on here please?
>>
>
> The "unable to get entry point" messages are Mostly Harmless (not all
> modules implement all of a client, server, canon_user, and auxprop
> plugin). In fact, none
On Fri, 25 Jan 2002, Olaf Zaplinski wrote:
> Can someone tell me what's going on here please?
The "unable to get entry point" messages are Mostly Harmless (not all
modules implement all of a client, server, canon_user, and auxprop
plugin). In fact, none do.
These messages are logged at the LOG
Hi *,
yesterday I switched from sasl-1.5.27 to sasl-2.1.0 and from imapd-2.0.16 to
imapd-2.1.1. Everything works fine since then, just as before. But I get
unknown log entries. When one mail arrives, the log entries are like this in
chronological order:
==> mail <==
Jan 25 19:08:40 binky send
How do you control the verbosity of messages posted to
/var/log/messages, maillog and imapd.log?
Harris Landgarten
How do you control the verbosity of messages posted to /var/log/messages,
maillog and imapd.log?
Harris Landgarten
Jim Grimmett schrieb am Thu, Jan 24, 2002 at 04:07:36PM -:
[...]
> try IMAP (as I've instructed it) but the firewall lets IMAPS through
> and cyrus is giving the message
>
> imapd: refused connection from xxx.xxx.xxx.xxx
>
> is it looking into hosts.allow (we're running redhat 6.2)? The cli
At 09:13 25/01/02, Phillip Hazel wrote:
>On Thu, 24 Jan 2002, John Holman wrote:
> > Actually, if it's true that there are no standards to be upheld, I also
> > think it would be better for Exim (which claims to be a Sendmail clone
> > insofar as the command line interface is concerned) to accept
On Thu, 24 Jan 2002, John Holman wrote:
> My guess is that there is no real standard, but I think it makes sense when
> passing a message to an MTA via stdin to comply with the conventions of the
> local operating system. That would mean LF under Unix, CRLF under Windows etc.
This seemed to me t
15 matches
Mail list logo
