text:
Auto saves mess double saving panes and so restore is messed up?!

I'm not really sure where the bug lies :( Since I use tmux-continuum with conjunction of tmux-resurrect my apps not restored. What I see is that there are panes more than one time after a continuum save, probably this is the error for not restoring apps anymore.
Here is an example. Saved lines for a session with manual resurrect save:
pane	mopidy	0	:ncmpcpp	1	:*	0	:/home/hoschi	1	ncmpcpp	:ncmpcpp
pane	mopidy	1	:zsh	0	:-	0	:/home/hoschi	1	zsh	:

And here the lines after continuum save:
pane	mopidy	0	:ncmpcpp	1	:*	0	:/home/hoschi	1	ncmpcpp	:ncmpcpp
pane	issues_work	1	:bash	1	:*	0	:/home/hoschi/repos/sweetp-code/services/github-issues	1	zsh	:
pane	mopidy	0	:ncmpcpp	1	:*	0	:/home/hoschi	1	ncmpcpp	:ncmpcpp
pane	mopidy	1	:zsh	0	:-	0	:/home/hoschi	1	zsh	:
pane	mopidy	0	:ncmpcpp	1	:*	0	:/home/hoschi	1	ncmpcpp	:ncmpcpp
pane	mopidy	1	:zsh	0	:-	0	:/home/hoschi	1	zsh	:
pane	notes	0	:mkd	1	:*	0	:/home/hoschi/Dropbox/notes	1	vim	:vim blog.md breeze-js.md
pane	mopidy	1	:zsh	0	:-	0	:/home/hoschi	1	zsh	:

Here are the attatched files:
manual save:
pane	1	0	:zsh	1	:*	0	:/home/hoschi	1	zsh	:
pane	activity	0	:zsh	1	:*	0	:/home/hoschi	1	zsh	:
pane	atom	0	:zsh	0	:-	0	:/home/hoschi/repos/html-tab	1	zsh	:
pane	atom	1	:zsh	1	:*	0	:/home/hoschi/repos/html-view-test	1	zsh	:
pane	base-node-service	0	:vim	1	:*	0	:/home/hoschi/repos/sweetp-code/services/base-nodejs	1	zsh	:
pane	base-node-service	1	:zsh	0	:-	0	:/home/hoschi/repos/sweetp-code/services/base-nodejs	1	zsh	:
pane	data	0	:badblocks	1	:*	0	:	1	badblocks	:sudo zsh
pane	git-sevice	0	:zsh	0	:-	0	:/home/hoschi/repos/sweetp-code/services/git	1	zsh	:
pane	git-sevice	1	:build	1	:*	0	:/home/hoschi/repos/sweetp-code/services/git	1	zsh	:
pane	git-sevice	2	:test	0	: 	0	:/home/hoschi/repos/sweetp-code/sandbox/testgit	1	zsh	:
pane	github-service	0	:vim	0	:-	0	:/home/hoschi/repos/sweetp-code/services/github-issues	1	zsh	:
pane	github-service	1	:git	1	:*	0	:/home/hoschi/repos/sweetp-code/services/github-issues	1	zsh	:
pane	github-service2	0	:bash	1	:*	0	:/home/hoschi/repos/sweetp-code/services/github-issues	1	zsh	:
pane	grf	0	:mc	0	: 	0	:/home/hoschi/repos/grf	1	zsh	:
pane	grf	0	:mc	0	: 	1	:/home/hoschi/repos/grf	0	zsh	:
pane	grf	1	:vim	0	: 	0	:/home/hoschi/repos/grf/plugin-grf/web-app/frontend	1	zsh	:
pane	grf	1	:vim	0	: 	1	:/home/hoschi/repos/grf/plugin-grf/web-app/frontend/resources	0	zsh	:
pane	grf	2	:work	1	:*	0	:/home/hoschi/repos/grf	0	zsh	:
pane	grf	2	:work	1	:*	1	:/home/hoschi/repos/grf	1	zsh	:
pane	grf	2	:work	1	:*	2	:/home/hoschi/repos/grf	0	zsh	:
pane	grf	3	:et-vim	0	: 	0	:/home/hoschi/repos/et-core	1	zsh	:
pane	grf	3	:et-vim	0	: 	1	:/home/hoschi/repos/et-core	0	zsh	:
pane	grf	4	:et-work	0	: 	0	:/home/hoschi/repos/et-core	1	zsh	:
pane	grf	5	:sass	0	: 	0	:/home/hoschi/repos/grf/plugin-multichannel/web-app	1	zsh	:
pane	grf	6	:stuff	0	:-	0	:/home/hoschi/repos/grf	0	zsh	:
pane	grf	6	:stuff	0	:-	1	:/home/hoschi/repos/grf	1	zsh	:
pane	issues_vim	0	:vim	1	:*	0	:/home/hoschi/repos/sweetp-code/services/github-issues	1	zsh	:
pane	issues_vim	0	:vim	1	:*	1	:/home/hoschi/repos/sweetp-code/services/github-issues	0	zsh	:
pane	issues_vim	1	:zsh	0	:-	0	:/home/hoschi/repos/sweetp-code/services/github-issues	1	zsh	:
pane	issues_work	0	:zsh	0	:-	0	:/home/hoschi/repos/sweetp-code/services/github-issues/sweetptest	1	zsh	:
pane	issues_work	1	:bash	1	:*	0	:/home/hoschi/repos/sweetp-code/services/github-issues	1	zsh	:
pane	mopidy	0	:ncmpcpp	1	:*	0	:/home/hoschi	1	ncmpcpp	:ncmpcpp
pane	mopidy	1	:zsh	0	:-	0	:/home/hoschi	1	zsh	:
pane	notes	0	:mkd	1	:*	0	:/home/hoschi/Dropbox/notes	1	vim	:vim blog.md breeze-js.md
pane	notes	1	:AA	0	:-	0	:/home/hoschi/Dropbox/notes	1	vim	:vim /home/hoschi/foo.md
pane	password-mngr	0	:vim	0	:-	0	:/home/hoschi/repos/sweetp-code/services/password-manager	1	zsh	:
pane	password-mngr	1	:git	1	:*	0	:/home/hoschi/bin/sweetp-project/server	1	zsh	:
pane	project-context-manager_second	0	:grunt	1	:*	0	:/home/hoschi/repos/sweetp-code/services/project-context-manager	1	zsh	:
pane	project-context-manager_second	1	:zsh	0	:-	0	:/home/hoschi/repos/sweetp-code/services/project-context-manager	1	zsh	:
pane	project-context-manager_vim	0	:vim	1	:*	0	:/home/hoschi/repos/sweetp-code/services/project-context-manager	1	zsh	:
pane	project-context-manager_vim	1	:git	0	:-	0	:/home/hoschi/repos/sweetp-code/services/project-context-manager	1	zsh	:
pane	serien	0	:desktop	1	:*	0	:/home/hoschi	1	zsh	:
pane	serien	0	:desktop	1	:*	1	:/home/hoschi	0	zsh	:
pane	startup	0	:zsh	1	:*	0	:/home/hoschi	1	zsh	:
pane	sw-dashboard	0	:vim	0	: 	0	:/home/hoschi/repos/sweetp-code/dashboard	1	zsh	:
pane	sw-dashboard	0	:vim	0	: 	1	:/home/hoschi/repos/sweetp-code/dashboard	0	zsh	:
pane	sw-dashboard	1	:work	1	:*	0	:/home/hoschi/repos/sweetp-code/dashboard	0	zsh	:
pane	sw-dashboard	1	:work	1	:*	1	:/home/hoschi/repos/sweetp-code/dashboard	1	zsh	:
pane	sw-dashboard	1	:work	1	:*	2	:/home/hoschi/repos/sweetp-code/dashboard	0	zsh	:
pane	sw-dashboard	2	:stable	0	:-	0	:/home/hoschi/repos/sweetp-code/dashboard-stable	1	zsh	:
pane	sw-main	0	:git	0	: 	0	:/home/hoschi/repos/sweetp-code/main	1	zsh	:
pane	sw-main	1	:build	0	: 	0	:/home/hoschi/repos/sweetp-code/main	0	zsh	:
pane	sw-main	1	:build	0	: 	1	:/home/hoschi/repos/sweetp-code/main	1	zsh	:
pane	sw-main	2	:dev-server	1	:*	0	:/home/hoschi/repos/sweetp-code/dev-server/server	1	zsh	:
pane	sw-main	2	:dev-server	1	:*	1	:/home/hoschi/repos/sweetp-code/dev-server/server	0	zsh	:
pane	sw-main	3	:test	0	:-	0	:/home/hoschi/repos/sweetp-code/dashboard	1	zsh	:
pane	sys-update	0	:zsh	1	:*	0	:/home/hoschi	1	zsh	:
pane	test-sw-dashboard	0	:zsh	1	:*	0	:/home/hoschi/repos/sweetp-code/dashboard	0	zsh	:
pane	test-sw-dashboard	0	:zsh	1	:*	1	:/home/hoschi/repos/sweetp-code/dashboard	0	zsh	:
pane	test-sw-dashboard	0	:zsh	1	:*	2	:/home/hoschi/repos/sweetp-code/dashboard	1	zsh	:
pane	tmux-conf	0	:vim	0	: 	0	:/home/hoschi	1	zsh	:
pane	tmux-conf	1	:man	0	: 	0	:/usr/share/man	1	zsh	:
pane	tmux-conf	2	:git	0	:-	0	:/home/hoschi/dotfiles	1	zsh	:
pane	tmux-conf	3	:zsh	1	:*	0	:/home/hoschi/.tmux/resurrect	1	zsh	:
pane	vim_config	0	:vimrc	0	: 	0	:/home/hoschi/dotfiles/.vim	1	zsh	:
pane	vim_config	1	:plugins	0	:-	0	:/home/hoschi/dotfiles/.vim/bundle	1	zsh	:
pane	vim_config	2	:my-snippets	1	:*	0	:/home/hoschi/dotfiles/.vim/mysnippets	1	zsh	:
pane	weechat	0	:WeeChat 1.1.1	1	:*	0	:/home/hoschi	1	weechat	:weechat
pane	workflow-service	0	:vim	1	:*	0	:/home/hoschi/repos/sweetp-code/services/project-workflow	1	zsh	:
pane	workflow-service	1	:zsh	0	:-	0	:/home/hoschi/repos/sweetp-code/services/project-workflow	1	zsh	:
pane	workflow-service2	0	:bash	1	:*	0	:/home/hoschi/repos/sweetp-code/services/project-workflow	1	zsh	:
window	1	0	1	:*	c97e,376x75,0,0,1
window	activity	0	1	:*	c97f,376x75,0,0,2
window	atom	0	0	:-	c980,376x75,0,0,3
window	atom	1	1	:*	c981,376x75,0,0,4
window	base-node-service	0	1	:*	c982,376x75,0,0,5
window	base-node-service	1	0	:-	c983,376x75,0,0,6
window	data	0	1	:*	5b87,227x23,0,0,75
window	git-sevice	0	0	:-	c984,376x75,0,0,7
window	git-sevice	1	1	:*	c985,376x75,0,0,8
window	git-sevice	2	0	: 	c986,376x75,0,0,9
window	github-service	0	0	:-	64ef,376x75,0,0,10
window	github-service	1	1	:*	64f0,376x75,0,0,11
window	github-service2	0	1	:*	64f1,376x75,0,0,12
window	grf	0	0	: 	5612,376x75,0,0[376x28,0,0,13,376x46,0,29,14]
window	grf	1	0	: 	5ed5,376x75,0,0[376x38,0,0,15,376x36,0,39,16]
window	grf	2	1	:*	0c97,376x75,0,0[376x39,0,0,17,376x35,0,40{188x35,0,40,18,187x35,189,40,19}]
window	grf	3	0	: 	7bce,376x75,0,0[376x36,0,0,20,376x38,0,37,21]
window	grf	4	0	: 	e4f1,376x75,0,0,22
window	grf	5	0	: 	e4f2,376x75,0,0,23
window	grf	6	0	:-	5cd4,376x75,0,0[376x44,0,0,24,376x30,0,45,25]
window	issues_vim	0	1	:*	9617,376x75,0,0[376x28,0,0,26,376x46,0,29,27]
window	issues_vim	1	0	:-	e4f7,376x75,0,0,28
window	issues_work	0	0	:-	e4f8,376x75,0,0,29
window	issues_work	1	1	:*	64f0,376x75,0,0,30
window	mopidy	0	1	:*	5cb8,181x62,0,0,38
window	mopidy	1	0	:-	5cb9,181x62,0,0,77
window	notes	0	1	:*	6479,146x75,0,0,39
window	notes	1	0	:-	e470,146x75,0,0,40
window	password-mngr	0	0	:-	e4f1,376x75,0,0,41
window	password-mngr	1	1	:*	e4f2,376x75,0,0,42
window	project-context-manager_second	0	1	:*	e4f3,376x75,0,0,43
window	project-context-manager_second	1	0	:-	e4f4,376x75,0,0,44
window	project-context-manager_vim	0	1	:*	e4f5,376x75,0,0,45
window	project-context-manager_vim	1	0	:-	e4f6,376x75,0,0,46
window	serien	0	1	:*	16da,376x75,0,0[376x40,0,0,47,376x34,0,41,48]
window	startup	0	1	:*	c97d,376x75,0,0,0
window	sw-dashboard	0	0	: 	d618,376x75,0,0[376x28,0,0,49,376x46,0,29,50]
window	sw-dashboard	1	1	:*	d342,376x75,0,0{214x75,0,0,51,161x75,215,0[161x39,215,0,52,161x35,215,40,53]}
window	sw-dashboard	2	0	:-	64f5,376x75,0,0,54
window	sw-main	0	0	: 	64f6,376x75,0,0,55
window	sw-main	1	0	: 	ded1,376x75,0,0[376x38,0,0,56,376x36,0,39,57]
window	sw-main	2	1	:*	2777,376x75,0,0{209x75,0,0,58,166x75,210,0,59}
window	sw-main	3	0	:-	e4f1,376x75,0,0,60
window	sys-update	0	1	:*	e4f2,376x75,0,0,61
window	test-sw-dashboard	0	1	:*	357a,376x75,0,0[376x20,0,0,62,376x19,0,21,63,376x34,0,41,64]
window	tmux-conf	0	0	: 	e636,145x76,0,0,65
window	tmux-conf	1	0	: 	e637,145x76,0,0,66
window	tmux-conf	2	0	:-	e638,145x76,0,0,67
window	tmux-conf	3	1	:*	663b,145x76,0,0,79
window	vim_config	0	0	: 	e4f9,376x75,0,0,68
window	vim_config	1	0	:-	e4fa,376x75,0,0,69
window	vim_config	2	1	:*	64f2,376x75,0,0,70
window	weechat	0	1	:*	64b3,109x75,0,0,71
window	workflow-service	0	1	:*	64f4,376x75,0,0,72
window	workflow-service	1	0	:-	64f5,376x75,0,0,73
window	workflow-service2	0	1	:*	64f6,376x75,0,0,74
state	tmux-conf

