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

THANK YOU ALPHA!! - SMTP - email_send_mandrill() - Super Super Fast Way of Sending thousands and thousands of emails...

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

    #16
    Re: THANK YOU ALPHA!! - SMTP - email_send_mandrill() - Super Super Fast Way of Sending thousands and thousands of emails.

    Hi Elbee,
    Thanks for the feedback. Maybe is an issue with their free service. I have been trying to get a support email so I can ask then why is this happening, but I cannot find any email or support forum for Mandrill, so if anybody have any email for them, please post it here or send it to me privately.

    Thanks!!!
    Edhy Rijo
    Progytech
    (Computer Consultants)
    The makers of CardTracking.Net
    www.progytech.com

    Comment


      #17
      Re: THANK YOU ALPHA!! - SMTP - email_send_mandrill() - Super Super Fast Way of Sending thousands and thousands of emails.

      I am currently on the free service. I really think that it is dependent on the time of day.
      Try different times and see how it goes.

      Comment


        #18
        Re: THANK YOU ALPHA!! - SMTP - email_send_mandrill() - Super Super Fast Way of Sending thousands and thousands of emails.

        Good thread! I wasn't even aware of the Mandrill API service until I saw this and now I'm tracking click throughs, opens, etc. Thanks for posting. With so many features it's great to have such an active forum community.
        Brad Weaver, President
        ComputerAid International
        Ottawa ON Canada
        Versailles KY USA
        www.compuaid.com

        Comment


          #19
          Re: THANK YOU ALPHA!! - SMTP - email_send_mandrill() - Super Super Fast Way of Sending thousands and thousands of emails.

          Curiosity is knocking over here, hoping to get some feedback as to how my alphaholics are using mandrill...

          I know when you set up sending single emails through mandrill you can get a result array that holds the following data...

          Here is what a typical item in the .result array looks like:
          result[1].email = “[email protected]
          result[1].status = “sent”
          result[1]._id = “some message id” — used to make queries against the Mandrill API for message status

          Now if I am using a datasource, under my current assumption I believe mandrill will only send back a response letting me know there wasn't any errors sending the data to its service (meaning it doesn't yet have responses for individual messages being delivered or rejected), is this correct? Or being the result is passed back to alpha as an array (per the information I put above) does this actually mean that really when I get a result from calling the send_to_mandrill() xbasic function I am getting back these unique ids and status' for each email (so really I could run through this array to find out which messages were sent)? If so has anyone already accomplished this?

          When I go to my API logs within mandrill I can see that these messages (using a datasource) are broken apart in the form of a JSON and each individual email message has its own "email, status, and _id" (the _id being the unique identifier for the message on mandrills servers). So, if the case is that the response I get back from mandrill to alpha with have this data but the status for each message will show as sent regardless if it was "delivered" or "reflected" (as for now the only thing mandrill knows is they received the data correctly and that is why they are saying it is "sent") but I'd have the unique ids so theoretically I could use them to query the mandrill service to find out the status of the message using their API perhaps (specifically the message.info calls and possibly using some sort of delay to give mandrills servers some time to send the messages)?

          Right now I haven't been sending out mass messages (20-30 at a time at most in a single datasource) but will soon be attempting to send a datasource with 500+ emails in it so it is likely this would need some sort of delay to let mandrills servers attempt to send the messages and receive responses before I query for the message status (or actually in this case when I do a message.info call using mandrills API it will be looking for the "state" of the message).

          Thanks for any and all feedback, please correct me if I am wrong in any of my assumptions!

          Comment


            #20
            Re: THANK YOU ALPHA!! - SMTP - email_send_mandrill() - Super Super Fast Way of Sending thousands and thousands of emails.

            So, I'm not able to get debugging to work on our server in live preview mode for an a5w page and I am having an issue getting a mandrill email set up using a datasource. However, when I moved the xbasic code to a dialog and set a button to run an ajax callback and run the same code (I mean literally no changes to the code) it ran perfectly...any ideas what would cause this issue? I have set some readout variables on the a5w page to show my datasource and pretty much everything else and all of it looks perfect when I run the a5w page on my browser (hence why it works perfectly on an ajax callback). I am beyond puzzled on this one, and wish I could get debugging to work in live preview mode so I could see what error mandrill was throwing back. If you have any other ideas on how I can try to debug the a5w page I would be greatly obliged (I thought I could do a button to call the a5w page but that doesn't work in development). Also as a side note, when I am building my a5w page the little "bug" button isn't enabled (I think this might be because I don't have mozilla on the server, is this the reason or do I need to change a setting to get the debug button to be enabled? And also would this even help in my case?). Thanks for being awesome my alphaholics!

            Comment


              #21
              Re: THANK YOU ALPHA!! - SMTP - email_send_mandrill() - Super Super Fast Way of Sending thousands and thousands of emails.

              I believe mandrill will only send back a response letting me know there wasn't any errors sending the data to its service (meaning it doesn't yet have responses for individual messages being delivered or rejected), is this correct?
              You can get success/fail/rejected/blacklisted/etc response back from Mandrill using their Web Hooks, under Settings. This response is asynchronous.

              Here is an example of how I grab all "hard bounces" back to my application. Under Web Hooks I just set the URL to "http://www.myapp.com/mandrill_response.a5w?p=mypassword&t=hard_bounce"

              The mandrill_response.a5w page receives a POST from Mandrill with bounce information. That information includes the original email address. I grab the POST, and match that email address up to the database record with the same email address, and then post this info to a table, which appears on the User's Dashboard as a BOUNCE, which they are then required to go correct. Mandrill, like all of these SMTP resources will temporarily blacklist any email address that keeps failing.

              I am converting this over to SparkPost because of Mandrill's decision to charge for minimal service. SparkPost has nearly the same Web Hooks arrangement.

              The benefit of posting your emails to a SMTP service, rather than just using their SMTP settings on your server, is the POST takes a fraction of the time compared to actually having your server send the email.
              Steve Wood
              See my profile on IADN

              Comment


                #22
                Re: THANK YOU ALPHA!! - SMTP - email_send_mandrill() - Super Super Fast Way of Sending thousands and thousands of emails.

                I converted today to SparkPost. So far everything is working very well. Also, there is a nice dashboard on SparkPost that gives you a lot of detail...

                Comment


                  #23
                  Re: THANK YOU ALPHA!! - SMTP - email_send_mandrill() - Super Super Fast Way of Sending thousands and thousands of emails.

                  Hi Lee,
                  If I may ask.. what was the function you used and what exactly did you type. I am having difficulty with the Login Auth part of it....
                  I am using the smtp_send function...
                  Thank you.
                  Calyxte

                  Comment

                  Working...
                  X