similar to: Setting "default_mail_env" Why is index->mailbox_path empty?

I'm having trouble getting the quota plugin to work with deliver. The quota in the database is not getting set. I am using dovecot-1.0-rc15. This server is not yet in production. Some values below are because I'm trying to test with the simplest possible case, and some because it's reading from a different database. Also, I noticed that "dovecot -n" doesn't display any

I am trying to set up dovecot under linux. (RH9 if it matters). I'm having trouble having it find the mail that is already delivered. What I would like is that mail is delivered by fetch mail to /var/spool/mail/mclay (that me) then have dovecot find it. I'm sure that I have not set the dovecot.conf file correctly. The documentation is unclear as to what "mbox" is and

On 5 Oct 2018, at 16.42, Tom Sommer <mail at tomsommer.dk <mailto:mail at tomsommer.dk>> wrote: > > On 2018-10-05 11:50, Tom Sommer wrote: >> On 2018-10-05 11:35, Timo Sirainen wrote: >>> On 4 Oct 2018, at 17.13, Tom Sommer <mail at tomsommer.dk <mailto:mail at tomsommer.dk>> wrote: >>>> On 2018-10-04 15:55, Timo Sirainen wrote:

On Mon, Feb 7, 2011 at 07:03, Robert McLay <the80sphreak at yahoo.co.uk> wrote: > > Hi Gene, > >> label cesg >> ?menu label ^CESG Software (GeneC Memdisk Hack) >> ?kernel images/memdisk-res2 >> ?append initrd=images/cesg.img mem=268435456 > > ?That worked! ?The box had 1536MB RAM and I forced it down to 256MB and > ?all is well. ?I've spent most

On Sun, Feb 6, 2011 at 07:49, Robert McLay <the80sphreak at yahoo.co.uk> wrote: > > ?Hi Gene, > > ?Not sure if you wanted this on/off list, feel free to forward to list > ?if you do. > >> Adding "int15maxres=#" will affect the memory calls that MEMDISK hooks >> into.? Specify the desired limit in bytes (ie "int15maxres=268435456" >> for

Hi, on a clustered Dovecot server installation that was recently moved from a shared GPFS filesystem to GFS2, occasional corruptions in the users' INBOXes started appearing, where a new incoming message would be appended directly after a block of NUL bytes, and be scanned by dovecot as being glued to the preceding message. I traced this to the file extension operation performed in

Program terminated with signal 6 GNU gdb (GDB) 7.0-debian Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was

==> /var/log/dovecot/dovecot.log <== Jun 9 09:58:26 spectre dovecot: lmtp: Fatal: master: service(lmtp): child 12635 killed with signal 11 (core dumped) This is another segmentation fault introduced in the current code. Please also look into fixing the other Core Dump I reported: http://www.dovecot.org/list/dovecot/2013-June/090795.html (gdb) bt full #0 0x00007f305d3df646 in

Hi- I was able to get a coredump out of the new pop3 (from 0.99.9-test4) by attempting to simulate the execution environment and simply running the pop3 program. Running the older pop3 from 0.99.8.1 works fine, repeatedly: % /usr/local/libexec/dovecot/pop3 quit +OK Logging out. However running the new one: % /usr/local/libexec/dovecot/pop3.new pop3(user9): Error: Corrupted index file

Hi. Trying to upgrade from Dovecot 1.1.11 to 1.1.13 but having a problem with imap process segfaulting. Backtrace is below. I presume it's related to these MAILBOXDIR changes but the only documentation is the single line in the news for changing to ":MAILBOXDIR=mailboxes" when using dbox. Current configuration is "mail_location = dbox:~/Mail" so what exactly should be

mbox-index.c uses a zero content length as a flag for an invalid Content-Length: header. Unfortunately zero is also a valid value for Content-Length. The patch below attempts to address the problem. *** mbox-index.h.orig Tue Apr 15 09:04:02 2003 --- mbox-index.h Sun Apr 20 11:42:12 2003 *************** *** 19,24 **** --- 19,25 ---- struct istream *input; uoff_t

I was unable to produce an IMAP core but have been successful with LMTP. Basically it crashes right upon login or delivery: Dec 20 08:55:23 nihlus dovecot: master: Dovecot v2.2.devel (9bc8d9b) starting up for imap, lmtp Dec 20 08:56:15 nihlus dovecot: imap(tlx at leuxner.net): Fatal: master: service(imap): child 5710 killed with signal 11 (core not dumped) Dec 20 08:57:23 nihlus dovecot:

Settings for mail_chroot and default_mail_env are not playing well together. It seems that default_mail_env is verified to exist *before* the chroot but is later used *after* the chroot. A configuration like this: * mail_chroot = /var/mail/example.com/username * default_mail_env = maildir:/Maildir Fails with the message: * stat(/Maildir) failed: No such file or directory As a

in the config file i have "ssl_disable = yes", however, i get this in my LOG_MAIL syslog: "Dec 17 00:21:07 host imap-master: Can't create temporary SSL parameters file /default/configured/directory/ssl-parameters.dat.tmp: No such file or directory" I know what the error is, and how to fix it, but it's an SSL thing which should have been disable according the

Hello, I am new to Dovecot and trying to setup on my Fedora Core 1 mail servers (actually migrating from uw to dovecot ;-) ). In my setup I use pam to authenticate virtual users. All the usernames include @domainname in their usernames like 'jane at somevhost.com'. Now path to user's home and INBOX includes /home/vhosts/<domainname>/home/<username>. I have added following

I'v set the default_mail_env to maildir:/var/maildir/%d/%u where /var/maildir/ is the root dorectory for my maildir tree and I'm getting the folowing error in the maillog : Jan 3 15:16:58 websrv pop3(roi): unlink(/var/maildir//roi/cur/new:2,T) failed: Is a directory Notice that the %d is missing. If I change to 'default_mail_env = maildir:/var/maildir/example.tld/%u' then

Hello all, I've a problem with maildir, pop3 and relocated indexes. My configuration is: default_mail_env = maildir:%h/Maildir:INDEX=/var/dovecot/index/% u:CONTROL=/var/dovecot/control/%u I created the "/var/dovecot/{index,control}/%u" directories, each one have rights 700 and the ownership is assigned to the user. When the pop clients connect, they fail with the error dovecot:

Hi there, I am trying to figure out hte Proper defualt_mail_env definition default_mail_env = mbox:%h/mail:INBOX=/usr/mail/%u (yes /usr/mail not /var/mail) Most users have their INBOX at /usr/mail/%u and some users have saved-folders and other mail folders in %h/mail *** right now i am unable to view my inbox. But I can view all the folders and contents of the %h/mail subdirs visible

Hi, I'm currently installing a dovecot Server to be a replacement for an uw-imapd. I dont want to touch the clients configuration, because I have too much users... Situation is the following: the mbox files are in the users homedirectory (~/MailImap), automounted via nfs In dovecot.conf I've set default_mail_env = mbox:%h/MailImap:INBOX=/var/mail/%u It works perfect without a value

Hi, First, I am new to dovecot. Before my Jan '08 meltdown, sendmail was sufficient. A friend set up dovecot and since things just-worked, I was happy with that. Now I have a new mailserver and what was installed nearly two years ago fails. My pal installed things in dovecot.conf this way: default_mail_env = maildir:~/Maildir but the new mail environment is too different to be