continuum save:
pane	1	0	:zsh	1	:*	0	:/home/hoschi	1	zsh	:
pane	1	0	:zsh	1	:*	0	:/home/hoschi	1	zsh	:
pane	1	0	:zsh	1	:*	0	:/home/hoschi	1	zsh	:
pane	activity	0	:zsh	1	:*	0	:/home/hoschi	1	zsh	:
pane	activity	0	:zsh	1	:*	0	:/home/hoschi	1	zsh	:
pane	activity	0	:zsh	1	:*	0	:/home/hoschi	1	zsh	:
pane	atom	0	:zsh	0	:-	0	:/home/hoschi/repos/html-tab	1	zsh	:
pane	atom	0	:zsh	0	:-	0	:/home/hoschi/repos/html-tab	1	zsh	:
pane	atom	0	:zsh	0	:-	0	:/home/hoschi/repos/html-tab	1	zsh	:
pane	atom	1	:zsh	1	:*	0	:/home/hoschi/repos/html-view-test	1	zsh	:
pane	atom	1	:zsh	1	:*	0	:/home/hoschi/repos/html-view-test	1	zsh	:
pane	atom	1	:zsh	1	:*	0	:/home/hoschi/repos/html-view-test	1	zsh	:
pane	base-node-service	0	:vim	1	:*	0	:/home/hoschi/repos/sweetp-code/services/base-nodejs	1	zsh	:
pane	base-node-service	0	:vim	1	:*	0	:/home/hoschi/repos/sweetp-code/services/base-nodejs	1	zsh	:
pane	base-node-service	0	:vim	1	:*	0	:/home/hoschi/repos/sweetp-code/services/base-nodejs	1	zsh	:
pane	base-node-service	1	:zsh	0	:-	0	:/home/hoschi/repos/sweetp-code/services/base-nodejs	1	zsh	:
pane	base-node-service	1	:zsh	0	:-	0	:/home/hoschi/repos/sweetp-code/services/base-nodejs	1	zsh	:
pane	base-node-service	1	:zsh	0	:-	0	:/home/hoschi/repos/sweetp-code/services/base-nodejs	1	zsh	:
pane	data	0	:badblocks	1	:*	0	:	1	badblocks	:sudo zsh
pane	data	0	:badblocks	1	:*	0	:	1	badblocks	:sudo zsh
pane	data	0	:badblocks	1	:*	0	:	1	badblocks	:sudo zsh
pane	git-sevice	0	:zsh	0	:-	0	:/home/hoschi/repos/sweetp-code/services/git	1	zsh	:
pane	git-sevice	0	:zsh	0	:-	0	:/home/hoschi/repos/sweetp-code/services/git	1	zsh	:
pane	git-sevice	0	:zsh	0	:-	0	:/home/hoschi/repos/sweetp-code/services/git	1	zsh	:
pane	git-sevice	1	:build	1	:*	0	:/home/hoschi/repos/sweetp-code/services/git	1	zsh	:
pane	git-sevice	1	:build	1	:*	0	:/home/hoschi/repos/sweetp-code/services/git	1	zsh	:
pane	git-sevice	1	:build	1	:*	0	:/home/hoschi/repos/sweetp-code/services/git	1	zsh	:
pane	git-sevice	2	:test	0	: 	0	:/home/hoschi/repos/sweetp-code/sandbox/testgit	1	zsh	:
pane	git-sevice	2	:test	0	: 	0	:/home/hoschi/repos/sweetp-code/sandbox/testgit	1	zsh	:
pane	github-service	0	:vim	0	:-	0	:/home/hoschi/repos/sweetp-code/services/github-issues	1	zsh	:
pane	git-sevice	2	:test	0	: 	0	:/home/hoschi/repos/sweetp-code/sandbox/testgit	1	zsh	:
pane	github-service	0	:vim	0	:-	0	:/home/hoschi/repos/sweetp-code/services/github-issues	1	zsh	:
pane	github-service	0	:vim	0	:-	0	:/home/hoschi/repos/sweetp-code/services/github-issues	1	zsh	:
pane	github-service	1	:git	1	:*	0	:/home/hoschi/repos/sweetp-code/services/github-issues	1	zsh	:
pane	github-service	1	:git	1	:*	0	:/home/hoschi/repos/sweetp-code/services/github-issues	1	zsh	:
pane	github-service	1	:git	1	:*	0	:/home/hoschi/repos/sweetp-code/services/github-issues	1	zsh	:
pane	github-service2	0	:bash	1	:*	0	:/home/hoschi/repos/sweetp-code/services/github-issues	1	zsh	:
pane	github-service2	0	:bash	1	:*	0	:/home/hoschi/repos/sweetp-code/services/github-issues	1	zsh	:
pane	grf	0	:mc	0	: 	0	:/home/hoschi/repos/grf	1	zsh	:
pane	github-service2	0	:bash	1	:*	0	:/home/hoschi/repos/sweetp-code/services/github-issues	1	zsh	:
pane	grf	0	:mc	0	: 	0	:/home/hoschi/repos/grf	1	zsh	:
pane	grf	0	:mc	0	: 	0	:/home/hoschi/repos/grf	1	zsh	:
pane	grf	0	:mc	0	: 	1	:/home/hoschi/repos/grf	0	zsh	:
pane	grf	0	:mc	0	: 	1	:/home/hoschi/repos/grf	0	zsh	:
pane	grf	1	:vim	0	: 	0	:/home/hoschi/repos/grf/plugin-grf/web-app/frontend	1	zsh	:
pane	grf	0	:mc	0	: 	1	:/home/hoschi/repos/grf	0	zsh	:
pane	grf	1	:vim	0	: 	0	:/home/hoschi/repos/grf/plugin-grf/web-app/frontend	1	zsh	:
pane	grf	1	:vim	0	: 	0	:/home/hoschi/repos/grf/plugin-grf/web-app/frontend	1	zsh	:
pane	grf	1	:vim	0	: 	1	:/home/hoschi/repos/grf/plugin-grf/web-app/frontend/resources	0	zsh	:
pane	grf	1	:vim	0	: 	1	:/home/hoschi/repos/grf/plugin-grf/web-app/frontend/resources	0	zsh	:
pane	grf	1	:vim	0	: 	1	:/home/hoschi/repos/grf/plugin-grf/web-app/frontend/resources	0	zsh	:
pane	grf	2	:work	1	:*	0	:/home/hoschi/repos/grf	0	zsh	:
pane	grf	2	:work	1	:*	0	:/home/hoschi/repos/grf	0	zsh	:
pane	grf	2	:work	1	:*	0	:/home/hoschi/repos/grf	0	zsh	:
pane	grf	2	:work	1	:*	1	:/home/hoschi/repos/grf	1	zsh	:
pane	grf	2	:work	1	:*	1	:/home/hoschi/repos/grf	1	zsh	:
pane	grf	2	:work	1	:*	2	:/home/hoschi/repos/grf	0	zsh	:
pane	grf	2	:work	1	:*	1	:/home/hoschi/repos/grf	1	zsh	:
pane	grf	2	:work	1	:*	2	:/home/hoschi/repos/grf	0	zsh	:
pane	grf	2	:work	1	:*	2	:/home/hoschi/repos/grf	0	zsh	:
pane	grf	3	:et-vim	0	: 	0	:/home/hoschi/repos/et-core	1	zsh	:
pane	grf	3	:et-vim	0	: 	0	:/home/hoschi/repos/et-core	1	zsh	:
pane	grf	3	:et-vim	0	: 	1	:/home/hoschi/repos/et-core	0	zsh	:
pane	grf	3	:et-vim	0	: 	0	:/home/hoschi/repos/et-core	1	zsh	:
pane	grf	3	:et-vim	0	: 	1	:/home/hoschi/repos/et-core	0	zsh	:
pane	grf	4	:et-work	0	: 	0	:/home/hoschi/repos/et-core	1	zsh	:
pane	grf	3	:et-vim	0	: 	1	:/home/hoschi/repos/et-core	0	zsh	:
pane	grf	4	:et-work	0	: 	0	:/home/hoschi/repos/et-core	1	zsh	:
pane	grf	4	:et-work	0	: 	0	:/home/hoschi/repos/et-core	1	zsh	:
pane	grf	5	:sass	0	: 	0	:/home/hoschi/repos/grf/plugin-multichannel/web-app	1	zsh	:
pane	grf	5	:sass	0	: 	0	:/home/hoschi/repos/grf/plugin-multichannel/web-app	1	zsh	:
pane	grf	5	:sass	0	: 	0	:/home/hoschi/repos/grf/plugin-multichannel/web-app	1	zsh	:
pane	grf	6	:stuff	0	:-	0	:/home/hoschi/repos/grf	0	zsh	:
pane	grf	6	:stuff	0	:-	0	:/home/hoschi/repos/grf	0	zsh	:
pane	grf	6	:stuff	0	:-	0	:/home/hoschi/repos/grf	0	zsh	:
pane	grf	6	:stuff	0	:-	1	:/home/hoschi/repos/grf	1	zsh	:
pane	grf	6	:stuff	0	:-	1	:/home/hoschi/repos/grf	1	zsh	:
pane	issues_vim	0	:vim	1	:*	0	:/home/hoschi/repos/sweetp-code/services/github-issues	1	zsh	:
pane	grf	6	:stuff	0	:-	1	:/home/hoschi/repos/grf	1	zsh	:
pane	issues_vim	0	:vim	1	:*	0	:/home/hoschi/repos/sweetp-code/services/github-issues	1	zsh	:
pane	issues_vim	0	:vim	1	:*	1	:/home/hoschi/repos/sweetp-code/services/github-issues	0	zsh	:
pane	issues_vim	0	:vim	1	:*	0	:/home/hoschi/repos/sweetp-code/services/github-issues	1	zsh	:
pane	issues_vim	0	:vim	1	:*	1	:/home/hoschi/repos/sweetp-code/services/github-issues	0	zsh	:
pane	issues_vim	1	:zsh	0	:-	0	:/home/hoschi/repos/sweetp-code/services/github-issues	1	zsh	:
pane	issues_vim	0	:vim	1	:*	1	:/home/hoschi/repos/sweetp-code/services/github-issues	0	zsh	:
pane	issues_vim	1	:zsh	0	:-	0	:/home/hoschi/repos/sweetp-code/services/github-issues	1	zsh	:
pane	issues_work	0	:zsh	0	:-	0	:/home/hoschi/repos/sweetp-code/services/github-issues/sweetptest	1	zsh	:
pane	issues_vim	1	:zsh	0	:-	0	:/home/hoschi/repos/sweetp-code/services/github-issues	1	zsh	:
pane	issues_work	0	:zsh	0	:-	0	:/home/hoschi/repos/sweetp-code/services/github-issues/sweetptest	1	zsh	:
pane	issues_work	1	:bash	1	:*	0	:/home/hoschi/repos/sweetp-code/services/github-issues	1	zsh	:
pane	issues_work	0	:zsh	0	:-	0	:/home/hoschi/repos/sweetp-code/services/github-issues/sweetptest	1	zsh	:
pane	issues_work	1	:bash	1	:*	0	:/home/hoschi/repos/sweetp-code/services/github-issues	1	zsh	:
pane	mopidy	0	:ncmpcpp	1	:*	0	:/home/hoschi	1	ncmpcpp	:ncmpcpp
pane	issues_work	1	:bash	1	:*	0	:/home/hoschi/repos/sweetp-code/services/github-issues	1	zsh	:
pane	mopidy	0	:ncmpcpp	1	:*	0	:/home/hoschi	1	ncmpcpp	:ncmpcpp
pane	mopidy	1	:zsh	0	:-	0	:/home/hoschi	1	zsh	:
pane	mopidy	0	:ncmpcpp	1	:*	0	:/home/hoschi	1	ncmpcpp	:ncmpcpp
pane	mopidy	1	:zsh	0	:-	0	:/home/hoschi	1	zsh	:
pane	notes	0	:mkd	1	:*	0	:/home/hoschi/Dropbox/notes	1	vim	:vim blog.md
pane	mopidy	1	:zsh	0	:-	0	:/home/hoschi	1	zsh	:
pane	notes	0	:mkd	1	:*	0	:/home/hoschi/Dropbox/notes	1	vim	:vim blog.md
pane	notes	1	:AA	0	:-	0	:/home/hoschi/Dropbox/notes	1	vim	:vim /home/hoschi/foo.md
pane	notes	1	:AA	0	:-	0	:/home/hoschi/Dropbox/notes	1	vim	:vim /home/hoschi/foo.md
pane	notes	0	:mkd	1	:*	0	:/home/hoschi/Dropbox/notes	1	vim	:vim blog.md
pane	password-mngr	0	:vim	0	:-	0	:/home/hoschi/repos/sweetp-code/services/password-manager	1	zsh	:
pane	password-mngr	0	:vim	0	:-	0	:/home/hoschi/repos/sweetp-code/services/password-manager	1	zsh	:
pane	notes	1	:AA	0	:-	0	:/home/hoschi/Dropbox/notes	1	vim	:vim /home/hoschi/Dropbox/foo.md
pane	password-mngr	1	:git	1	:*	0	:/home/hoschi/bin/sweetp-project/server	1	zsh	:
pane	password-mngr	1	:git	1	:*	0	:/home/hoschi/bin/sweetp-project/server	1	zsh	:
pane	password-mngr	0	:vim	0	:-	0	:/home/hoschi/repos/sweetp-code/services/password-manager	1	zsh	:
pane	project-context-manager_second	0	:grunt	1	:*	0	:/home/hoschi/repos/sweetp-code/services/project-context-manager	1	zsh	:
pane	project-context-manager_second	0	:grunt	1	:*	0	:/home/hoschi/repos/sweetp-code/services/project-context-manager	1	zsh	:
pane	password-mngr	1	:git	1	:*	0	:/home/hoschi/bin/sweetp-project/server	1	zsh	:
pane	project-context-manager_second	1	:zsh	0	:-	0	:/home/hoschi/repos/sweetp-code/services/project-context-manager	1	zsh	:
pane	project-context-manager_second	1	:zsh	0	:-	0	:/home/hoschi/repos/sweetp-code/services/project-context-manager	1	zsh	:
pane	project-context-manager_second	0	:grunt	1	:*	0	:/home/hoschi/repos/sweetp-code/services/project-context-manager	1	zsh	:
pane	project-context-manager_vim	0	:vim	1	:*	0	:/home/hoschi/repos/sweetp-code/services/project-context-manager	1	zsh	:
pane	project-context-manager_vim	0	:vim	1	:*	0	:/home/hoschi/repos/sweetp-code/services/project-context-manager	1	zsh	:
pane	project-context-manager_second	1	:zsh	0	:-	0	:/home/hoschi/repos/sweetp-code/services/project-context-manager	1	zsh	:
pane	project-context-manager_vim	1	:git	0	:-	0	:/home/hoschi/repos/sweetp-code/services/project-context-manager	1	zsh	:
pane	project-context-manager_vim	1	:git	0	:-	0	:/home/hoschi/repos/sweetp-code/services/project-context-manager	1	zsh	:
pane	project-context-manager_vim	0	:vim	1	:*	0	:/home/hoschi/repos/sweetp-code/services/project-context-manager	1	zsh	:
pane	project-context-manager_vim	1	:git	0	:-	0	:/home/hoschi/repos/sweetp-code/services/project-context-manager	1	zsh	:
pane	serien	0	:desktop	1	:*	0	:/home/hoschi	1	zsh	:
pane	serien	0	:desktop	1	:*	0	:/home/hoschi	1	zsh	:
pane	serien	0	:desktop	1	:*	1	:/home/hoschi	0	zsh	:
pane	serien	0	:desktop	1	:*	0	:/home/hoschi	1	zsh	:
pane	serien	0	:desktop	1	:*	1	:/home/hoschi	0	zsh	:
pane	startup	0	:zsh	1	:*	0	:/home/hoschi	1	zsh	:
pane	startup	0	:zsh	1	:*	0	:/home/hoschi	1	zsh	:
pane	serien	0	:desktop	1	:*	1	:/home/hoschi	0	zsh	:
pane	startup	0	:zsh	1	:*	0	:/home/hoschi	1	zsh	:
pane	sw-dashboard	0	:vim	0	: 	0	:/home/hoschi/repos/sweetp-code/dashboard	1	zsh	:
pane	sw-dashboard	0	:vim	0	: 	0	:/home/hoschi/repos/sweetp-code/dashboard	1	zsh	:
pane	sw-dashboard	0	:vim	0	: 	0	:/home/hoschi/repos/sweetp-code/dashboard	1	zsh	:
pane	sw-dashboard	0	:vim	0	: 	1	:/home/hoschi/repos/sweetp-code/dashboard	0	zsh	:
pane	sw-dashboard	0	:vim	0	: 	1	:/home/hoschi/repos/sweetp-code/dashboard	0	zsh	:
pane	sw-dashboard	0	:vim	0	: 	1	:/home/hoschi/repos/sweetp-code/dashboard	0	zsh	:
pane	sw-dashboard	1	:work	1	:*	0	:/home/hoschi/repos/sweetp-code/dashboard	0	zsh	:
pane	sw-dashboard	1	:work	1	:*	0	:/home/hoschi/repos/sweetp-code/dashboard	0	zsh	:
pane	sw-dashboard	1	:work	1	:*	0	:/home/hoschi/repos/sweetp-code/dashboard	0	zsh	:
pane	sw-dashboard	1	:work	1	:*	1	:/home/hoschi/repos/sweetp-code/dashboard	1	zsh	:
pane	sw-dashboard	1	:work	1	:*	1	:/home/hoschi/repos/sweetp-code/dashboard	1	zsh	:
pane	sw-dashboard	1	:work	1	:*	1	:/home/hoschi/repos/sweetp-code/dashboard	1	zsh	:
pane	sw-dashboard	1	:work	1	:*	2	:/home/hoschi/repos/sweetp-code/dashboard	0	zsh	:
pane	sw-dashboard	1	:work	1	:*	2	:/home/hoschi/repos/sweetp-code/dashboard	0	zsh	:
pane	sw-dashboard	1	:work	1	:*	2	:/home/hoschi/repos/sweetp-code/dashboard	0	zsh	:
pane	sw-dashboard	2	:stable	0	:-	0	:/home/hoschi/repos/sweetp-code/dashboard-stable	1	zsh	:
pane	sw-dashboard	2	:stable	0	:-	0	:/home/hoschi/repos/sweetp-code/dashboard-stable	1	zsh	:
pane	sw-dashboard	2	:stable	0	:-	0	:/home/hoschi/repos/sweetp-code/dashboard-stable	1	zsh	:
pane	sw-main	0	:git	0	: 	0	:/home/hoschi/repos/sweetp-code/main	1	zsh	:
pane	sw-main	0	:git	0	: 	0	:/home/hoschi/repos/sweetp-code/main	1	zsh	:
pane	sw-main	0	:git	0	: 	0	:/home/hoschi/repos/sweetp-code/main	1	zsh	:
pane	sw-main	1	:build	0	: 	0	:/home/hoschi/repos/sweetp-code/main	0	zsh	:
pane	sw-main	1	:build	0	: 	0	:/home/hoschi/repos/sweetp-code/main	0	zsh	:
pane	sw-main	1	:build	0	: 	0	:/home/hoschi/repos/sweetp-code/main	0	zsh	:
pane	sw-main	1	:build	0	: 	1	:/home/hoschi/repos/sweetp-code/main	1	zsh	:
pane	sw-main	1	:build	0	: 	1	:/home/hoschi/repos/sweetp-code/main	1	zsh	:
pane	sw-main	1	:build	0	: 	1	:/home/hoschi/repos/sweetp-code/main	1	zsh	:
pane	sw-main	2	:dev-server	1	:*	0	:/home/hoschi/repos/sweetp-code/dev-server/server	1	zsh	:
pane	sw-main	2	:dev-server	1	:*	0	:/home/hoschi/repos/sweetp-code/dev-server/server	1	zsh	:
pane	sw-main	2	:dev-server	1	:*	0	:/home/hoschi/repos/sweetp-code/dev-server/server	1	zsh	:
pane	sw-main	2	:dev-server	1	:*	1	:/home/hoschi/repos/sweetp-code/dev-server/server	0	zsh	:
pane	sw-main	2	:dev-server	1	:*	1	:/home/hoschi/repos/sweetp-code/dev-server/server	0	zsh	:
pane	sw-main	2	:dev-server	1	:*	1	:/home/hoschi/repos/sweetp-code/dev-server/server	0	zsh	:
pane	sw-main	3	:test	0	:-	0	:/home/hoschi/repos/sweetp-code/dashboard	1	zsh	:
pane	sw-main	3	:test	0	:-	0	:/home/hoschi/repos/sweetp-code/dashboard	1	zsh	:
pane	sw-main	3	:test	0	:-	0	:/home/hoschi/repos/sweetp-code/dashboard	1	zsh	:
pane	sys-update	0	:zsh	1	:*	0	:/home/hoschi	1	zsh	:
pane	sys-update	0	:zsh	1	:*	0	:/home/hoschi	1	zsh	:
pane	sys-update	0	:zsh	1	:*	0	:/home/hoschi	1	zsh	:
pane	test-sw-dashboard	0	:zsh	1	:*	0	:/home/hoschi/repos/sweetp-code/dashboard	0	zsh	:
pane	test-sw-dashboard	0	:zsh	1	:*	0	:/home/hoschi/repos/sweetp-code/dashboard	0	zsh	:
pane	test-sw-dashboard	0	:zsh	1	:*	0	:/home/hoschi/repos/sweetp-code/dashboard	0	zsh	:
pane	test-sw-dashboard	0	:zsh	1	:*	1	:/home/hoschi/repos/sweetp-code/dashboard	0	zsh	:
pane	test-sw-dashboard	0	:zsh	1	:*	1	:/home/hoschi/repos/sweetp-code/dashboard	0	zsh	:
pane	test-sw-dashboard	0	:zsh	1	:*	1	:/home/hoschi/repos/sweetp-code/dashboard	0	zsh	:
pane	test-sw-dashboard	0	:zsh	1	:*	2	:/home/hoschi/repos/sweetp-code/dashboard	1	zsh	:
pane	test-sw-dashboard	0	:zsh	1	:*	2	:/home/hoschi/repos/sweetp-code/dashboard	1	zsh	:
pane	tmux-conf	0	:vim	0	: 	0	:/home/hoschi	1	zsh	:
pane	test-sw-dashboard	0	:zsh	1	:*	2	:/home/hoschi/repos/sweetp-code/dashboard	1	zsh	:
pane	tmux-conf	0	:vim	0	: 	0	:/home/hoschi	1	zsh	:
pane	tmux-conf	0	:vim	0	: 	0	:/home/hoschi	1	zsh	:
pane	tmux-conf	1	:man	0	: 	0	:/usr/share/man	1	zsh	:
pane	tmux-conf	1	:man	0	: 	0	:/usr/share/man	1	zsh	:
pane	tmux-conf	1	:man	0	: 	0	:/usr/share/man	1	zsh	:
pane	tmux-conf	2	:git	0	:-	0	:/home/hoschi/dotfiles	1	zsh	:
pane	tmux-conf	2	:git	0	:-	0	:/home/hoschi/dotfiles	1	zsh	:
pane	tmux-conf	2	:git	0	:-	0	:/home/hoschi/dotfiles	1	zsh	:
pane	tmux-conf	3	:zsh	1	:*	0	:/home/hoschi/.tmux/resurrect	1	zsh	:
pane	tmux-conf	3	:zsh	1	:*	0	:/home/hoschi/.tmux/resurrect	1	zsh	:
pane	tmux-conf	3	:zsh	1	:*	0	:/home/hoschi/.tmux/resurrect	1	zsh	:
pane	vim_config	0	:vimrc	0	: 	0	:/home/hoschi/dotfiles/.vim	1	zsh	:
pane	vim_config	0	:vimrc	0	: 	0	:/home/hoschi/dotfiles/.vim	1	zsh	:
pane	vim_config	0	:vimrc	0	: 	0	:/home/hoschi/dotfiles/.vim	1	zsh	:
pane	vim_config	1	:plugins	0	:-	0	:/home/hoschi/dotfiles/.vim/bundle	1	zsh	:
pane	vim_config	1	:plugins	0	:-	0	:/home/hoschi/dotfiles/.vim/bundle	1	zsh	:
pane	vim_config	1	:plugins	0	:-	0	:/home/hoschi/dotfiles/.vim/bundle	1	zsh	:
pane	vim_config	2	:my-snippets	1	:*	0	:/home/hoschi/dotfiles/.vim/mysnippets	1	zsh	:
pane	vim_config	2	:my-snippets	1	:*	0	:/home/hoschi/dotfiles/.vim/mysnippets	1	zsh	:
pane	weechat	0	:WeeChat 1.1.1	1	:*	0	:/home/hoschi	1	weechat	:weechat
pane	vim_config	2	:my-snippets	1	:*	0	:/home/hoschi/dotfiles/.vim/mysnippets	1	zsh	:
pane	weechat	0	:WeeChat 1.1.1	1	:*	0	:/home/hoschi	1	weechat	:weechat
pane	weechat	0	:WeeChat 1.1.1	1	:*	0	:/home/hoschi	1	weechat	:weechat
pane	workflow-service	0	:vim	1	:*	0	:/home/hoschi/repos/sweetp-code/services/project-workflow	1	zsh	:
pane	workflow-service	0	:vim	1	:*	0	:/home/hoschi/repos/sweetp-code/services/project-workflow	1	zsh	:
pane	workflow-service	0	:vim	1	:*	0	:/home/hoschi/repos/sweetp-code/services/project-workflow	1	zsh	:
pane	workflow-service	1	:zsh	0	:-	0	:/home/hoschi/repos/sweetp-code/services/project-workflow	1	zsh	:
pane	workflow-service2	0	:bash	1	:*	0	:/home/hoschi/repos/sweetp-code/services/project-workflow	1	zsh	:
pane	workflow-service	1	:zsh	0	:-	0	:/home/hoschi/repos/sweetp-code/services/project-workflow	1	zsh	:
pane	workflow-service	1	:zsh	0	:-	0	:/home/hoschi/repos/sweetp-code/services/project-workflow	1	zsh	:
window	1	0	1	:*	c97e,376x75,0,0,1
window	activity	0	1	:*	c97f,376x75,0,0,2
window	atom	0	0	:-	c980,376x75,0,0,3
window	atom	1	1	:*	c981,376x75,0,0,4
window	base-node-service	0	1	:*	c982,376x75,0,0,5
window	base-node-service	1	0	:-	c983,376x75,0,0,6
window	data	0	1	:*	5b87,227x23,0,0,75
window	git-sevice	0	0	:-	c984,376x75,0,0,7
window	git-sevice	1	1	:*	c985,376x75,0,0,8
window	git-sevice	2	0	: 	c986,376x75,0,0,9
window	github-service	0	0	:-	64ef,376x75,0,0,10
window	github-service	1	1	:*	64f0,376x75,0,0,11
window	github-service2	0	1	:*	64f1,376x75,0,0,12
window	grf	0	0	: 	5612,376x75,0,0[376x28,0,0,13,376x46,0,29,14]
window	grf	1	0	: 	5ed5,376x75,0,0[376x38,0,0,15,376x36,0,39,16]
window	grf	2	1	:*	0c97,376x75,0,0[376x39,0,0,17,376x35,0,40{188x35,0,40,18,187x35,189,40,19}]
window	grf	3	0	: 	7bce,376x75,0,0[376x36,0,0,20,376x38,0,37,21]
window	grf	4	0	: 	e4f1,376x75,0,0,22
window	grf	5	0	: 	e4f2,376x75,0,0,23
window	grf	6	0	:-	5cd4,376x75,0,0[376x44,0,0,24,376x30,0,45,25]
window	issues_vim	0	1	:*	9617,376x75,0,0[376x28,0,0,26,376x46,0,29,27]
window	issues_vim	1	0	:-	e4f7,376x75,0,0,28
window	issues_work	0	0	:-	e4f8,376x75,0,0,29
window	issues_work	1	1	:*	64f0,376x75,0,0,30
window	mopidy	0	1	:*	5cb8,181x62,0,0,38
window	mopidy	1	0	:-	5cb9,181x62,0,0,77
window	notes	0	1	:*	6479,146x75,0,0,39
window	notes	1	0	:-	e470,146x75,0,0,40
window	password-mngr	0	0	:-	e4f1,376x75,0,0,41
window	password-mngr	1	1	:*	e4f2,376x75,0,0,42
window	project-context-manager_second	0	1	:*	e4f3,376x75,0,0,43
window	project-context-manager_second	1	0	:-	e4f4,376x75,0,0,44
window	project-context-manager_vim	0	1	:*	e4f5,376x75,0,0,45
window	project-context-manager_vim	1	0	:-	e4f6,376x75,0,0,46
window	serien	0	1	:*	16da,376x75,0,0[376x40,0,0,47,376x34,0,41,48]
window	startup	0	1	:*	c97d,376x75,0,0,0
window	sw-dashboard	0	0	: 	d618,376x75,0,0[376x28,0,0,49,376x46,0,29,50]
window	sw-dashboard	1	1	:*	d342,376x75,0,0{214x75,0,0,51,161x75,215,0[161x39,215,0,52,161x35,215,40,53]}
window	sw-dashboard	2	0	:-	64f5,376x75,0,0,54
window	sw-main	0	0	: 	64f6,376x75,0,0,55
window	sw-main	1	0	: 	ded1,376x75,0,0[376x38,0,0,56,376x36,0,39,57]
window	sw-main	2	1	:*	2777,376x75,0,0{209x75,0,0,58,166x75,210,0,59}
window	sw-main	3	0	:-	e4f1,376x75,0,0,60
window	sys-update	0	1	:*	e4f2,376x75,0,0,61
window	test-sw-dashboard	0	1	:*	357a,376x75,0,0[376x20,0,0,62,376x19,0,21,63,376x34,0,41,64]
window	tmux-conf	0	0	: 	e4b6,109x75,0,0,65
window	tmux-conf	1	0	: 	e4b7,109x75,0,0,66
window	tmux-conf	2	0	:-	e4b8,109x75,0,0,67
window	tmux-conf	3	1	:*	e4b3,109x75,0,0,81
window	vim_config	0	0	: 	e4f9,376x75,0,0,68
window	vim_config	1	0	:-	e4fa,376x75,0,0,69
window	vim_config	2	1	:*	64f2,376x75,0,0,70
window	weechat	0	1	:*	6103,35x75,0,0,71
window	workflow-service	0	1	:*	64f4,376x75,0,0,72
window	workflow-service	1	0	:-	64f5,376x75,0,0,73
window	workflow-service2	0	1	:*	64f6,376x75,0,0,74
state	tmux-conf
pane	workflow-service2	0	:bash	1	:*	0	:/home/hoschi/repos/sweetp-code/services/project-workflow	1	zsh	:
pane	workflow-service2	0	:bash	1	:*	0	:/home/hoschi/repos/sweetp-code/services/project-workflow	1	zsh	:
window	1	0	1	:*	c97e,376x75,0,0,1
window	activity	0	1	:*	c97f,376x75,0,0,2
window	atom	0	0	:-	c980,376x75,0,0,3
window	atom	1	1	:*	c981,376x75,0,0,4
window	1	0	1	:*	c97e,376x75,0,0,1
window	base-node-service	0	1	:*	c982,376x75,0,0,5
window	base-node-service	1	0	:-	c983,376x75,0,0,6
window	activity	0	1	:*	c97f,376x75,0,0,2
window	data	0	1	:*	5b87,227x23,0,0,75
window	atom	0	0	:-	c980,376x75,0,0,3
window	git-sevice	0	0	:-	c984,376x75,0,0,7
window	git-sevice	1	1	:*	c985,376x75,0,0,8
window	atom	1	1	:*	c981,376x75,0,0,4
window	git-sevice	2	0	: 	c986,376x75,0,0,9
window	base-node-service	0	1	:*	c982,376x75,0,0,5
window	github-service	0	0	:-	64ef,376x75,0,0,10
window	base-node-service	1	0	:-	c983,376x75,0,0,6
window	github-service	1	1	:*	64f0,376x75,0,0,11
window	data	0	1	:*	5b87,227x23,0,0,75
window	github-service2	0	1	:*	64f1,376x75,0,0,12
window	git-sevice	0	0	:-	c984,376x75,0,0,7
window	grf	0	0	: 	5612,376x75,0,0[376x28,0,0,13,376x46,0,29,14]
window	git-sevice	1	1	:*	c985,376x75,0,0,8
window	grf	1	0	: 	5ed5,376x75,0,0[376x38,0,0,15,376x36,0,39,16]
window	git-sevice	2	0	: 	c986,376x75,0,0,9
window	grf	2	1	:*	0c97,376x75,0,0[376x39,0,0,17,376x35,0,40{188x35,0,40,18,187x35,189,40,19}]
window	github-service	0	0	:-	64ef,376x75,0,0,10
window	github-service	1	1	:*	64f0,376x75,0,0,11
window	grf	3	0	: 	7bce,376x75,0,0[376x36,0,0,20,376x38,0,37,21]
window	grf	4	0	: 	e4f1,376x75,0,0,22
window	github-service2	0	1	:*	64f1,376x75,0,0,12
window	grf	5	0	: 	e4f2,376x75,0,0,23
window	grf	0	0	: 	5612,376x75,0,0[376x28,0,0,13,376x46,0,29,14]
window	grf	6	0	:-	5cd4,376x75,0,0[376x44,0,0,24,376x30,0,45,25]
window	grf	1	0	: 	5ed5,376x75,0,0[376x38,0,0,15,376x36,0,39,16]
window	issues_vim	0	1	:*	9617,376x75,0,0[376x28,0,0,26,376x46,0,29,27]
window	grf	2	1	:*	0c97,376x75,0,0[376x39,0,0,17,376x35,0,40{188x35,0,40,18,187x35,189,40,19}]
window	issues_vim	1	0	:-	e4f7,376x75,0,0,28
window	grf	3	0	: 	7bce,376x75,0,0[376x36,0,0,20,376x38,0,37,21]
window	issues_work	0	0	:-	e4f8,376x75,0,0,29
window	grf	4	0	: 	e4f1,376x75,0,0,22
window	issues_work	1	1	:*	64f0,376x75,0,0,30
window	grf	5	0	: 	e4f2,376x75,0,0,23
window	mopidy	0	1	:*	5cb8,181x62,0,0,38
window	grf	6	0	:-	5cd4,376x75,0,0[376x44,0,0,24,376x30,0,45,25]
window	mopidy	1	0	:-	5cb9,181x62,0,0,77
window	issues_vim	0	1	:*	9617,376x75,0,0[376x28,0,0,26,376x46,0,29,27]
window	notes	0	1	:*	6479,146x75,0,0,39
window	issues_vim	1	0	:-	e4f7,376x75,0,0,28
window	notes	1	0	:-	e470,146x75,0,0,40
window	issues_work	0	0	:-	e4f8,376x75,0,0,29
window	password-mngr	0	0	:-	e4f1,376x75,0,0,41
window	issues_work	1	1	:*	64f0,376x75,0,0,30
window	password-mngr	1	1	:*	e4f2,376x75,0,0,42
window	mopidy	0	1	:*	5cb8,181x62,0,0,38
window	project-context-manager_second	0	1	:*	e4f3,376x75,0,0,43
window	mopidy	1	0	:-	5cb9,181x62,0,0,77
window	project-context-manager_second	1	0	:-	e4f4,376x75,0,0,44
window	notes	0	1	:*	6479,146x75,0,0,39
window	project-context-manager_vim	0	1	:*	e4f5,376x75,0,0,45
window	notes	1	0	:-	e470,146x75,0,0,40
window	project-context-manager_vim	1	0	:-	e4f6,376x75,0,0,46
window	password-mngr	0	0	:-	e4f1,376x75,0,0,41
window	serien	0	1	:*	16da,376x75,0,0[376x40,0,0,47,376x34,0,41,48]
window	password-mngr	1	1	:*	e4f2,376x75,0,0,42
window	startup	0	1	:*	c97d,376x75,0,0,0
window	project-context-manager_second	0	1	:*	e4f3,376x75,0,0,43
window	sw-dashboard	0	0	: 	d618,376x75,0,0[376x28,0,0,49,376x46,0,29,50]
window	project-context-manager_second	1	0	:-	e4f4,376x75,0,0,44
window	sw-dashboard	1	1	:*	d342,376x75,0,0{214x75,0,0,51,161x75,215,0[161x39,215,0,52,161x35,215,40,53]}
window	project-context-manager_vim	0	1	:*	e4f5,376x75,0,0,45
window	sw-dashboard	2	0	:-	64f5,376x75,0,0,54
window	project-context-manager_vim	1	0	:-	e4f6,376x75,0,0,46
window	sw-main	0	0	: 	64f6,376x75,0,0,55
window	serien	0	1	:*	16da,376x75,0,0[376x40,0,0,47,376x34,0,41,48]
window	sw-main	1	0	: 	ded1,376x75,0,0[376x38,0,0,56,376x36,0,39,57]
window	startup	0	1	:*	c97d,376x75,0,0,0
window	sw-main	2	1	:*	2777,376x75,0,0{209x75,0,0,58,166x75,210,0,59}
window	sw-dashboard	0	0	: 	d618,376x75,0,0[376x28,0,0,49,376x46,0,29,50]
window	sw-main	3	0	:-	e4f1,376x75,0,0,60
window	sys-update	0	1	:*	e4f2,376x75,0,0,61
window	sw-dashboard	1	1	:*	d342,376x75,0,0{214x75,0,0,51,161x75,215,0[161x39,215,0,52,161x35,215,40,53]}
window	sw-dashboard	2	0	:-	64f5,376x75,0,0,54
window	test-sw-dashboard	0	1	:*	357a,376x75,0,0[376x20,0,0,62,376x19,0,21,63,376x34,0,41,64]
window	sw-main	0	0	: 	64f6,376x75,0,0,55
window	tmux-conf	0	0	: 	e4b6,109x75,0,0,65
window	sw-main	1	0	: 	ded1,376x75,0,0[376x38,0,0,56,376x36,0,39,57]
window	tmux-conf	1	0	: 	e4b7,109x75,0,0,66
window	tmux-conf	2	0	:-	e4b8,109x75,0,0,67
window	sw-main	2	1	:*	2777,376x75,0,0{209x75,0,0,58,166x75,210,0,59}
window	tmux-conf	3	1	:*	e4b3,109x75,0,0,81
window	sw-main	3	0	:-	e4f1,376x75,0,0,60
window	vim_config	0	0	: 	e4f9,376x75,0,0,68
window	sys-update	0	1	:*	e4f2,376x75,0,0,61
window	vim_config	1	0	:-	e4fa,376x75,0,0,69
window	test-sw-dashboard	0	1	:*	357a,376x75,0,0[376x20,0,0,62,376x19,0,21,63,376x34,0,41,64]
window	vim_config	2	1	:*	64f2,376x75,0,0,70
window	tmux-conf	0	0	: 	e4b6,109x75,0,0,65
window	weechat	0	1	:*	6103,35x75,0,0,71
window	tmux-conf	1	0	: 	e4b7,109x75,0,0,66
window	workflow-service	0	1	:*	64f4,376x75,0,0,72
window	tmux-conf	2	0	:-	e4b8,109x75,0,0,67
window	workflow-service	1	0	:-	64f5,376x75,0,0,73
window	tmux-conf	3	1	:*	e4b3,109x75,0,0,81
window	workflow-service2	0	1	:*	64f6,376x75,0,0,74
window	vim_config	0	0	: 	e4f9,376x75,0,0,68
window	vim_config	1	0	:-	e4fa,376x75,0,0,69
window	vim_config	2	1	:*	64f2,376x75,0,0,70
window	weechat	0	1	:*	6103,35x75,0,0,71
window	workflow-service	0	1	:*	64f4,376x75,0,0,72
window	workflow-service	1	0	:-	64f5,376x75,0,0,73
window	workflow-service2	0	1	:*	64f6,376x75,0,0,74
state	tmux-conf
state	tmux-conf

