From: Sumitra Sharma <sumitraartsy@gmail.com>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: bagasdotme@gmail.com, outreachy@lists.linux.dev
Subject: Re: your mail
Date: Sun, 19 Mar 2023 02:53:28 -0700 [thread overview]
Message-ID: <20230319095328.GE50179@sumitra.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2303190956470.2867@hadrien>
On Sun, Mar 19, 2023 at 10:02:46AM +0100, Julia Lawall wrote:
>
>
> On Sun, 19 Mar 2023, Sumitra Sharma wrote:
>
> > On Sun, Mar 19, 2023 at 09:35:50AM +0100, Julia Lawall wrote:
> > > > Actually, the only issue I faced was that the outreachyfirstpatch
> > > > document does not contain the information of how one can set their inbox in mutt.
> > > > Due to which I had problems to send and reply mails. This below
> > > > configuration update will enable the inbox at the client side.
> > > >
> > > > How about this...
> > > >
> > > > Under the section "Configure esmtp":
> > > >
> > > > ###
> > > > Next, set up the mail client, mutt, with some defaults, by creating a .muttrc file in your homedirectory:
> > > >
> > > > Note: The imap_pass, smtp_pass would be the App password or
> > > > the mailbox password.
> > > >
> > > > set sendmail="/usr/bin/esmtp"
> > > > set envelope_from=yes
> > > > set from="Your Name <my.email@gmail.com>"
> > > > set use_from=yes
> > > > set edit_headers=yes
> > > >
> > > > # IMAP settings
> > > > set imap_user = "username@gmail.com"
> > > > set imap_pass = "<mailbox password>"
> > > >
> > > > # SMTP settings
> > > > set smtp_url = "smtps://username@smtp.gmail.com"
> > > > set smtp_pass = "<mailbox password>"
> > > >
> > > > # Remote Gmail folders
> > > > set folder = "imaps://imap.gmail.com/"
> > > > set spoolfile = "+INBOX"
> > > > set postponed = "+[Gmail]/Drafts"
> > > > set record = "+[Gmail]/Sent Mail"
> > > > set trash = "+[Gmail]/Trash"
> > > > ###
> > >
> > > Does this have anything to do with esmpt?
> > >
> >
> > In the current version of the outreachy firstpatch document the configuration
> > steps for .esmtp and .muttrc are written under the heading
> > "Configure esmtp" and also to configure esmtp we are creating the muttrc
> > file. So, both are linked in a way.
>
> I don't think so. Comfiguring esmtp requires adding some information to
> the .muttrc, but people who don't want to configure esmtp may also want to
> add information to the .muttrc.
>
Then, why dont we rename the section as "Configure MTA"
then it will go as follows:
> >
> > > Does "<mailbox password>" mean that you have to put your password in plain
> > > text?
> > >
> >
> > Yes, but it is always prefered to use the app password for better security.
>
> The existing text about sending mesages with mutt says:
>
> identity "my.email@gmail.com"
> hostname smtp.gmail.com:587
> username "my.email@gmail.com"
> password "ThisIsNotARealPassWord"
> starttls required
>
> Why not put "ThisIsNotARealPassWord" in your text as well, if that is
> what you expect people to do?
>
> That is, when you put something in quotes, the reader doedn't know whether
> they are supposed to put exactly the thing that you have put in the quotes
> or something else. I guess that for eg "smtps://username@smtp.gmail.com"
> they should fill in their real username. But for "<mailbox password>" it
> is not clear what is expected.
>
###
Configure MTA
Note: These instructions assume you're using esmtp, but if you already have another mail transfer agent (MTA) installed, you do not need to install esmtp. Instead, change the .muttrc file "sendmail" line to be the path to your MTA. Mutt uses ssmtp by default, so if your MTA is ssmtp, you can leave that line out entirely.
First, create a .esmtprc file with the right permissions:
touch ~/.esmtprc
chmod g-rwx ~/.esmtprc
chmod o-rwx ~/.esmtprc
Edit the .esmtprc in your home directory, and add lines like this:
identity "my.email@gmail.com"
hostname smtp.gmail.com:587
username "my.email@gmail.com"
password "ThisIsNotARealPassWord"
starttls required
(For Yahoo mail, replace hostname line with:
hostname smtp.mail.yahoo.com:587
Next, set up the mail client, mutt, with some defaults, by creating a .muttrc file in your homedirectory:
Note: The imap_pass, smtp_pass would be the App password or the mailbox password.
set sendmail="/usr/bin/esmtp"
set envelope_from=yes
set from="Your Name <my.email@gmail.com>"
set use_from=yes
set edit_headers=yes
# IMAP settings
set imap_user = "username@gmail.com"
set imap_pass = "<ThisIsNotARealPassWord>"
# SMTP settings
set smtp_url = "smtps://username@smtp.gmail.com"
set smtp_pass = "<ThisIsNotARealPassWord>"
# Remote Gmail folders
set folder = "imaps://imap.gmail.com/"
set spoolfile = "+INBOX"
set postponed = "+[Gmail]/Drafts"
set record = "+[Gmail]/Sent Mail"
set trash = "+[Gmail]/Trash"
###
Regards,
Sumitra
> julia
next prev parent reply other threads:[~2023-03-19 9:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 16:36 Sumitra Sharma
2023-03-17 16:47 ` your mail Julia Lawall
2023-03-17 18:17 ` Sumitra Sharma
2023-03-19 8:09 ` Sumitra Sharma
2023-03-19 8:35 ` Julia Lawall
2023-03-19 8:56 ` Sumitra Sharma
2023-03-19 9:02 ` Julia Lawall
2023-03-19 9:53 ` Sumitra Sharma [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-16 12:31 Gilbert Adikankwu
2023-10-16 12:34 ` your mail Julia Lawall
2023-10-16 12:42 ` Gilbert Adikankwu
2023-10-16 13:23 ` Julia Lawall
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=20230319095328.GE50179@sumitra.com \
--to=sumitraartsy@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=julia.lawall@inria.fr \
--cc=outreachy@lists.linux.dev \
/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