search for: somedude

...e -f someone-else < /path/to/temp/email' All good, expected behavior. A perl snippet: local $/=undef; open FH, "< ./demo.mail"; my $stringified = <FH>; # this is roughly equivalent to how other LDA queues work. close FH; open (CMD_OUT, " /usr/lib/dovecot/deliver -f somedude\@someplace.com -d anotherdude\@destination.dom $stringified |"); my $test = <CMD_OUT>; print $test; The above code errors out because the expected behavior is $stringified is supposed to be a file name. It would be great if deliver could be fed the email as a string so I don't have...

I''m starting to get into using migrations, but I''m trying to figure out the best practice for prepopulating database tables. I''m talking about support tables that need to have data before the application can run. Before I just had a sql script with all the drop and create statements, and some insert statements at the bottom. I know there are a million ways to do