tmux conf:
# Activity monitoring
#setw -g monitor-activity on
#set -g visual-activity on

# Highlight active window
#set-window-option -g window-status-current-bg red

set -g default-terminal "screen-256color"

# utf8 is on
set -g utf8 on
set -g status-utf8 on

# address vim mode switching delay (http://superuser.com/a/252717/65504)
set -s escape-time 0

# tmux messages are displayed for 4 seconds
#set -g display-time 4000

# refresh 'status-left' and 'status-right' more often
#set -g status-interval 5

# Highlight active pane
#set-option -g pane-active-border-style bold
set-option -g pane-active-border-bg blue

# use powerline as status line
source '/home/hoschi/src/powerline/powerline/bindings/tmux/powerline.conf'

# create splits by | and -
unbind %
bind | split-window -h
bind - split-window -v

unbind p
# -n is for 'no prefix' !
bind-key -n F7 previous-window
bind-key a previous-window
bind-key -n F8 next-window
bind-key e next-window

bind-key C-b last-window

# renumber window so they have always continuing numbers
set -g renumber-windows on
# use relative indices for window movement with auto indices
bind-key A swap-window -t -1
bind-key E swap-window -t +1

# use vim motion keys while in copy mode
setw -g mode-keys vi

# use mouse!
set -g mode-mouse on
set -g mouse-resize-pane on
set -g mouse-select-pane on
set -g mouse-select-window on

