6 git-imap-send - Send a collection of patches from stdin to an IMAP folder
17 This command uploads a mailbox generated with 'git format-patch'
18 into an IMAP drafts folder. This allows patches to be sent as
19 other email is when using mail clients that cannot read mailbox
20 files directly. The command also works with any general mailbox
21 in which emails have the fields "From", "Date", and "Subject" in
24 Typical usage is something like:
26 git format-patch --signoff --stdout --attach origin | git imap-send
32 To use the tool, imap.folder and either imap.tunnel or imap.host must be set
33 to appropriate values.
39 The folder to drop the mails into, which is typically the Drafts
40 folder. For example: "INBOX.Drafts", "INBOX/Drafts" or
41 "[Gmail]/Drafts". Required to use imap-send.
44 Command used to setup a tunnel to the IMAP server through which
45 commands will be piped instead of using a direct network connection
46 to the server. Required when imap.host is not set to use imap-send.
49 A URL identifying the server. Use a `imap://` prefix for non-secure
50 connections and a `imaps://` prefix for secure connections.
51 Ignored when imap.tunnel is set, but required to use imap-send
55 The username to use when logging in to the server.
58 The password to use when logging in to the server.
61 An integer port number to connect to on the server.
62 Defaults to 143 for imap:// hosts and 993 for imaps:// hosts.
63 Ignored when imap.tunnel is set.
66 A boolean to enable/disable verification of the server certificate
67 used by the SSL/TLS connection. Default is `true`. Ignored when
70 imap.preformattedHTML::
71 A boolean to enable/disable the use of html encoding when sending
72 a patch. An html encoded patch will be bracketed with <pre>
73 and have a content type of text/html. Ironically, enabling this
74 option causes Thunderbird to send the patch as a plain/text,
75 format=fixed email. Default is `false`.
78 Specify authenticate method for authentication with IMAP server.
79 Current supported method is 'CRAM-MD5' only. If this is not set
80 then 'git imap-send' uses the basic IMAP plaintext LOGIN command.
87 ..........................
89 folder = "INBOX.Drafts"
90 tunnel = "ssh -q -C user@example.com /usr/bin/imapd ./Maildir 2> /dev/null"
91 ..........................
95 .........................
97 folder = "INBOX.Drafts"
98 host = imap://imap.example.com
101 ..........................
103 Using direct mode with SSL:
105 .........................
107 folder = "INBOX.Drafts"
108 host = imaps://imap.example.com
113 ..........................
118 To submit patches using GMail's IMAP interface, first, edit your ~/.gitconfig
119 to specify your account settings:
123 folder = "[Gmail]/Drafts"
124 host = imaps://imap.gmail.com
125 user = user@gmail.com
130 You might need to instead use: folder = "[Google Mail]/Drafts" if you get an error
131 that the "Folder doesn't exist".
133 Once the commits are ready to be sent, run the following command:
135 $ git format-patch --cover-letter -M --stdout origin/master | git imap-send
137 Just make sure to disable line wrapping in the email client (GMail's web
138 interface will wrap lines no matter what, so you need to use a real
143 It is still your responsibility to make sure that the email message
144 sent by your email program meets the standards of your project.
145 Many projects do not like patches to be attached. Some mail
146 agents will transform patches (e.g. wrap lines, send them as
147 format=flowed) in ways that make them fail. You will get angry
148 flames ridiculing you if you don't check this.
150 Thunderbird in particular is known to be problematic. Thunderbird
151 users may wish to visit this web page for more information:
152 http://kb.mozillazine.org/Plain_text_e-mail_-_Thunderbird#Completely_plain_email
156 linkgit:git-format-patch[1], linkgit:git-send-email[1], mbox(5)
160 Part of the linkgit:git[1] suite