When jarsigner says "Key Associated with [alias] not a private key" it almost certainly meant to say that you got your password wrong.

Add your comment...

Related Posts

• Fortune Cookies for Android 1.50
• Where did that app icon go, Android?
• Immature Gmail Exploit
• Is it safe to open securedoc.html (Cisco Registered Envelope)?
• The Secret Diary of a Xamarin Android Developer, Aged 48 1/3

(All Code Posts)

(Published to the Fediverse as: Not a Private Key #code #monodroid Check that you have the right password when jarsigner says Key Associated with alias not a private key. )

Here’s a quick code snippet that configures SmtpClient to send email using Gmail’s SMTP server:

This can be frustratingly difficult to get right so I’ll run through each setting quickly.

DeliveryMethod: Set to SmtpDeliveryMethod.Network, the alternatives are copying the email to a directory for pickup by a different application. We want to connect directly to Gmail.

UseDefaultCredentials: False, as we’ll be providing our own credentials later. Setting properties in the right order is apparently important for SmtpClient, although the Microsoft documentation doesn’t mention this. Make sure you set UseDefaultCredentials to false before setting the Credentials property.

EnableSsl: True. SSL or TLS is required.

Host: smtp.gmail.com for this example. Note that this server restricts you to sending 2,000 emails per day. There is a less restrictive option for G Suite customers (smtp-relay.gmail.com) and a more restrictive server that can only send messages to Gmail or G Suite addresses (aspmx.l.google.com).

Port: Google says to use 465 for SSL and 587 for TLS. I’ve found that 587 with EnableSSL set to true works fine.

Credentials: Your Gmail address and password in a NetworkCredential. If your account has 2 step (multi factor) authentication then this won’t work. You can generate an app password easily and use this instead of your regular password. It’s also possible to use OAuth.

In the comments below Shika Helmy suggests also setting the Timeout property to 20000.

You can now use smtp.Send() to send the email.

Because it’s likely to be your personal account and there is a 2,000 message cap on sending I’d only recommend using this for small scale projects. You don’t want to get your Gmail account blocked. For higher volume I’d look at using SendGrid or similar.

One last note - while I’ve used SmtpClient for all sorts of trivial email needs over the years the latest Microsoft documentation marks it obsolete and warns:

SmtpClient and its network of types are poorly designed, we strongly recommend you use https://github.com/jstedfast/MailKit and https://github.com/jstedfast/MimeKit instead

Hope this expanded article helps. I still come back here periodically to cut and paste rather than mess up the property order again...

Add your comment...

Related Posts

• Immature Gmail Exploit
• I Love Email
• Moon on a Wire
• Reading and Writing Office 365 Excel from a Console app using the Microsoft.Graph C# Client API
• Outlook/Office iCal feed 400 bad request error with C# WebClient

(All Code Posts)

(Published to the Fediverse as: Sending email via GMail in C#/.NET using SmtpClient #code #smtp #email #google How to use the C# SmtpClient to send an email through the Gmail SMTP server (updated for two factor authentication). )

I've developed a bunch of stupid, niche and vaguely promising apps on top of the Twitter API. During that time I've slogged through various painful and rapid shifts like changing IDs, authentication schemes and diktats handed down on which parts of the ecosystem Twitter would like to control. I've had to roll my own OAuth and even re-word a blog post to Twitter Support's satisfaction to get a blocked application unblocked again. It's been a pretty frustrating experience but worth rolling with the punches until the past week.

Twitter suspended Cleat, a tool for posting from the command line. So I emailed to ask why, too much effort for them to explain the rationale at the time they're putting the suspension in place I guess. I got an auto-response asking for information they must have already had and I replied to this. A few days later I still hadn't heard back so I emailed again and the ticket had been automatically closed. 

So far just the standard fuck-off-and-die support that you'd expect from a growing company that no longer wants to talk to it's users. But the auto-reply directed me to https://support.twitter.com/forms/ to file a new ticket. None of the options there relate to developers or a suspended application. I tried filing a ticket under 'deactivated account' which seemed the closest.

That form has a hard-coded 'With love,' valediction. Whoever thought that was cute should go through the process of trying to get help a few times. 

This attempt auto-responded to say that my account was not suspended, and would I like to fuck-off-and-die or got back to the forms center?

So I tried another form that actually seemed to submit but haven't heard anything back.

I'd be happy to update my software if I know which vague shifting facet of the Twitter terms of use I'd fallen foul of. Or at least I would have been. I'm just so sick of it that I've pulled Cleat and I'm done with any more personal projects that use the Twitter API. 

Add your comment...

Related Posts

• bye, bye, Miss Deprecated API
• Pulling the plug on Facebook and Twitter, Tweet Archive
• Got It
• The Trust Project, Fake News and a Partial Facebook Uninstall
• Fight Facebook with Email

(All Code Posts)

(Published to the Fediverse as: Twitter's API has got too painful for me #code #twitter #cleat #commandline #api Twitter's opaque API policies have led to me no longer developing on the platform. )

Testing posting by email with a picture of the moon from last night...

I've extended BlogEngine.NET to post by email. Not horrible for the very specific case of this blog and a short list of email clients. I shudder to think of extending it to the general emails and different templates.

Add your comment...

Related Posts

• Migrating from Blogger to BlogEngine.NET
• Geotagging posts in BlogEngine.NET
• The curious case of the missing slugs (in BlogEngine.net 2.8)
• Fight Facebook with Email
• Converting Blogger ATOM export to BlogML

(All Code Posts)

(Published to the Fediverse as: Moon on a Wire #code #blogengine.net Picture of the Moon close to a wire. This is actually a test of posting by email from blogengine.net. )