I'm trying to get imapd 2.1.15 to work on a freebsd 5.1 machine with
SASL 2.1.13 (I think)
Imapd respond to connections but dies whenever an attempt is made to
authenticate to it:
Oct 6 22:22:14 ash kernel: pid 27479 (imapd), uid 60: exited on signal
11
Oct 6 22:22:14 ash master[27475]: proc
Title: Untitled Document
남한강포기김치
5kg/19,500원
남한강총각김치
5kg/24,500원
On Mon, 6 Oct 2003, Etienne Goyer wrote:
> How would one get the separator from an mupdate server ? In IMAP,
> NAMESPACE or LIST "" "" would do it. What is the equivalent in mupdate?
There isn't an equivilent in mupdate. Since all the hosts are
cooperating, they all should know what the hierar
On Tue, 7 Oct 2003, Chris Hastie wrote:
> I'm trying to get imapd 2.1.15 to work on a freebsd 5.1 machine with
> SASL 2.1.13 (I think)
>
> Imapd respond to connections but dies whenever an attempt is made to
> authenticate to it:
>
> Oct 6 22:22:14 ash kernel: pid 27479 (imapd), uid 60: exited on
Hi….
I’ve a problem with
kerberos… i saying in .configure what –with-auth= unix… and
when do it make throw error what not found any directory.
Any idea??
Thx in advance
I'm currently operating a Cyrus server listening in the following
configuration, and authenticating via PLAIN/LOGIN with a saslauthd backend
(only relevant config lines listed):
imapcmd="imapd -U 30" listen="localhost:imap"
imaps cmd="imapd -s -U 30" listen="imaps"
pop3s cmd=
Hi Daniel...
I can't answer your question, but I am wondering what client behavior you
have seen in this regard that is incorrect?
Thanks very much...
Jim
--On Tuesday, October 07, 2003 4:13 PM -0400 Daniel Whelan
<[EMAIL PROTECTED]> wrote:
I'm currently operating a Cyrus server listening in
On Tue, 7 Oct 2003, Daniel Whelan wrote:
> My question is, can I offer the IMAP port to any client but configure it
> such that they are required to STARTTLS to communicate? This would help
> with some picky email clients that don't like to deal with the alternate
> IMAPS port properly. Thanks!
I
Daniel Whelan wrote:
I'm currently operating a Cyrus server listening in the following
configuration, and authenticating via PLAIN/LOGIN with a saslauthd
backend (only relevant config lines listed):
imapcmd="imapd -U 30" listen="localhost:imap"
imaps cmd="imapd -s -U 30" listen="i
We currently have a single IMAP server and we are considering two
Solaris 8/9 HA Cyrus configurations:
#1. IMAP Aggregator (murder)
#2. Cyrus on a Veritas cluster (common file system with parallel service
groups)
After looking at the murder design, it seems to me that it's a lot
more compli
--Ken Murchison <[EMAIL PROTECTED]> wrote:
Assuming that you want to prevent plaintext passwords from being
transmitted in the clear, set the following in imapd.conf:
allowplaintext: no
Whoops, totally missed that. For some reason I believed that this would
kill the PLAIN and LOGIN authentication
I'll go ahead and answer my own question, as I evidently haven't been
paying as much attention to the mailing list as I should have lately and
found my solution buried back a couple months. On 30 July 2003 Matt
Bernstein started a thread entitled "requiring encryption but not from
localhost?",
On Tue, 7 Oct 2003, Ben Carter wrote:
> and an MTA on each cluster member, because with the murder
> configuration, you probably have to end up with a load-balancing switch
> in front of murder front-end machines which in turn are in front of the
This is not the case. Simple DNS round-robining i
--On Tuesday, October 07, 2003 6:43 PM -0400 Rob Siemborski
<[EMAIL PROTECTED]> wrote:r
On Tue, 7 Oct 2003, Ben Carter wrote:
and an MTA on each cluster member, because with the murder
configuration, you probably have to end up with a load-balancing switch
in front of murder front-end machines
On Tue, 7 Oct 2003, Ben Carter wrote:
> > This is not the case. Simple DNS round-robining is sufficient.
>
> How is simple DNS round-robin sufficient? More than one MUA caches the DNS
> lookups for its mail servers. I know that at least one version of
> Netscape Communicator used to. It probab
Hi. I've searched this mailing list and come across some posts which
indicate that cyrus 2.2 (I'm running Cyrus-IMAP 2.2.1 with Postfix 2.0.9
on FreeBSD 4.8) is not case sensitive when dealing with user
accounts/email addresses. That doesn't appear to be the case with my
installation. Whenever
On Tue, 7 Oct 2003, Avtar Gill wrote:
> Hi. I've searched this mailing list and come across some posts which
> indicate that cyrus 2.2 (I'm running Cyrus-IMAP 2.2.1 with Postfix 2.0.9
> on FreeBSD 4.8) is not case sensitive when dealing with user
> accounts/email addresses. That doesn't appear to
Hello!
I'm having a strange problem on which I cannot find any answers anywhere
:)
I'm using Cyrus 2.1.15 with imapd and pop3 servers and I'm getting weird
error MSGes. When I try this:
+OK moron Cyrus POP3 v2.1.15-IPv6-Debian-2.1.15-0woody.1.0 server ready
<[EMAIL PROTECTED]>
user nporenta
+OK N
> This wasn't actually my original question, but if I set allowplaintext to
> no, my webmail no longer is able to connect (as it wants an unencrypted
> connection). So, I'll ask a more complicated question:
>
> Can I selectively allow 127.0.0.1 to connect plaintext? Alternately, can I
> allow p
cyrus30751 1 0 Sep26 ?00:00:12 /usr/cyrus/bin/master -d
cyrus26549 30751 0 Oct07 ?00:00:00 pop3d
cyrus29490 30751 0 Oct07 ?00:00:00 pop3d
cyrus30492 30751 0 Oct07 ?00:00:00 pop3d
cyrus 1131 30751 0 Oct07 ?00:00:00
Igor Brezac wrote:
On Tue, 7 Oct 2003, Avtar Gill wrote:
Here are the relevant parts of my imapd.conf file, I can provide the
entire file if necessary..
sasl_pwcheck_method: auxprop
sasl_auxprop_plugin: sasldb
sasldb_path: /usr/local/etc/sasldb2
username_tolower: yes
You want lmtp_downcase
21 matches
Mail list logo
