Paul J Stevens <[EMAIL PROTECTED]> said: > Aaron Stone wrote: >> >> The code I started to write in May (I found an old working tree with it) >> passes the entire dsnuser struct into sort_and_deliver and splits up a few >> of the loops in pipe and sort into separate functions. This is a better >> way to go longterm, because it allows us to add new fields to the dsnuser >> struct and then use them in different places in the delivery chain without >> having to change function signatures all the time. > > Sounds like best practice to me. > >> The really simple solution is to pass a default mailbox and a flag >> indication if the first mailbox should be created if not found, or if the >> fallback mailbox should be used instead (and created if not found). > > If both are encapsulated in the dsnuser, yes. > >> The subaddress could be the first mailbox, and the -m argument would be >> the fallback (-M just overwrites the subaddress). Whatever is specified in >> -m/-M would always be created if not found. > > Agree. > >> Sound like a plan? > > Since this stuff is targetted for 2.x (> 2.0) why not do the right thing
Ok, it's a plan :-) I'm going to start porting the dsnuser changes from my May tree into the current CVS. I figure this'll take one evening to code and another evening to test. Should be in CVS by this weekend. Aaron --
