similar to: POP3 notice if password expired

Displaying 20 results from an estimated 1000 matches similar to: "POP3 notice if password expired"

2006 Jun 28
4
1.0.rc1 released
I think the code is now stable enough to be called the first release candidate. Please report any bugs, new and old. The filesystem quota numbers should be correct now? http://dovecot.org/releases/dovecot-1.0.rc1.tar.gz http://dovecot.org/releases/dovecot-1.0.rc1.tar.gz.sig * PAM: If user's password is expired, give "Password expired" error message to the user. Now actually
2006 Jun 28
4
1.0.rc1 released
I think the code is now stable enough to be called the first release candidate. Please report any bugs, new and old. The filesystem quota numbers should be correct now? http://dovecot.org/releases/dovecot-1.0.rc1.tar.gz http://dovecot.org/releases/dovecot-1.0.rc1.tar.gz.sig * PAM: If user's password is expired, give "Password expired" error message to the user. Now actually
2006 Jun 18
10
1.0 RC1 status
Today I finally caught up with my mail. I've now read all the mails from the Dovecot list from this year and all my private mails from last few years (totaling around 500 unread mails). If you think there's still something I should have replied to, please re-send it because I've either missed it or just skipped it for some reason. (Except there are still a couple of mails from this
2013 Dec 12
0
[LLVMdev] Making LLVM safer in out-of-memory situations
On Dec 12, 2013, at 04:25 , Gasiunas, Vaidas <vaidas.gasiunas at sap.com> wrote: > To address these requirements we have developed a set of patches improving performance and malfunction safety of certain compiler passes and would be interested in contributing them at some point. Before proposing concrete changes, we would like to know what the general interest is with respect to making
2014 Jan 03
2
[LLVMdev] Making LLVM safer in out-of-memory situations
Hi Andy, > I would think you could use a simple allocation scheme on the host side and then allocate a single block (or perhaps one code block and one data block) in the target process to receive everything, since everything is loaded on the host before you need to copy it to the target process. But perhaps I'm missing something regarding your particular scenario. > In any event,
2005 May 15
1
Bug#191637: New rules for qpopper
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
2013 Dec 12
7
[LLVMdev] Making LLVM safer in out-of-memory situations
Hello, Philipp Becker and me, Vaidas Gasiunas, are developers at SAP and part of a team developing a C-like domain-specific language for the SAP HANA in-memory database. We use LLVM as a backend to translate our language to native code, primarily on x86-64 platforms. Our programs are created dynamically, compiled and optimized in a running database. As a result of that we have special
2005 May 30
2
Migration from pop3 to imapd
Dear list, I am planing to set up dovecot-imapd on my production-mail server which currently only runs pop3 via qpopper on debian-sarge. It would be best, if I could only use imapd and use the existing pop3- server (qpopper) as it is. Is this possible? Can the user both use pop3 (qpopper) and imapd (dovecot) in parallel then? Where does dovecot-imapd store its mails? Does it store its mail in
2013 Sep 09
1
Is dovecot locking properly?
Hello, I'm attempting to move form qpopper 4.1 to Dovecot 2.2.5 on Linux. When a user checks POP mail qpopper seems to make a .username.pop temporary file in the same /var/mail directory as the mbox INBOX file. Watching what dovecot does I don't see this happening. Is this .pop file a lock file or just a temporary file? If its a temp file does dovecot do the same thing elsewhere?
2006 Aug 18
1
dovecot vs qpopper performance testing results
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
2011 Jul 05
2
Converting from qpopper mbox to dovecot maildir
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
2005 Oct 17
1
qpoppers XUIDL
Hello, does anybody know how to make XUIDLs compatible to qpopper? I'm migrating from qpopper and one of my test-migration-accounts leaves the mail on the server. As soon as I switch to dovecot it downloads the mails again and again.. bye! Dominik
2013 Dec 13
0
[LLVMdev] Making LLVM safer in out-of-memory situations
On 12/12/13 4:25 AM, Gasiunas, Vaidas wrote: > Hello, > > Philipp Becker and me, Vaidas Gasiunas, are developers at SAP and part of a team developing a C-like domain-specific language for the SAP HANA in-memory database. We use LLVM as a backend to translate our language to native code, primarily on x86-64 platforms. Our programs are created dynamically, compiled and optimized in a
2009 Dec 21
1
qpopper to dovecot migration
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
2005 Feb 08
2
PoP3 AutoDeletion
Qpopper has a compile time option '--enable-auto-delete Automatically delete downloaded msgs' Is there anything similar in dovecot. I'm trying to migrate from qpopper to dovecot any help is appreciated.
2006 Sep 21
6
Dovecot Usage Poll
Hi all, I'm trying to get a feel for how many sites are using Dovecot and the size of the installation. Jonathan's query about big sites spurred my curiousity. I'd like to take an informal poll and will post results to the list. I'm interested in hearing from those of you who are using dovecot in a real-life/production type environment (not just testing). Please email me
2013 Dec 13
4
[LLVMdev] Making LLVM safer in out-of-memory situations
Hi Philip, Thanks for the positive response from all of you! > One question: How are you handling EOM? Error return? Custom region allocator? When running into an Out-of-memory situation we're currently only doing an error return, i.e. the compilation fails, but does so without crashing the process in which the compilation/jitting occurs. It is ok for us if llvm returns with a
2005 Sep 01
3
qpopper UIDLs and migrating to dovecot/maildir
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
2016 Feb 21
2
Dovecot Bulletin
I'd like to revisit and old post if I may, will/does Dovecot support the old qpopper "Bulletin" ability? Basically I need a simple way of posting bulletins to all domain users. Qpopper maintained a bulletin db for each user and sent them the next bulletin in sequence. Thanks in advance Kevin
2013 Dec 13
0
[LLVMdev] Making LLVM safer in out-of-memory situations
----- Original Message ----- > From: "Philipp Becker" <philipp.becker at sap.com> > To: "Philip Reames" <listmail at philipreames.com>, "LLVM Dev" <llvmdev at cs.uiuc.edu> > Sent: Friday, December 13, 2013 6:55:59 AM > Subject: Re: [LLVMdev] Making LLVM safer in out-of-memory situations > > Hi Philip, > > Thanks for the