similar to: [Pigeonhole Sieve interpreter] :create argument and lda_mailbox_autosubscribe setting

Hello I use real unix users on the mailhub and I would like to automate home directories creation for new users. I found lda_mailbox_autocreate and lda_mailbox_autosubscribe statements in 15-lda.conf file ( dovecot 2.0.11 ) which seem to be the right things for me :-) I use Postfix 2.8.1 with Dovecot LDA mailbox_command = /usr/local/libexec/dovecot/dovecot-lda All Mailboxes are located in

In the old wiki: http://wiki1.dovecot.org/LDA -m <mailbox>: Destination mailbox (default is INBOX). If the mailbox doesn't exist, it's created (unless -n is used). If message couldn't be saved to the mailbox for any reason, it's delivered to INBOX instead. -s: Subscribe to mailboxes that are automatically created (via -m parameter or fileinto Sieve action). (v1.1.3+)

Hi, Due to some reasons I've to support both dovecot 1.2 and dovecot 2.x, and I just found that the -s parameter I used to autosubscribe to sieve folders doesn't exist anymore in dovecot 2.x The problem arises because (AFAIK) in postfix's master.cf you can only specify one configuration, and I used to have this: dovecot unix - n n - - pipe

I have a plot where the values of the y axis go from a positive number to a negative number and I want the x axis to intercept at zero rather than at the bottom of the y axis, regardless of its value. Can anyone help me to do this? Thanks in advance Vivien Vivien Kent MSc Oxon PhD candidate Evolutionary Anthropology Research Group Department of Anthropology Durham University Dawson

Ok I understand more what you meant. In fact I don’t care about the pdb size, at least as a first step, so it won’t be a problem for me to have duplicated symbols. Concerning TypeIndices my plan if possible is not to generate a pdb for my jit and merge it, but instead directly extract debug info from a DwarfContext just after llvm::object::ObjectFile is emitted by the JIT engine and complete the

Ok I see.. what do you mean by “making sure to de-duplicate records as necessary” ? Le jeu. 17 janv. 2019 à 19:09, Zachary Turner <zturner at google.com> a écrit : > It's possible in theory to support incremental updates to a PDB (the file > format is designed specifically with that in mind). But this functionality > was never added to the PDB library since lld doesn't

I'm sorry but I don't think I understand the question. But if you can't produce a pdb using MSVC, it is hard to imagine that only lld can do, unless MSVC linker has a bug. On Wed, Mar 14, 2018 at 3:07 PM Vivien Millet <vivien.millet at gmail.com> wrote: > Hi, thanks for the answers, i tried to use LINK.EXE to produce a pdb, but > unfortunately, it produces an empty pdb

Hi Zachary ! If there a way to easily create a new PDBFileBuilder from an existing PDBFile or can/should I do the translation myself ? I would like to start from a builder filled with the EXE PDB data and then complete its DBI stream with the JIT module/symbols. Thanks ! Le mer. 16 janv. 2019 à 23:41, Vivien Millet <vivien.millet at gmail.com> a écrit : > Thank you Zachary ! > I

Hello, i discovered that when a sieve rule "fileinto drawer;" tries to deliver a mail into a non existent drawer, the drawer gets created. This is neat, but is there also a way to automatically subcribe to the created folder ? Regards, Oliver Eales

(Yes you are right this is my fault) Considering the string table, it only seems to contains file relative informations in every pdb I am using, and it looks correct but I will check it. I looked at the pdb.cpp code about checksums and tables, I copied some stuff and got things wrong according to cvdump, then I simplified the process of copying the table and it worked (in cvdump it finds the file

Dear All, Thanks ofr the great job so far. I have crawled the doc & web, and did not find oh to check for the presence of a folder ina? a mailbox? I know about "fileinto :create" of course, but the purpose is slightly different: I want to automate the move into a folder based on some rules but *only if* an associated folder is present (which name is based on the rule),

Sure. Along the way I’m happy to answer any specific questions you might have too even if it’s for your downstream project On Wed, Jan 16, 2019 at 1:38 PM Vivien Millet <vivien.millet at gmail.com> wrote: > I would be up to improve pdbutil but I doubt I have enough knowledge or > time to provide the complete merge feature, it would still be a very > specific kind of merge as you

Hi Lang, That would be great ! :) For now I found a hack which consist of loading a "full of NOP" DLL, use my own DllMemMgr which allocates JIT sections inside the DLL virtual space, backup the memory inside some buffers, unload the DLL, copy the buffer inside the DLL file, create the PDB, reload the DLL file which hopefully in 99% is reloaded at the same virtual address (this allow me

Hello Zachary, Sorry for replying so lately but It's been a week I'm thinking an working hard on your "dll memory buffer" idea to see if it works and give you feedbacks ! And it works pretty well until now : I shared on the list what I did : - create a .ASM file full of "int 3" instructions (to ensure that if we execute over the boundaries we instantly break. -

Hello everyone! I just released dovecot-metadata-8, which is an implementation of RFC 5464 (IMAP METADATA), allowing to add comments/annotations/metadata to folders of an email account. The major feature is that it works with Akonadi, or more specifically the Kolab backend thereof, while being dovecot-2.0 compatible. The module consists of 3 plugins, two IMAP frontends and one backend: *

Hi Vivien, I'm not familiar with Windows development, but I believe you could dump the object file to disk then run LINK.EXE to produce the PDB. Alternatively, I think LLD can also produce PDB files (Rui -- is that right?), in which case you may be able to use that. Is the aim to be able to debug JIT'd code? Which debugger do you plan to use? -- Lang. On Thu, Mar 8, 2018 at 4:23 AM,

Hi, thanks for the answers, i tried to use LINK.EXE to produce a pdb, but unfortunately, it produces an empty pdb (i have debug symbols in the dumped .obj because I can see them with PEViewer). It is probably because i have undefined symbols, which is logical because i'm dumping machine code which points to running native code. I still dont understand why LINK.EXE is not able to produce a

Well, that’s certainly possible, but improving llvm-pdbutil is another possibility. Doing it directly in your jit compiler will probably save you time though, since you won’t have to worry about writing tests and going through code review On Wed, Jan 16, 2019 at 1:01 PM Vivien Millet <vivien.millet at gmail.com> wrote: > Thanks for the tips ! > When you talk about doing all of this I

"IR" often refers to the general concept/semantics, not only the textual format in .ll files (there are 3 main forms - bitcode, textual IR, and the in-memory representation (llvm::Module, etc - constructed using IRBuilder)). A great place to start is to look at what Clang does to produce debug info - it uses IRBuilder, for instance. So you could look at how Clang uses the IRBuilder when

On Fri, Mar 9, 2018 at 7:00 PM Lang Hames <lhames at gmail.com> wrote: > Hi Vivien, > > I'm not familiar with Windows development, but I believe you could dump > the object file to disk then run LINK.EXE to produce the PDB. > Alternatively, I think LLD can also produce PDB files (Rui -- is that > right?), in which case you may be able to use that. > Yes, lld can