similar to: serious Qpopper 3.0 vulnerability (fwd)

Hi, some more info on the previous admw0rm alert. Fwd'd from BugTraq Greetings, Jan-Philip Velders ---------- Forwarded message ---------- Date: Fri, 26 Mar 1999 21:17:40 +0100 From: Mixter <mixter@HOME.POPMAIL.COM> To: BUGTRAQ@NETSPACE.ORG Subject: Re: ADM Worm. Worm for Linux x86 found in wild. The "ADM w0rm" is public and can be found at:

Hello Dovecot users, Recently I was asked to use Mercurial for the ManageSieve development just like Dovecot. As a matter of fact I have been using Mercurial for some time now. Now that I am back from a short and active vacation I am ready to publish my repositories. The repositories are publicly available at: http://hg.rename-it.nl/ The -patch repositories are so-called Mercurial Queues (MQ)

Hello, Anyone have information on whether RedHat-5.0+ is affected by the recent (today's) CERT advisory regarding QPOP? thanks, -bp -- B. James Phillippe <bryan@terran.org> Linux Software Engineer, WGT Inc. http://earth.terran.org/~bryan

I''ve got qualcomm''s qpopper2.2, and am not sure if its vulnerable. The advisory mentions pop and imap servers, but only says: version of IMAP (Section B). If your POP server is based on the University of Washington IMAP server code, you should also upgrade to the latest version of IMAP. Until you can take one of these actions, I installed the new imapd about 3

Hi, I am planning a migration from Qpopper 4.0.5 to Dovecot.. I need to use mbox format (because Openwebmail does not have native Maildir support yet) and pop3. The system will have about 1500 users, once migrating is complete. To avoid users downloading their mailboxes all over again, i need to set "pop3_reuse_xuidl = yes".. But that option works since Dovecot 1.0alpha1. RHEL

Hello, I have read in lots of places about how I should use pop3_reuse_xuidl = yes to prevent pop3 users having to re-download mail (and duplicate their e-mail) after a migration. This fails with the message: pop3_uidl_format setting is missing from config file Which setting for pop3_uidl_format should I set to prevent the e-mail being downloaded again?

Heya, We are in the process of migrating from qpopper to dovecot as POP3 server (and IMAP as well) and we hit the UIDL issue with dovecot. Qpopper uses its own algorithm to create UIDL values and if you set it up to write them down in the mbox file as X-UIDL, then dovecot can use them (pop_uidl_reuse = yes). But if you don't use that feature from qpopper, than X-UIDLs are missing and there

I currently have a Centos server with Sendmail and Qpopper supporting about 50 mail users. I am planning to replace Qpopper with Dovecot to allow some users to have IMAP access to their mail (others will still use POP3.) Is there anything special to be aware of in setting up this migration? Thanks for your comments. Gerald

Hello, As this is my first post to the list, first and foremost I'd like to thank Timo for writing great software; we've successfully moved to Dovecot for over 10,000 users from UW-IMAP and get great performance. On our overloaded staff POP3/IMAP server, we are looking at replacing qpopper+uw-imapd with dovecot, as an interim before moving them to the main Unix mailstore. The system is

I'm hoping to migrate to dovecot from qpopper, with the eventual goal of enabling IMAP. However, my qpopper installation is fairly specialized, so I thought I'd ask here to see if anyone could get me headed down the best path. Here's the situation. I'm running FreeBSD and have a virtual domains setup with an extremely hacked LDA to do delivery to mailboxes within hashed

package logcheck-database tags 125794 pending tags 191637 pending thanks I've been running the latest version of qpopper from unstable for a few days and I've added the following rules to CVS: ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ in.qpopper\[[0-9]+\]: connect from [._[:alnum:]-]+$ ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ in.qpopper\[[0-9]+\]: \(v[.[:digit:]]+\) POP login by user

Hi All, Our test users re-download the mail they've left on the server when they switch from Qpopper to Dovecot. Qpopper includes the X-UIDL header - X-UIDL: X8V"!E)<"!58?"!"9C"! - on read messages. Any suggestions are appreciated. I've included my dovecot configuration. Thank you, Tristan --- Tristan Tristan Goguen CEO, ILAP? T: 416-250-5600 ext. 205 F:

We have an older mail server using qpopper and the mbox format which we need to update to dovecot and maildir format. I have read through the docs on migrating from mbox to maildir, as well as a few nuggets on how to migrate from qpopper to dovecot, and I was wondering if I could get some suggestions on best practices for this specific migration. Would the built in dovecot conversion plugin be a

Hi, I did some performance testing with dovecot and qpopper, if anyone is interested.. Hardware: Dual Xeon 2.8 with HT enabled (dmesg sees 4 cpu-s), 1 GB RAM, SCSI RAID 1 with 2x Maxtor Atlas 10K V disks. Software: CentOS 4.3, Qpopper 4.08 in standalone mode vs Dovecot 1.0-0_19.rc6, ext3 filesystem Mailbox format Mbox, tested Pop3 with PAM authentication My setup had 15 test users with 15

hi all, I am hoping to convert a 350K user qpopper installation using mbox to dovecot and maildir (pop3 only). many of the users "leave mail on server", and qpopper's UIDL format isn't (yet) supported by dovecot. since the UIDLs have been written by qpoppper to the existing mbox files (and will be preserved when the mboxes are converted to maildir) it would be possible to do

Hi List, what do you think is the best way to migrate (to a new maschine) round about 30000 mboxes (Qpopper) with an amount of 43Gigs data, to maildir format (Dovecot). I think there are two ways: 1. - stop services (smtp and pop3) on the old maschine - copy the mboxes to the new maschine - run a conversion script (for excample: "Perfect_maildir" http://perfectmaildir.home-dn.net/)

From: "Wolfgang Koller" <koller2@fgr.wu-wien.ac.at> Organization: University of Economics, Vienna Date: Tue, 23 Nov 1999 16:29:22 CET (+0100) MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT CC: r-bugs@biostat.ku.dk, r-help@stat.math.ethz.ch References: <153DF9230E8@fgr.wu-wien.ac.at> X-mailer: Pegasus Mail

Hi, As the "new Sieve implementation" is using a "gratefully stolen copy of deliver.c from dovecot" (i.e. a dirty code in mail-raw.c), would it be possible for the Sieve piece 1 - to be using files from dovecot directly rather than copying&changing it (which is very bad for maintenance) 2 - to be incorporated in the hg/mercurial tree of dovecot ? Thanks a lot

At the LLVM Developers' Meeting in November, I promised to work on isolating a subset of the current test suite that is useful for benchmarking. Having looked at this in more detail, most of the applications and benchmarks in the test suite are useful for benchmarking, and so I think that a better way of phrasing it is that we should construct a list of programs in the test suite that are not

Hi, I'm looking for a solution to access pop mails (sendmail in linux) securely. Most of the access would be from window clients (outlook express etc). Is there a way to encrypt the password (like ssh2) when authenticating with sendmail? Any info is greatly appereceiated. Thx. Regards, Wong.