# scroll with mouse wheel in pane, not in terminals scrollbuffer
set -g terminal-overrides 'xterm*:smcup@:rmcup@'

# set history size
set -g history-limit 10000

##CLIPBOARD selection integration
##Requires prefix key before the command key
#Copy tmux paste buffer to CLIPBOARD
#
#
# attention: install xclip!

# bind C-c run "tmux show-buffer | xclip -i -selection clipboard"
# replaced with tmux-yank plugin:
# Mouse Support
# When making a selection using tmux mode-mouse on or mode-mouse copy-mode, you
# cannot rely on the default 'release mouse after selection to copy' behavior.
# Instead, press y before releasing mouse.

#Copy CLIPBOARD to tmux paste buffer and paste tmux paste buffer
bind C-v run "tmux set-buffer -- \"$(xclip -o -selection clipboard)\"; tmux paste-buffer"

# List of plugins
set -g @tpm_plugins "              \
  tmux-plugins/tpm                 \
  tmux-plugins/tmux-resurrect   \
  tmux-plugins/tmux-continuum   \
  tmux-plugins/tmux-copycat   \
  tmux-plugins/tmux-yank   \
  tmux-plugins/tmux-open   \
  tmux-plugins/tmux-sessionist     \
"
# Other examples:
# github_username/plugin_name    \
# git@github.com/user/plugin     \
# git@bitbucket.com/user/plugin  \

