similar to: [POP3] RFC2449 conformance?

Greetings, is anybody aware of an extension to POP3 that supports UIDL ranges? It would be very useful for keep-messages-on-server setups (yes, I know, IMAP4 domain) to be able to do UIDL 21-42 to obtain just these 22 UIDs (this would always have to be a multi-line reply, just like UIDL without argument). If such a thing does not exist yet, perhaps a keyword such as "[X]UIDLRANGES" in

Hello, looks like SASL capability reported by dovecot in response to POP3 CAPA command doesn't conforms with rfc2449 which says: Examples: C: CAPA S: +OK Capability list follows S: TOP S: USER S: SASL CRAM-MD5 KERBEROS_V4 S: RESP-CODES S: LOGIN-DELAY 900 S: PIPELINING

RFC2449 defines the IN-USE extended POP3 response code as 8.1.2. The IN-USE response code This occurs on an -ERR response to an AUTH, APOP, or PASS command. It indicates the authentication was successful, but the user's maildrop is currently in use (probably by another POP3 client). http://www.faqs.org/rfcs/rfc2449.html In contrast to this, the POP3 login code in

I tried to run dovecot 1.0 built by myself but encountered the above problem. See the error traces below. First of all, the password and user are correct, as it worked with the 0.99 rpm version of dovecot. I also hand verified with ssh. I also attached the dovecot config file below. Any ideas? Jun fetchmail output on client: ------------------------------------- fetchmail: POP3< +OK

There seems to be a protocol mismatch between eudora and dovecot when using pop. The login interchange with, for example, mozilla, is as follows: MO: [connects] DC: +OK dovecot ready. MO: CAPA DC: +OK DC: CAPA DC: TOP DC: USER DC: UIDL DC: RESP-CODES DC: STLS DC: SASL PLAIN DC: . MO: USER yyy DC: +OK MO: PASS xxxxxxxx DC: +OK Logged in. But with eudora, with apparently equivalent

Hello, I have dovecot q1.0-0_22.rc7 up and running on a server: I can read email from squirrelmail just fine. When I try to download email with fetchmail, however, I get the result below. Why is that happening? In dovecot.conf I have: protocols = imap imaps pop3, so why should pop3 or imap fail? Where should I look? (I'll fix the certificates problem after I've managed to get in

Hi, a few days ago I started to get some complaints about authentication delays from Thunderbird POP3 users. After some debugging it turned out that the problem was introduced somewhere between 1.2rc3 and 1.2rc7 (1.2.0 is still affected). A session with Thunderbird 2.0.0.22 against 1.2rc3 looks like this: <<< +OK Dovecot ready. >>> CAPA <<< +OK <<< CAPA

ear All, I configured Postfix 2.3.3-2 on CentOS 5.2 using SASL Dovecot authentication put I am facing the problem to receive mails . My postconf -n result is: [root at mails ~]# postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix debug_peer_level = 2

Hi, today I've finished migration from uw-imap daemons to shiny and fast dovecot. With thanks of dovecot my mail server load average drops by factor of ten even with ancient unix mailboxes. ;-) So, the only thing I've discovered is what POP3 uidls are different than ones used in the uw-imap. Luckily, the difference are only in the format string used in uidl response. So, I've

Hi, While investigating the problem with Thunderbird auths I found the following happening: Escape character is '^]'. +OK Dovecot ready. CAPA +OK CAPA TOP USER UIDL RESP-CODES PIPELINING SASL PLAIN . AUTH PLAIN + + + -ERR Authentication failed. This is what is happening during a Thunderbird connection, when each '+' happens dovecot does an sql query on the sql server for user

# HG changeset patch # User Matthias Andree <matthias.andree at gmx.de> # Date 1246993296 -7200 # Branch HEAD # Node ID c884491cb1a61ef50e227fcf4bb77d2e449c1e3a # Parent dff7312629a72f6ee90ab470ad0d50dfa68e6f71 Fix VPATH build of RQUOTA support. Some rpcgen derive #include "..." paths from the infile argument. This will be off for VPATH builds, as the generated rquota_xdr.c code

Hi, I'm trying to set up dovecot to do pop3 from Eudora, but it keeps breaking on authentication attempts using plain auth. When I snoop the connection with tcpflow, here's what I see: 128.174.246.068.00110-062.107.004.050.49653: +OK dovecot ready. 128.174.246.068.00110-062.107.004.050.49653: +OK dovecot ready. 128.174.246.068.00110-062.107.004.050.49653:

From nmap: 995/tcp open ssl/pop3 Dovecot pop3d |_ sslv2: server still supports SSLv2 |_ pop3-capabilities: USER CAPA UIDL PIPELINING RESP-CODES TOP SASL(PLAIN LOGIN) pop3 allows SSLv2, imap doesn't. In my dovecot.conf I have: ssl_cipher_list = ALL:!LOW:!SSLv2 at the global level. Do I need to put it inside the protocol pop3{} section? Patrick

Dear all I am currently setting up a Samba server and am experiencing a bit of a problem with printing: I have a Canon LBP-1000 connected to the Samba server via the parallel port. Printing directly from the machine works fine. Printing to the printer directly attached to my W2K client works fine, too. When I try to print from the W2K client to the printer connected to the Samba server, however,

Hello, I am in the process of migrating a hosting setup from UW-IMAP to Dovecot. The protocols available to mail clients are IMAP and POP3 both before and after migration. I also wanted to change the mail storage format from MBOX to Maildir. However, at this point I hit a major snag with Dovecot and POP3 UIDL (unique identification listing for POP3 mailboxes). Several of the customers connecting

Hi, I'm trying to migrate from maildir to mdbox while preserving the pop3 UIDL (and the imap UID). The problem is, for maildir we use (for compatiblity with qpopper): pop3_uidl_format = %f Problem is, as soon as I convert that to mdbox, then whenever a client issues the UIDL command via a POP connection, the connection is closed and this error is displayed in the log: Error: UIDL: File

Hi all, attached is a patch against 0.99.10.4 that fixes the STAT, LIST and UIDL POP3 command output in the case that they're issued after one or more messages have been deleted. Examples of incorrect behavior (bad spots marked with '***') C: STAT S: +OK 2 806 C: LIST S: +OK 2 messages: S: 1 403 S: 2 403 S: . C: UIDL S: +OK S: 1 1076749908.12

Hi, We're upgrading a cluster of servers from v1.0.15 to v1.1.x or v1.2.x. It appears that the UIDL generation mechanism has changed, and thus we'll be getting POP3 dups with users that leave mail on server (which is a nasty practice, I know). From checking the sources, and performing a number of controlled tests in various scenarios, here is the outcome: upgrade from 1.0.15 to

Hi, I have only recently become aware of Dovecot and gave it a try. The previous 0.99.9.1 version didn't work well for me (OpenSSL), I dropped it, but 0.99.10 has come just in time (saw it on freshmeat) and I thought I'd give it another try if it promised SSL fixes, and it's sorta working for me (i. e. it works with mutt, Mozilla, sylpheed, but not cone -- but cone is beta and has SSL

Hi there, I've just been experimenting with the latest courier-dovecot-migrate.pl script and I notice that it favours keeping pop3 UIDL ordering rather than IMAP UID preservation. There is this comment (line 312): # POP3 clients may want to get POP3 UIDLs in the same order always. # Preserve the order even if it causes IMAP UIDs to change. Does anyone have details as to which