Duply has no dedicated mailing list. Please use the trackers below. Nonetheless if you plan to use duply / duplicity on a regular basis or are already doing so you should consider to join duplicity's mailing list where the latest releases, occurring bugs and other topics around duplicity including duply are discussed.
Duply has two ticket systems on sourceforge. Before mailing the maintainer you should use these. Other users might have the same problems and might find your entry or comment helpful.
Important: Please have the kindness to check if your bug or missing feature is already in the tracker by using the search function. If so, simply add your observations to the appropriate ticket. Thank you.
Please give a short description of your issue accompanied by
- the command line that lead to the error (add -v9 for debug verbosity of duplicity in case of a python error stack)
- the complete output of your duply command
- ideally a test case that helps to reproduce the error
Important: Do not forget to obfuscate private data (passwords,usernames,hosts ...) in all data submitted.
All steps done? Well then off you go to the duply bug tracker.
You think duply is missing a feature? I guess you are right :), so go on and deliver a patch ;). You can find the latest development code to modify on the code page.
Not a developer? Well, sh*** happens. Why don't you try to become one. You should really try, because editing bash scripts is easier than you might think and will help you in your daily life on the command line.
In case you won't/can't deliver a patch I look forward to your suggestions. Any idea is a contribution that brings duply closer to perfection. Create a new feature request on the duply feature request tracker but please use the search function first to prevent duplicate entries.