Jump to content

furioussnail

Members
  • Posts

    124
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by furioussnail

  1. Hello!
    After upgrading Blesta to its latest version and running the upgrade script, new incoming support requests bounce with the standard message ("Our system received your email, but was unable to process it for one of the following reasons") with the subject header set to "Ticket:". The templates are the default ones. The attached image shows the config for the support department. Also, the logs reveal no issues even with debug mode enabled.
    maillog: 
    Sep 29 10:05:46 portal postfix/local[29136]: 638C3BB807: to=<support-blesta@portal.example.com>, orig_to=<support-blesta@support.example.com>, relay=local, delay=2.9, delays=0.02/0.02/0/2.8, dsn=2.0.0, status=sent (delivered to command: /usr/bin/php /blesta/index.php plugin/support_manager/ticket_pipe/index/1)
    The pipe test creates a ticket successfully.
    Any suggestions on how to fix this or at least debug further are highly appreciated.

    Thank you!

    Screenshot 2023-09-29 at 16.28.09.jpg

  2. Hello.

    When adding a service based on the Plesk module users can login from Blesta into their panel. However, the problem is that the login link provided by Blesta directs to the control panel based on IP. This is a big issue since the certificates for the panels are issued by domain name instead of IP. Could you please make it direct based on host name instead?

    Thank you.

  3. On 5/24/2019 at 9:38 PM, Paul said:

    4.6 beta 1 should be out as early as Tuesday/Wednesday. We may be able to add 2CO to Github, but not before 4.6 is released, it's not the right time to do it and would interfere with our release.

    Sounds good to me. If Blesta 4.6 comes with a fixed 2CO module I don't think the upload to Git is necessary anyway.

    Thank you.

  4. 11 hours ago, Lampard said:

    2Checkout payment gateway is now recording payments after i used Secret Word.

    Under "Integrations" -> "Webhooks & API" there is a "Secret Word" section with the following options: "Instant Notification Service (INS) secret word" and "Buy link secret word". Which one did you use?

  5. 3 hours ago, Jono said:

    @Lampard Are you having the same issue as @furioussnail, where you can submit a payment in 2checkout, but a successful transaction is not recorded in Blesta?  I ask because I have not been able to even make a payment.  The fields in 2checkout do not seem to line up with the credentials asked for in Blesta.  What mapping are you using?  "Merchant Code" => "Vendor Account Number"?  "INS Secret Word" => "Secret Word"?

    Thanks for your help, I think it's becoming more and more clear that we need an update to the gateway that allows you to choose which version of 2checkout you are using.

    It looks like I am having the same control panel but for payments I am using the old API. And somehow the old API isn't working right. My customers see the old payment form, with the old logo. I think 2checkout/Avangate is set to migrate everyone to their latest API.

    Thank you.

  6. On 3/7/2019 at 6:38 PM, Jono said:

    Hi, sorry for the delay.  It sounds like this may be some new 2Checkout API?  I have been looking at existing functionality but it sounds like that may be a new thing altogether.  I hope to have time to investigate that possibility either today or tomorrow.

    Cool. Thank you. Hope to get an update for this plugin soon.

  7. 1 minute ago, Blesta.Store said:

    more work to do? the simple way Blesta does it?

    Yes, I realize that the way it is currently being done might be the best way for a billing solution for the masses. However, we also should realize that if someone manages to spoof a ticket message then hashing might not help. The attacker would require to to know both, the email address and the message title even without a hash.

    The way I see it, email address + ticket code + message subject makes for a good enough hash.

  8. 18 hours ago, Paul said:

    That's right, but the headers can be spoofed, that's why the ticket hash.

    Probably for a general purpose billing system as Blesta the existing implementation is the best. In general email validation should be the concern of admins (talking server security administration). However, I actually appreciate how Blesta team built this.

    Thank you for your replies. I appreciate it.

  9. 2 hours ago, Blesta.Store said:

    It doesn't work because the support manager is looking for the hash in the subject. It' show it ties it to the authorised ticket I believe.

    You could probably edit the support system to use the ticket.code but then I could open a ticket reply with your ticket.code if I knew it and just add a reply to the random ticket no authentication. 

    The original "from" header can be used for matching.

  10. Uh, sorry. I meant {ticket.code} not {ticket.id}. Maybe matching a combination of "from" header (email address) with {company.code} (something like ACME) and {ticket.code} could solve this issue. Of course, if a message comes from another address it should be considered a different ticket. I see that some other platforms somehow manage to do.

    By the way, how does Blesta handle CC and BCC?

  11. I think this can be addressed by setting a more standardized hash. For example if admins set ticket subject to contain something like {company.code}-{ticket.id} Blesta could recognize the ticket as the same based on given format. This way Gmail and other similar email clients will be able to organize tickets properly. {company.code} could be an identifier like ACME for ACME Industries.

×
×
  • Create New...