# initializes TMUX plugin manager
# https://github.com/tmux-plugins/tpm
run-shell ~/.tmux/plugins/tpm/tpm

# https://github.com/tmux-plugins/tmux-resurrect
set -g @resurrect-processes 'ssh "git log" ~grunt-wrapper tail weechat vim ncmpcpp dmesg'

# https://github.com/tmux-plugins/tmux-continuum
set -g @continuum-restore 'on'

# https://github.com/tmux-plugins/tmux-open
# o      = open a highlighted selection with the system default program. open for OS X or xdg-open for Linux.
# Ctrl-o = open a highlighted selection with the $EDITOR

# https://github.com/tmux-plugins/tmux-copycat
# prefix + /        = regex search (strings work too)
# prefix + ctrl-f = simple file search
# prefix + ctrl-g = jumping over git status files (best used after git status command)
# prefix + ctrl-u = url search (http, ftp and git urls)
# prefix + ctrl-d = number search (mnemonic d, as digit)

Hey, thank you for reporting this issue.
Do you have the latest versions of both tmux-resurrect and tmux-continuum?
What is your status-interval option value $ tmux -g show status-interval?
I see you have set -g status-interval 5 in the tmux.conf, but that is commented out.
About "double" saving - that could happen if status-interval is low (5 seconds is low) and saving takes relatively long (5-10 seconds). Here's the possible scenario how that could happen:

automatic saving starts and will take 10 seconds to complete
in the meantime, another automatic save is started (because the first one is not done yet) and it duplicates entries in the last file

I think I addressed this possibility, but I will look into this again.
I will be pretty responsive over the weekend so your replies would be helpful @hoschi!

Hi,
I've been investigating and trying to reproduce this issue.
I've set very aggressive auto-save settings:

set -g status-interval 2 # tmux setting that influences how often last timestamp will be checked
set -g @continuum-save-interval '1' # auto save happens every 60 seconds
I also have a large number of panes and windows so save takes around 5-7 seconds

I couldn't notice anything unusual with the "continuum" last file. The content was all ok.
I've also inspected the code and after the first review I think we have mechanism in place that should prevent multiple saves happening at the same time..
So, can you please fetch latest tmux-continuum and tmux-resurrect versions and try this again? I'm curious about the results.
One other thing I noticed about your tmux.conf: set -g @tpm_plugins "... and run-shell ~/.tmux/plugins/tpm/tpm lines should be at the very bottom of tmux.conf.
It's possible set -g @continuum-restore 'on' line was not detected because of that.

show -g status-interval gives me '2' for the value. Man pages states it is 15, so I configured that in my tmux.conf now. Also I moved the lines down as you said. I removed resurrect and continuum from ~/.tmux/plugins added and hit Ctrl-I to install it again.
But I got the same result as before when the first continuum auto save takes place :(
This line is actually fake (because of privacy):
pane    notes   1   :AA 0   :-  0   :/home/hoschi/Dropbox/notes 1   vim :vim /home/hoschi/foo.md

the dir name has a space in it. E.g. /home/hoschi/foo bar/foo.md which leads to a wrong restore. It restores vim /home/hoschi/foo instead of /home/hoschi/foo bar/foo.md. I know this is restore, not save ... but this is the only thing I saw as secondary problem.
I have no other idea what can break continuum auto save. I thought of strange session names or so, but then resurrect should also fail.

Hi,
I also am experiencing the same problem. Every now and then I get triplicate entries the autosave file. This can be a real issue if this file is used by resurrect to recover a session. The worst case is when a vim session is recovered, the addition lines are send to vim and that can mess up a code file/document. in the I have made the following changes:
The end of my .tmux.conf:
set -g @resurrect-processes 'vifm ssh'
#set -g @resurrect-processes ':all:'
set -g @resurrect-strategy-vim 'session'
set -g @resurrect-save-bash-history 'on'
set -g @continuum-restore 'on'
Save every thirty minutes
set -g @continuum-save-interval '30'
set -g @tpm_plugins '
tmux-plugins/tpm
tmux-plugins/tmux-sensible
tmux-plugins/tmux-resurrect
tmux-plugins/tmux-continuum
tmux-plugins/tmux-open
'
run-shell '~/.tmux/plugins/tpm/tpm'

We likely fixed this problem via #61. I'll close the issue now. If anyone reproduces this same problem again, please reopen.

authors: bruno- hoschi yamsu

repo: tmux-plugins/tmux-continuum


text:
pain_control.tmux' returned 127

What is the meaning of this error?

chmod +x pain_control.tmux
https://stackoverflow.com/a/10038458/13477305

source: gharchive/issue

authors: YonatanSimson ajr-dev

repo: tmux-plugins/tmux-pain-control

license: mit

license_type: permissive

license_source: bigquery


text:
Fix terminal setting and use page breaks between prompts

This PR does two things:
First, it hardcodes the terminal setting to dumb. This is the default, but if the user happens to be using a different setting (as I am) then it will break aider since it is built on prompt-toolkit.
Second, Aider will output a series of Unicode dashes between the prompts. However, it doesn't query for the correct size and instead just hardcodes the number of dashes to insert. Emacs already has a nice way to handle these separators via page-break-lines. This has the advantage that it will always span the entire window, even when resizing.

Hi @CeleritasCelery, Thanks for the PR! I tried your change in my laptop, comments:

For the first commit, it might be a good idea. actually i have little knowledge about comint-terminfo-terminal.
For the second one, i only saw slightly color change on the page break line,

and the previous one before change seems OK to me? (I am using a Macbook Pro)

The old separator is hardcoded to 80 characters (because the terminal is dumb). If the window is narrower than that it will wrap and if it is wider it will not span the whole line. It is not a big thing, but I feel like it makes the interface nicer.

Got it. Thanks for the replying. Is there a way to achieve that without adding a package dependency?

I implemented a dependency-free solution based on this code. I think it looks better overall.

Tested and it works. Thanks for the contribution.

source: gharchive/pull-request

authors: CeleritasCelery tninja

license_source: github-api


text:
Stuck at updating network configuration

I'm running this script and passing the password to log into the router settings as a parameter.
The script gets stuck here:
Fetching auth token from http://192.168.12.1/TMI/v1/auth/login ... Obtained auth token! Fetching network configuration from http://192.168.12.1/TMI/v1/network/configuration ... Obtained network config! Updating network configuration at http://192.168.12.1/TMI/v1/network/configuration ...
If I log into the router settings and then visit "192.168.12.1/TMI/v1/network/configuration" , this is what gets displayed :
{   "result": {     "error": "AuthorizationError",     "message": "Not Authorized, Access token is missing or invalid",     "statusCode": 401   } }

The script disables the built-in WiFi of the unit. If you're connecting via this WiFi, it will stop working once the update is applied.

license: MIT


text:
Add CHIP-8 test suite to the list of testing tools

My "test suite" seems to be helping a lot of people who stumble upon it. So I figured it would be a shame not to mention it in this excellent list :) I was a bit unsure about where in the list to put it, hope this is the most logical order.

Thanks!

authors: Timendus tobiasvl


text:
Added support for input switch

Support one input switch for ON/OFF the LED strip. Also possible to program three modes (short / medium / long press)

Hey @szepnorbee Any chance this input could also send a message back onto MQTT? so that code somewhere else could take actions from the button press too? :)

repo: toblum/McLighting


text:
Dynamically Request Log Level?

This is a question and feature request, I guess. Is there a way to have a client request the minimum Log Level and have the hub respond dynamically only when that Log Level is hit?
I'm impatient and just started with the project, so I may figure it out myself. If I do, I'll post it here for posterity. Maybe it could added to the wiki or sample. IDK

@da3dsoul I wanted you to know that the SignalRTarget does not set up the Hub.  This target establishes a HubProxy for connecting to the SignalR Hub at the Uri and Name that is specified for the target.  The library also provides the common ILoggingHub interface for the SignalR service set up.
I include a diagram to show how it currently works.

So - the target is not handling the Hub behavior.  If we wanted to have the Client communicate a log level to the Hub, we would need to enhance the ILoggingHub interface and provide an implementation of the LoggingHub to provide that behavior.

Yeah I figured it out after the fact. What I meant was dynamically via query strings, but I'm not sure that's ideal after my experience with SignalR.


text:
Todoist - add Button to detail view

Describe the changes you'd like
Add the Toggl Button to the Todoist task detail view
Relevant links or screenshots

Additional context
Currently you need to close the task and go back to the main list to start a timer.

User request

repo: toggl/toggl-button


text:
Revert "Add tests. (#5)"

This reverts commit 130dabe05c9880341cfeb6a1222422301f29a15e.

The tests fail on Windows, and there is currently no good way to let the surrounding system about it.
Once that is in place I will reland it.
TBR.

ok

authors: erikcorry floitsch

repo: toitlang/pkg-host


text:
Reconsider providing hup as a readiness value for all *nix platforms.

For epoll, HUP indicates that both the read and the write directions of a socket are closed. With kqueue, read and write directions are tracked separately. Each direction can have an optional EOF filter indicating that the direction is closed. There is no way to know that both directions are closed without tracking additional state.
However, for TCP, EOF for the write direction is equivalent to HUP. This does not apply to other types of evented handles.
The question is, how should this be normalized?
One option is to have hup be a platform specific readiness value. Another option would be to translate EPOLLHUP -> "write EOF" and document that for TCP, this indicates a HUP.

This is a continuation of discussion starting here.
cc @Thomasdezeeuw @asomers

I'm going to think about this a bit more over the weekend so it might take me a while to respond to this and #939. However I'm looking for some examples of how HUP is used currently, the only usage I could find is from Tokio.
If anyone uses HUP readiness could you share how you're using it, or point us to the code? I think that would help make a decision on how to handle this.

@Thomasdezeeuw Ideally we can get #939 merged & released sooner than later as it is causing issues in production (cloudflare hit this recently).

We could merge #939 and determine how to handle HUP cross-platform for 0.7.

@Thomasdezeeuw I think that is the best strategy.

#983 makes is_hup available on all platforms. Anything else that needs to be done?

@Thomasdezeeuw The main question is if HUP will be triggered on only linux or on all *nix platforms. I believe we have to stick with Linux only here. I believe that all that is left to close this issue is verify that all HUP related code is deleted from kqueue.

Shouldn't we document the different meaning for HUP on epoll/kqueue platforms and support both?

@Thomasdezeeuw I do not know of a way to unify hup across linux & kqueue in a way that is more useful than just responding to read / write. In order for specialized events to be useful, they need stronger guarantees. This would allow the user to issuing syscalls when they know how the call will respond. AFAIK, there is no way to detect a full socket close on kqueue reliably w/o maintaining state:
https://github.com/tokio-rs/mio/pull/958/commits/17e2c7abee8b80e8d061f5b7c0c731b009cfee1c

Since HUP isn't supported by all platforms, i.e. Windows doesn't have it, I think it should be a bit of a second class citizen and documentation that it's very platform specific what HUP actually means. Or we should remove it completely, because as you said it's not really possible to mimic any platforms' behaviour.

I would leave it but document that it is only fired on Linux.

