Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook



The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic

Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.

If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.

Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.

Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

SparkPost Deprecating TLSv1.0 - next steps?

  • Filter
  • Time
  • Show
Clear All
new posts

    SparkPost Deprecating TLSv1.0 - next steps?

    I'm a bit late on this scene and have been caught without preparing for this change. SparkPost's tip to maintain continuity doesn't help. Here's the advice,

    "If you are using TLSv1.0, you should do one (1) of the following:

    If you are using proprietary code, then have your in-house development team update the code to use at least TLSv1.1.
    If you are using 3rd party software, then verify that your client supports at least TLSv1.1 and upgrade the client."
    I am the 'development team' and I have no idea how to get my 'secret code' back into action.

    Do the SparkPost users out there have any tips for my 'next steps?'

    Thanks in advance.


    Re: SparkPost Deprecating TLSv1.0 - next steps?


    As there's no built-in SparkPost functions in V11 I've written my own. I'm now using this with AA as well as it's not possible to specify the security protocol using the built-in 'email_send_sparkpost()'.

    Sample function below...

    FUNCTION E_Send_SparkPost AS C (API_key as C, email_from as C, email_alias as C, email_to as C, email_subject as C, email_message as C, email_attachments as C, email_html_message as C)
    dim result as C
    dim send_it as C
    dim ps as p
    dim pm as p
    result = email_smtp_open(ps, "", 587, "SMTP_Injection",API_key, "STARTTLS")
    if result then
    	pm.from = email_from
    	pm.from_alias = email_alias = email_to
    	pm.subject = email_subject
    	pm.message = email_message
    	pm.attachments = email_attachments
    	pm.html_message = email_html_message
    	'Inline images for HTML messages - set IRelated to 'true' if sending inline images as attachments
    	if email_html_message <> "" then
    		pm.lRelated = .T.
    		pm.lRelated = .F.
    	end if		
    	send_it = email_smtp_send(pm,ps)
    end if
    result = ps.buffer
    E_Send_SparkPost = result
    For desktop users, I've also been testing SparkPost using the Alpha email settings on the desktop and although you can't specifiy STARTTLS on the sending tab of the email settings form you can modify the windows registry directly with the correct value. For A5V11 the location is 'Computer\HKEY_CURRENT_USER\Software\Alpha Software\Alpha Five 11.0\init\email\profiles\profile1\SMTPSecureConnectionType' and should be set to 'STARTTLS' . A5V10 uses a similar path and AA uses 'Alpha Anywhere 12.0' Once set up this will work using the standard A5 emailing functions.

    If you're supplying your own parameters then just specify "STARTTLS" in your email_smtp_open command instead of "TLS"

    Hope this helps any others using sparkpost.