FYI: pop-before-smtp works with cyrus-imapd-2.1.4
I just wanted to let people know that the postfix addon software "pop-before-smtp" works seamlessly with cyrus-imapd-2.1.4 It's a great little script that checks the imapd log for valid pop3/imap logins and then writes the users IP to a hashed file that the smtpd daemon can check to validate a relay. Jeff
Re: [PATCH] Updated master.c process counting patch
Henrique de Moraes Holschuh wrote: >I am, thus, somewhat wary of adding SHUT_RDWR inconditionally. Maybe we >could add a runtime-option that very busy sites can set if they need even >faster socket recycling? > > That sounds like a good idea.
Patch for SMTP after IMAP
Hi, I whipped this up because I needed this functionality. I have no idea if it's suitable for general use. Here is what it does: A new configuration value of 'relaydb' is added to /etc/imapd.conf as follows: relaydb: /etc/mail/access.db Then, whenever someone successfully logs into POP or IMAP, their IP address is added as a RELAY into the sendmail access db, using the db3 database routines. It's not the most elegant solution but it worked fine for me, so you may wish to include it in the main product (or not, in which case I'll keep the patch). The patch can be found at: http://secondwivescafe.com/cyrus-imap-POPB4SMTP-patch.txt Ron
Re: does cvt_cyrusdb work? is it normal to have "DBERRORS db3: xlockers" messages?
Luca Olivetti wrote: > Anyway, before using the new imapd, I converted the seen db for myself > (/var/lib/imap/user/l/luca.seen) with cvt_cyrusdb, but *all* messages > appeared as unseen. > Is cvt_cyrusdb supposed to work for the seen.db? I just tried the same but with skiplist and it did work. So flat --> db3 didn't work, but flat --> skiplist does. No DBERRORS so far, but it has been working for just a couple of hours. I'll see if this also solves the mozilla unseen problem. Bye -- Luca Olivetti Wetron Automatización S.A. http://www.wetron.es/ Tel. +34 93 5883004 Fax +34 93 5883007
Re: does cvt_cyrusdb work? is it normal to have "DBERRORS db3: xlockers" messages?
Jeff Bert wrote: >>Luca Olivetti wrote: >>Is that example configuration not good? >> > > > Dunno for sure. I tend to change something and test... change and test... > change and test... but I didn't write everything down so I have to admit I'm > not sure how I got rid of those db3 errors... I had them too but don't > now... it might be how I compiled postfix that solved it: > > # make -f Makefile.init makefiles \ > CCARGS="-DHAS_MYSQL -I/usr/local/mysql/include \ > -DHAS_DB -I/usr/include/db3" \ > AUXLIBS="-L/usr/local/mysql/lib -lmysqlclient -lz -lm \ > -L/usr/lib -ldb-3.3" > > And then installed cyrus-sasl and cyrus-imapd. > > When I first installed the cyrus rpms I got those db errors also and then > starting messing with stuff and finally got rid of them. Maybe > it was the postfix compile. Don't see how that relates to it, the errors I see are from the various cyrus programs. Anyway, even with these errors everything is working fine, but then this is my home system with just two users. I'm a little nervious with these errors because next week I'll install the same configuration at work (replacing the previous mandrake7.0+cyrus 1.6.24). Bye -- Luca Olivetti Wetron Automatización S.A. http://www.wetron.es/ Tel. +34 93 5883004 Fax +34 93 5883007
RE: does cvt_cyrusdb work? is it normal to have "DBERRORS db3: x lockers" messages?
> Luca Olivetti wrote:
> Is that example configuration not good?
>
Dunno for sure. I tend to change something and test... change and test...
change and test... but I didn't write everything down so I have to admit I'm
not sure how I got rid of those db3 errors... I had them too but don't
now... it might be how I compiled postfix that solved it:
# make -f Makefile.init makefiles \
CCARGS="-DHAS_MYSQL -I/usr/local/mysql/include \
-DHAS_DB -I/usr/include/db3" \
AUXLIBS="-L/usr/local/mysql/lib -lmysqlclient -lz -lm \
-L/usr/lib -ldb-3.3"
And then installed cyrus-sasl and cyrus-imapd.
When I first installed the cyrus rpms I got those db errors also and then
starting messing with stuff and finally got rid of them. Maybe
it was the postfix compile.
As you know I'm not anywhere near an expert... I just trying to relate my
experience. Since we use similar systems in Linux-Mandrake I thought that
mine might shed some light on yours.
Jeff
> >
> > # standard standalone server implementation
> >
> > START {
> > # do not delete this entry!
> >recover cmd="ctl_cyrusdb -r"
> >mboxlist cmd="ctl_mboxlist -r"
> >deliver cmd="ctl_deliver -r"
>
> according to the manpage ctl_mboxlist and ctl_deliver don't have an -r
> option now, this functionality is included in ctl_cyrusdb.
>
> []
yes, when you run the command it says it's depricated but if you are logging
via 'local6.debug' for cyrus you'll see that the ctl_mboxlist does run and
completes.
>
> > EVENTS {
> > # this is required
> > # checkpoint cmd="ctl_cyrusdb -c" period=30
> >checkpoint cmd="ctl_mboxlist -c" period=30
>
> ctl_mboxlist doesn't have a -c option now. Its functionality is in
> ctl_cyrusdb.
>
same as above, you get a report that it's depricated but it runs and reports
in the log file but, I'm going to put my cyrus.conf back to using the
ctl_cyrusdb for both STARTUP and EVENTS and see if I have any problems.
Re: [PATCH] Updated master.c process counting patch
On Thu, 16 May 2002, Jeremy Howard wrote: > I *strongly* recommend also including shutdown.diff. This is important > in Linux to avoid sockets handing around in CLOSE_WAIT state. Remove the I had a talk with some kernel people, and they confirmed that. shutdown(socket, SHUT_RD) should _always_ be done under linux if you really don't need to read from the socket anymore. For AF_INET* sockets, anyway. shutdown(socket, SHUT_RDWR) will reduce the CLOSE_WAIT state even more, however it effectively trashes the connection; I don't like this idea very much. It is far more amiable to the client if you let it read the last stuff you sent it (such as error messages!) at its own leisure. I am, thus, somewhat wary of adding SHUT_RDWR inconditionally. Maybe we could add a runtime-option that very busy sites can set if they need even faster socket recycling? -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
Re: does cvt_cyrusdb work? is it normal to have "DBERRORS db3: xlockers" messages?
Jeff Bert wrote:
> Luca,
>
> When I built the cyrus-sasl-2.1.2 rpm from your source files I noticed that
> the "make" output never had a "-I/usr/include/db3" which is where the
> include files for BerkeleyDB3.3 are stored from the Mandrake RPM's.
It's there in my Makefiles, so that this is not the problem.
(OTOH I don't understand why it's not there in yours, after all the
configure script is the same. Note that it's not there in the top
directory Makefile but only in the various subdirectories where's it's
needed)
>
> I added a "CPPFLAGS=-I/usr/include/db3" in the cyrus-sasl.spec file before
> compiling... but not sure if it made a differece because:
>
> Also, I modified the cyrus.conf file to be more like the older version
> instead of the newer ones... here's mine... not sure which solved the
> problem, the .spec file mod or the .conf file mod:
The cyrus.conf included in the spec file is the example one shipped with
cyrus-2.1.4 (check in the "conf" subdirectory).
Is that example configuration not good?
>
> # standard standalone server implementation
>
> START {
> # do not delete this entry!
>recover cmd="ctl_cyrusdb -r"
>mboxlist cmd="ctl_mboxlist -r"
>deliver cmd="ctl_deliver -r"
according to the manpage ctl_mboxlist and ctl_deliver don't have an -r
option now, this functionality is included in ctl_cyrusdb.
[]
> EVENTS {
> # this is required
> # checkpoint cmd="ctl_cyrusdb -c" period=30
>checkpoint cmd="ctl_mboxlist -c" period=30
ctl_mboxlist doesn't have a -c option now. Its functionality is in
ctl_cyrusdb.
Bye
--
Luca Olivetti
Wetron Automatización S.A. http://www.wetron.es/
Tel. +34 93 5883004 Fax +34 93 5883007
日本 bb 槍限時清倉大特賣，全部批發價現貨供應
Title: ¥Í¦s¹CÀ¸ BBºj¤j¯S½æ ¡@ ¡C¯uºj1¡G1¤ñ¨Ò³]p ¡C®g³t§Ö¤õ¤O±j ¡C³æµo³sµo®gÀ» ¡C³Ì·s¼W±jM9§@«~ ¡C¤õ¤O±j¤j¡A½æ®y³Ì¨Î ¡Cºë±K¶ì¿û§÷½è¡A¥i½Õ¼u¹D ¡C¤é¥»KSC2001¦~©³³Ì·s¤O§@ ¡C´¤§â¿W¯S¡A³]p³y«¬ºë¬ü ¡C§ï¨}¤õ¤O¡A¬ï³z¤O¯S±j ::¡@¡@¡@¯S»ù¸ê°T¨Ñ±z°Ñ¦Ò¡@¡@«Ü©êºp¥´ÂZ±z¡@¡@ :: ¤£§Æ±æ¦A¦¬¨ì¦¹«H½Ð¨Ó«H¡[EMAIL PROTECTED]
