Good to know. When sending a general post@posterous.com, your posterous group blogs will not receive the article. And I agree, it would not seem logical if they did. So therefore the #-hashtag addressing in the email works only for the blogs listed in the autopost settings. Also logical. And that's why originally this post hadn't been autoposted to creativeposting, ok.
But when sending a post@creativeposting.posterous.com, Posterous treats my post as a generic post for all autoposts including the ones for this group. Mmmhh, not sure about the logic there, but that's why initially the tests messages of creativeposting had been published in 1moment.org and qompute.net.
Anyway as this "forward of the original post is addressed to #creativeposting@creativeposting.posterous.com this autopost should work.
———- Forwarded message ———-
From: Moritz Schroeder
Date: Tue, Dec 15, 2009 at 9:02 PM
Subject: Sorry for the (now deleted) test posts on qompute and 1moment
To: #qompute@qompute.posterous.com, #creativeposting@posterous.com, post@posterous.com [As I am writing this post as an email, I always am tempted to start writing something like "Dear Reader" ]
From: Moritz Schroeder
Date: Tue, Dec 15, 2009 at 9:02 PM
Subject: Sorry for the (now deleted) test posts on qompute and 1moment
To: #qompute@qompute.posterous.com, #creativeposting@posterous.com, post@posterous.com [As I am writing this post as an email, I always am tempted to start writing something like "Dear Reader"
]
When testing, something always can have unintentional results. In this case, I have (and still am) exploring Posterous, a service that some call light-blog or tumbl-blog. The most interesting feature is the possibility to send a post via email. Nothing unique about that function, Blogger, WordPress and also Tumblr and Soup.io have it – as I guess have most blog-like publishing services.
What makes it special is the way Posterous handles attached files, the way you can fine-tune autoposting to other size by playing with email address, such as flickr+facebook@posterous.com, or #qompute@posterous.com, the way you can include tags for example by adding ((tags:qompute, 1moment)) in subject title line.
Enough about that, so what happened regarding my erroneously published posts on 1moment.org and qompute.net? To play around with posterous, I created a special blog for this purpose: creativeposting.posterous.com including it's cousins on Blogger and WordPress, ie creativeposting.blogspot.com and creativeposting.wordpress.com.
I enabled creativeposting.posterous.com as a group blog. On the groups details I added the two external cousin blogs. As the group email address is post@creativeposting.posterous.com I assumed wrongly that the autoposting settings of my general Posterous account would be ignored. They were not, lesson learned.
I have deleted qompute from my general posterous autposts and moved it to the group settings of qompute.posterous.com. The addresses I am using for this are:
- #qompute@qompute.posterous.com (to forward the post to qompute.net)
- #creativeposting@posterous.com (for testing purposes, because I am not sure if I have to use the full group email address including the host name)
- post@posterous.com (to apologise to you for the various meaningless posts
Good to know. When sending a general post@posterous.com, your posterous group blogs will not receive the article. And I agree, it would not seem logical if they did. So therefore the #-hashtag addressing in the email works only for the blogs listed in the autopost settings. Also logical. And that’s …
