Anton Yuzhaninov

Other Instapaper-like service in #269

+1 It will be useful to rewrite incomplete To: and From: headers. Like done in Postfix with [local_header_rewrite_clients](http://www.postfix.org/postconf.5.html#local_header_rewrite_clients) and [append_at_myorigin](http://www.postfix.org/postconf.5.html#append_at_myorigin). Default Posfix behavior is to rewrite headers for local submitted...

MAILTO= in your crontab files is bad workaround: - it is easy to add N aliases to /etc/aliases like ``` www: root foobar: root nobody: root root: [email protected], [email protected] ```...

10.3 is oldest officially release now, so we can assume that `makefs` and `mkimg` are present on a build host.

I can confirm that is actively used in ham.

If digest still need, just add configuration option: secure password hash (bcrypt or scrypt) without digest support or hash for digest support. But I doubt that DAV without https is...

As I can see Baikal stores data in same version as the was uploaded by client without conversion. For reading requests Baikal converts all vCards to version supported by client...

When DAV server URL is changed `vdirsyncer` asks to run `vdirsyncer discover`. In this case I will expect similar behavior (but only because I know what happens after URL change)....

I prefer second option. To force convert to 4.0 user can delete local files and re-download all from CardDAV server.

As I remember with `Accept: */*` baikal will return 3.0.