Current state on master is that Event::is_hup is provided on all unix platforms, but different when this occurs (i.e. it's platform specific we just pass on the information the OS provides) and this is clearly stated in the documentation. @carllerche anything left you want to here?

@Thomasdezeeuw To be conservative, I would like to update the docs (for now) to say that linux is the only platform that is guaranteed to receive HUP events.

as far as I know, we can only receive RDHUP events from kqueue...

I was thinking about all the platform specific events; maybe we should just document which flags it checks for and point to the OS documentation.

@Thomasdezeeuw sure, we can do that.
I think the only events we can guarantee cross platform will be readable and writeable.

@carllerche yes all the others have not about not being cross platform.

I think #1037 solves this for the most part, so closing.

authors: Thomasdezeeuw carllerche

repo: tokio-rs/mio


text:
Re-translation of simplified Chinese language

This is a pull request that I reopened, and I'm sorry for my last pull request that was confusing.
my english is not very good, i used google translate.

Thank you for updating the translations.


text:
GSGL 'inverse' undeclared in tutorial

I followed the tutorial/book. In the chapter about Gouraud shading I always get an error about the GSGL inverse function.
     Running `target/debug/gltest`
thread '<main>' panicked at 'called `Result::unwrap()` on an `Err` value: CompilationError("ERROR: 0:8: Invalid call of undeclared identifier \'inverse\'\n")', ../src/libcore/result.rs:732

I'm on a mid-2013 MacBook Air with OS X 10.11 with Rust 1.3 stable.

The function is likely not implemented :-/

The function is available for OSX if GLSL version "400" is specified.

@tomaka, the matrix seems to be the same for each vertex -- isn't it better to invert it once in the CPU and then put inverted into the uniform?

isn't it better to invert it once in the CPU and then put inverted into the uniform?

Yeah that's what you usually do in a real game or engine. But it's a bit tedious to write an invert function in Rust, and out of scope of the tutorial.

@tomaka, sorry for slightly diverging from the original topic. And probably the question is silly.
Nevertheless, what would you recommend to use to do Matrix/Vector arithmetics when needed in an application using Glium?
Implementing by myself 'invert' or 'multiply' (just to name a few) seems to be a bit wrong.

There's nalgebra and cgmath. Cgmath is more oriented towards gamedev.

Closing in favor of #1311

authors: RGafiyatullin palango tomaka

repo: tomaka/glium


text:
The depth mapping is not linear

This is not a problem in the code but in the documentation.
The docs claim that the mapping from the z coord of gl_Position to the depth value that will be read from the zbuffer is linear, while it isn't. These parts should be rewritten.

In fact not an issue. The non-linearity comes from the perspective matrix. I misunderstood that.


text:
Can't connect through POP3

I can't seem to connect through pop3, both with or without SSL.
Context

I can connect through SMTP with SSL, but I can't connect through POP3 at all. With or without SSL, on port 110 or 995. I have opened up both ports in my docker-compose file and also added ENABLE_POP3=1 to it. I
I get my SSL certificates through Let's Encrypt. It's also setup for mail.mydomain.com.
When I'm trying to connect the logs show the following error:
Mar 11 19:16:08 mail dovecot: pop3-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=102.102.101.10, lip=172.12.0.2, TLS: Disconnected, session=<AkHN2yd45sgKfVIL>

Edit: Gmail (web) returns the following error when trying to connect: SSL error: unknown CA (alert 48).
I ran:
docker exec mail openssl s_client -connect 0.0.0.0:25 -starttls imap -CApath /etc/ssl/certs/

It returns Verify return code: 0 (ok), but it fails on port 143, and all other ports from what I can see.
Possible Fix

I noticed dovecot is looking for its certificates at /etc/dovecot/ssl/dovecot.pem. Is that based on my Let's Encrypt certificates? Is there any way to check if they are legit?
I've read people with this error didn't had their SSL certificates in order.
Your Environment

Amount of RAM available: N/A
Mailserver version used: latest stable
Docker version used: 17.09.0-ce
Environment settings relevant to the config:
ENABLE_POP3=1
SSL_TYPE=letsencrypt
Any relevant stack traces ("Full trace" preferred): N/A

How did you setup SSL in your docker_compose?

I'm using the letsencrypt container from linuxserver. The letsencrypt folder is mounted to /etc/letsencrypt. Below is the docker-compose file. It is seperated from the mailserver docker-compose file since I followed the readme instructions, but I'm intending to merge them when the mailserver works.
  letsencrypt:
    image: linuxserver/letsencrypt
    container_name: letsencrypt
    cap_add:
      - NET_ADMIN
    ports:
      - "80:80"
      - "443:443"
    environment:
      - PUID=1000
      - PGID=1000
      - EMAIL=something@tld.com
      - URL=something.com
      - SUBDOMAINS=plex,sonarr,radarr,mail
      - VALIDATION=http
      - TZ=Europe/Paris
    volumes:
      - /home/ubuntu/web:/config

I noticed you wrote that dovecot is looking for the certificate at etc/dovecot/ssl/dovecot.pem and that means either you did not set ssl type to letsencrypt or the certification files are not available.
Could you run the following and post the output:
docker exec mail ls /etc/letsencrypt/live/$HOSTNAME/

docker exec mail cat /etc/dovecot/conf.d/10-ssl.conf

With $HOSTNAME replaced with your actual hostname

I initially forgot to mount the letsencrypt folder, but fixed it soon after. Perhaps that has something to do with it?
The files seem to be there now:
ubuntu@host:~/apps/mail$ sudo docker exec mail ls /etc/letsencrypt/live/hostname/
README
cert.pem
chain.pem
fullchain.pem
privkey.pem
privkey.pfx

ubuntu@host:~/apps/mail$ sudo docker exec mail cat /etc/dovecot/conf.d/10-ssl.conf
##
## SSL settings
##

# SSL/TLS support: yes, no, required. <doc/wiki/SSL.txt>
ssl = required

# PEM encoded X.509 SSL/TLS certificate and private key. They're opened before
# dropping root privileges, so keep the key file unreadable by anyone but
# root. Included doc/mkcert.sh can be used to easily generate self-signed
# certificate, just make sure to update the domains in dovecot-openssl.cnf
ssl_cert = </etc/dovecot/ssl/dovecot.pem
ssl_key = </etc/dovecot/ssl/dovecot.key

# If key file is password protected, give the password here. Alternatively
# give it when starting dovecot with -p parameter. Since this file is often
# world-readable, you may want to place this setting instead to a different
# root owned 0600 file by using ssl_key_password = <path.
#ssl_key_password =

# PEM encoded trusted certificate authority. Set this only if you intend to use
# ssl_verify_client_cert=yes. The file should contain the CA certificate(s)
# followed by the matching CRL(s). (e.g. ssl_ca = </etc/ssl/certs/ca.pem)
#ssl_ca =

# Require that CRL check succeeds for client certificates.
#ssl_require_crl = yes

# Directory and/or file for trusted SSL CA certificates. These are used only
# when Dovecot needs to act as an SSL client (e.g. imapc backend). The
# directory is usually /etc/ssl/certs in Debian-based systems and the file is
# /etc/pki/tls/cert.pem in RedHat-based systems.
#ssl_client_ca_dir =
#ssl_client_ca_file =

# Request client to send a certificate. If you also want to require it, set
# auth_ssl_require_client_cert=yes in auth section.
#ssl_verify_client_cert = no

# Which field from certificate to use for username. commonName and
# x500UniqueIdentifier are the usual choices. You'll also need to set
# auth_ssl_username_from_cert=yes.
#ssl_cert_username_field = commonName

# DH parameters length to use.
ssl_dh_parameters_length = 2048

# SSL protocols to use
ssl_protocols = !SSLv3,!TLSv1,!TLSv1.1

# SSL ciphers to use
ssl_cipher_list = ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256

# Prefer the server's order of ciphers over client's.
ssl_prefer_server_ciphers = yes

# SSL crypto device to use, for valid values run "openssl engine"
#ssl_crypto_device =

Please rebuild the container with
docker-compose down && docker-compose up -d --build

So that the startup script change the path to letsencrypt certificates.
Then you should be able to connect to your server :)

