Thanks, the problem was in base64. Timeout for 1 sec. I use only for
testing.
2010/6/29 Steffen Kaiser
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Tue, 29 Jun 2010, Неворотин Вадим wrote:
>
> my $base64 = encode_base64("\0$login\0$passwd");
>> $s
Yes, but this module doesn't work with my dovecot)) So I've tried to
manually debug it - and it really does not work and has an error somewhere.
Dovecot 1.2.10 from Debian backports.
2010/6/29 Anton Dollmaier
> Hi,
>
>
>
> I've wrote such script:
>>
>
> use Authen::SASL::Authd, as suggested b
-- Forwarded message --
From: Неворотин Вадим
Date: 2010/6/29
Subject: Re: [Dovecot] Work with auth socket
To: Steffen Kaiser
Hmm, I have some problems with realization of authentication throw dovecot
socket.
I've wrote such script:
#!/usr/bin/perl
$login = "test
Thank you!
2010/6/24 Steffen Kaiser
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> On Thu, 24 Jun 2010, Неворотин Вадим wrote:
>
> I need to use Dovecot auth socket from my perl script to validate user's
>> passwords (for jabber server). Is th
I need to use Dovecot auth socket from my perl script to validate user's
passwords (for jabber server). Is there any information about how to
communicate with dovecot auth socket?
2010/5/5 Steffen Kaiser
>
> First:
> Is it a typo or did you replaced %%u by %Lu ? Note the different number of
> %'s.
>
No, of course I try to replace %u with %Lu. And also %%u with %%Lu. It's not
working, so I think it's a bug.
> Second:
You can have passdb return set/overwrite "user", just
Today I've found a very irritating bug:
I use
mail_location = maildir:/var/mail/%u/
in my dovecot.conf. And if user type Username, username, USERname etc at
login dovecot create a different Maildir's for one real user. But LDA works
corretly and save all messages to lowercase username mailbox. N
uot;full-access" masteruser is really good for me[?]
2010/4/16 Timo Sirainen
> On Fri, 2010-04-16 at 16:57 +0400, Неворотин Вадим wrote:
> > I've add
> >
> > $ENV{'MASTER_USER'} = $ENV{'USER'};
> >
> > to my postlogin-imap script, and i
on about this feature[?])
2010/4/16 Timo Sirainen
> On Fri, 2010-04-16 at 15:30 +0400, Неворотин Вадим wrote:
> > Hmm[?] For what can I use masterusers, if I even can't read with
> masteruser
> > user's mails from INBOX? And where can I read about masterusers in that
&g
ri, 2010-04-09 at 20:53 +0400, Неворотин Вадим wrote:
> > Well, the main idea of master users is to able to log in as normal user
> with
> > master password. So IMAP client shoudn't know at all that it work with
> > masteruser password. And IMAP process must be exactly the sam
ug in
master users implementation. I see a big difference
2010/4/9 Eric Rostetter
> Quoting Неворотин Вадим :
>
> It's look like a big bug. As I understang there shouldn't be any different
>> between logging in with masteruser and normal log in. But in my system I
>
It's look like a big bug. As I understang there shouldn't be any different
between logging in with masteruser and normal log in. But in my system I
can't use masteruser at all due to IMAP errors.
2010/4/9 Eric Rostetter
> Quoting ? ? :
>
> I have very strange problem with masteruser
I have very strange problem with masteruser. See two logs below:
# telnet localhost 143
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE
STARTTLS AUTH=PLAIN AUTH=LOGIN] Welcome to our post server!
x login ne
Thanks! Master Users are very good solution for me.
2010/4/8 Timo Sirainen
> On Thu, 2010-04-08 at 01:38 +0400, Неворотин Вадим wrote:
> > Hmm, PREAUTH is cool. But all Perl CPAN modules for IMAP can work only
> throw
> > UNIX local sockets (or usual internet connection).
Hmm, PREAUTH is cool. But all Perl CPAN modules for IMAP can work only throw
UNIX local sockets (or usual internet connection). May be there is an
ability to create a socket when launchind 'dovecot --exec-mail imap' instead
of working directly with STDIN/STDOUT?
As I see in 2.0 there willn't be ability to control which flags should be
shared, and which should be per-user. But may be there is some plans to
implement settings to control that?
It'll be great if you can write in dovecot-shared file which flags should be
per-user. It's very usefull for group m
I've configure Dovecot with shared namespace and IMAP ACL's to make a group
mailboxes. I use maildir mailboxes, and I add dovecot-shared file to each
group mailbox. So each user with access to group mailbox has their own \Seen
flag. And now I need automatically delete a mail from server after 2 wee
I need to change ALC for mailboxes from a script on my server. As I
understand now I can correctly change ACL only via telnet using IMAP
commands. And moreover I need to know user's password for it. Is there any
plans to add inheritance of ACL and ability to manage it directly from a
server? And if
I need to create a shared folder (mailbox for group mailing list) with
access of several accounts to it. But all peoples with access to this
mailbox should be able to work with this folder absolutely in the same way,
as with local mailbox. Each user should be able to delete emails and mark it
as re
Well, I've asked this question in Postfix mail list and after discussion as
I understand Postfix 2.7 send all necessary client information to Dovecot
socket. But I haven't try this solution yet.
2010/2/18 Timo Sirainen
> On Mon, 2010-02-15 at 14:00 +0300, Неворотин Вадим wrote:
&
I use Dovecot for SASL authentication from Postfix. In Postfix main.cf I
have:
smtpd_sasl_type = dovecot
It works good, but now I need to allow users to connect by IMAP only from
given IP adresses. I've added extra field allow_nets to passdb in Dovecot,
and IMAP authentication works fine. But now
21 matches
Mail list logo