search for: mcnaughti

https://bugzilla.mindrot.org/show_bug.cgi?id=1585 andrew at mcnaughty.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrew at mcnaughty.com -- You are receiving this mail because: You are watching the assignee of the bug.

https://bugzilla.mindrot.org/show_bug.cgi?id=1585 --- Comment #15 from andrew at mcnaughty.com --- +1 The usefulness of this is increasing with the increasing use of automation in system administration. It's increasingly feasible to automate and distribute configuration files populated with host details, but there's no good way to integrate this with a user's own preferences. --

https://bugzilla.mindrot.org/show_bug.cgi?id=1585 --- Comment #18 from andrew at mcnaughty.com --- I think this is an obviously useful thing to add to openssh, and I've yet to see any argument against it, but given that it's been 6 years I'm not holding my breath. As a simple workaround, I'd suggest people create a directory called `.ssh/config.d`, touch `.ssh/config.d/00_empty`

I have a fairly standard antispam/dspam setup: postfix delivers to dspam, which classifies and tags the mail, and then passes it to postfix which uses sieve to put mail into the appropriate folders based on dspam's classification. I also have the antispam plugin watching mail being moved between folders and re-training dpsam accordingly. If I now add some sieve filter rules which put

On 21/08/15 19:49, Guillaume Lakano - DOVECOT wrote: > Aug 20 20:21:14 mail imap: antispam: running mailtrain backend program parameter 1 -D --username=guillaume.XXXX at mydomain.com > Aug 20 20:21:14 mail imap: antispam: running mailtrain backend program parameter 2 --spam That looks like it should be three parameters, not two? Also, read this:

On 21/09/15 17:28, Alex Bulan wrote: > The result is the same with or without "<" before the file path. With > "<" the inode atime is updated at Dovecot startup, so the file is at > least opened, but Dovecot still can't verify the cert. > > The only place in the Wiki that shows an example of ssl_client_ca_file > is on this page, and there's no

I put up a question on serverfault first, which has the details, including a stack trace: http://serverfault.com/questions/713687/dovecot-antispam-error-storing-mail . Details also copied below. Is this a known bug? If I built dovecot from source rather than using the Ubuntu 14.04 packages, would I expect that to help? Are there any configuration details that might be relevant? (dovecot -n