search for: retrs

Hello, Dovecot log is showing too many POP3 RETR entries which are identical lines. I also suspect that it is causing high pop traffic eating most of the network bandwidth. Here are some of the lines out of 11009 in a day. Such pattern is observed only for few users. dovecot version is 2.1.17. ============== Mar 20 00:00:07 pi3 dovecot: pop3(user at example.com): Disconnected: Logged out

Hi, Looks like there's a bug while logging RETR bytes. Is this really a bug? What should I check in order make it work? /etc/dovecot.conf pop3_logout_format = top=%t/%T, retr=%r/%R, del=%d/%m, size=%s Sample log: dovecot: Apr 26 18:03:55 Info: pop3(xxxx): Logout. top=0/0, retr=1/ del=1/1, size=3556 dovecot: Apr 26 18:03:46 Info: pop3(xxxx): Logout. top=0/0, retr=4/ del=4/4, size=66191

Hi All, I'm using gluster as dispersed volume and I send to ask for very serious thing. I have 3 servers and there are 9 bricks. My volume is like below. ------------------------------------------------------ Volume Name: TEST_VOL Type: Disperse Volume ID: be52b68d-ae83-46e3-9527-0e536b867bcc Status: Started Snapshot Count: 0 Number of Bricks: 1 x (6 + 3) = 9 Transport-type: tcp Bricks:

Hello, I am very new to R, and this is certainly and uber-newby question: I am trying to read a vector of numeric data that contains the log of daily DJI returns and simply plot a histogram of it. The data I have is in a text file format, on each line a number represents the log of the returns of one day. I have problems in reading this in a vector numeric format. If I try

Hi, i've upgraded from 1.0.5 to 1.1.2 on 2 server and work fine for user that grab email on client, but some customer (that leave the email on server) have 2 problems. Some client can't read new mail: dovecot: Aug 19 11:00:46 Info: pop3-login: Login: user=<agenzia>, method=PLAIN, rip=xxx, lip=91.102.48.12 dovecot: Aug 19 11:00:46 Info: POP3(agenzia): Disconnected: Logged out

Hello, I'm getting the following error while Mozilla Mail is downloading >4000 emails: The RETR command did not succeed. Error retrieving message. Mail server xxx responded: Message is deleted. So what's the error? Can't I retrieve a message, that has been marked as deleted before? If the Mesage-ID wouldn't exist, the error message would be different. I don't know

I have recently installed new untangle firewalls ( untangle.com) in Bridge mode at two office locations. Both offices collect mail from a Fedora 9, postfix,dovecot server at location #1. Since the install of the untangles i have been plagued by Thunderbird Errors while trying to POP email. The error says "RETR" command failed. If the user logs into the webmail (Squirrelmail) on the

Starting at 05:32 this morning, one user on my dovecot server is receiving hundreds of copies of old email. This is a short excerpt from my dovecot.log showing the problem: > dovecot: Nov 03 05:27:02 Info: pop3-login: Login: > user=<howard at obfusca.ted>, method=PLAIN, rip=::ffff:81.44.31.210, > lip=::ffff:zz.zz.zz.zz, TLS > dovecot: Nov 03 05:27:02 Info: POP3(howard at

Hi, I have problems with pop3 migration, the server disconect the dovesync when fetching mails after 5 minutes with this error in server log: xx.xx.xx.xx [28F4] 11:54:05 <<< RETR 6548 xx.xx.xx.xx [28F4] 11:54:05 >>> +OK 47522 octets xx.xx.xx.xx [28F4] 11:54:05 <<< RETR 6549 xx.xx.xx.xx [28F4] 11:54:05 >>> +OK 355289 octets xx.xx.xx.xx [28F4] 11:54:05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 21 Mar 2017, Bappasaheb Nirmal wrote: > Dovecot log is showing too many POP3 RETR entries which are identical lines. > I also suspect that it is causing high pop traffic eating most of the network > bandwidth. Here are some of the lines out of 11009 in a day. Such pattern is > observed only for few users. dovecot version is

My ISP uses Dovecot and I have had an ongoing problem for a while using several email clients. Sometimes the response to a retr request is mal-formed. The expected response "+OK nnn octets" is not returned. The response looks like it started somewhere in the message headers. Sometimes a retry can clear the problem but I usually need to delete the first message via a putty session.

A Client runs a RAS network. Users access mailboxes using Outlook Express. The server runs dovecot-1.0.3-13_60. Almost a week ago users began to report that they can't retrieve their mail. The session starts, they seem to retrieve messages, but then the client reports a problem and the session is terminated. Here's what I have in the log: May 28 08:56:46 server dovecot: pop3-login:

Hi. -alpha2 broke the retr-byte-count field of the pop3_logout_format with the following change: -Added %R (reverse string) and %H (hash string) variable modifiers. %R as modifier conflicts on expand with %R as retr-byte-count in pop3_logout_format resulting in expanded strings like: top=0/0, retr=1/ del=0/1, size=431 seen in -alpha3 -alpha4 cvs as of 04.11.2005 FreeBSD 5.4-R, both i386

Since December 2014, clients using the Python poplib library (getmail in my case) started to limit the line length of RETR and other command responses sent from the server to 2048 bytes: See https://bugs.python.org/issue16041 (Included at least in Python-2.7.9) Dovecot doesn't have line split in the POP3 module, so Python fails to retrieve messages with long lines. RFC 1939 says: "

I have Dovecot 2.1.17 on Centos, all working well since yesterday one user complaining he can not retrieve emails, TBird mail client says like '1 of 9' and, doesn't go any further. that's on several of his PCs using TBird, on a LAN behind f/wall, quite physically remote to server, server in Sydney, remote client is SEAsia looking at logs I see emails access, looking at server

El vie, 10-04-2015 a las 10:21 +0900, Timo Sirainen escribi?: > On 09 Apr 2015, at 06:52, Guillermo M. Narvaja <guillermo.narvaja at fierro.com.ar> wrote: > > > > Since December 2014, clients using the Python poplib library (getmail in > > my case) started to limit the line length of RETR and other command > > responses sent from the server to 2048 bytes: >

I have two accounts where the inboxes sometimes get corrupted. In that case they begin with "FFrom". I saw similar reports in July/August last year. So I applied the patch http://dovecot.org/pipermail/dovecot/attachments/20100720/e87b32ae/attachment-0001.bin Yesterday a mbox corruption happened again. Here are the log lines. Jun 29 18:08:12 mail dovecot: pop3-login: Login:

On 09 Apr 2015, at 06:52, Guillermo M. Narvaja <guillermo.narvaja at fierro.com.ar> wrote: > > Since December 2014, clients using the Python poplib library (getmail in > my case) started to limit the line length of RETR and other command > responses sent from the server to 2048 bytes: > > See https://bugs.python.org/issue16041 (Included at least in > Python-2.7.9) >

On 10 Apr 2015, at 17:51, Guillermo M. Narvaja <guillermo.narvaja at fierro.com.ar> wrote: > > El vie, 10-04-2015 a las 10:21 +0900, Timo Sirainen escribi?: >> On 09 Apr 2015, at 06:52, Guillermo M. Narvaja <guillermo.narvaja at fierro.com.ar> wrote: >>> >>> Since December 2014, clients using the Python poplib library (getmail in >>> my case)

Dear all, Hi. This is imacat from Taiwan. We are running Dovecot 1.1.1. I received complaints from one of my colleagues. She checks her mails both from home and from office, so she left her mails in the server for 3 days. This morning she got lots of received mails again. I tracked the syslog, and found the following records: ============ Jul 2 18:39:59 odin dovecot: POP3(mindyw):