Open djbrooke opened 3 years ago
Based on the discussions today, the actual solution, as a delivery for the next release, may be something along the lines of:
1) If the installation deploys the release and chooses to do nothing, everything stays as it is now: The form keeps generating an email, with the user's email address put into the "Reply-To:" header. 2) If they choose to configure the "use RT for support requests" option, the form opens a new RT ticket via REST API. 3) If they are not using RT, they have an additional new option: "do-not-use-reply-to" - in which case the form keeps sending email, but without the extra header. (And adds the user's email address to the message text).
Kinda straightforward/not unnecessarily disruptive - ?
@landreev that sounds great.
👍
ADA would be interested in this for the purposes of linking to our ticketing system as well - OSTicket (https://github.com/osTicket)
@stevenmce are you still interested in this feature?
@sbarbosadataverse Are you still encountering the problem of our emails sent via the support form ending up in users' spam folders?
The support form at dataverse.harvard.edu currently relays messages in a way that is running afoul of spam filters by using the user’s email as the return address and with mismatched domain headers. We can expect that other installations may run into this as well. We should investigate a configuration that allows the support form to communicate with support ticketing systems via API or some other method instead of generating an email with mismatched headers. For this first iteration I’m interested in setting up something with RT:
https://bestpractical.com/request-tracker https://rt-wiki.bestpractical.com/wiki/REST#Java https://docs.opennms.org/opennms/releases/27.1.0/javadoc/org/opennms/netmgt/rt/RequestTracker.html