- Several mbox fixes, upgrade recommended for test68 mbox users
- Possibly fixes some IMAP hangs where Dovecot just stopped replying
- Fixed delay-newmail workaround. It was badly broken before.
And somewhat off topic advertisement:
I got a bit distracted from Dovecot a week ago when a guy started mailing me about wanting to write an irssi2 client as a project to learn Ruby. Half a year ago I had written a semi-working irssi2 server but I got stuck with it because I wasn't interested about writing client for it. Now that the client actually works, irssi2's development has kind of exploded :)
Irssi2 is a bit related to Dovecot too, in that it'll be integrated with it more or less tightly to provide instant messaging support. Nothing prevents extending irssi2-protocol to support all other kinds of realtime events either, for example to send new mail notifications.
If you're interested, see:
http://main.irssi.org/projects/irssi2.html
And for the lazy, here's the introduction copy&pasted:
Shortly put, irssi2 is to instant messaging what IMAP is to mail. You can safely exit your irssi2 client, and irssi2 server just keeps on going. When you connect back with your client, you can see all the discussion that happened while you were away (and even older discussion, too, if you want).
You can also use multiple clients even at the same time, so you could for example keep one client always open at home and still be able to check what's going on with your mobile phone.
Irssi2 clients are encouraged to keep their configuration in server side, so nothing should prevent you from temporarily using another irssi2 client from your friend's home with no other configuration needed than irssi2 server's address, your username and password.
Irssi2 is designed to support multiple chat protocols (IRC, SILC, MSN, ICQ, etc.) but without ignoring hardcore IRC users. That means that unlike all other similar attempts (such as Jabber), irssi2's client-server protocol will actually allow fully featured irssi2 IRC client to be written with no compromises (but still the same client can be used to talk to MSN and elsewhere).
Note that irssi2 isn't trying to replace IRC servers (yet ;). irssi2 server simply connects to normal IRC servers just as a regular IRC client. To prevent mixups with these terms, IRC servers are usually called "gateways" in irssi2.
Funky stuff, I'm sure I'll annoy you with an obscure bug I dig up shortly ;)
As for Irssi2, looks very interesting, I may be tinkering with it shortly.
Gonna see if I can write a minor patch for dovecot this week so that we can see number of messages downloading in a pop3 session in the logfile. Similar to the way UW does it, will be very useful for us at work trying to trace customers POP problems, I will submit it if anyone will find it useful.
Regards Andrew
On Sun, 2005-05-08 at 20:33 +0300, Timo Sirainen wrote:
- Several mbox fixes, upgrade recommended for test68 mbox users
- Possibly fixes some IMAP hangs where Dovecot just stopped replying
- Fixed delay-newmail workaround. It was badly broken before.
And somewhat off topic advertisement:
I got a bit distracted from Dovecot a week ago when a guy started mailing me about wanting to write an irssi2 client as a project to learn Ruby. Half a year ago I had written a semi-working irssi2 server but I got stuck with it because I wasn't interested about writing client for it. Now that the client actually works, irssi2's development has kind of exploded :)
Irssi2 is a bit related to Dovecot too, in that it'll be integrated with it more or less tightly to provide instant messaging support. Nothing prevents extending irssi2-protocol to support all other kinds of realtime events either, for example to send new mail notifications.
If you're interested, see:
http://main.irssi.org/projects/irssi2.html
And for the lazy, here's the introduction copy&pasted:
Shortly put, irssi2 is to instant messaging what IMAP is to mail. You can safely exit your irssi2 client, and irssi2 server just keeps on going. When you connect back with your client, you can see all the discussion that happened while you were away (and even older discussion, too, if you want).
You can also use multiple clients even at the same time, so you could for example keep one client always open at home and still be able to check what's going on with your mobile phone.
Irssi2 clients are encouraged to keep their configuration in server side, so nothing should prevent you from temporarily using another irssi2 client from your friend's home with no other configuration needed than irssi2 server's address, your username and password.
Irssi2 is designed to support multiple chat protocols (IRC, SILC, MSN, ICQ, etc.) but without ignoring hardcore IRC users. That means that unlike all other similar attempts (such as Jabber), irssi2's client-server protocol will actually allow fully featured irssi2 IRC client to be written with no compromises (but still the same client can be used to talk to MSN and elsewhere).
Note that irssi2 isn't trying to replace IRC servers (yet ;). irssi2 server simply connects to normal IRC servers just as a regular IRC client. To prevent mixups with these terms, IRC servers are usually called "gateways" in irssi2.
-- Andrew Hutchings (A-Wing) Linux Guru - Netserve Consultants Ltd. - www.domaincity.co.uk Admin - North Wales Linux User Group - www.nwlug.org.uk BOFH excuse 170: popper unable to process jumbo kernel
On 128, 05 08, 2005 at 06:57:48PM +0100, Andrew Hucthings wrote:
Funky stuff, I'm sure I'll annoy you with an obscure bug I dig up shortly ;)
Gonna see if I can write a minor patch for dovecot this week so that we can see number of messages downloading in a pop3 session in the logfile. Similar to the way UW does it, will be very useful for us at work trying to trace customers POP problems, I will submit it if anyone will find it useful.
Don't waste your time :) Take a look at the attached patch.
-- Andrey Panin | Linux and UNIX system administrator pazke@donpac.ru | PGP key: wwwkeys.pgp.net
On Mon, 2005-05-09 at 11:19 +0400, Andrey Panin wrote:
On 128, 05 08, 2005 at 06:57:48PM +0100, Andrew Hucthings wrote:
Funky stuff, I'm sure I'll annoy you with an obscure bug I dig up shortly ;)
Gonna see if I can write a minor patch for dovecot this week so that we can see number of messages downloading in a pop3 session in the logfile. Similar to the way UW does it, will be very useful for us at work trying to trace customers POP problems, I will submit it if anyone will find it useful.
Don't waste your time :) Take a look at the attached patch.
Many thanks Andrey, that is just what we needed :)
Well done to Timo too, a test version I can't seem to break (and I tried all the usual GUI clients IMAP stumbles with), roughly customer 15000 logins since midday (about 2 and a half hours ago) with no errors :)
Regards Andrew
Andrew Hutchings (A-Wing) Linux Guru - Netserve Consultants Ltd. - www.domaincity.co.uk Admin - North Wales Linux User Group - www.nwlug.org.uk BOFH excuse 305: IRQ-problems with the Un-Interruptible-Power-Supply
Hello Andrey Panin <pazke@donpac.ru>, Monday, May 9, 2005, 9:19:57 AM, you wrote:
Gonna see if I can write a minor patch for dovecot this week so that we can see number of messages downloading in a pop3 session in the logfile. Similar to the way UW does it, will be very useful for us at work trying to trace customers POP problems, I will submit it if anyone will find it useful.
AP> Don't waste your time :) Take a look at the attached patch.
It's GREAT!
Is there any chance that will be included in the main build tree?
Ciao, luigi
-- 43rd Law of Computing: Anything that can go wr Segmentation fault.
Timo: Feature request here I think, I would love this patch (or similar) to be in the tree. Already creating mrtg graphs based on it to see what is really happening.
Regards Andrew
On Wed, 2005-05-11 at 16:21 +0200, Luigi Rosa wrote:
Hello Andrey Panin <pazke@donpac.ru>, Monday, May 9, 2005, 9:19:57 AM, you wrote:
Gonna see if I can write a minor patch for dovecot this week so that we can see number of messages downloading in a pop3 session in the logfile. Similar to the way UW does it, will be very useful for us at work trying to trace customers POP problems, I will submit it if anyone will find it useful.
AP> Don't waste your time :) Take a look at the attached patch.
It's GREAT!
Is there any chance that will be included in the main build tree?
Ciao, luigi
-- Andrew Hutchings (A-Wing) Linux Guru - Netserve Consultants Ltd. - www.domaincity.co.uk Admin - North Wales Linux User Group - www.nwlug.org.uk BOFH excuse 371: Incorrectly configured static routes on the corerouters.
- Timo Sirainen shaped the electrons to say...
- Several mbox fixes, upgrade recommended for test68 mbox users
- Possibly fixes some IMAP hangs where Dovecot just stopped replying
- Fixed delay-newmail workaround. It was badly broken before.
FYI - vpopmail is still broken.
First - there is a compile error:
Install prefix ...................... : /pkg/dovecot-1.0-test69 File offsets ........................ : 64bit I/O loop method ..................... : epoll Building with SSL support ........... : yes (OpenSSL) Building with IPv6 support .......... : no Building with pop3 server ........... : yes Building with mail delivery agent .. : yes Building with user database modules . : passdb passwd passwd-file vpopmail (modules) Building with password lookup modules : passwd passwd-file shadow vpopmail (modules)
passdb-vpopmail.c: In function vpopmail_verify_plain': passdb-vpopmail.c:52: error: invalid type argument of ->'
If that line is commented out (it looks harmless, and none of the other passdb files have it) - the compile finishes. However, when trying to log in to an account that is a virtual domain:
Info: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=127.0.0.1 rip=127.0.0.1 resp=AHRlc3Rmb29AemVl>cC5vcmcAYWJjMTIz Info: auth(default): vpopmail(testfoo@zeep.org,127.0.0.1): crypted password=$1$H5Xxe$fPVY0KaKV49HD1dmXnSPG. Info: auth(default): client out: OK 1 user=testfoo Info: auth(default): master in: REQUEST 1 30716 1 Info: auth(default): vpopmail(testfoo,127.0.0.1): unknown user Error: auth(default): userdb(testfoo,127.0.0.1): user not found from userdb Info: auth(default): master out: NOTFOUND 1 Info: imap-login: Internal login failure: testfoo [127.0.0.1]
Config section looks like:
auth default { mechanisms = plain
userdb passwd {}
userdb vpopmail {}
passdb shadow {}
passdb vpopmail {}
user = root
count = 2}
This used to work in the -test5x range.
Thanks for any insight.
-D
Welcome to hell. Here's your accordion.
participants (5)
-
Andrew Hucthings
-
Andrey Panin
-
Dan Sully
-
Luigi Rosa
-
Timo Sirainen