2 .\" Title: git-imap-send
3 .\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author]
4 .\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
7 .\" Source: Git 2.34.1.182.ge773545c7f
10 .TH "GIT\-IMAP\-SEND" "1" "12/10/2021" "Git 2\&.34\&.1\&.182\&.ge77354" "Git Manual"
11 .\" -----------------------------------------------------------------
12 .\" * Define some portability stuff
13 .\" -----------------------------------------------------------------
14 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
15 .\" http://bugs.debian.org/507673
16 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
17 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
20 .\" -----------------------------------------------------------------
21 .\" * set default formatting
22 .\" -----------------------------------------------------------------
23 .\" disable hyphenation
25 .\" disable justification (adjust text to left margin only)
27 .\" -----------------------------------------------------------------
28 .\" * MAIN CONTENT STARTS HERE *
29 .\" -----------------------------------------------------------------
31 git-imap-send \- Send a collection of patches from stdin to an IMAP folder
35 \fIgit imap\-send\fR [\-v] [\-q] [\-\-[no\-]curl]
40 This command uploads a mailbox generated with \fIgit format\-patch\fR into an IMAP drafts folder\&. This allows patches to be sent as other email is when using mail clients that cannot read mailbox files directly\&. The command also works with any general mailbox in which emails have the fields "From", "Date", and "Subject" in that order\&.
42 Typical usage is something like:
44 git format\-patch \-\-signoff \-\-stdout \-\-attach origin | git imap\-send
59 Use libcurl to communicate with the IMAP server, unless tunneling into it\&. Ignored if Git was built without the USE_CURL_FOR_IMAP_SEND option set\&.
64 Talk to the IMAP server using git\(cqs own IMAP routines instead of using libcurl\&. Ignored if Git was built with the NO_OPENSSL option set\&.
68 To use the tool, \fBimap\&.folder\fR and either \fBimap\&.tunnel\fR or \fBimap\&.host\fR must be set to appropriate values\&.
72 The folder to drop the mails into, which is typically the Drafts folder\&. For example: "INBOX\&.Drafts", "INBOX/Drafts" or "[Gmail]/Drafts"\&. Required\&.
77 Command used to setup a tunnel to the IMAP server through which commands will be piped instead of using a direct network connection to the server\&. Required when imap\&.host is not set\&.
82 A URL identifying the server\&. Use an
84 prefix for non\-secure connections and an
86 prefix for secure connections\&. Ignored when imap\&.tunnel is set, but required otherwise\&.
91 The username to use when logging in to the server\&.
96 The password to use when logging in to the server\&.
101 An integer port number to connect to on the server\&. Defaults to 143 for imap:// hosts and 993 for imaps:// hosts\&. Ignored when imap\&.tunnel is set\&.
106 A boolean to enable/disable verification of the server certificate used by the SSL/TLS connection\&. Default is
107 \fBtrue\fR\&. Ignored when imap\&.tunnel is set\&.
110 imap\&.preformattedHTML
112 A boolean to enable/disable the use of html encoding when sending a patch\&. An html encoded patch will be bracketed with <pre> and have a content type of text/html\&. Ironically, enabling this option causes Thunderbird to send the patch as a plain/text, format=fixed email\&. Default is
118 Specify authenticate method for authentication with IMAP server\&. If Git was built with the NO_CURL option, or if your curl version is older than 7\&.34\&.0, or if you\(cqre running git\-imap\-send with the
120 option, the only supported method is
121 \fICRAM\-MD5\fR\&. If this is not set then
123 uses the basic IMAP plaintext LOGIN command\&.
134 folder = "INBOX\&.Drafts"
135 tunnel = "ssh \-q \-C user@example\&.com /usr/bin/imapd \&./Maildir 2> /dev/null"
148 folder = "INBOX\&.Drafts"
149 host = imap://imap\&.example\&.com
157 Using direct mode with SSL:
164 folder = "INBOX\&.Drafts"
165 host = imaps://imap\&.example\&.com
180 .nr an-no-space-flag 1
188 You may want to use \fBsslVerify=false\fR while troubleshooting, if you suspect that the reason you are having trouble connecting is because the certificate you use at the private server \fBexample\&.com\fR you are trying to set up (or have set up) may not be verified correctly\&.
192 Using Gmail\(cqs IMAP interface:
199 folder = "[Gmail]/Drafts"
200 host = imaps://imap\&.gmail\&.com
201 user = user@gmail\&.com
213 .nr an-no-space-flag 1
221 You might need to instead use: \fBfolder = "[Google Mail]/Drafts"\fR if you get an error that the "Folder doesn\(cqt exist"\&.
229 .nr an-no-space-flag 1
237 If your Gmail account is set to another language than English, the name of the "Drafts" folder will be localized\&.
241 Once the commits are ready to be sent, run the following command:
247 $ git format\-patch \-\-cover\-letter \-M \-\-stdout origin/master | git imap\-send
253 Just make sure to disable line wrapping in the email client (Gmail\(cqs web interface will wrap lines no matter what, so you need to use a real IMAP client)\&.
256 It is still your responsibility to make sure that the email message sent by your email program meets the standards of your project\&. Many projects do not like patches to be attached\&. Some mail agents will transform patches (e\&.g\&. wrap lines, send them as format=flowed) in ways that make them fail\&. You will get angry flames ridiculing you if you don\(cqt check this\&.
258 Thunderbird in particular is known to be problematic\&. Thunderbird users may wish to visit this web page for more information: \m[blue]\fBhttp://kb\&.mozillazine\&.org/Plain_text_e\-mail_\-_Thunderbird#Completely_plain_email\fR\m[]
261 \fBgit-format-patch\fR(1), \fBgit-send-email\fR(1), mbox(5)
264 Part of the \fBgit\fR(1) suite