Jump to content

Alex

Members
  • Posts

    145
  • Joined

  • Last visited

Posts posted by Alex

  1. Hey guys,

     

    In my testing of the "Email Client" feature I have found that content typed under the "Text" tab will be delivered but anything typed in the "HTML" tab is never delivered. I have only tested this minimally so it needs confirmation/denial from other parties. (We don't need HTML for our stuff, so we have no incentive to further test this, but it may matter to other Blesta users.)

     

    Cheers,

    Alex

  2. Hey guys,

     

    I am fairly confident stating that using SMTP w/ SSL on port 465 does not work with Blesta. I am able to get piping and SMTP w/ TLS on 587 working fine but I have tried 4 separate e-mail providers using SMTP w/ SSL on port 465 that I can verify work with the same settings on other clients but it never works with Blesta.

     

    Specifically, I get the same error in the Blesta logs for all providers:

     

    Connection could not be established with host sub.domain.tld [Connection timed out #110]

     

    (Don't ask if I actually put that host in our config. Just using it as an example/placeholder for the various providers I have used for testing.)

     

    Thanks,

    Alex

  3. If he doesn't reply in the next day or so, then yeah probably email.

     

    If said e-mail provider doesn't get their act together quickly this may actually be less of an issue for us as we may stand up our own mail servers which can support standard AUTH. But, I would still advocate for this feature as we would prefer to use the more secure AUTH methods, regardless of the mail server.

  4. Patching Blesta

    See Patching Blesta in the User Manual for instructions.

     

    I noticed that the footer of Blesta showed version 3.0.2 upon logging in after uploading the new patch files but prior to running an upgrade at /admin/upgrade. This could be a bit misleading to some. If it's a feature of patches that don't require database updates, etc. then it should probably be documented. Otherwise, may want to avoid updating the version number until an upgrade has actually been run.

  5. Cody may be able to provide some direction for getting this to work for you now, I'm not sure.

     

    We are aiming for an 8 week +/- 2 week release cycle, but this will vary and we expect our 3.1 release to take a little longer, since we've spent much of our time since release resolving bugs. Moving forward, we expect the number of bug reports to diminish. We expected to receive a higher number of bug reports after our initial 3.0 release, being that it's all new code.

     

    Give us a few releases to get in our groove.

     

    Sounds good, thanks Paul. Should I email Cody or just await a response here?

  6. It's assigned to CORE-741 and tentatively slated for v3.2.

     

    It will add a new authentication mode drop down, with plain, login, cram-md5, and null/none as options.

     

    Perfect! That sounds great. That's exactly what my mail clients have. Do you have a release schedule for 3.1 and 3.2? Any chance of getting the run down on how I can patch my own copy of Blesta to support this in the meantime?

     

    Is it like a password but a file?

     

    No, it still just uses your password (or IMAP key in my case, but that's another story), it's just a different way of exchanging it between the client (Blesta in this case) and the mail server. It doesn't require anything from you other than ensuring that your mail server supports it. (cPanel/WHM e-mail accounts do not yet support it)

  7. Every mail server I've ever used besides Exim via cPanel/WHM (sadly) supports it and it's supported in all major clients. Exim already supports it (http://www.exim.org/exim-html-current/doc/html/spec_html/ch-smtp_authentication.html) and a feature request has been submitted to cPanel (http://features.cpanel.net/responses/add-cram-md5-as-an-email-authentication-method) so it's reasonable to believe it will soon be supported in the one place I know of that it isn't already.

     

    Wikipedia (http://en.wikipedia.org/wiki/CRAM-MD5) says

    it is quite often supported by SMTP-AUTH Mail submission agents.

     

    It's usually called "Encrypted Password," especially in email clients, instead of the more technical "CRAM-MD5" which I suspect is why you don't recognize it.

  8. * [CORE-714] - Universal Module: Configure label shows a numerical ID instead of the product name during checkout * [CORE-715] - Order Plugin: Inactive and Restricted packages appear normally on order pages

     

    Thanks guys. I'll report more bugs soon, only I'll use the forum this time. :)

×
×
  • Create New...