Did that, still a no go. :(
10-ssl.conf still contains:
ssl_cert = </etc/dovecot/ssl/dovecot.pem
ssl_key = </etc/dovecot/ssl/dovecot.key

That's strange.
Could you provide your startup log?

Sure, here it is. I masked my domain for privacy purposes.
mail    | 2018-03-12 20:05:37,425 CRIT Supervisor running as root (no user in config file)
mail    | 2018-03-12 20:05:37,425 INFO Included extra file "/etc/supervisor/conf.d/saslauth.conf" during parsing
mail    | 2018-03-12 20:05:37,425 INFO Included extra file "/etc/supervisor/conf.d/supervisor-app.conf" during parsing
mail    | 2018-03-12 20:05:37,471 INFO RPC interface 'supervisor' initialized
mail    | 2018-03-12 20:05:37,471 CRIT Server 'unix_http_server' running without any HTTP authentication checking
mail    | 2018-03-12 20:05:37,472 INFO supervisord started with pid 7
mail    | 2018-03-12 20:05:38,475 INFO spawned: 'postsrsd' with pid 10
mail    | 2018-03-12 20:05:38,476 INFO spawned: 'mailserver' with pid 11
mail    |
mail    | 2018-03-12 20:05:38,527 INFO success: postsrsd entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | 2018-03-12 20:05:38,527 INFO success: mailserver entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | #
mail    | #
mail    | # docker-mailserver
mail    | #
mail    | #
mail    |
mail    | Initializing setup
mail    | Checking configuration
mail    | Configuring mail server
mail    | 2018-03-12 20:05:38,835 INFO exited: postsrsd (exit status 0; expected)
mail    |   * Spamassassin is disabled. You can enable it with 'ENABLE_SPAMASSASSIN=1'
mail    |   * Clamav is disabled. You can enable it with 'ENABLE_CLAMAV=1'
mail    | Starting Misc
mail    | Starting mail server
mail    | 2018-03-12 20:05:42,083 INFO spawned: 'cron' with pid 106
mail    | 2018-03-12 20:05:42,083 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | cron: started
mail    | 2018-03-12 20:05:42,299 INFO spawned: 'rsyslog' with pid 108
mail    | 2018-03-12 20:05:42,299 INFO success: rsyslog entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | rsyslog: started
mail    | 2018-03-12 20:05:42,494 INFO spawned: 'dovecot' with pid 113
mail    | 2018-03-12 20:05:42,495 INFO success: dovecot entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | dovecot: started
mail    | 2018-03-12 20:05:42,703 INFO spawned: 'opendkim' with pid 120
mail    | 2018-03-12 20:05:42,704 INFO success: opendkim entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | opendkim: started
mail    | 2018-03-12 20:05:42,877 INFO spawned: 'opendmarc' with pid 124
mail    | 2018-03-12 20:05:42,877 INFO success: opendmarc entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | opendmarc: started
mail    | 2018-03-12 20:05:43,044 INFO spawned: 'postfix' with pid 137
mail    | 2018-03-12 20:05:43,044 INFO success: postfix entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | postfix: started
mail    | 2018-03-12 20:05:43,218 INFO spawned: 'fail2ban' with pid 166
mail    | 2018-03-12 20:05:43,220 INFO success: fail2ban entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | fail2ban: started
mail    | 2018-03-12 20:05:43,399 INFO spawned: 'changedetector' with pid 170
mail    | 2018-03-12 20:05:43,399 INFO success: changedetector entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | changedetector: started
mail    | 2018-03-12 20:05:43,594 INFO spawned: 'amavis' with pid 232
mail    | 2018-03-12 20:05:43,595 INFO success: amavis entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | amavis: started
mail    |
mail    | #
mail    | # mail.domain.com is up and running
mail    | #
mail    |
mail    | Mar 12 20:05:45 mail postfix/master[972]: daemon started -- version 3.1.8, configuration /etc/postfix
mail    | Mar 12 20:05:45 mail amavis[232]: starting. /usr/sbin/amavisd-new at mail.domain.com amavisd-new-2.10.1 (20141025), Unicode aware
mail    | Mar 12 20:05:45 mail amavis[232]: Net::Server: Group Not Defined.  Defaulting to EGID '111 111'
mail    | Mar 12 20:05:45 mail amavis[232]: Net::Server: User Not Defined.  Defaulting to EUID '109'
mail    | Mar 12 20:05:45 mail amavis[232]: Module Amavis::Conf        2.404
mail    | Mar 12 20:05:45 mail amavis[232]: Module Archive::Zip        1.59
mail    | Mar 12 20:05:45 mail amavis[232]: Module BerkeleyDB          0.55
mail    | Mar 12 20:05:45 mail amavis[232]: Module Compress::Raw::Zlib 2.069
mail    | Mar 12 20:05:45 mail amavis[232]: Module Compress::Zlib      2.069001
mail    | Mar 12 20:05:45 mail amavis[232]: Module Digest::MD5         2.54
mail    | Mar 12 20:05:45 mail amavis[232]: Module Encode              2.80_01
mail    | Mar 12 20:05:45 mail amavis[232]: Module File::Temp          0.2304
mail    | Mar 12 20:05:45 mail amavis[232]: Module IO::Socket::IP      0.37
mail    | Mar 12 20:05:45 mail amavis[232]: Module MIME::Entity        5.508
mail    | Mar 12 20:05:45 mail amavis[232]: Module MIME::Parser        5.508
mail    | Mar 12 20:05:45 mail amavis[232]: Module MIME::Tools         5.508
mail    | Mar 12 20:05:45 mail amavis[232]: Module Mail::Header        2.18
mail    | Mar 12 20:05:45 mail amavis[232]: Module Mail::Internet      2.18
mail    | Mar 12 20:05:45 mail amavis[232]: Module Net::LibIDN         0.12
mail    | Mar 12 20:05:45 mail amavis[232]: Module Net::Server         2.008
mail    | Mar 12 20:05:45 mail amavis[232]: Module Scalar::Util        1.4202
mail    | Mar 12 20:05:45 mail amavis[232]: Module Socket              2.020_03
mail    | Mar 12 20:05:45 mail amavis[232]: Module Time::HiRes         1.9733
mail    | Mar 12 20:05:45 mail amavis[232]: Module Unix::Syslog        1.1
mail    | Mar 12 20:05:45 mail amavis[232]: Amavis::ZMQ code     NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: Amavis::DB code      loaded
mail    | Mar 12 20:05:45 mail amavis[232]: SQL base code        NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: SQL::Log code        NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: SQL::Quarantine      NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: Lookup::SQL code     NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: Lookup::LDAP code    NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: AM.PDP-in proto code loaded
mail    | Mar 12 20:05:45 mail amavis[232]: SMTP-in proto code   loaded
mail    | Mar 12 20:05:45 mail amavis[232]: Courier proto code   NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: SMTP-out proto code  loaded
mail    | Mar 12 20:05:45 mail amavis[232]: Pipe-out proto code  NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: BSMTP-out proto code NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: Local-out proto code loaded
mail    | Mar 12 20:05:45 mail amavis[232]: OS_Fingerprint code  NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: ANTI-VIRUS code      NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: ANTI-SPAM code       NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: ANTI-SPAM-EXT code   NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: ANTI-SPAM-C code     NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: ANTI-SPAM-SA code    NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: Unpackers code       loaded
mail    | Mar 12 20:05:45 mail amavis[232]: DKIM code            NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: Tools code           NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: Found $file            at /usr/bin/file
mail    | Mar 12 20:05:45 mail amavis[232]: No $altermime,         not using it
mail    | Mar 12 20:05:45 mail amavis[232]: Internal decoder for .mail
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .Z    at /bin/uncompress
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .gz   at /bin/gzip -d
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .bz2  at /bin/bzip2 -d
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .xz   at /usr/bin/xz -dc
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .lzma at /usr/bin/xz -dc --format=lzma
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .lrz  at /usr/bin/lrzip -q -k -d -o -
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .lzo  at /usr/bin/lzop -d
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .lz4  at /usr/bin/lz4c -d
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .rpm  at /usr/bin/rpm2cpio
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .cpio at /bin/pax
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .tar  at /bin/pax
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .deb  at /usr/bin/ar
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .rar  at /usr/bin/unrar-free
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .arj  at /usr/bin/arj
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .arc  at /usr/bin/nomarch
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .zoo  at /usr/bin/zoo
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .doc  at /usr/bin/ripole
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .cab  at /usr/bin/cabextract
mail    | Mar 12 20:05:45 mail amavis[232]: Internal decoder for .tnef
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .zip  at /usr/bin/7za
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .kmz  at /usr/bin/7za
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .7z   at /usr/bin/7zr
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .jar  at /usr/bin/7z
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .swf  at /usr/bin/7z
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .lha  at /usr/bin/7z
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .iso  at /usr/bin/7z
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .exe  at /usr/bin/unrar-free; /usr/bin/arj
mail    | Mar 12 20:05:45 mail amavis[232]: No decoder for       .F
mail    | Mar 12 20:05:45 mail amavis[232]: Deleting db files  in /var/lib/amavis/db
mail    | Mar 12 20:05:45 mail amavis[232]: Creating db in /var/lib/amavis/db/; BerkeleyDB 0.55, libdb 5.3
mail    | Mar 12 20:06:01 mail dovecot: ssl-params: SSL parameters regeneration completed

Ah, forgot to mention: Could you enable DMS_DEBUG with adding DMS_DEBUG=1 to your docker-compose and then rebuild the container?

Ah right. Here it is:
ubuntu@host:~/apps/mail$ sudo docker-compose down && sudo docker-compose up -d --build
Stopping mail ... done
Removing mail ... done
Removing network mail_default
Creating network "mail_default" with the default driver
Creating mail ...
Creating mail ... done
ubuntu@host:~/apps/mail$ sudo docker-compose logs -f mail
Attaching to mail
mail    | 2018-03-12 23:19:14,575 CRIT Supervisor running as root (no user in config file)
mail    | 2018-03-12 23:19:14,575 INFO Included extra file "/etc/supervisor/conf.d/saslauth.conf" during parsing
mail    | 2018-03-12 23:19:14,575 INFO Included extra file "/etc/supervisor/conf.d/supervisor-app.conf" during parsing
mail    | 2018-03-12 23:19:14,592 INFO RPC interface 'supervisor' initialized
mail    | 2018-03-12 23:19:14,592 CRIT Server 'unix_http_server' running without any HTTP authentication checking
mail    | 2018-03-12 23:19:14,592 INFO supervisord started with pid 7
mail    | 2018-03-12 23:19:15,595 INFO spawned: 'postsrsd' with pid 10
mail    | 2018-03-12 23:19:15,597 INFO spawned: 'mailserver' with pid 11
mail    |
mail    | #
mail    | 2018-03-12 23:19:15,645 INFO success: postsrsd entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | 2018-03-12 23:19:15,645 INFO success: mailserver entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | #
mail    | # ENV
mail    | #
mail    | #
mail    |
mail    | SASLAUTHD_LDAP_FILTER=
mail    | FETCHMAIL_POLL=300
mail    | POSTGREY_DELAY=300
mail    | SASLAUTHD_LDAP_SEARCH_BASE=
mail    | SASLAUTHD_MECHANISMS=
mail    | SA_SPAM_SUBJECT=***SPAM*****
mail    | SPOOF_PROTECTION=0
mail    | LDAP_BIND_PW=
mail    | HOSTNAME=mail.domain.com
mail    | ENABLE_LDAP=0
mail    | OVERRIDE_HOSTNAME=
mail    | SASLAUTHD_LDAP_PASSWORD=
mail    | LDAP_SERVER_HOST=
mail    | POSTMASTER_ADDRESS=postmaster@domain.com
mail    | LDAP_SEARCH_BASE=
mail    | LDAP_BIND_DN=
mail    | PUID=1000
mail    | ENABLE_POSTFIX_VIRTUAL_TRANSPORT=
mail    | TLS_LEVEL=modern
mail    | SA_TAG=2.0
mail    | ENABLE_MANAGESIEVE=0
mail    | SMTP_ONLY=0
mail    | PERMIT_DOCKER=network
mail    | SA_TAG2=6.31
mail    | PGID=1000
mail    | PWD=/
mail    | POSTFIX_DAGENT=
mail    | LDAP_QUERY_FILTER_USER=
mail    | DOVECOT_TLS=
mail    | HOME=/root
mail    | SA_KILL=6.31
mail    | DEBIAN_FRONTEND=noninteractive
mail    | DMS_DEBUG=1
mail    | ENABLE_FAIL2BAN=1
mail    | SSL_TYPE=letsencrypt
mail    | SUPERVISOR_PROCESS_NAME=mailserver
mail    | POSTSCREEN_ACTION=enforce
mail    | SUPERVISOR_ENABLED=1
mail    | LDAP_QUERY_FILTER_ALIAS=
mail    | SASLAUTHD_LDAP_SERVER=
mail    | SASL_PASSWD=
mail    | SASLAUTHD_LDAP_BIND_DN=
mail    | ENABLE_SPAMASSASSIN=0
mail    | ENABLE_POSTGREY=0
mail    | ENABLE_FETCHMAIL=0
mail    | VIRUSMAILS_DELETE_DELAY=
mail    | SASLAUTHD_MECH_OPTIONS=
mail    | SHLVL=1
mail    | ENABLE_SASLAUTHD=0
mail    | SUPERVISOR_GROUP_NAME=mailserver
mail    | DOVECOT_USER_FILTER=
mail    | ENABLE_CLAMAV=0
mail    | SASLAUTHD_LDAP_SSL=
mail    | PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
mail    | DOVECOT_PASS_FILTER=
mail    | POSTGREY_TEXT=Delayed by postgrey
mail    | ONE_DIR=0
mail    | SUPERVISOR_SERVER_URL=unix:///dev/shm/supervisor.sock
mail    | POSTGREY_MAX_AGE=35
mail    | ENABLE_POP3=1
mail    | LDAP_QUERY_FILTER_GROUP=
mail    | LDAP_START_TLS=
mail    | _=/usr/bin/printenv
mail    |
mail    | #
mail    | #
mail    | # docker-mailserver
mail    | #
mail    | #
mail    |
mail    | Initializing setup
mail    |   Registering check,setup,fix,misc and start-daemons functions
mail    |   * _check_environment_variables() registered
mail    |   * _check_hostname() registered
mail    |   * _setup_default_vars() registered
mail    |   * _setup_dovecot() registered
mail    |   * _setup_dovecot_local_user() registered
mail    |   * _setup_dkim() registered
mail    |   * _setup_ssl() registered
mail    |   * _setup_docker_permit() registered
mail    |   * _setup_mailname() registered
mail    |   * _setup_amavis() registered
mail    |   * _setup_dmarc_hostname() registered
mail    |   * _setup_postfix_hostname() registered
mail    |   * _setup_dovecot_hostname() registered
mail    |   * _setup_postfix_sasl() registered
mail    |   * _setup_postfix_override_configuration() registered
mail    |   * _setup_postfix_sasl_password() registered
mail    |   * _setup_security_stack() registered
mail    |   * _setup_postfix_aliases() registered
mail    |   * _setup_postfix_vhost() registered
mail    |   * _setup_postfix_dhparam() registered
mail    |   * _setup_postfix_postscreen() registered
mail    |   * _setup_postfix_access_control() registered
mail    |   * _setup_environment() registered
mail    |   * _fix_var_mail_permissions() registered
mail    |   * _fix_var_amavis_permissions() registered
mail    |   * _fix_cleanup_clamav() registered
mail    |   * _misc_save_states() registered
mail    |   * _start_daemons_cron() registered
mail    |   * _start_daemons_rsyslog() registered
mail    |   * _start_daemons_dovecot() registered
mail    |   * _start_daemons_opendkim() registered
mail    |   * _start_daemons_opendmarc() registered
mail    |   * _start_daemons_postfix() registered
mail    |   * _start_daemons_fail2ban() registered
mail    |   * _start_changedetector() registered
mail    |   * _start_daemons_amavis() registered
mail    | Checking configuration
mail    |   Check that there are no conflicts with env variables [_check_environment_variables]
mail    |   Check that hostname/domainname is provided or overidden (no default docker hostname/kubernetes) [_check_hostname]
mail    |   * Domain has been set to domain.com
mail    |   * Hostname has been set to mail.domain.com
mail    | Configuring mail server
mail    |   Setting up default variables [_setup_default_vars]
mail    |   * Set ENABLE_LDAP=0
mail    |   * Set OVERRIDE_HOSTNAME=
mail    |   * Set DMS_DEBUG=1
mail    |   * Set ENABLE_CLAMAV=0
mail    |   * Set ENABLE_FAIL2BAN=1
mail    |   * Set FETCHMAIL_POLL=300
mail    |   * Set TLS_LEVEL=modern
mail    |   * Set ENABLE_SPAMASSASSIN=0
mail    |   * Set POSTGREY_DELAY=300
mail    |   * Set POSTGREY_TEXT=Delayed by postgrey
mail    |   * Set ENABLE_POSTGREY=0
mail    |   * Set POSTGREY_MAX_AGE=35
mail    |   * Set POSTMASTER_ADDRESS=postmaster@domain.com
mail    |   * Set ENABLE_FETCHMAIL=0
mail    |   * Set ENABLE_MANAGESIEVE=0
mail    |   * Set POSTSCREEN_ACTION=enforce
mail    |   * Set ENABLE_POP3=1
mail    |   * Set ENABLE_SASLAUTHD=0
mail    |   * Set SMTP_ONLY=0
mail    |   * Set SPOOF_PROTECTION=0
mail    |   Setting up Dovecot
mail    | 2018-03-12 23:19:15,757 INFO exited: postsrsd (exit status 0; expected)
mail    |   Setting up Dovecot Local User
mail    |   * Checking file line endings
mail    |   * Regenerating postfix user list
mail    |   * user 'requests' for domain 'domain.com' with password '********'
mail    |   Setting up DKIM
mail    |   * DKIM keys added for: domain.com
mail    |   * Changing permissions on /etc/opendkim
mail    |   Setting up SSL
mail    |   * TLS configured with 'modern' ciphers
mail    |   Setting up PERMIT_DOCKER Option
mail    |   * Adding docker network in my networks
mail    |   Setting up Mailname
mail    |   * Creating /etc/mailname
mail    |   Setting up Amavis
mail    |   * Applying hostname to /etc/amavis/conf.d/05-node_id
mail    |   Setting up dmarc
mail    |   * Applying hostname to /etc/opendmarc.conf
mail    |   Applying hostname and domainname to Postfix
mail    |   * Applying hostname to /etc/postfix/main.cf
mail    |   Applying hostname to Dovecot
mail    |   * Applying hostname to /etc/dovecot/conf.d/15-lda.conf
mail    |   Setting up Postfix Override configuration
mail    |   * No extra postfix settings loaded because optional '/tmp/docker-mailserver/postfix-main.cf' not provided.
mail    |   * No extra postfix settings loaded because optional '/tmp/docker-mailserver/postfix-master.cf' not provided.
mail    |   * set the compatibility level to 2
mail    |   Setting up Postfix SASL Password
mail    |   * Warning: 'SASL_PASSWD' is not provided. /etc/postfix/sasl_passwd not created.
mail    |   Setting up Security Stack
mail    |   * Spamassassin is disabled. You can enable it with 'ENABLE_SPAMASSASSIN=1'
mail    |   * Clamav is disabled. You can enable it with 'ENABLE_CLAMAV=1'
mail    |   * Fail2ban enabled
mail    |   Setting up Postfix Aliases
mail    |   * Warning 'config/postfix-virtual.cf' is not provided. No mail alias/forward created.
mail    |   Setting up Postfix vhost
mail    |   Setting up Postfix dhparam
mail    |   * No state dir, we use the dhparams generated on image creation
mail    |   * Configuring postscreen
mail    |   * Configuring user access
mail    |   Setting up /etc/environment
mail    |   Checking /var/mail permissions
mail    |   * Fixing /var/mail permissions
mail    |   Checking $amavis_state_dir permissions
mail    |   * Permissions in /var/lib/amavis look OK
mail    |   Cleaning up disabled Clamav
mail    | Starting Misc
mail    | Starting mail server
mail    |   Starting cron2018-03-12 23:19:19,168 INFO spawned: 'cron' with pid 107
mail    | 2018-03-12 23:19:19,168 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | cron: started
mail    |   Starting rsyslog 2018-03-12 23:19:19,383 INFO spawned: 'rsyslog' with pid 109
mail    | 2018-03-12 23:19:19,383 INFO success: rsyslog entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | rsyslog: started
mail    |   Starting dovecot services  Starting pop3 services2018-03-12 23:19:19,592 INFO spawned: 'dovecot' with pid 114
mail    | 2018-03-12 23:19:19,592 INFO success: dovecot entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | dovecot: started
mail    |   Starting opendkim 2018-03-12 23:19:19,818 INFO spawned: 'opendkim' with pid 123
mail    | 2018-03-12 23:19:19,818 INFO success: opendkim entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | opendkim: started
mail    |   Starting opendmarc 2018-03-12 23:19:19,985 INFO spawned: 'opendmarc' with pid 125
mail    | 2018-03-12 23:19:19,985 INFO success: opendmarc entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | opendmarc: started
mail    |   Starting postfix2018-03-12 23:19:20,153 INFO spawned: 'postfix' with pid 138
mail    | 2018-03-12 23:19:20,154 INFO success: postfix entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | postfix: started
mail    |   Starting fail2ban 2018-03-12 23:19:20,324 INFO spawned: 'fail2ban' with pid 167
mail    | 2018-03-12 23:19:20,324 INFO success: fail2ban entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | fail2ban: started
mail    |   Starting changedetector2018-03-12 23:19:20,493 INFO spawned: 'changedetector' with pid 170
mail    | 2018-03-12 23:19:20,493 INFO success: changedetector entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | changedetector: started
mail    |   Starting amavis2018-03-12 23:19:20,673 INFO spawned: 'amavis' with pid 199
mail    | 2018-03-12 23:19:20,673 INFO success: amavis entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | amavis: started
mail    |
mail    | #
mail    | # mail.domain.com is up and running
mail    | #
mail    |
mail    | Mar 12 23:19:21 mail amavis[199]: starting. /usr/sbin/amavisd-new at mail.domain.com amavisd-new-2.10.1 (20141025), Unicode aware
mail    | Mar 12 23:19:21 mail postfix/master[973]: daemon started -- version 3.1.8, configuration /etc/postfix
mail    | Mar 12 23:19:21 mail amavis[199]: Net::Server: Group Not Defined.  Defaulting to EGID '111 111'
mail    | Mar 12 23:19:21 mail amavis[199]: Net::Server: User Not Defined.  Defaulting to EUID '109'
mail    | Mar 12 23:19:21 mail amavis[199]: Module Amavis::Conf        2.404
mail    | Mar 12 23:19:21 mail amavis[199]: Module Archive::Zip        1.59
mail    | Mar 12 23:19:21 mail amavis[199]: Module BerkeleyDB          0.55
mail    | Mar 12 23:19:21 mail amavis[199]: Module Compress::Raw::Zlib 2.069
mail    | Mar 12 23:19:21 mail amavis[199]: Module Compress::Zlib      2.069001
mail    | Mar 12 23:19:21 mail amavis[199]: Module Digest::MD5         2.54
mail    | Mar 12 23:19:21 mail amavis[199]: Module Encode              2.80_01
mail    | Mar 12 23:19:21 mail amavis[199]: Module File::Temp          0.2304
mail    | Mar 12 23:19:21 mail amavis[199]: Module IO::Socket::IP      0.37
mail    | Mar 12 23:19:21 mail amavis[199]: Module MIME::Entity        5.508
mail    | Mar 12 23:19:21 mail amavis[199]: Module MIME::Parser        5.508
mail    | Mar 12 23:19:21 mail amavis[199]: Module MIME::Tools         5.508
mail    | Mar 12 23:19:21 mail amavis[199]: Module Mail::Header        2.18
mail    | Mar 12 23:19:21 mail amavis[199]: Module Mail::Internet      2.18
mail    | Mar 12 23:19:21 mail amavis[199]: Module Net::LibIDN         0.12
mail    | Mar 12 23:19:21 mail amavis[199]: Module Net::Server         2.008
mail    | Mar 12 23:19:21 mail amavis[199]: Module Scalar::Util        1.4202
mail    | Mar 12 23:19:21 mail amavis[199]: Module Socket              2.020_03
mail    | Mar 12 23:19:21 mail amavis[199]: Module Time::HiRes         1.9733
mail    | Mar 12 23:19:21 mail amavis[199]: Module Unix::Syslog        1.1
mail    | Mar 12 23:19:21 mail amavis[199]: Amavis::ZMQ code     NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: Amavis::DB code      loaded
mail    | Mar 12 23:19:21 mail amavis[199]: SQL base code        NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: SQL::Log code        NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: SQL::Quarantine      NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: Lookup::SQL code     NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: Lookup::LDAP code    NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: AM.PDP-in proto code loaded
mail    | Mar 12 23:19:21 mail amavis[199]: SMTP-in proto code   loaded
mail    | Mar 12 23:19:21 mail amavis[199]: Courier proto code   NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: SMTP-out proto code  loaded
mail    | Mar 12 23:19:21 mail amavis[199]: Pipe-out proto code  NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: BSMTP-out proto code NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: Local-out proto code loaded
mail    | Mar 12 23:19:21 mail amavis[199]: OS_Fingerprint code  NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: ANTI-VIRUS code      NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: ANTI-SPAM code       NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: ANTI-SPAM-EXT code   NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: ANTI-SPAM-C code     NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: ANTI-SPAM-SA code    NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: Unpackers code       loaded
mail    | Mar 12 23:19:21 mail amavis[199]: DKIM code            NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: Tools code           NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: Found $file            at /usr/bin/file
mail    | Mar 12 23:19:21 mail amavis[199]: No $altermime,         not using it
mail    | Mar 12 23:19:21 mail amavis[199]: Internal decoder for .mail
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .Z    at /bin/uncompress
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .gz   at /bin/gzip -d
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .bz2  at /bin/bzip2 -d
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .xz   at /usr/bin/xz -dc
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .lzma at /usr/bin/xz -dc --format=lzma
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .lrz  at /usr/bin/lrzip -q -k -d -o -
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .lzo  at /usr/bin/lzop -d
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .lz4  at /usr/bin/lz4c -d
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .rpm  at /usr/bin/rpm2cpio
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .cpio at /bin/pax
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .tar  at /bin/pax
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .deb  at /usr/bin/ar
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .rar  at /usr/bin/unrar-free
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .arj  at /usr/bin/arj
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .arc  at /usr/bin/nomarch
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .zoo  at /usr/bin/zoo
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .doc  at /usr/bin/ripole
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .cab  at /usr/bin/cabextract
mail    | Mar 12 23:19:21 mail amavis[199]: Internal decoder for .tnef
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .zip  at /usr/bin/7za
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .kmz  at /usr/bin/7za
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .7z   at /usr/bin/7zr
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .jar  at /usr/bin/7z
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .swf  at /usr/bin/7z
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .lha  at /usr/bin/7z
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .iso  at /usr/bin/7z
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .exe  at /usr/bin/unrar-free; /usr/bin/arj
mail    | Mar 12 23:19:21 mail amavis[199]: No decoder for       .F
mail    | Mar 12 23:19:21 mail amavis[199]: Deleting db files  in /var/lib/amavis/db
mail    | Mar 12 23:19:21 mail amavis[199]: Creating db in /var/lib/amavis/db/; BerkeleyDB 0.55, libdb 5.3
mail    | Mar 12 23:21:32 mail dovecot: ssl-params: SSL parameters regeneration completed

Okay. Your environment variable for the ssl type is correctly set. That means the start-mailserver script is not able to access the letsencrypt files.
So either if [ -e "/etc/letsencrypt/live/$HOSTNAME/fullchain.pem" ]; then or if [ -e "/etc/letsencrypt/live/$HOSTNAME/privkey.pem" ]; then fails.
You could test what is not working with adding a notify line (see the other lines around).
I will provide an pull request maybe tomorrow what prints what fails in some of these cases.
When you cannot find a way to fix it by your own: Have a look at the wiki page for custom ssl certs. You could easily add your letsencrypt files manually :)

