[chirp_devel] Submitting patches via SMTP

[Pavel Milanes Costa (CO7WT)]

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 at gmail.com>
method = smtp
to = chirp_devel at intrepid.danplanet.com
cc =  pavelmc at gmail.com

[smtp]
host = smtp.gmail.com
username = pavelmc at 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 at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
> Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers