From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2013310EC for ; Sun, 19 Mar 2023 09:02:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=inria.fr; s=dc; h=date:from:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=Ukm8dSqGOWpoJwHSWY019Qn+Q/OtHQ+9Jf6Du/QX7Eo=; b=Bh9RFDVE8dnuPBzpbMbjrfa7FM6abf4i5257S3WU8+4KbQzZfsIrHimf ZJ6eO8WST1CqZI1/qTaicpFMpivLRCMQZ7XBcbcu6IDqMAd3RL8mUrChq ae1tID0RnMCAvGGK8arXZ/1KYwWxNN/foj5Vx2W3WOHJ6ccKj4N3/OCjf Y=; Authentication-Results: mail3-relais-sop.national.inria.fr; dkim=none (message not signed) header.i=none; spf=SoftFail smtp.mailfrom=julia.lawall@inria.fr; dmarc=fail (p=none dis=none) d=inria.fr X-IronPort-AV: E=Sophos;i="5.98,273,1673910000"; d="scan'208";a="50599408" Received: from 231.85.89.92.rev.sfr.net (HELO hadrien) ([92.89.85.231]) by mail3-relais-sop.national.inria.fr with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Mar 2023 10:02:47 +0100 Date: Sun, 19 Mar 2023 10:02:46 +0100 (CET) From: Julia Lawall X-X-Sender: jll@hadrien To: Sumitra Sharma cc: bagasdotme@gmail.com, outreachy@lists.linux.dev Subject: Re: your mail In-Reply-To: <20230319085612.GD50179@sumitra.com> Message-ID: References: <20230319080955.GA50179@sumitra.com> <20230319085612.GD50179@sumitra.com> User-Agent: Alpine 2.22 (DEB 394 2020-01-19) Precedence: bulk X-Mailing-List: outreachy@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII 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 " > > > set use_from=yes > > > set edit_headers=yes > > > > > > # IMAP settings > > > set imap_user = "username@gmail.com" > > > set imap_pass = "" > > > > > > # SMTP settings > > > set smtp_url = "smtps://username@smtp.gmail.com" > > > set smtp_pass = "" > > > > > > # 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. > > > Does "" 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 "" it is not clear what is expected. julia