Ah that's good to hear. I can see what happens around those lines in start-mailserver.sh. I would be able to add the notify, but I don't know how to apply it to my docker-composer. I'll take a look at the custom SSL certs. Cheers!

Perhaps this helps. I tried the manual files. The log returns (in green):
mail    |   * Configuring certificates using cert /tmp/ssl/live/domain.com/cert.pem and key /tmp/ssl/live/domain.com/privkey.pem
mail    |   * SSL configured with 'Manual' certificates

However I see amazon servers is doing something like a ping every few seconds (very annoying by the way) because it keeps giving me:
mail    | Mar 13 23:33:07 mail postfix/submission/smtpd[992]: SSL_accept error from ec2-13-126-248-148.ap-south-1.compute.amazonaws.com[13.126.248.148]: -1
mail    | Mar 13 23:33:07 mail postfix/submission/smtpd[992]: warning: TLS library problem: error:1417D102:SSL routines:tls_process_client_hello:unsupported protocol:../ssl/statem/statem_srvr.c:974:
mail    | Mar 13 23:33:07 mail postfix/submission/smtpd[992]: lost connection after STARTTLS from ec2-13-126-248-148.ap-south-1.compute.amazonaws.com[13.126.248.148]
mail    | Mar 13 23:33:07 mail postfix/submission/smtpd[992]: disconnect from ec2-13-126-248-148.ap-south-1.compute.amazonaws.com[13.126.248.148] ehlo=1 starttls=0/1 commands=1/2

However Gmail still returns SSL error: unknown CA (alert 48), and the log for that requests still returns:
mail    | Mar 13 23:33:25 mail dovecot: pop3-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=102.102.101.10, lip=172.20.0.2, TLS: Disconnected, session=<zudZr1Nnw47RVYCJ>

I'm starting to doubt the way I did my Let's Encrypt validation. As I mentioned before I validated through http, but it's for the subdomain mail.domain.com. Not sure if that's enough to get the required certificates?

The unsupported protocol error could be added by setting TLS_LEVEL to intermediate. This also enables  TLSv1, TLSv1.1 and some older ciphers that are disabled by default.
I'm not sure why Gmail is not accepting the CA. Did you test your SSL configuration with checktls.com?

That website helped me out. I used cert.pem instead of fullchain.pem. Now it's working, with TLS_LEVEL set to intermediate. Thank you so much!

authors: akmet rourke

repo: tomav/docker-mailserver


text:
Amazon SES Manual DKIM Signing #470

#470

Thank you @ifokeev!

authors: ifokeev tomav


text:
Added reject_authenticated_sender_login_mismatch

Kudos to @TechnicLab who had the idea and found that "undesired behaviour"
This will deny authorized clients to send with a different than their owned mail-address.
So there remain some considerations:

With this in place people may not be sending mails under their aliases as well. (Except they configure an account for every alias(which they would have to do with a normal client program anyway))
Might their be use cases where someone wants to send mails as a different user?

See also #825
partially solves #524

@17Halbe Thank you! It is working for LDAP.

Yes I don't see a reason why this shouldn't be working with ldap.
It is comparing the logged in email address with the one sending. If they are identical, the request is granted. This shouldn't make a difference for ldap.

Yes, as I said, if root@mailserver.com trys to send an email as (his alias) postmaster@mailserver.com, it would fail.
In that case one has to set a seperate mailaccount for postmaster@mailserver.com up to be able to send mail from postmaster@mailserver.com.
I don't know, does anyone does that?
Receiving mails for your alias of course is not a problem.
In my opinion the behaviour of not allowing someone to send a mail with a spoofed address (even non existing ones) should be default. If someone would need to send an email via an alias, they should actually consider setting this account up as a regular one. IMHO that's not what aliases are for. I always considered them as more restrictive "catch-all" addresses.
How do you use them?

I'm still thinking about this. we could probably work around the alias problem if you consider it neccessary.

@17Halbe in my personal setup I use on the iPhone mail app and there I have setup some aliasses so that I can email with the same account back but maintain the alias in the reply.
Example:
main account: johan@domain.com
Alias: alias@domain.com
When I reply to a email that arrived on the alias it replies with the alias from and should be valid to me.
If not this might break more then desired on multiple setups.

Ok, we then need a setup differenciating between ldap and the standard setup.
I will provide a solution for the standard setup. I‘ll try my best for ldap.
Do we need an exception for mails containing delimiters as well?

I don't use it but if you can include them yes.

We have set up our servers internally to send reports from servername@domain.com so the source of the report can easily be identified.  All these severs are not set up to receive mail, so they do not have valid accounts in the email system.  If suddenly all those reports started being rejected, that would be a problem.  If you do decide to make changes like this, please do NOT make them default, and be sure to add a well documented control such as an env variable to allow users to choose which behavior they wish.
Regards,
:D
Sent from my iPhone

On Mar 4, 2018, at 12:05 PM, Johan Smits notifications@github.com wrote:
I don't use it but if you can include them yes.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Just to clarify, this PR is just denying a logged in(!) user to send mails with another than his account address or (going to be implemented) his alias addresses.
Would this work for your setup?

We have not gotten emails to be sent without logging in a user with smtp. We are currently using a test user login (the same login for multiple servers) as a work around until we are able to determine why our servers can’t simply deliver unauthenticated on port 25 to a local user.  While this isn’t a preferred long term solution, I would not like to see this work around permanently denied in the future. We should at least implement an env variable to control this behaviour.
:D
Sent from my iPhone

On Mar 4, 2018, at 1:56 PM, 17Halbe notifications@github.com wrote:
Just to clarify, this PR is just denying a logged in(!) user to send mails with another than his account address or (going to be implemented) his alias addresses.
Would this work for your setup?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

So I introduced a new env variable, which default value is deactivating reject_authenticated_sender_login_mismatch.
For a new upcoming release in the hopefully upcoming release channel system I would suggest to implement reject_authenticated_sender_login_mismatch as a default. It's really easy to delete out of main.cf if one really needs to work around it.
In the end I think most people would agree that sending mails for a different account is wrong. ;)
Tested ldap implementation only in the test.bats. Can someone please check if this would work with an alias in ldap. I just copy pasted the ldap config from https://github.com/tomav/docker-mailserver/pull/825
bind             = yes
bind_dn          = cn=admin,dc=domain,dc=com
bind_pw          = admin
query_filter     = (&(|(mail=%s)(mailalias=%s))(mailEnabled=TRUE))
result_attribute = mail
search_base      = ou=people,dc=domain,dc=com
server_host      = mail.domain.com
start_tls        = no
version          = 3

Does that look correct?

Nevermind. Just reverted the ldap lookup to the already existing tables and added test for aliases as well. This should now be a safe ldap implementation!

This looks very good! Waiting for @tomav to let me know when the release branches are setup to I can merge it.

So if you're going to merge this to a new release I would suggest switching the default to enable SPOOF_PROTECTION. This PR can be merged without changing the current behaviour at all. It's disabled by default. You have to set SPOOF_PROTECTION to 1 to make it work.
What about merging it now and I'll provide a PR for the new release to make spoof protection the default setting?

@17Halbe thats a good idea. Merged it so you can provide a new PR once the branching is done.

Good work on this @17Halbe!
:D

authors: 17Halbe TechnicLab dmcgrandle johansmitsnl


text:
prevent duplicates -- issues

Although the previous message and the next message is identical, the new toast message renders. Kindly advise.

Will be resolved when this is merged with the master.

Released v2.8.0

authors: RangarajKaushikSundar tomchentw

repo: tomchentw/react-toastr


text:
Add a jetton balance tracker ("lost & found")

In case the user lost address for a jetton he minted
— using an indexed api (for example with tonApi jetton/getBalances)
— scanning the chain for TXNs containing the mint operation
challenges are:

dealing with older TXNs (if they were archived, that is)
distinguishing jettons which the user only holds compares to a minter created by him

Привет! Когда будет зачисление TON???

authors: IGCrypto shaharyakir

repo: ton-blockchain/minter


text:
associated resources support for controllers

This is a 🐞 bug fix.
This is a 🙋♂ feature or enhancement.

[ ] I've added tests (if it's a bug, feature or enhancement)
[ ] I've adjusted the documentation (if it's a feature or enhancement)
[x] The test suite passes (run bundle exec rspec to verify this)

Summary
Allow creation of Assocaited Resources within controllers.
Context
Gitter question
Version Changes
patch

Released in v2.3.1

repo: tongueroo/jets


text:
Add rocket display function

In this parrt of the project, we I have implemented the following;

Fetched data from the API
Displayed this data on the rockets page
styled according to the design.

Hi @Divinity-dev  👏🏽,
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉
Highlights

Good job working on the requested changes 👏
No Linter error ✅

Optional suggestions
Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you consider them as they can improve your code. Some of them were simply missed by the previous reviewer, and addressing them will improve your application.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Remember to tag me(@rotimiazeez) in your question so I can receive the notification.

As described in the Code reviews limits policy, you have a limited number of reviews per project (check the exact number in your Dashboard). If you think the code review was unfair, you can request a second opinion using this form.

authors: Divinity-dev tonnytech


text:
Why not reciving sketch or psd files?

Look at Webbsy or ExportUI they receive a file with layers named with a sentence for better conversion.

These packages rely on designers to name the layers and order it properly. So if the designer messes up, the output will not be ideal. This approach reduces the workload of the designer and frontend developer, while the later can focus more on the logic behind the UI.

@r4kh answered the question perfectly!

authors: MatheusRV r4kh tonybeltramelli