I’m noticing weird behavior with the List-ID headers from the new forum software and I’m generating this test topic so I can do a couple of tests.
Wow, the latency is high on this thing. It’s been over 10 minutes since I posted this topic and still no email. Anyone know how long it generally takes to get the email after a post is made?
Finally got the first email. Looks like latency is around 20 minutes. As opposed to essentially real-time for a true mailing list.
Inbound e-mails are only checked every 5 minutes. Notifications are delayed 10 minutes to allow users a chance to edit and finalize their posts.
Testing email reply capability…
Here’s a dump of what I’ve learned about email support so far:
-
Outbound latency: 20 minutes, long enough to make participation in a real-time conversation futile.
-
Inbound latency: 5 minutes, tolerable but still longer than a real mailing list
-
List-ID: Inconsistent, varies according to topic, with no way to predict in advance (because we can’t know what topics someone might create). Making a suitable list filter probably won’t be possible unless your email client allows something like a regex-based filter. From: and List-Archive: are equally unusable as filters. List-Unsubscribe seems to be consist so far and might work in a pinch. List-ID Examples:
List-Id: <talk.dallasmakerspace.org>
List-Id: <network.talk.dallasmakerspace.org>
List-Id: <off topic.talk.dallasmakerspace.org>
My current attempt at a filter is trying to match on *.talk.dallasmakerspace.org
-
A duplicate of each email reply is sent back to sender, haven’t found a way to block or filter them yet. Even more annoying, the duplicate doesn’t contain any List-ID value at all. Haven’t found any way yet to prevent these from cluttering up the inbox.
-
It’s all HTML email with lots of icons and graphics. Haven’t found a way to generate text-based emails yet.
On Mon, 2014-10-27 at 22:27 +0000, Andrew LeCody wrote:
My List-ID filter failed on this crazy one:
List-Id: <metal shop.work shop.talk.dallasmakerspace.org>
Not sure why but the filter rules in Evolution gag on it. Maybe it’s because of the embedded spaces. I’ve switched to filtering on List-Unsubscribe headers that contain the string “talk.dallasmakerspace.org” - seems to be working so far.
Yikes, another problem. If you quote the previous email in your email reply, it’s parsed incorrectly when it’s assimilated into the forum. (see my reply to Andrew above). Here’s the original text of the email body (entering this locally through the forum webpage), compare to the way it was rendered above, where all the content was lost.
On Mon, 2014-10-27 at 22:27 +0000, Andrew LeCody wrote: > Inbound e-mails are only checked every 5 minutes. > Notifications are delayed 10 minutes to allow users a > chance to edit and finalize their posts.Thanks. 5 minutes matches my measurement for inbound emails but I’m getting a pretty consistent 20 minute delay on outbound.
-Steve
Why not just check the website every so-often? Email was never marketed towards being instantaneous, that’s why they invented Instant Messaging
List-ID is completely consistent, each of those entries is a different category which would have been entirely separate and hard to find groups/lists.
You can choose to watch, track or mute categories individually.
Because I find web-based forums annoying and slow to use. Mailing lists tend to be fast and convenient. Instantaneous response is not need but most mailing lists have a latency of seconds to minutes, which is way different than a half-hour!
By a consistent List-ID, I mean one that is predictable so that I can make a filter rule that sends all DMS mailing list mail into a DMS folder and prevents it from cluttering the inbox. It appears Discourse is using the LIst-ID more like a Subj: header with a different value for each topic. But I’ve found a work-around by using the List-Unsubscribe header which so far seems consistent (identical) on each email regardless of the topic/subject.
Steve...
I filter mine with @dallasmakerspace.org and it works just fine.
If you want separate filters for various topics, then create filters off that using key words. It works.
:)
Sorry, but 10-20 minutes is not half an hour.
Not trying to be “that asshole,” but you’re being an alarmist for no reason.
And I am visiting the website right now because I couldn’t have this conversation with you via email due to the latency. I’ve already read and replied but I still have received either of your emails yet. So it looks to me like this is a great replacement for the phpBB forum but is not a usable replacement for the mailing list (for me at least).
Update: sorry folks not ignoring you, forum says it won’t let me post any more for 22 hours. …but if you see this, I can still edit existing posts!
@steevithak you are misunderstanding List-ID, the values are directly related to category and are 100% predictable. A topic created in the Laser category will be laser.talk.dallasmakerspace.org, a topic created in Network will be network.talk.dallasmakerspace.org. This is exactly the same as how List-ID works for the various lists we had on Google Groups.
Interesting discussion, I hope to see how this all pans out in email as well, because for this test to work out it need to be a replacement for both the email and forum. I think you can change some of the issues in your personal settings, example how long it wait to send you an email. not sure about the latency for the other direction?
I can’t reply anymore what gives with that?
Also, another possible issue with email replies, Lampy (Ken Purcell) seemed to reply via email on another thread and his unsubscribe link followed into the post. wouldn’t you unsubscribe him from the list by just clicking that link? Is there anything that can be done to keep this from happening? Or is this a none issue?
This all happened in the making root beer thread.
I lowered the notification delay to 5 minutes (from 10 minutes) and I’m looking into faster polling of the e-mail addresses. The concern with polling frequency is getting blocked by Google for abusive behavior, also load on the server.
Accounts less than 24 hours old are rate limited on the number of replies they can submit.
Lampy’s mail client likely misquoted the message, we saw that a lot on the google groups.