^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1) .. _email_clients:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 3) Email clients info for Linux
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 4) ============================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 5)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 6) Git
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 7) ---
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 8)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 9) These days most developers use ``git send-email`` instead of regular
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10) email clients. The man page for this is quite good. On the receiving
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11) end, maintainers use ``git am`` to apply the patches.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13) If you are new to ``git`` then send your first patch to yourself. Save it
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14) as raw text including all the headers. Run ``git am raw_email.txt`` and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) then review the changelog with ``git log``. When that works then send
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16) the patch to the appropriate mailing list(s).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18) General Preferences
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19) -------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 21) Patches for the Linux kernel are submitted via email, preferably as
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 22) inline text in the body of the email. Some maintainers accept
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 23) attachments, but then the attachments should have content-type
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 24) ``text/plain``. However, attachments are generally frowned upon because
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 25) it makes quoting portions of the patch more difficult in the patch
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 26) review process.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 27)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 28) It's also strongly recommended that you use plain text in your email body,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 29) for patches and other emails alike. https://useplaintext.email may be useful
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 30) for information on how to configure your preferred email client, as well as
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 31) listing recommended email clients should you not already have a preference.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 32)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 33) Email clients that are used for Linux kernel patches should send the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 34) patch text untouched. For example, they should not modify or delete tabs
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 35) or spaces, even at the beginning or end of lines.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 36)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 37) Don't send patches with ``format=flowed``. This can cause unexpected
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 38) and unwanted line breaks.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 39)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 40) Don't let your email client do automatic word wrapping for you.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 41) This can also corrupt your patch.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 42)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 43) Email clients should not modify the character set encoding of the text.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 44) Emailed patches should be in ASCII or UTF-8 encoding only.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 45) If you configure your email client to send emails with UTF-8 encoding,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 46) you avoid some possible charset problems.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 47)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 48) Email clients should generate and maintain "References:" or "In-Reply-To:"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 49) headers so that mail threading is not broken.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 50)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 51) Copy-and-paste (or cut-and-paste) usually does not work for patches
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 52) because tabs are converted to spaces. Using xclipboard, xclip, and/or
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 53) xcutsel may work, but it's best to test this for yourself or just avoid
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 54) copy-and-paste.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 55)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 56) Don't use PGP/GPG signatures in mail that contains patches.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 57) This breaks many scripts that read and apply the patches.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 58) (This should be fixable.)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 59)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 60) It's a good idea to send a patch to yourself, save the received message,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 61) and successfully apply it with 'patch' before sending patches to Linux
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 62) mailing lists.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 63)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 64)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 65) Some email client (MUA) hints
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 66) -----------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 67)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 68) Here are some specific MUA configuration hints for editing and sending
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 69) patches for the Linux kernel. These are not meant to be complete
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 70) software package configuration summaries.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 71)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 72)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 73) Legend:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 74)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 75) - TUI = text-based user interface
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 76) - GUI = graphical user interface
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 77)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 78) Alpine (TUI)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 79) ************
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 80)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 81) Config options:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 82)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 83) In the :menuselection:`Sending Preferences` section:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 84)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 85) - :menuselection:`Do Not Send Flowed Text` must be ``enabled``
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 86) - :menuselection:`Strip Whitespace Before Sending` must be ``disabled``
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 87)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 88) When composing the message, the cursor should be placed where the patch
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 89) should appear, and then pressing :kbd:`CTRL-R` let you specify the patch file
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 90) to insert into the message.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 91)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 92) Claws Mail (GUI)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 93) ****************
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 94)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 95) Works. Some people use this successfully for patches.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 96)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 97) To insert a patch use :menuselection:`Message-->Insert File` (:kbd:`CTRL-I`)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 98) or an external editor.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 99)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 100) If the inserted patch has to be edited in the Claws composition window
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 101) "Auto wrapping" in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 102) :menuselection:`Configuration-->Preferences-->Compose-->Wrapping` should be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 103) disabled.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 104)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 105) Evolution (GUI)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 106) ***************
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 107)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 108) Some people use this successfully for patches.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 109)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 110) When composing mail select: Preformat
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 111) from :menuselection:`Format-->Paragraph Style-->Preformatted` (:kbd:`CTRL-7`)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 112) or the toolbar
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 113)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 114) Then use:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 115) :menuselection:`Insert-->Text File...` (:kbd:`ALT-N x`)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 116) to insert the patch.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 117)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 118) You can also ``diff -Nru old.c new.c | xclip``, select
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 119) :menuselection:`Preformat`, then paste with the middle button.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 120)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 121) Kmail (GUI)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 122) ***********
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 123)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 124) Some people use Kmail successfully for patches.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 125)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 126) The default setting of not composing in HTML is appropriate; do not
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 127) enable it.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 128)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 129) When composing an email, under options, uncheck "word wrap". The only
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 130) disadvantage is any text you type in the email will not be word-wrapped
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 131) so you will have to manually word wrap text before the patch. The easiest
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 132) way around this is to compose your email with word wrap enabled, then save
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 133) it as a draft. Once you pull it up again from your drafts it is now hard
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 134) word-wrapped and you can uncheck "word wrap" without losing the existing
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 135) wrapping.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 136)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 137) At the bottom of your email, put the commonly-used patch delimiter before
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 138) inserting your patch: three hyphens (``---``).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 139)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 140) Then from the :menuselection:`Message` menu item, select
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 141) :menuselection:`insert file` and choose your patch.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 142) As an added bonus you can customise the message creation toolbar menu
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 143) and put the :menuselection:`insert file` icon there.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 144)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 145) Make the composer window wide enough so that no lines wrap. As of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 146) KMail 1.13.5 (KDE 4.5.4), KMail will apply word wrapping when sending
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 147) the email if the lines wrap in the composer window. Having word wrapping
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 148) disabled in the Options menu isn't enough. Thus, if your patch has very
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 149) long lines, you must make the composer window very wide before sending
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 150) the email. See: https://bugs.kde.org/show_bug.cgi?id=174034
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 151)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 152) You can safely GPG sign attachments, but inlined text is preferred for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 153) patches so do not GPG sign them. Signing patches that have been inserted
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 154) as inlined text will make them tricky to extract from their 7-bit encoding.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 155)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 156) If you absolutely must send patches as attachments instead of inlining
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 157) them as text, right click on the attachment and select :menuselection:`properties`,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 158) and highlight :menuselection:`Suggest automatic display` to make the attachment
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 159) inlined to make it more viewable.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 160)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 161) When saving patches that are sent as inlined text, select the email that
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 162) contains the patch from the message list pane, right click and select
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 163) :menuselection:`save as`. You can use the whole email unmodified as a patch
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 164) if it was properly composed. Emails are saved as read-write for user only so
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 165) you will have to chmod them to make them group and world readable if you copy
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 166) them elsewhere.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 167)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 168) Lotus Notes (GUI)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 169) *****************
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 170)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 171) Run away from it.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 172)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 173) IBM Verse (Web GUI)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 174) *******************
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 175)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 176) See Lotus Notes.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 177)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 178) Mutt (TUI)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 179) **********
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 180)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 181) Plenty of Linux developers use ``mutt``, so it must work pretty well.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 182)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 183) Mutt doesn't come with an editor, so whatever editor you use should be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 184) used in a way that there are no automatic linebreaks. Most editors have
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 185) an :menuselection:`insert file` option that inserts the contents of a file
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 186) unaltered.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 187)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 188) To use ``vim`` with mutt::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 189)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 190) set editor="vi"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 191)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 192) If using xclip, type the command::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 193)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 194) :set paste
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 195)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 196) before middle button or shift-insert or use::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 197)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 198) :r filename
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 199)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 200) if you want to include the patch inline.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 201) (a)ttach works fine without ``set paste``.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 202)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 203) You can also generate patches with ``git format-patch`` and then use Mutt
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 204) to send them::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 205)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 206) $ mutt -H 0001-some-bug-fix.patch
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 207)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 208) Config options:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 209)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 210) It should work with default settings.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 211) However, it's a good idea to set the ``send_charset`` to::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 212)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 213) set send_charset="us-ascii:utf-8"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 214)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 215) Mutt is highly customizable. Here is a minimum configuration to start
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 216) using Mutt to send patches through Gmail::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 217)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 218) # .muttrc
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 219) # ================ IMAP ====================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 220) set imap_user = 'yourusername@gmail.com'
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 221) set imap_pass = 'yourpassword'
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 222) set spoolfile = imaps://imap.gmail.com/INBOX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 223) set folder = imaps://imap.gmail.com/
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 224) set record="imaps://imap.gmail.com/[Gmail]/Sent Mail"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 225) set postponed="imaps://imap.gmail.com/[Gmail]/Drafts"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 226) set mbox="imaps://imap.gmail.com/[Gmail]/All Mail"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 227)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 228) # ================ SMTP ====================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 229) set smtp_url = "smtp://username@smtp.gmail.com:587/"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 230) set smtp_pass = $imap_pass
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 231) set ssl_force_tls = yes # Require encrypted connection
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 232)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 233) # ================ Composition ====================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 234) set editor = `echo \$EDITOR`
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 235) set edit_headers = yes # See the headers when editing
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 236) set charset = UTF-8 # value of $LANG; also fallback for send_charset
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 237) # Sender, email address, and sign-off line must match
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 238) unset use_domain # because joe@localhost is just embarrassing
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 239) set realname = "YOUR NAME"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 240) set from = "username@gmail.com"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 241) set use_from = yes
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 242)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 243) The Mutt docs have lots more information:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 244)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 245) https://gitlab.com/muttmua/mutt/-/wikis/UseCases/Gmail
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 246)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 247) http://www.mutt.org/doc/manual/
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 248)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 249) Pine (TUI)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 250) **********
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 251)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 252) Pine has had some whitespace truncation issues in the past, but these
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 253) should all be fixed now.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 254)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 255) Use alpine (pine's successor) if you can.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 256)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 257) Config options:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 258)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 259) - ``quell-flowed-text`` is needed for recent versions
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 260) - the ``no-strip-whitespace-before-send`` option is needed
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 261)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 262)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 263) Sylpheed (GUI)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 264) **************
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 265)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 266) - Works well for inlining text (or using attachments).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 267) - Allows use of an external editor.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 268) - Is slow on large folders.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 269) - Won't do TLS SMTP auth over a non-SSL connection.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 270) - Has a helpful ruler bar in the compose window.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 271) - Adding addresses to address book doesn't understand the display name
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 272) properly.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 273)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 274) Thunderbird (GUI)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 275) *****************
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 276)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 277) Thunderbird is an Outlook clone that likes to mangle text, but there are ways
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 278) to coerce it into behaving.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 279)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 280) - Allow use of an external editor:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 281) The easiest thing to do with Thunderbird and patches is to use an
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 282) "external editor" extension and then just use your favorite ``$EDITOR``
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 283) for reading/merging patches into the body text. To do this, download
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 284) and install the extension, then add a button for it using
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 285) :menuselection:`View-->Toolbars-->Customize...` and finally just click on it
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 286) when in the :menuselection:`Compose` dialog.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 287)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 288) Please note that "external editor" requires that your editor must not
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 289) fork, or in other words, the editor must not return before closing.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 290) You may have to pass additional flags or change the settings of your
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 291) editor. Most notably if you are using gvim then you must pass the -f
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 292) option to gvim by putting ``/usr/bin/gvim -f`` (if the binary is in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 293) ``/usr/bin``) to the text editor field in :menuselection:`external editor`
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 294) settings. If you are using some other editor then please read its manual
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 295) to find out how to do this.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 296)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 297) To beat some sense out of the internal editor, do this:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 298)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 299) - Edit your Thunderbird config settings so that it won't use ``format=flowed``.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 300) Go to :menuselection:`edit-->preferences-->advanced-->config editor` to bring up
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 301) the thunderbird's registry editor.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 302)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 303) - Set ``mailnews.send_plaintext_flowed`` to ``false``
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 304)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 305) - Set ``mailnews.wraplength`` from ``72`` to ``0``
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 306)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 307) - :menuselection:`View-->Message Body As-->Plain Text`
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 308)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 309) - :menuselection:`View-->Character Encoding-->Unicode (UTF-8)`
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 310)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 311) TkRat (GUI)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 312) ***********
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 313)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 314) Works. Use "Insert file..." or external editor.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 315)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 316) Gmail (Web GUI)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 317) ***************
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 318)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 319) Does not work for sending patches.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 320)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 321) Gmail web client converts tabs to spaces automatically.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 322)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 323) At the same time it wraps lines every 78 chars with CRLF style line breaks
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 324) although tab2space problem can be solved with external editor.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 325)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 326) Another problem is that Gmail will base64-encode any message that has a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 327) non-ASCII character. That includes things like European names.
Orange Pi5 kernel
Deprecated Linux kernel 5.10.110 for OrangePi 5/5B/5+ boards
3 Commits
0 Branches
0 Tags