• Resolved Elia

    (@prettyboyelias)


    Hi there, we have 3 questions

    1) We use Mailster + Amazon SES and don’t receive any emails from your plugin. All other plugins send emails without any problems. We also don’t have email logs. And the emails are enabled on the website.

    Could you take a look please?

    2) Users don’t have the avatars for some reason:
    https://gyazo.com/0e7bd61298cb18546c0c73d82cdca6ac
    In order to see them you need to hover over them.

    The source of the issue could be the opacity = 0
    https://gyazo.com/6defd63e0daca3762e0ba12b78603f4d

    How can we fix this?

    3) How can we change the default agent? At the moment the website admin receive all the tickets. We want to change this so another person would receive all the tickets.

    Thanks a lot!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author awesomesupport

    (@awesomesupport)

    Hello:

    1. Unfortunately we’re not familiar with Mailster. We have used Mailgun and Sendgrid in the past. Maybe another user on these forums are familar with it and can jump in and help you out. You might also want to make sure you have the emails enabled in TICKETS->SETTINGS->EMAIL tab.

    2. Chances are there’s a conflict in your theme or one of your other plugins. What happens if you switch the theme to the WP 2016/17 theme? Do you see the Avatars then?

    3. Please see this document on how to add a new agent Once you have more than one agent the plugin will assign new tickets to the agent with the least number of open tickets. You can also change the default agent in the settings.

    Thread Starter Elia

    (@prettyboyelias)

    Hi thanks a lot for the answer.

    The issue #1 with Mailster is still here so we can’t use the plugin ??

    The problem starts when we use Mailster + Amazon SES (as the delivery service). When we use Mailster + Gmail every emails deliver without a problem.

    So the Mailster support assume 2 potential issues:

    1) If you send via Amazon SES they require you to verify the used reply-to addresses.

    I guess AS uses the users email address in the reply-to field which is of course not verified at Amazon.

    Here’s a discussion about this topic: https://forums.aws.amazon.com/message.jspa?messageID=219015

    2) What can happen is that your current delivery method doesn’t like the headers “Awesome support” is using:
    “MIME-Version: 1.0”,
    “Content-type: text/html; charset=utf-8”,
    “From: $from_name <$from_email>”,
    “Reply-To: $reply_name <$reply_email>”,
    // “Subject: $subject”,
    “X-Mailer: Awesome Support/” . WPAS_VERSION,

    Which can get altered via ‘wpas_email_notifications_email’ filter

    ——————–

    Do you have an idea on how to fix this issue? Please help us.

    Plugin Author awesomesupport

    (@awesomesupport)

    Hi:

    I see the issue in the Amazon thread. I will add a feature request to our requests list for explicit SNS support. But I don’t know of any other customer who wants to use it so the number of votes on this would likely be just 1 (yours). We can add support for it as a paid custom project of course but as far as the free plugin goes I doubt that we have enough votes to move it to the top of the request list.

    Sorry for the bad news on this.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘3 questions’ is closed to new replies.