[chirp_devel] Submitting patches via SMTP
I am still having issues sending patches to the chirp-devel group. I am told that the don't make it to the mailing list. I have set up the following SMTP services...
working SMTP services SendInBlue kc9hi.net Gmail not working SMTP services Comcast
I just now got Gmail as my SMTP server working again. So I just sent the complete set of 7 new patches that I have created since the latest CHIRP daily build. I did not CC: myself and I did not receive them in my email from the mailing list. Therefore I have no idea if they were sent successfully.
If I have to, I can go back to having patchbomb send them directly to me so I can forward them to the chirp-devel mailing list. That seems to be the only thing lately that has been close to reliable.
Jim KC9HI
Hi Jim,
The best way to check is to look at the archives. Here you'll see that all your patches made it to the list:
http://intrepid.danplanet.com/pipermail/chirp_devel/2021-November/date.html
With GMail, you generally don't receive mail you sent, since GMail figures you've already seen it.
I haven't had issues sending patches via GMail, but (a) I haven't sent anywhere near as many as you have, and (b) I've since switched to submitting pull requests via GitHub instead.
Martin. KD6YAM
On Fri, Nov 26, 2021 at 10:46 AM Jim Unroe via chirp_devel < chirp_devel@intrepid.danplanet.com> wrote:
I am still having issues sending patches to the chirp-devel group. I am told that the don't make it to the mailing list. I have set up the following SMTP services...
working SMTP services SendInBlue kc9hi.net Gmail not working SMTP services Comcast
I just now got Gmail as my SMTP server working again. So I just sent the complete set of 7 new patches that I have created since the latest CHIRP daily build. I did not CC: myself and I did not receive them in my email from the mailing list. Therefore I have no idea if they were sent successfully.
If I have to, I can go back to having patchbomb send them directly to me so I can forward them to the chirp-devel mailing list. That seems to be the only thing lately that has been close to reliable.
Jim KC9HI _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
I use Gmail, but as gmail uses 2FA your normal password will not work.
You have to setup an application password for that service (google: gmail generate an application password), once you do that, all works. A sample of my `.hgrc` file on linux
===========%<=====================
[email] from = Pavel Milanes (CO7WT) pavelmc@gmail.com method = smtp to = chirp_devel@intrepid.danplanet.com cc = pavelmc@gmail.com
[smtp] host = smtp.gmail.com username = pavelmc@gmail.com password = nonononononononononono port = 587 tls = True
===========%<=====================
And as Jim mentions, the cc to you will not work as gmail ignore it.
73.
El 11/26/21 a las 1:45 p. m., Jim Unroe via chirp_devel escribió:
I am still having issues sending patches to the chirp-devel group. I am told that the don't make it to the mailing list. I have set up the following SMTP services...
working SMTP services SendInBlue kc9hi.net Gmail not working SMTP services Comcast
I just now got Gmail as my SMTP server working again. So I just sent the complete set of 7 new patches that I have created since the latest CHIRP daily build. I did not CC: myself and I did not receive them in my email from the mailing list. Therefore I have no idea if they were sent successfully.
If I have to, I can go back to having patchbomb send them directly to me so I can forward them to the chirp-devel mailing list. That seems to be the only thing lately that has been close to reliable.
Jim KC9HI _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
On Fri, Nov 26, 2021 at 2:59 PM Pavel Milanes Costa (CO7WT) via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
I use Gmail, but as gmail uses 2FA your normal password will not work.
You have to setup an application password for that service (google: gmail generate an application password), once you do that, all works. A sample of my `.hgrc` file on linux
Gmail hasn't forced me to use 2FA yet, so that currently isn't a factor for me.
===========%<=====================
[email] from = Pavel Milanes (CO7WT) pavelmc@gmail.com method = smtp to = chirp_devel@intrepid.danplanet.com cc = pavelmc@gmail.com
[smtp] host = smtp.gmail.com username = pavelmc@gmail.com password = nonononononononononono port = 587 tls = True
===========%<=====================
And as Jim mentions, the cc to you will not work as gmail ignore it.
Not exactly. I don't get the email back from the chirp-devel mailing list (chirp_devel@intrepid.danplanet.com). The cc: works fine with gmail. It is only when I include cc: to myself that I receive anything in my gmail email that shows that the patch was sent.
Jim KC9HI
participants (3)
-
Jim Unroe -
Martin Cooper -
Pavel Milanes Costa (CO7WT)