> From: Rudy Gevaert [mailto:[EMAIL PROTECTED]
>
> Larry Rosenbaum wrote:
>
> >>If I understoond you correct, you are saying that I cando a tls
connect
> >>with in Cyrus::IMAP::Admin? Right?
> >
> >
> > Yes.
>
> Ok. Can you provide any pointers how to go about it then? I
previously
> asked how
Larry Rosenbaum wrote:
If I understoond you correct, you are saying that I cando a tls connect
with in Cyrus::IMAP::Admin? Right?
Yes.
Ok. Can you provide any pointers how to go about it then? I previously
asked how to use tls with cyradm but my question remained unanswered.
Thanks in
> From: [EMAIL PROTECTED] [mailto:info-cyrus-
> [EMAIL PROTECTED] On Behalf Of Rudy Gevaert
> Subject: Re: unable to login with cyradm
>
> Larry Rosenbaum wrote:
> > Cyrus IMAP v2.3.3 and above have TLS support. You might have to add the
> > "--tls" switch
Larry Rosenbaum wrote:
Cyrus IMAP v2.3.3 and above have TLS support. You might have to add the
"--tls" switch to make it work. For older versions see the patch on
https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=2036
Hi Larry,
If I understoond you correct, you are saying that I cando a tls
You can use the port 143 only in localhost for access to cyradm.
You have to change the cyrus.conf file like that:
imap cmd="imapd" listen="localhost:imap" prefork=1
#imap cmd="imapd" listen="imap" prefork=5
imaps cmd="imapd -s" listen="imaps" prefork=5
- ANNA -
Q
Joe Harvell wrote:
I used cyradm a long time ago to set up two mailboxes, and now I need to
use it again, but I can't login:
I am running cyrus-imapd 2.2.12. I know that the latest 2.3 version
supports TLS with cyradm. But I am not ready to upgrade. I just want
to be able to run cyradm from t
EMAIL PROTECTED] On Behalf Of Daniel Eckl
> Sent: Wednesday, August 02, 2006 10:41 AM
> To: Joe Harvell
> Cc: info-cyrus@lists.andrew.cmu.edu
> Subject: Re: unable to login with cyradm
>
> Hi Joe!
>
> Cyradm (or only your cyradm? Dunno...) might not be SSL capable.
>
>
addendum to my info:
http://article.gmane.org/gmane.mail.imap.cyrus/824
http://article.gmane.org/gmane.mail.imap.cyrus/21264/
Best,
Daniel
Daniel Eckl schrieb:
Hi Joe!
Cyradm (or only your cyradm? Dunno...) might not be SSL capable.
So either use port 143 to connect or if you have to user IMA
Hi Joe!
Cyradm (or only your cyradm? Dunno...) might not be SSL capable.
So either use port 143 to connect or if you have to user IMAPS Port 993,
then you could establish an ssl tunnel with stunnel program.
Best,
Daniel
Joe Harvell schrieb:
Could someone *please* take a look at this?
Joe H
Could someone *please* take a look at this?
Joe Harvell wrote:
> I used cyradm a long time ago to set up two mailboxes, and now I need to
> use it again, but I can't login:
>
> I am running cyrus-imapd 2.2.12. I know that the latest 2.3 version
> supports TLS with cyradm. But I am not ready to
You have the -u and -a parameters mixed up.
You want to authenticate (-a) as 'cyrus' and be authorized (-u) as USER.
In your imapd.conf file you have
sasl_mech_list: PLAIN
So the only SASL mechanism that will be advertised by the server is
PLAIN. It will only be advertised if you connect se
I forward your answer to cyrus mailing list.
--- Begin Message ---
Thanks for the response, but unfortunately I dont know which
authentication I am using, and how t configure it.
The documentation says when you run imtest , it gives you the AUTH
methods enabled, for me it does not show
Hi,
I use the imtest command as following:
./imtest -u USER (for me, it's the ldap uid of user) -a USER -m login
(or plain) -s (for ssl) -v pc-systeme.cict.fr
or ./imtest -u USER -a USER -m login (or plain) -p imap -v localhost
Carole.
Imran Aziz wrote:
Hello All,
I have finally managed
Try it with testsaslauthd first to see if saslauthd is working
correctly.
>testsaslauthd -u cyrus -p password
0: OK "Success."
-Patrick
On Jun 2, 2005, at 8:47 AM, Imran Aziz wrote:
Hello All,
I have finally managed to install Cyrus IMAP. But I am unable to
login to the server to create ne
On Wed, 7 Jul 2004, Wil Cooley wrote:
> On Wed, 2004-07-07 at 12:45, Mike Beattie wrote:
>
> > And I hate to point out, but then, if a malicious user manages to find a
> > flaw in cyrus they could hypothetically use that flaw to get a copy of
> > /etc/shadow. (If I'm mistaken, *please* correct me)
On Wed, 2004-07-07 at 12:45, Mike Beattie wrote:
> And I hate to point out, but then, if a malicious user manages to find a
> flaw in cyrus they could hypothetically use that flaw to get a copy of
> /etc/shadow. (If I'm mistaken, *please* correct me)
>
> Only the second worst thing after actually
On Wed, Jul 07, 2004 at 10:47:39AM -0700, Wil Cooley wrote:
> No, saslauthd runs as root--it's role is to provide authentication
> services, often for PAM or shadow authentication, which requires root
> access. It's a much better solution than creating a 'shadow' group and
> making /etc/shadow rea
On Wed, Jul 07, 2004 at 07:19:11PM +0200, Dudi Goldenberg wrote:
> Thank you all people!
>
> The problem was that /etc/default/saslauthd was reset to default values
> after a apt-get update.
>
> Once I noticed that saslauthd was not running it didn't take much to
> find & fix it.
Speaking with m
On Wed, 2004-07-07 at 08:44, Patrick Welche wrote:
> > What about saslauthd?
>
> I don't actually use saslauthd, but assume that it too will become user cyrus..
No, saslauthd runs as root--it's role is to provide authentication
services, often for PAM or shadow authentication, which requires roo
Am Mi, den 07.07.2004 schrieb Louis LeBlanc um 17:09:
> > > This kinda begs the question, what exactly *should* the permissions be
> > > for sasldb2.db?
> > >
> > > Lou
> >
> > chown root:root /etc/sasldb2
> > chmod 600 /etc/sasldb2
> >
> > (the database has no .db ending)
>
> It appears that
Thank you all people!
The problem was that /etc/default/saslauthd was reset to default values
after a apt-get update.
Once I noticed that saslauthd was not running it didn't take much to
find & fix it.
Regards,
Dudi
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://c
On Wed, Jul 07, 2004 at 11:10:48AM -0400, Louis LeBlanc wrote:
> > > On 07/07/04 02:29 PM, Patrick Welche sat at the `puter and typed:
> > I happen to use
> >
> > -rw--- 1 cyrus mail 24576 May 10 23:43 /etc/sasldb2
>
> This is helpful. I guess you're running imapd as cyrus:mail?
Well, I
On 07/07/04 03:25 PM, Patrick Welche sat at the `puter and typed:
> On Wed, Jul 07, 2004 at 09:56:31AM -0400, Louis LeBlanc wrote:
> > On 07/07/04 02:29 PM, Patrick Welche sat at the `puter and typed:
> > > On Wed, Jul 07, 2004 at 12:03:12AM +0200, Dudi Goldenberg wrote:
> > > > Jul 6 23:58:32 mai
On 07/07/04 04:29 PM, Alexander Dalloz sat at the `puter and typed:
> Am Mi, den 07.07.2004 schrieb Louis LeBlanc um 15:56:
>
> > This kinda begs the question, what exactly *should* the permissions be
> > for sasldb2.db?
> >
> > Lou
>
> chown root:root /etc/sasldb2
> chmod 600 /etc/sasldb2
>
>
Am Mi, den 07.07.2004 schrieb Louis LeBlanc um 15:56:
> This kinda begs the question, what exactly *should* the permissions be
> for sasldb2.db?
>
> Lou
chown root:root /etc/sasldb2
chmod 600 /etc/sasldb2
(the database has no .db ending)
Alexander
--
Alexander Dalloz | Enger, Germany | GPG
On Wed, Jul 07, 2004 at 09:56:31AM -0400, Louis LeBlanc wrote:
> On 07/07/04 02:29 PM, Patrick Welche sat at the `puter and typed:
> > On Wed, Jul 07, 2004 at 12:03:12AM +0200, Dudi Goldenberg wrote:
> > > Jul 6 23:58:32 mail cyrus/imapd[2205]: badlogin: localhost[127.0.0.1]
> > > Any hint what to
On 07/07/04 02:29 PM, Patrick Welche sat at the `puter and typed:
> On Wed, Jul 07, 2004 at 12:03:12AM +0200, Dudi Goldenberg wrote:
> > Jul 6 23:58:32 mail cyrus/imapd[2205]: badlogin: localhost[127.0.0.1]
> > Any hint what to look for?
>
> Clues in /var/log/authlog ? file permissions on /etc/sa
On Wed, Jul 07, 2004 at 12:03:12AM +0200, Dudi Goldenberg wrote:
> Jul 6 23:58:32 mail cyrus/imapd[2205]: badlogin: localhost[127.0.0.1]
> Any hint what to look for?
Clues in /var/log/authlog ? file permissions on /etc/sasldb2 ?
capability string when trying to connect with imtest ?
(Just guessin
28 matches
Mail list logo
