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

Announcement

Collapse

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

Problems with email_send()

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Problems with email_send()

    I know this has been discussed before, but I have a new wrinkle (pun intended :)).

    This is working great for me on the local webroot but not on the server. This has been reported by others. Pat had pointed out that when running from the remote server, the email profile must be specified. That did not correct the problem for me. I downloaded the latest patch - no luck.

    However, here is the wrinkle - If I run the full version on the remote server, and start the server from within it, then the email_send() works. It does not work from the stand alone application server. AND, 2 identical emails are sent every time I run the command! Remember, this works fine from the local host, and only one email is sent. From the remote server, does not work at all from the stand alone app server, and works, but sends 2 identical emails from the desktop app server.

    Does anyone have a clue as to what is going on here?

    Gary
    Gary S. Traub, Ph.D.


    #2
    Re: Problems with email_send()

    Gary

    Are you sending through a secure connection to the mail server or through a regular connection (ie port 110)?

    I haven't done enough investigation, but have seen the secure connection only work through the full version of A5 and not through the stand alone application server.

    If you can make a reproducible case, then submit a bug report.
    Al Buchholz
    Bookwood Systems, LTD
    Weekly QReportBuilder Webinars Thursday 1 pm CST

    Occam's Razor - KISS
    Normalize till it hurts - De-normalize till it works.
    Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
    When we triage a problem it is much easier to read sample systems than to read a mind.
    "Make it as simple as possible, but not simpler."
    Albert Einstein

    http://www.iadn.com/images/media/iadn_member.png

    Comment


      #3
      Re: Problems with email_send()

      Hi Al,

      I am using port 110.

      Here is the code that I am using:

      dim result as n
      'result=email_send(e_to,e_subj,e_msg)

      result=email_send(e_to,e_subj,e_body,"",e_cc,e_bcc,.F.,"","","default")

      if result=1
      ?"Email sent to "+e_to
      else if result=0
      ?"Email was not sent"
      end if

      By the way, the issue of sending to emails was do to my being bleery eyed - I actually had 2 email_send() statements. Commenting 1 of them eliminated the duplicate emails - of course :o

      It seems reproducible to me. I will submit a bug report. Thanks for the info.

      Gary
      Gary S. Traub, Ph.D.

      Comment


        #4
        Re: Problems with email_send()

        In a web application, I suggest that you send email using Xbasic that does NOT use profiles.

        The following example shows how you can send an email using lower level xbasic than email_send()

        Code:
        vTo = "[email protected]" 
        dim pm as P
        dim ps as P
        dim email_result as l
        vMessageStr = "here is may messsage."
        flag = email_smtp_open(ps, "mymailserver (e.g. mail.mycompany.com)", 25, "myuserid", "mypassword")
        if flag = .f. then 
                'report an error to the user
                end 
        end if 
        pm._to = vTo
        pm.from = "[email protected]"
        pm.from_alias = "Your Name"
        pm.subject = "Subject"
        pm.attachments = ""
        pm.html_message = "<HTML>Here is my message</HTML>"
        email_result = email_smtp_send(pm, ps)
        email_smtp_close(ps)

        Comment


          #5
          Re: Problems with email_send()

          Selwyn,

          I'm using email_send2() in several applications with no problem, and I subscribe to "if it ain't broke do something else that will make money", but I'm wondering if I should go back and change those in my spare time?

          Pat
          Pat Bremkamp
          MindKicks Consulting

          Comment


            #6
            Re: Problems with email_send()

            Originally posted by Pat Bremkamp View Post
            Selwyn,

            I'm using email_send2() in several applications with no problem, and I subscribe to "if it ain't broke do something else that will make money", but I'm wondering if I should go back and change those in my spare time?

            Pat
            There is no need to change what's working. email_send2() does however rely on a stored profile.

            The advantage of the technique i describe is that it does not use profiles - so you can see exactly what all of the email settings are and perhaps even dynamically change them.

            for example, say your web app is sending out a large mailing. you might want to send the first 100 from one mail server, then switch to a different server for the next 100 messages, and so on.

            Comment


              #7
              Re: Problems with email_send()

              I use email_send2() exclusively, but really see the benefit of what Selwyn described. I could control one or more profiles from my own database rather than from the server's email config, which is a little harder to get to.

              I'd use the full set of parameters to include the autowrap setting at the end, which should be set to false:

              email_smtp_send(pm,ps,.f.,.f.)
              Steve Wood
              See my profile on IADN

              Comment

              Working...
              X