Gnus development mailing list
 help / color / mirror / Atom feed
From: Albert Krewinkel <krewinkel@moltkeplatz.de>
To: ding@gnus.org
Subject: Updates to sieve-manage.el
Date: Sat, 04 May 2013 16:48:28 +0200	[thread overview]
Message-ID: <87sj22dcn7.fsf@caffelatte.moltkeplatz.de> (raw)

Hi all,

I tried to get sieve-manage working with my dovecot/pigeonhole server.
It didn't quite work out of the box, so I made a few adjustments to the
code.  The result is in my github-repo at
git://github.com/tarleb/gnus.git (in the "sieve" branch).

Most noticable changes:
 - Added support for starttls
 - Allowing multibyte-process buffers (couldn't get
   string-parsing/encoding working without it)
 - Slightly nicer looking code (IMHO of course)
 - An ugly workaround which I intend to fix by the end of
   next week.

Any feedback on the code or advice on how to get this upstream would be
highly appreciated.

Thanks,

Albert



             reply	other threads:[~2013-05-04 14:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-04 14:48 Albert Krewinkel [this message]
2013-05-05 12:50 ` Julien Danjou
2013-05-06 16:27   ` Albert Krewinkel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sj22dcn7.fsf@caffelatte.moltkeplatz.de \
    --to=krewinkel@moltkeplatz.de \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).