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

Emails with unwanted cc

  • Filter
  • Time
  • Show
Clear All
new posts

  • Emails with unwanted cc

    Tonight this happened again, and it's happened twice before, I don't know why. This is for an SAAS application, so there are many companies using it, and no one company should see anything from another, of course.

    I have a runtime instance that processes a work queue -- it simply runs on a timer every 60 seconds, works wonderfully.

    Much of what that runtime does is process and send emails -- I use the email_send2() function. And it sends thousands of emails a month, just fine.

    Except, tonight again, one user of one company showed us emails he received as a cc: recipient of another company's emails.

    So, the Xbasic instruction for the email is in the work queue, of course, and it proved that this email was never constructed with a cc

    And I have another function that stores a copy of the email just processed by the runtime instance, again proving that there was never a cc: recipient in the Xbasic.

    So I can prove all over the place that there's no cc: in the emails going out, yet an apparently random user from Company A is getting Company B's emails as the cc: recipient.

    And this is just what this user has showed us -- I have no idea if there might be others going out that aren't even reported to us. This isn't good at all.

    So, any ideas where to look, what to do, how to figure out what's going on?

  • #2
    Re: Emails with unwanted cc

    Because your are using desktop runtime parts maybe something is not thread safe and obviously is not. Maybe solution to this special problem is to always clear cc before sending email.


    • #3
      Re: Emails with unwanted cc

      I use the email_send2() function and am not having any issues. I send the emails one at a time though.
      Win 10 64 Development, Win 7 64 WAS 11-1, 2, Win 10 64 AA-1,2, MySql, dbForge Studio The Best MySQL GUI Tool IMHO.


      • #4
        Re: Emails with unwanted cc

        Thanks. Mine go one at a time as well.

        Ken - Good suggestion - I'm going to amend my code with a specific = ""


        • #5
          Re: Emails with unwanted cc

          Steve, my guess is you are sending emails in at least two parts of your script and is being set to a value in an early part and later you do send another email with no cc so it uses the value set earlier. So = "" as well as some or all all other Message values is a safe way forward in every block of email send code.


          • #6
            Re: Emails with unwanted cc

            Well, I've set the cc = "" in all my emails now.

            It's possible what you and Ken think is the issue, though why it only happens once in a while would seem to be a good question.

            The simplified version of the work queue processor execution function is:

            sql = "select * from WorkQueue where IsCompleted = 0"
            rs = cn.ResultSet
            flag = rs.nextRow()
            while flag
            	do_text ="WorkData")
            	for each line in do_text
            	flag = rs.nextRow()
            end while
            This isn't always of sending emails, but emails make up a major portion of the days' work. Each email begins with the standard dim message as p but that just may not be enough.

            I think I'm going to look into Evaluate_template_private() as well.


            • #7
              Re: Emails with unwanted cc

              Do you delete message prior to dimming it?
              Pat Bremkamp
              MindKicks Consulting


              • #8
                Re: Emails with unwanted cc

                I had not, Pat, until this discussion pointed pretty strongly to the probable source of the problem. It's among the amendments I've made to quash this.


                • #9
                  Re: Emails with unwanted cc

                  I don't think Evaluate_template_private() will be very useful in any multi-lined code as each line is evaluated in its own variable name-space.
                  The key here is really as Pat suggested, for the work queue processor, delete all pointer variables then dim. I say all because over time new scripts get added and who knows what they may contain. We are creatures of habit and tend to use the same variable names over and over in similar situations.