From: Pankaj Gupta <pagupta@vmware.com>
To: Ali Alnubani <alialnu@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Jochen Behrens <jbehrens@vmware.com>,
Yong Wang <yongwang@vmware.com>,
Sreeram Ravinoothala <sravinoothala@vmware.com>,
"admin@dpdk.org" <admin@dpdk.org>
Subject: Re: Help: e-mail did not go through to the dev@dpdk.org list.
Date: Mon, 2 May 2022 19:52:45 +0000 [thread overview]
Message-ID: <BYAPR05MB5624E26285C5E2B8B83E9C56C9C19@BYAPR05MB5624.namprd05.prod.outlook.com> (raw)
In-Reply-To: <DM4PR12MB516736AB848480B0C9BF1F5FDAC19@DM4PR12MB5167.namprd12.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2490 bytes --]
Hi All,
I was able to send the email to dev@dpdk.org<mailto:dev@dpdk.org> today after doing following git and smtp configuration.
Git config:
git config --global sendemail.smtpencryption tls
git config --global sendemail.smtpserver mail.messagingengine.com
git config --global sendemail.smtpuser tanuk@fastmail.fm
git config --global sendemail.smtpserverport 587
git config --global sendemail.smtppass hackme
SMTP config:
root=YourAccount@gmail.com
mailhub=smtp.gmail.com:587
AuthUser=YourAccount@gmail.com
AuthPass=YourGmailPassword
UseTLS=YES
UseSTARTTLS=YES
I can see my emails at https://mails.dpdk.org/archives/dev/2022-May/author.html
Thanks,
Pankaj
From: Ali Alnubani <alialnu@nvidia.com>
Date: Monday, May 2, 2022 at 12:25 PM
To: Pankaj Gupta <pagupta@vmware.com>, dev@dpdk.org <dev@dpdk.org>
Cc: Jochen Behrens <jbehrens@vmware.com>, Yong Wang <yongwang@vmware.com>, Sreeram Ravinoothala <sravinoothala@vmware.com>, admin@dpdk.org <admin@dpdk.org>
Subject: Re: Help: e-mail did not go through to the dev@dpdk.org list.
⚠ External Email
> From: Pankaj Gupta <pagupta@vmware.com>
> Sent: Saturday, April 30, 2022 12:23 AM
> To: dev-request@dpdk.org <dev-request@dpdk.org>; dev@dpdk.org <dev@dpdk.org>
> Cc: Jochen Behrens <jbehrens@vmware.com>; Yong Wang <yongwang@vmware.com>; Sreeram Ravinoothala <sravinoothala@vmware.com>
> Subject: Help: e-mail did not go through to the dev@dpdk.org list.
>
> Hi All,
> I sent 8 patches, twice today, but these patches are not visible in archive https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmails.dpdk.org%2Farchives%2Fdev%2F2022-April%2Fthread.html&data=05%7C01%7Cpagupta%40vmware.com%7Cc81938f995674696327b08da2c718c1a%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C1%7C637871163457119867%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=NrqMQd7NW0f8%2BaR%2B7Lj05PSj3AUKjUe4%2B%2F57NBGhkzI%3D&reserved=0.
>
>
> How do I figure out what went wrong with those emails?
Hello Pankaj,
Did you make sure the SMTP status was successful in git-send-email's output? Can you please double check for any errors and if there aren't any, provide the timestamp and message-id of one of the patches?
Thanks,
Ali
________________________________
⚠ External Email: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender.
[-- Attachment #2: Type: text/html, Size: 8641 bytes --]
prev parent reply other threads:[~2022-05-02 19:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 21:23 Pankaj Gupta
2022-05-02 19:25 ` Ali Alnubani
2022-05-02 19:52 ` Pankaj Gupta [this message]
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=BYAPR05MB5624E26285C5E2B8B83E9C56C9C19@BYAPR05MB5624.namprd05.prod.outlook.com \
--to=pagupta@vmware.com \
--cc=admin@dpdk.org \
--cc=alialnu@nvidia.com \
--cc=dev@dpdk.org \
--cc=jbehrens@vmware.com \
--cc=sravinoothala@vmware.com \
--cc=yongwang@vmware.com \
/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;
as well as URLs for NNTP newsgroup(s).