Have you considered using something other than SMTP for message delivery?
We haven’t, but could certainly consider it if that’s considered best practice. To make sure I’m understanding, are you suggesting having our scripts post to Discourse by interacting with the website through HTML like a human would? Or do Discourse sites support an API that the scripts could target directly? If you have pointers or examples of how we might approach this, that would be very useful; we’re definitely still very new to Discourse administration.
Or, I was wondering whether there might be some other trick that we could use in the email headers to cause Discourse to append them to the existing topic rather than creating a new one. I’m assuming making the subject line “Re: linux64 testing” is insufficient and that it’s the
Reply-to: address and/or email header metadata that causes a reply to append to a topic rather than starting a new one? (in which case, we could manually create topics for every possible script subject line in the category, figure out what that meta-data was, and then embed it into our script, but that would feel pretty fiddly if there were already a way to auto-merge mails into an existing topic by subject line, particularly for scripts that might generate new subject lines over time).
That’s a very specific use case to ask to change a whole behavior.
Perhaps, but to be fair, in the OP, I was only asking about whether there’s a way to achieve what we wanted and expressing confusion that we were getting multiple topics with the same title in spite of having the “allow duplicate topic” settings unchecked. I wasn’t able to find any documentation indicating that this was the expected behavior and thought that since Discourse rejects mails on all sorts of bases (e.g., “that subject line doesn’t seem to be a sentence”) we might’ve gotten bounces saying “that topic title already exists within this category” (not that it would’ve made me any happier, it just would’ve seemed more consistent with the checkbox titles).
But, I also don’t think the behavior change is all that odd to request: I think it’s really great and powerful that Discourse sites can accept posts by email. And in our case, it’s 80% of the way to a good solution for having scripts generate updates to existing Discourse topics. And the feature request seemed similar to others I’d seen on Discourse-meta that did get implemented in that it seems clearly useful (in that lots of projects have scripts that generate mails) and didn’t strike me as being inherently in opposition to Discourse’s philosophy (though again, we’re new to the administration side of things). That’s not to say that it’s a no-brainer in any way, just that it wasn’t obvious to me that posing the question was unreasonable.