similar to: maildirmake -q quota equivalent to set quota

Since I am using dovecot I do not have courier installed, but Courier had a very handy tool for making maildir folders called `maildirmake` which I used in some automated backup scripts. How do I duplicate maildirmake in dovecot? for example: #!/bin/bash # v1.2a Testing for new dovecot install # Archive mail from folders without [0-9]{4} Maildirs # after they are 21 days old to a yearly folder

Dear All, We would like to migrate our existing courier to dovecot. After reading document on website and doing some tests, here are some issues we met. 1. According the the wiki, it seems to imply that once migrating from courier to dovecot, pop3 users may "lost/forget" their download "index/ history" which cause them to download again old mails that are kept on

Does dovecot support shared folders, maildir style? I've set it up, using the maildirmake from debian maildrop to create folders. I have a number of as-yet unresolved issues, so I haven't been able to test with many clients. It's interesting that dovecot manages to present folders as siblings (rather than children) of INBOX. But mutt, at least, doesn't seem to see the shared

It is possibile to call maildirmake at login-time? My final goal is to create maildir at login time (like courier-imapd) or at least to create .INBOX.Trash, .INBOX.Drafts, .INBOX.Sent dir for virtual user /home/vmail/domains/$virtual_domain/$virtual_user/ .... with already exsistant Maildir (created by postfix) Thanks in advance

On Tue, Mar 11, 2014 at 11:08 AM, Eric PEYREMORTE <eric.peyremorte at iut-valence.fr> wrote: > Le 11/03/2014 15:27, Ady a ?crit : > >>> Le 11/03/2014 10:32, Eric PEYREMORTE a ?crit : >>> Some news here. I didn't test with 5.01 yet (didn't see that one sorry). >>> With 5.01 i don't have any problem. Problems begin with 5.10. >>> --

?Hi,? On 10 March 2014 18:13, Eric PEYREMORTE <eric.peyremorte at iut-valence.fr>wrote: > Ok i give up. I will stick with the old version version (4.07) which works > well with dell 380 and 790. > > I tried to understand what happened between 4.07 and 5 but i don't have > the skill to understand low level c. > > Seems that the memory management changed a lot, maybe

Le 11/03/2014 00:56, Gene Cumm a ?crit : > On Mon, Mar 10, 2014 at 7:55 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On Mon, Mar 10, 2014 at 7:15 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >>> On Mon, Mar 10, 2014 at 6:52 PM, Schlomo Schapiro <schlomo at schapiro.org> wrote: >>>> Hi, >>>> >>>> On 10 March 2014 18:13,

Yes on optiplex 790 i upgraded from A07 to A18 (there was a nic upgrade) but it didn't change anything.. On optiplex 380 i upgraded from bios A01 to A07(don't know if upgrade contained pxe or not)... I tried, lpxelinux.0 and it wasn't faster. Only v4.07 helped on these machines. Tomorrow, i will give a try with 6.03pre2. In wireshark, i saw no errors, the packet length was the

> Le 11/03/2014 10:32, Eric PEYREMORTE a ?crit : > Some news here. I didn't test with 5.01 yet (didn't see that one sorry). > With 5.01 i don't have any problem. Problems begin with 5.10. > -- > Eric PEYREMORTE Hello Eric: To sum up your report: _ 4.0x works; _ 4.10-pre22 (lwip branch) works; _ 5.01 (elflink branch) works; _ 5.10 (lwip merge into elflink) fails; I

On Mon, Mar 10, 2014 at 7:15 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Mon, Mar 10, 2014 at 6:52 PM, Schlomo Schapiro <schlomo at schapiro.org> wrote: >> Hi, >> >> On 10 March 2014 18:13, Eric PEYREMORTE <eric.peyremorte at iut-valence.fr>wrote: >> >>> Ok i give up. I will stick with the old version version (4.07) which works

Hello, we're operating dovecot on a small server. Some years ago, we migrated from courier IMAP to dovecot. Therefore, we defined our default Namespace "inbox" with prefix "INBOX." to have this compatible. I found this in some migration docs those days. Generally, everything worked as expected. Our only namespace is configured like this: namespace inbox { separator = .

Notice the same thing happens with optiplex 790 (core i5 sandy bridge). With 790 too everything is ok with pxelinx 4.0.7. I'll post a wireshark later. Le 25/02/2014 17:06, H. Peter Anvin a ?crit : > On 02/25/2014 07:45 AM, H. Peter Anvin wrote: >> On 02/25/2014 07:07 AM, Eric PEYREMORTE wrote: >>> I did some additional tests : >>> >>> On a dell optiplex

Hi, We only have Dell computers here. We have about 100 optiplex 380. Here is a link to download my wireshark traces : http://dl.free.fr/qgCPEM5Uo In this traces i tested pxelinux and lpxelinux 6.03 on optiplex 740(the one working) and optiplex 380. pxelinux works on both computers but very slowly on 380 as seen in traces. lpxelinux works only on 740. On 380 it seems to enter in a kind of

username GiuseppeCefaratti PostFix HOWTO par 3.3 Create users mailbox ... To setup *Maildir* mail boxes for our example user john we cano use the *?maildirmake?* command. We must do this for existing users and also in */etc/skel* so new users automatically get the same setup. To setup our *Maildir*, change directories to john home and run: maildirmake Maildir To make our sub folders run:

Just hoping to get some dev eyes on this. I'm incredibly reluctant to throw the word 'bug' around (since 99 times out of 100, it's not -- it's almost always the config), but I can't think of any way that this could be a config issue, esp when the pre-2.2.34 version works as expected. I noticed during troubleshooting that dovecot errors out if I try to create a subfolder

On 02/25/2014 07:07 AM, Eric PEYREMORTE wrote: > I did some additional tests : > > On a dell optiplex 380, i disabled internal nic, added a 3com 905c tx > external pci nic : very slow too. > On a dell 740(which is always fast), i put the 3com to be sure : very fast. > > So it seems it is not related to the nic itself. To be sure it wasn't > just one failing computer i

<div><br><div><font color="#990099">-----Timo Sirainen <tss@iki.fi> wrote: -----<br></font><blockquote><font face="monospace" size="3"><br>You can change mail_executable setting to point to some binary file<br>which calls maildirmake or does whatever, and finally execute Dovecot's<br>imap

Hi, I've just upgraded an old samba 3.0.23 on an old Fedora Core 5 to samba 3.5.4 using an rpm built from the source. Everything works fine, but when i start the server i get some error messages(see below). Before i start the server there is no connection (tested with lsof and fuser) on the 139 and 445 ports, smbd or nmbd aren't running. With the old version i never had this

Hi there ! I've read many documentation today but i can't understand samba 4 internal ldap server. I'm currently using samba3 with openldap backend. I'm considering using samba4 as my new domain controller in ADS mode. I have few questions : - Can i connect to the new ldap server from a remote machine ( ldapsearch on port 389 ) ? If no why ? - So, can i connect pam for linux

Hi! My plea to readers: =================== Pls., people who only want strictly technical issues to read, and frown at any broader context regardless how intrinsically related, but not strictly technically related, it might be, skip all the way, all the way to, search for exact words: "strictly technical" or visually, find two lines of sole "===" characters. Thank you!