Re: [Gossip] thoughts for right now and the future
Jeff Breidenbach wrote in : |As I've mentioned in the past, Mail Archive is alive and well in most |respects. The one exceptions is customer support, for which I am That is adorable. |The service is hosted in the United States, and you might have heard |about an upcoming election in this country. There is a chance that |this may include confusion, chaos, and especially disinformation. If |such things reach our tiny corner of the internet, please tell me so I |can take whatever action is necessary. | |I want to say something else about this election. Back when dinosaurs |roamed the earth and I was a teenager, I was full of questions. One |thing that confused me was the idea of hate crimes. If someone does |something bad, the penalty is usually more severe if it is part of a |hate crime. Why? If it was murder, the victim is equally dead either |way. How could this possibly be fair? | |Eventually, I decided that people are naturally susceptible to us |vs. them thinking. I am Jewish, with a German last name. So for me, I |think back to World War II. What we now call hate crimes was once |mainstream thinking. I think we made these laws to be extra |vigilant against falling back into that trap. Dear Jeff Breidenbach, beside your personal matter, that of your family, and the very much understandable and supportable thinking and feeling of your own. And letting aside the history of the United States a bit. Maybe. I think it is a structural misunderstanding, intellectual, but surely emphatical failure to compare the world leading (some say suppressing) super force U.S.A. with the Germany of the 30s, may Americas public discourse have ridden this comparison (sic) or not. Doing so surely is cold cruelty, is abuse, is murdering and torturing millions of people a second time. You should not say things like "What we now call hate crimes was once mainstream thinking". For one hate has always been, and always will be, unless all human beings of the world listen to the philosophical outcome and truth of our forefathers and mothers that lived many thousand years ago. Or like the Dalai Lama said in the interview of his 50th anniversary in India, "it is all there". It is all there, for thousands of years. I am happy that you think that modern U.S.A. has the solution to finally make it happen, i personally am not convinced. As your family seems to originate in Germany, you should remember or learn that Germany was a rising middle force by the end of the 19th century, with a population that almost doubled over thirty years, with leading (in the sense of being in the front line of the forwarders, of going forward) human beings, in science, in culture, architecture, but also philosophy etc. Like Lebensreform. The age was so as such, it was called Belle Epoche. White humanity started truly penetrating chemistry, biology, and healing for terrible illnesses slowly came in sight. If you realize that 30 percent of all Germans at that time seem to have died from Tuberculosis -- just imagine how coughful that time must have been --, .. unbelievable. Much could be said indeed, English Wikipedia for example is very much focused on the "German Naval Race" against the Britons. (Of course lots of the world did so, Argentina, Brasil, also U.S.A. i think. Due to the tremendous technological improvements what was top today was too old tomorrow.) I never read there that many ships were build for the Ostsee, nor that the target was to have about 60 percent of the Naval of the Britons, nor that Germany build wonderful civil ships which' fame lasted for hundred years and more, like the beautiful Flying P-Liners, and "dream boats" for crossing the Atlantic, setting new speed and interior marks. The beauty. The refinement. The culture. The optimism. Much could be said on Germany by that time, also negative things of course, but mind you that dark brains always exist, and the question is how to handle them. Our Emperor, and our Princess, the most beautiful in the World (;-), they spend money on poor Children. And that is also true literally. Anyhow, the sharpness increased everywhere, and contracts were made, in the end made family members fight each other until death. You know many Royal Families around Europe were tightly related. Especially England, Germany and Russia. But the storm of life blew heavy, and there was nothing anyone could do against it. It happened. So here we are at the begin of World War I., where all of Germany stood together almost for the first time, in history. You could count the war against France, started by France, in 1870/1. You know how terrible the French raped and plundered through Germany a few decades before that. I do not say that German's are Angels, mind you. But after Bismarck was removed by our still young Emperor, wasn't it only social improvement, science, discovery, and culture? Colonies you might say, and you are right; much of what happened was done by
Re: [Gossip] [email protected] no longer archived ..
Hello Jeff. Steffen Nurpmeso wrote in <20200725174622.qd5fb%[email protected]>: |Jeff Breidenbach wrote in |: ||I checked and for whatever reason, they simply aren't sending email to ||[email protected]. No idea why. If you can help make that happen, ||archiving will work again. | |I will forward it. | ||While we are talking, I wants folks to know that the Mail Archive \ ||itself is ||running fine (knock on wood). But I can't keep up with the support \ ||requests ||though, so sorry to everyone affected by that. | |It's a pity i do not have more money to spend also for "hobby" |projects like MailArchive. |Thank You! I am sorry, i did not get any response from Unicode officials, it seems the industry backing Unicode is no longer interested, and they left for web forums etc., leaving behind rag rugs of the past. Sorry for the noise, and thanks again for the MailArchive!! Ciao from Germany, --steffen | |Der Kragenbaer,The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] [email protected] no longer archived ..
Hello Jeff! Jeff Breidenbach wrote in : |Hi Steffen, | |I checked and for whatever reason, they simply aren't sending email to |[email protected]. No idea why. If you can help make that happen, |archiving will work again. I will forward it. |While we are talking, I wants folks to know that the Mail Archive itself is |running fine (knock on wood). But I can't keep up with the support requests |though, so sorry to everyone affected by that. It's a pity i do not have more money to spend also for "hobby" projects like MailArchive. Thank You! --steffen | |Der Kragenbaer,The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] [email protected] no longer archived ..
Hi Steffen, I checked and for whatever reason, they simply aren't sending email to [email protected]. No idea why. If you can help make that happen, archiving will work again. While we are talking, I wants folks to know that the Mail Archive itself is running fine (knock on wood). But I can't keep up with the support requests though, so sorry to everyone affected by that. Jeff ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Partial match search
>What type of partial match search is supported on mail-archive? Here's the short and long explanation of search syntax. https://www.mail-archive.com/faq.html#search https://www.mail-archive.com/searching.html ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] The Mail Archive transitioning away from a small business
On Sun, Jan 27, 2019 at 7:22 PM Jeff Breidenbach wrote: > > So far, so good with this transition. Happy 2019 to everyone. Thanks for keeping this awesome service running. Happy New Year! Yang ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] The Mail Archive transitioning away from a small business
So far, so good with this transition. Happy 2019 to everyone. Jeff > ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Bands of central molecule
I don't know the full process but I'm pretty sure it involves reversing the polarity on the phase capacitor, if that might get you started. -- Matt Morgan [email protected] On Sat, Sep 15, 2018, at 7:13 AM, [email protected] wrote: > Hello SIESTA users, > > I have to calculate band of a electrode-molecule-electrode system, > especially the central molecule of a device, if anyone knows please give > me suggestions how to calculate. > > Regards > Surender > > ___ > Gossip mailing list > https://www.mail-archive.com/[email protected] > https://www.mail-archive.com/cgi-bin/mailman/options/gossip ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] rcpp-devel: Can't reply via email
Thanks for the report. There was a bug in list name validation. Should be fixed now. Jeff ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] exporting mailing lists in mbox format
Sorry for missing this earlier. There is no self service mechanism for downloading raw mail, in pat to prevent address harvesting. The normal procedure is to contact support team with a request. Unfortunately this is an 11 year old mailing list, and a bunch of the raw mail has been moved to very cold storage. We're talking disk drives that are not connected at all, sitting in a box. It's not going to be easy or fast to pull the data. If your main goal is merging archives on mail-archive.com, that can be done at the HTML level without pulling ancient raw mail. Super easy if the more recent list is new or has mbox available. The procedure for merges is a support request, to [email protected]. Jeff ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Replacing StartCom certificate
The Mail Archive has switched certificate authorities, and dropped extended validation. Please let me know if you notice any problems. ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] doing simple data analysis on list archives
Glad you were able to get things working. For search experts out there, The Mail Archive uses Lucene search syntax. See the following documentation. http://www.mail-archive.com/faq.html#search http://www.mail-archive.com/searching.html More specifically, the site uses the default Lucene query parser, except for two things. We default the parser to the AND instead of OR. And we support the special search term "sort:newest" which puts results in chronological order. query_parser.setDefaultOperator(QueryParser.Operator.AND) Sounds like things are going well. But if you need a small tweak to the search engine, just ask. ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] doing simple data analysis on list archives
On 04/22/2017 11:12 AM, Matt Morgan wrote:
On 04/20/2017 06:15 PM, Dossy Shiobara wrote:
On 4/20/17 4:43 PM, Matt Morgan wrote:
I guess what I'm asking, is there an easy path from mail-archive.com
search results into a spreadsheet (I guess mySQL or postgres would be
OK too) or some other kind of analysis tool?
I thought about doing this in Node.js but that would require a bit more
machinery that isn't available "out of the box" and I didn't want you to
get hung up on any dependencies, so, here it is in PHP which should work
with just out-of-the-box PHP (on most platforms, anyway):
$ php -r '
$dom = new DOMDocument;
$dom->loadHTML(file_get_contents("https://www.mail-archive.com/search?l=mcn-l%40mcn.edu&q=%28%2Bjob+OR+%2Bposition%29&f=1";));
$doc = simplexml_import_dom($dom);
$out = fopen("php://output", "w");
fputcsv($out, array("link", "subject", "date", "name", "message"));
$msg = array();
foreach ($doc->body->div[0]->children() as $node) {
switch ($node->getName()) {
case "h3":
$msg["subj"] = (string) $node->span->a;
$msg["link"] = "https://www.mail-archive.com"; .
(string)
$node->span->a["href"];
break;
case "div":
$msg["date"] = (string) $node->span[0]->span->a;
$msg["name"] = (string) $node->span[2]->a;
break;
case "blockquote":
$msg["body"] = (string) $node->span->pre;
break;
case "br":
fputcsv($out, array($msg["link"], $msg["subj"],
$msg["date"], $msg["name"], $msg["body"]));
$msg = array();
break;
default: break;
}
}' | tee msgs.csv
Closing the loop on this, Dossy's script works perfectly. In my case I
had to install php-xml, but that was it (and if you use php at all you
probably already have that).
I think I may have found a bug in the search engine. Compare these two
queries:
1. search for
(+job OR +position)
https://www.mail-archive.com/search?l=mcn-l%40mcn.edu&q=%28%2Bjob+OR+%2Bposition%29&start=0
(1167 results, all of which have at least one occurrence of "job" or
"position").
2. search for
job OR position
https://www.mail-archive.com/search?l=mcn-l%40mcn.edu&q=job+OR+position&x=13&y=18
(10185 results, many of which have no occurrences of either "job" or
"position").
I had expected query #2 to do what I wanted, but I had to fuss with
the parens and plus signs to get it to actually limit the results to
items with one of the words. Even
+job OR +position
without the parens got me results with neither word.
Oops, had meant to add that the + signs turned out not to be
necessary. But I had to have the OR statement in parens for it to do
what I expected.
___
Gossip mailing list
https://www.mail-archive.com/[email protected]
https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] doing simple data analysis on list archives
On 04/20/2017 06:15 PM, Dossy Shiobara wrote:
On 4/20/17 4:43 PM, Matt Morgan wrote:
I guess what I'm asking, is there an easy path from mail-archive.com
search results into a spreadsheet (I guess mySQL or postgres would be
OK too) or some other kind of analysis tool?
I thought about doing this in Node.js but that would require a bit more
machinery that isn't available "out of the box" and I didn't want you to
get hung up on any dependencies, so, here it is in PHP which should work
with just out-of-the-box PHP (on most platforms, anyway):
$ php -r '
$dom = new DOMDocument;
$dom->loadHTML(file_get_contents("https://www.mail-archive.com/search?l=mcn-l%40mcn.edu&q=%28%2Bjob+OR+%2Bposition%29&f=1";));
$doc = simplexml_import_dom($dom);
$out = fopen("php://output", "w");
fputcsv($out, array("link", "subject", "date", "name", "message"));
$msg = array();
foreach ($doc->body->div[0]->children() as $node) {
switch ($node->getName()) {
case "h3":
$msg["subj"] = (string) $node->span->a;
$msg["link"] = "https://www.mail-archive.com"; . (string)
$node->span->a["href"];
break;
case "div":
$msg["date"] = (string) $node->span[0]->span->a;
$msg["name"] = (string) $node->span[2]->a;
break;
case "blockquote":
$msg["body"] = (string) $node->span->pre;
break;
case "br":
fputcsv($out, array($msg["link"], $msg["subj"],
$msg["date"], $msg["name"], $msg["body"]));
$msg = array();
break;
default: break;
}
}' | tee msgs.csv
Closing the loop on this, Dossy's script works perfectly. In my case I
had to install php-xml, but that was it (and if you use php at all you
probably already have that).
I think I may have found a bug in the search engine. Compare these two
queries:
1. search for
(+job OR +position)
https://www.mail-archive.com/search?l=mcn-l%40mcn.edu&q=%28%2Bjob+OR+%2Bposition%29&start=0
(1167 results, all of which have at least one occurrence of "job" or
"position").
2. search for
job OR position
https://www.mail-archive.com/search?l=mcn-l%40mcn.edu&q=job+OR+position&x=13&y=18
(10185 results, many of which have no occurrences of either "job" or
"position").
I had expected query #2 to do what I wanted, but I had to fuss with the
parens and plus signs to get it to actually limit the results to items
with one of the words. Even
+job OR +position
without the parens got me results with neither word.
Thanks,
Matt
___
Gossip mailing list
https://www.mail-archive.com/[email protected]
https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] doing simple data analysis on list archives
On 4/20/17 4:43 PM, Matt Morgan wrote:
> I guess what I'm asking, is there an easy path from mail-archive.com
> search results into a spreadsheet (I guess mySQL or postgres would be
> OK too) or some other kind of analysis tool?
I thought about doing this in Node.js but that would require a bit more
machinery that isn't available "out of the box" and I didn't want you to
get hung up on any dependencies, so, here it is in PHP which should work
with just out-of-the-box PHP (on most platforms, anyway):
$ php -r '
$dom = new DOMDocument;
$dom->loadHTML(file_get_contents("https://www.mail-archive.com/search?l=mcn-l%40mcn.edu&q=%28%2Bjob+OR+%2Bposition%29&f=1";));
$doc = simplexml_import_dom($dom);
$out = fopen("php://output", "w");
fputcsv($out, array("link", "subject", "date", "name", "message"));
$msg = array();
foreach ($doc->body->div[0]->children() as $node) {
switch ($node->getName()) {
case "h3":
$msg["subj"] = (string) $node->span->a;
$msg["link"] = "https://www.mail-archive.com"; . (string)
$node->span->a["href"];
break;
case "div":
$msg["date"] = (string) $node->span[0]->span->a;
$msg["name"] = (string) $node->span[2]->a;
break;
case "blockquote":
$msg["body"] = (string) $node->span->pre;
break;
case "br":
fputcsv($out, array($msg["link"], $msg["subj"],
$msg["date"], $msg["name"], $msg["body"]));
$msg = array();
break;
default: break;
}
}' | tee msgs.csv
HTH, HAND,
Dossy
--
Dossy Shiobara | "He realized the fastest way to change
[email protected] | is to laugh at your own folly -- then you
http://panoptic.com/ | can let go and quickly move on." (p. 70)
* WordPress * jQuery * MySQL * Security * Business Continuity *
___
Gossip mailing list
https://www.mail-archive.com/[email protected]
https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Some mails missing from [email protected] archive
We use MHonArc to render emails for the web, which is open source. So any impatient programmers who are really hungry for this feature may want to dust off their Perl programming skills. Jeff ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Some mails missing from [email protected] archive
Hi, Jeff Squyres wrote: > strip the large attachment? Extra bonus points for replacing it with > a smaller attachment containing text indicating that the large > attachment had been stripped. And a star for stating a digest, e.g. SHA256, of the stripped attachment so others can check they've found it somewhere else. -- Cheers, Ralph. https://plus.google.com/+RalphCorderoy ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Some mails missing from [email protected] archive
On Feb 16, 2017, at 1:48 AM, Jeff Breidenbach wrote: > > In addition we have a max message size, which is currently set to 150KB. > The reason for this is we had serious abuse issues with large messages > back in the day, and also we don't really want to cater towards attachment > heavy mailing lists. A mailing list full of PowerPoint slides or similar > consumes > thousands of times the resource of textual lists. Makes perfect sense. In this case, a large attachment was definitely the culprit. Our user had sent a ~6MB text file attachment. This happens occasionally on our lists -- we actually ask our users to send config.log or other such debugging files so that we can help diagnose their problems (Open MPI has a quite large configure script, and yes, it can produce a ~6MB config.log (!)). In general, would it be possible to still archive the mail, but strip the large attachment? Extra bonus points for replacing it with a smaller attachment containing text indicating that the large attachment had been stripped. :-) -- Jeff Squyres [email protected] ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Some mails missing from [email protected] archive
Hi Jeff, > PSA: Per https://www.mail-archive.com/faq.html#support, use > [email protected] for support questions about the Mail Archive. But https://www.mail-archive.com/faq.html#support says Examples of appropriate topics for [email protected]: My list does not show up in the archives. List messages are not getting archived ... -- Cheers, Ralph. https://plus.google.com/+RalphCorderoy ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Some mails missing from [email protected] archive
No it's fine, this is a topic of general interest. Missing mail typically means a false positive from spam filtering. We previously used Postini, and when they shut down switched to Spam Hero. There's definitely room for improvement and I'm always open to suggestions if anyone knows of something better. In addition we have a max message size, which is currently set to 150KB. The reason for this is we had serious abuse issues with large messages back in the day, and also we don't really want to cater towards attachment heavy mailing lists. A mailing list full of PowerPoint slides or similar consumes thousands of times the resource of textual lists. I am sorry if you were the collateral damage victim of either of these mechanisms and we're happy to do a re-import missed messages. ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Some mails missing from [email protected] archive
PSA: Per https://www.mail-archive.com/faq.html#support, use [email protected] for support questions about the Mail Archive. Sorry for the noise, folks! > On Feb 15, 2017, at 9:03 AM, Jeff Squyres (jsquyres) > wrote: > > I just noticed this morning that there are some recent mails sent to our > mailing list that are not available on > https://www.mail-archive.com/[email protected]/. > > Specifically: > > 1. Here's the beginning of a thread started on 8 Feb, mail sent by Siegmar > Gross: https://www.mail-archive.com/[email protected]/msg30591.html > > 2. mail-archive is showing 3 replies: > > 2a. Sent by me on 8 Feb, > https://www.mail-archive.com/[email protected]/msg30592.html > 2b. Sent by Gilles on 8 Feb, > https://www.mail-archive.com/[email protected]/msg30606.html > 2c. Sent by me today (15 Feb), > https://www.mail-archive.com/[email protected]/msg30631.html > > 3. However, there are 2 more mails from Siegmar that are not shown on > mail-archive.com (and searching for their message IDs doesn't turn them up, > either). Specifically: > > 3a. Siegmar replied to the 2b mail on 9 Feb (to the entire list -- not a > unicast reply), message ID: > [email protected] > 3b. Siegmar replied to the 2c mail on 9 Feb (to the entire list -- not a > unicast reply), message ID: > [email protected] > > But neither 3a nor 3b are showing on mail-archive. > > Indeed, in the 2c mail (from me / on mail-archive), you can see that I'm > replying to the 3b mail (which isn't on mail-archive). > > Any idea how this could have happened? Is there a way to tell if > mail-archive received this mail, but chose not to display it (e.g., a false > positive anti-spam or anti-virus measure)? Is there a way to tell if this > has happened in other cases? > > ...ah, I see what might have happened. Siegmar attached "config.log" to the > 3a and 3b mails (a text config file that we asked him to send as a debugging > measure). Could that have caused them to get dropped from the mail-archive > side, e.g., as an anti-virus/spam mechanism? > > Assuming that if I attached the two missing mails here (containing > "config.log" attachments), they'd get dropped again, I've uploaded these two > messages elsewhere. Can they be added to the [email protected] mail-archive? > >http://jeff.squyres.com/for-mail-archive/ > > Thank you! > > -- > Jeff Squyres > [email protected] > > > ___ > Gossip mailing list > https://www.mail-archive.com/[email protected] > https://www.mail-archive.com/cgi-bin/mailman/options/gossip -- Jeff Squyres [email protected] ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] The Mail Archive, 2016
Thank you for providing an excellent service! > On Jan 3, 2017, at 12:32 AM, Jeff Breidenbach wrote: > > A lot of crazy stuff happened in 2016. Looking back, what parts > of that touched The Mail Archive? > > Let's start with mundane computer stuff. Uptime was great, the service > was online for the entire year except for 9 hours, 12 minutes. Some > additional hard drives were converted to SSD, and some RAM was added > just to make things a little faster. Our SSL certificate vendor > surprised us when they were bought by another company. We plan to change > vendors in 2017, and will be dropping the extended validation > certificate as part of this. Software was very stable. The most visible > improvement was making The Mail Archive's homepage mobile friendly, but > there were a few behind the scenes tweaks especially to the search > engine. Version control says only about 600 lines code changed in total > over the year. > > In July, Lars Magne Ingebrigtsen decided to stop running Gmane, which is > another long running email archiving service. We offered him support > (mostly emotional!) and so far it looks like that service has transferred > to new hands. Hopefully that will be successful. It's another reminder > just how much people behind infrastructure matter. In November, we > changed policy to make message deletion a little easier than before. So > far there has not been a significant difference in the number of > requested deletions. From a traffic perspective, overall visitors > continues to decline. We are keeping an eye on this and will make > adjustments as appropriate. This year we donated to The Marine Mammal > Center, Doctors Without Borders, and Planned Parenthood. > > As always, thank you for using the service and I hope we can contribute > positively to 2017. > > Jeff > ___ > Gossip mailing list > https://www.mail-archive.com/[email protected] > https://www.mail-archive.com/cgi-bin/mailman/options/gossip -- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Replacing StartCom certificate
Hi Jeff, > This quite a bummer, as it took a whole lot of paperwork to get that > EV certificate which presumably will have to be redone with a new > vendor. Why bother with an EV? Google don't, nor Facebook IIRC. Go LetsEncrypt? -- Cheers, Ralph. https://plus.google.com/+RalphCorderoy ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Replacing StartCom certificate
On Thu, Oct 20, 2016 at 10:44:47PM -0500, Yang Yu wrote: > According to the bug, the current action affects new certificates > (including EV) only. > https://bugzilla.mozilla.org/show_bug.cgi?id=1311832 > > imo StartCom/WoSign won't be able to issue legitimate certificates for > a while, but they can backdate just like they did before. Mozilla are wise to that possibility: | However, many eyes are on the Web PKI and if such additional back-dating is | discovered (by any means), Mozilla will immediately and permanently revoke | trust in all WoSign and StartCom roots. See page 11 of: https://docs.google.com/document/d/1C6BlmbeQfn4a9zydVi2UvjBGv6szuSB4sMYUcVrR8vQ/preview The amazing list of wrong-doing documented by Mozilla doesn't give me much confidence these CAs will fully mend their ways, even if they resist the suicide of trying to back-date around the temporary ban. If I had any certificates issued by either, I'd be looking to promptly replace them with certificates from a different CA, partly so I didn't have to worry that they might try back-dating and my certificates would stop being trusted, but also who wants to do business with organisations like these? Cheers, Olly ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Replacing StartCom certificate
Hi Jeff, According to the bug, the current action affects new certificates (including EV) only. https://bugzilla.mozilla.org/show_bug.cgi?id=1311832 imo StartCom/WoSign won't be able to issue legitimate certificates for a while, but they can backdate just like they did before. On Thu, Oct 20, 2016 at 9:23 PM, Jeff Breidenbach wrote: > Thanks for the heads up. Highly appreciated. I'm impressed that you know the > certificate > vendor for The Mail Archive. I was not aware of the drama going on with > StartCom. > Is it correct that the removal only applies to new certificates, and > therefore the > deadline for action is May 3, 2017 when the current certificate expires? Or > is it more > urgent than that? Also, does the trust store removal include extended > validation > certificates? This quite a bummer, as it took a whole lot of paperwork to > get that EV > certificate which presumably will have to be redone with a new vendor. > > > ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Replacing StartCom certificate
Thanks for the heads up. Highly appreciated. I'm impressed that you know the certificate vendor for The Mail Archive. I was not aware of the drama going on with StartCom. Is it correct that the removal only applies to new certificates, and therefore the deadline for action is May 3, 2017 when the current certificate expires? Or is it more urgent than that? Also, does the trust store removal include extended validation certificates? This quite a bummer, as it took a whole lot of paperwork to get that EV certificate which presumably will have to be redone with a new vendor. ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Archiving stopped after server and system changed
Thanks a lot, Jeff! Was able to change the behaviour on the server. Archiving works like a charm now - even within the same list :-) Cheers! Marco On 08/28/2016 07:53 AM, Jeff Breidenbach wrote: > Ezmlm defaults to "X-No-Archive: Yes" in the header, which > prohibits archiving. I checked and confirmed that the following > message-id has the anti-archiving header. You'll need to turn > that header off to use The Mail Archive. > > ae39af47dd7f5a4a96234b8e6bcac1050112122...@ox-ex.oxid-esales.local ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Archiving stopped after server and system changed
Ezmlm defaults to "X-No-Archive: Yes" in the header, which prohibits archiving. I checked and confirmed that the following message-id has the anti-archiving header. You'll need to turn that header off to use The Mail Archive. ae39af47dd7f5a4a96234b8e6bcac1050112122...@ox-ex.oxid-esales.local ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Start of Thread Email was Wrongly Threaded.
You are correct, we match subject lines in absence of explicit headers. The matching window is the most recent 3000 messages. This was more important two decades ago when mail user agents were less fastidious with headers. Will think about it. Thanks for the feedback and sorry for the misthread. If this is causing trouble for others as well, please speak up now. https://www.mail-archive.com/faq.html#threading https://www.mhonarc.org/MHonArc/doc/faq/threads.html ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Outage?
Thanks for asking. We had some problems on May 15 during a cascading failure of hard drives. Archiving was paused for about a day and there was also some downtime during investigation. No data was lost. Today archiving was paused for about an hour while the failed hard disks were being replaced. There was also about 10 minutes of downtime for computer rebooting. In general, The Mail Archive publishes uptime and archiving latency statistics in realtime. We're currently at 99.88% uptime for the previous 12 months, which is actually a bit better than historical average. You can see the latency spike from today in the graph. http://www.mail-archive.com/faq.html#monitoring This week has otherwise been fine. Does this match your experience? ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: Confirm your data
Unable to display full message. Please click here to view this messageerror code: 3338
Re: Confirm your data
Unable to display full message. Please click here to view this messageerror code: 7073
Re: Confirm your account
Unable to load message please click here to view.
Re: [Gossip] certificate chain is incomplete
Yes no more warnings on android. Thanks for the quick fix. Yang On Sat, Jan 9, 2016 at 10:45 PM, Jeff Breidenbach wrote: > Thanks for the detailed report. I made some changes and now > get a 'A' rating on the online test. Does this fix the Android > problems? ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] certificate chain is incomplete
Thanks for the detailed report. I made some changes and now get a 'A' rating on the online test. Does this fix the Android problems? ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] not getting emails from redhat.com lists
Our inbound spam filtering service, SpamHero, decided that the confirmation message was phishing. Sending it through now, and we'll discuss this with the SpamHero folks. Suggestions for alternate spam filtering services are always welcome. ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] archive not updated for [email protected] mailinglist
All the quarantined TDF messages were from you, except for one from bugzilla. No idea why. Anyway, I've whitelisted both the entire opendocumentfoundation.org domain, and also you specifically. Yell if you see any more trouble. Best thing you can do to help is continue keeping TDF lists from being taken over by spammers. ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] archive not updated for [email protected] mailinglist
Hi Jeff, On Wed, Jul 1, 2015 at 1:01 AM, Jeff Breidenbach wrote: > The spam filtering service we use (SpamHero) quarantined that message along > with some others. I've released the messages from quarantine and also > adjusted > the whitelist to hopefully reduce or prevent this from happening in the > future. Thanks a lot for the quick fix. > I'm sorry about this and we would definitely consider switching to a better > spam filtering service if we can find one. No worries - let us know if we (TDF) can do something to avoid getting flagged :-) ciao Christian ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] archive not updated for [email protected] mailinglist
The spam filtering service we use (SpamHero) quarantined that message along with some others. I've released the messages from quarantine and also adjusted the whitelist to hopefully reduce or prevent this from happening in the future. I'm sorry about this and we would definitely consider switching to a better spam filtering service if we can find one. ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Porting digested new list archives to mail-archive
A more detailed response was sent over private mail, but the short answers are (1) yes, as per FAQ (2) thanks for the suggestion, will add it to the list of things to think about. ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Porting digested new list archives to mail-archive
OK, I'm ready with the archives to upload, with 2 questions before I do so (actually, only the first question is related to the upload): 1. Shall I create the mail-archive entry first and have it start auto-archiving new mail and wait until that's up and running before sending you the old archives (to make sure that there are no gaps, for instance, and so that you already have a working repository to put them in)? 2. (Not directly related to my imminent import) In a previous question I had asked about having an "index" that allowed you to jump directly to a month/year rather than scrolling page by page via "Previous" and "Next" to which you replied No active plans around the monthly index feature request. I can only guarantee such a thing would not happen any time soon. Same answer for the modifying the thread index. I do appreciate the feedback and interest and will keep in mind. which is understandable from the standpoint of it being a new feature. However, I noticed that the "Previous/Next" links go to a page that has fixed links like https://www.mail-archive.com/[email protected]/mail2.html, .../mail3.html, .../mail4.html, etc. (and ../thrdN.html for the thread view). So it would seem a relatively simple matter to have a fixed footer on each index page (whether by date or thread): Page 1 2 3 4 5 6 7 8 9 10 ... going as far as the number of pages that exist. It would at least allow someone to one-click fast-forward to estimate a date (the current option is to realize that that's how it's structured by seeing the URL and then manually guessing at a number and editing the URL). Shahrukh ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Porting digested new list archives to mail-archive
This is probably going to work fine, and let's go ahead and give it a try. If it doesn't work, we'll discuss, figure it out, and try again. Yeah, I'm probably over-analyzing but getting to this point was definitely useful since I now have more confidence what my scripts need to do and what they don't. Will need several more days before I have things in shape to send you, at which points I'll send an email directly to the support with the pertinent links to the files and a simple README with anything I think may help you figure out what is what. Thanks for all the help and to Earl and Matt for chipping in too. Shahrukh ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Porting digested new list archives to mail-archive
Yes, you can safely leave out To, Message-id, and Received. Consequences are what you'd expect, like the inability to do a message-id search and find that particular message. You are correct. Posting address is manually assigned during the bulk import process, and automatically determined from headers for regular inbound mail. Think of it as if Mail Archive was trying to put every message in a folder, where the folder name is the posting address. The folder name is indexed, so is available for search. You are exactly correct about the 'l' parameter. This is probably going to work fine, and let's go ahead and give it a try. If it doesn't work, we'll discuss, figure it out, and try again. ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Porting digested new list archives to mail-archive
Jeff, Thanks again--more things are clear now. But your response raises more questions in my mind as well. Please bear with me, we're almost there I think. Keeping in mind that I am splitting Digests into individual messages, I have to fake whatever headers are not already there within the individual messages. In the case of my digests, the existing headers are only: Date: From: Subject: To this I add a ^From_ line just before the date line to make it an mbox format (this is taken from the Digest header and copied in front of each email in the digest, so it's identical for several emails. An example of this ^From_ line is this: From - Mon Nov 28 11:00:05 2005 Now, with this background, here are my further questions: 1. I thought I would have to add a "To:" line to my "faked" headers, but you are saying that it is never used, is it OK if the To: line is completely absent? The only things indexed for search are: message-id, 2. Will it choke if there is no Message-ID? I know this is used in threading but in an earlier email you said that in the absence of Message-ID it would thread on Subject, but just want to make sure it won't reject the email without a Message-ID field. ... subject ... sender name (extracted from From: header) No issue on these. ... date (usually extracted from the Recieved: header) 3. Hmm, again, there is no Received header. Will it properly take the date from the Date: field in that case and not choke on the absence of any Received headers? The date field format (from an actual example) is: Date:Mon, 28 Nov 2005 17:55:14 +1100 ... posting address (for example, [email protected] ... Every message is > sorted and organized according to posting address ... but the To: header > is never indexed for search, never used during import, and there is no > benefit for you to adjust it. 4. This is where I'm most confused now. Where *is* the posting address extracted from if not from the To: header? Is it an internal field in your archive message database that is (a) predetermined manually in an import, (b) mapped to a fixed internally stored name for new incoming email (based on headers including To:) and nothing else? In your earlier response, where I had asked about the varying forms of To: addresses in my old archives that needed to be imported (e.g., [email protected], [email protected], [email protected]) in terms of confusing search (since I incorrectly imagined that the To: line would be looked for in the search), you had replied: Search will have no concept of alternative list names. There is no reasonable way to overcome this. but now you say search never looks at the To: lines and they aren't used in imports either. So in light of your latest response I don't understand now why search would have an issue of "alternative list names"--they are alternative To: lines but the same list, and the variations exist only in archives--new email would have a consistent To: line reflecting the current posting address. A merged archive will have the same posting address for every message, with no memory about what life was like before the merge. OK, this is consistent with the "To:" line never being used for search. So the "l=" parameter in the search would always have to be the new list name following a merge, correct? That shouldn't be an issue. Shahrukh ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Porting digested new list archives to mail-archive
The only things indexed for search are: message-id, subject, date (usually extracted from the Recieved: header), sender name (extracted from From: header), posting address (for example, [email protected]), archival message number, and message body. Every message is sorted and organized according to posting address. The To: header is examined when sorting regular inbound mail and is a factor when deciding where it belongs. But the To: header is never indexed for search, never used during import, and there is no benefit for you to adjust it. A merged archive will have the same posting address for every message, with no memory about what life was like before the merge. ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Porting digested new list archives to mail-archive
1. Yes, we override list name on import. OK, so they are threaded and paginated independently of what's in the "To:" line. 2. Search will have no concept of alternative list names. There is no reasonable way to overcome this. Hmm, I don't understand this, given your answer to (1) above. If the primary list name is [email protected], then by your convention, it seems that going to www.mail-archive.com/[email protected]/ would bring up the "home page" for that list archive. There is no way to restrict a search just to "pages under this page"? I.e., that the only way to get a particular list is to match explicitly the contents of the "To:" field for that list? 3. Why not use the tool that Earl mentioned? Because it seems with nmh I would have to do it manually on a digest by digest basis. So with hundreds of digests and thousands of created individual files which I would then need to remerge, I really need a script that processes an mbox of hundreds of Digests in one fell swoop, creating a slightly smaller compliant mbox of all the individual emails, which is the script that I have just finished writing. Besides, if I have to do additional processing, e.g., to replace old To: lines with the new list name to avoid the search problem, I need a script anyway (albeit a simpler one). (I'll make this script available once I'm done, so it will have been completely debugged and well tested, since it may be useful to others in the future.) 4. We always merge into the new list name and set up an HTTP redirect so that the old URLs are not broken. Merges are done via a manual request to support staff. OK, that's clear. But then it would have the same search issue, would it not? I.e., that while the merged list would appear as one in the summary and threads pages, a searcher would have to search for one or the other (or use an OR operator in the search, which seems like another way to overcome this, i.e., create a search with a hidden field containing the OR of all variants). Shahrukh ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Porting digested new list archives to mail-archive
1. Yes, we override list name on import. 2. Search will have no concept of alternative list names. There is no reasonable way to overcome this. 3. Why not use the tool that Earl mentioned? 4. We always merge into the new list name and set up an HTTP redirect so that the old URLs are not broken. Merges are done via a manual request to support staff. ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Porting digested new list archives to mail-archive
Still working on processing the old email digests to convert them to individual emails in mbox format for import. Meanwhile, though, I thought of a new issue which has to do with identifying the list name from the email headers, given that the list name (and consequently the email address in the To: line) varies. The list is currently identified in the To: line as [email protected] and the last 10 years' archives should be consistent (that's the easy part). Before that, though, it was hosted with Listserv software on a different host and was identified as [email protected] which in some very old digests ca. 1994 show up as tango-l%[email protected] (the uga.edu part could vary depending on what BITNET-to-Internet gateway was used). In addition, the list was called TANGO for a short while before it was changed to TANGO-L. In summary, we have the following, which are all the same list: [email protected] [email protected] tango-l%[email protected] (with possibly gateways other than uga.edu) [email protected] tango%[email protected] (with possibly gateways other than uga.edu) So, with this background, my questions are: 1. Since this is for a manual archive import (as opposed to incoming email that has to be filtered intelligently), you would have all the files and could presumably just force it to go to the same database. Is this true? 2. Even if you did that, though, would searches work reliably? I would want the first of the above addresses ([email protected]) to be the primary address by which the list would be identified, so for search queries, people would always identify the list as [email protected], as that's what it's been for the last 10 years. But would ALL the above variants then be included in the search? I.e., is there an internal tag created with the archive that identifies it with just one email address for queries, regardless of what's on the "To:" field of an individual message? No one is going to be searching for this list with anything other than "Tango-L" (most likely) or "[email protected]", notwithstanding the alternate forms. 3. Any other things to think about regarding this issue? I have resigned myself to writing scripts for splitting some old digests into mbox-format individual emails for import, so if there is something else I need to on each message to address this new issue, I could incorporate it into the script. I could just force all the "To:" headers to [email protected], obliterating all the previous forms, which clearly would solve the problem, but do I need to? (It is extra work, and some are already in mbox format that I would otherwise not need to touch, but would to make this change.) 4. If, in the future, the list were to move to a different host and have an address like [email protected] (a "permanent" change) how could I ensure that it continued to go to the same archive? And is there would be a single list tag in a search query that would get posts from that archive (and only that archive) regardless of whether they posts were pre-move or post-move? In this hypothetical situation indeed people may search with the mit.edu domain OR tango-L.com domain, and ideally it would call up the same combined archive. (I did read the FAQ article on "My list splits into multiple archives" which touches on this issue, but it seems relevant mostly to incoming mail filtering rather than old archive processing.) Shahrukh On 4/15/2015 2:29 AM, Jeff Breidenbach wrote: Statute of limitations is typically 3 kilomessages on a normal non-import list, but should (I think) be unlimited on bulk import. Conversion to unix newlines is required and is manual; doesn't matter who does it. Still prefer to do whole import at once especially if tricky; less labor, also less likely to break URLs if it takes multiple attempts to get it right. But we can accommodate two stages. Imports are done on weekends only. ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Porting digested new list archives to mail-archive
Statute of limitations is typically 3 kilomessages on a normal non-import list, but should (I think) be unlimited on bulk import. Conversion to unix newlines is required and is manual; doesn't matter who does it. Still prefer to do whole import at once especially if tricky; less labor, also less likely to break URLs if it takes multiple attempts to get it right. But we can accommodate two stages. Imports are done on weekends only. ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Porting digested new list archives to mail-archive
On 4/14/2015 9:25 PM, Jeff Breidenbach wrote: * I recommend doing the import all at once, rather than in stages. Not for technical reasons, it just saves manual labor. OK, I may do it in 2 stages, since 1/2 the archives are in mbox format that can be imported instantly. The other half are in Digests that I need to create the scripts and process them through a few thousand emails, which could take some weeks. But no more than 2 stages, if that's OK ...? * Happy to make a tarball of the HTML after the import. ... Either way, you would be totally on your own from there; Sounds good and more than reasonable. * Threading is done MHonArc and discussed here. http://www.mail-archive.com/faq.html#threading OK, that was helpful. Basically that References: and In-Reply-To: are used first, but in their absence, Subject: matching is used. That works. It didn't, however, answer my "statute of limitations" question, i.e., in the absence of Message-ID: clues, and relying on Subject: only, if there was a time span beyond which it would not link two likely different threads that happened to have the same subject (e.g., someone used the same subject but a year later). Not a big deal anyway--just curiosity. On 4/14/2015 11:27 AM, Earl Hood wrote: For MIME digest messages, MUAs like nmh are able to extract such messages out into individual files, which can be subsequently packed into mbox format. I have hundreds of digests each with perhaps a dozen messages to process, so it needs to be a script that basically creates "mbox of all messages" from "mbox of Digests" in one (or a few) fell swoop. I have a psuedo-code awk program written that should do that, that I need to further code into real awk, but it should work, just a question of time to write and debug it, and then to process all the files through it and verify that it worked OK. I did find a sed script at http://sed.sourceforge.net/grabbag/scripts/splitdig.sed that allegedly does this, but while it's instructional, it doesn't seem robust enough, seemingly relying on any line with all dashes (as few as one!) as being a demarcation, whereas that could easily occur in the text (preceding a signature, for example, or as a separator). Besides, sed is a "write-only" language (you can program it as you go if you know it well enough, but good luck going back and figuring out what a sed program actually does and how to modify or tweak it!). :-) One more question: Some of the "mbox" files that I propose to submit are in fact Thunderbird mail folders. As far as I can tell, they conform entirely with mbox format (leading ^From_ line, escaped >From if leading in body), but does anyone know of any "gotchas" with this? Also, my files are all Windows based, but I assume CR/LF vs. LF is handled automatically and trivially, correct? (Or should I do the conversion to Unix format myself?) Shahrukh ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Porting digested new list archives to mail-archive
* I recommend doing the import all at once, rather than in stages. Not for technical reasons, it just saves manual labor. * Happy to make a tarball of the HTML after the import. It will look like basic MHonArc output and cosmetically differ quite a bit from what is served, because there is significant cosmetic alteration during serving time. If you choose to scrape instead, I don't have a favorite tool to recommend. Either way, you would be totally on your own from there; we didn't design for this and would not help with harder stuff like broken links, local search, etc. * No active plans around the monthly index feature request. I can only guarantee such a thing would not happen any time soon. Same answer for the modifying the thread index. I do appreciate the feedback and interest and will keep in mind. * Threading is done MHonArc and discussed here. http://www.mail-archive.com/faq.html#threading ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Porting digested new list archives to mail-archive
On Mon, Apr 13, 2015 at 11:19 AM, Matt Morgan wrote: >> 2. Now the harder one. From Sep 1994 (inception) to Apr 2006, the lists >> were hosted using L-Soft's LISTSERV software, which did not keep archives. >> However, I have a complete set of all traffic from that time period, but >> they are all in Daily Digest format, i.e., with a "Table of Contents" in the >> front and several emails afterwards. I have MOST (but not all) of these >> available as MIME digests with each message in a different MIME multipart >> segment. I also have ALL of them available as a non-MIME digest, with a >> fixed text separator (like a row of ) between messages. I would propose >> to send these as an mbox format of digest files but each email in each >> digest message would still need to be separated out. (a) Can mail-archive do >> this digest parsing, or do I need to find or write a script to do this >> myself? (b) If mail-archive can do it, do you have a preference for MIME vs. >> non-MIME digest? (c) And if MIME, can you handle the few for which I only >> have non-MIME digests? > > I can't help with this one; skipping. For MIME digest messages, MUAs like nmh are able to extract such messages out into individual files, which can be subsequently packed into mbox format. If you have mhonarc installed, you can use the mha-decode with the -dcd-digest option to have all digest messages extracted into separate files. --ewh ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Porting digested new list archives to mail-archive
Thanks Matt and Jeff for your answers--they were very helpful. So, as I understand it: - Sending link to mailman raw archives will take care of all posts from 2006 to present (for which the mailman archives exist). - Listserv digest format to individual email mbox format conversion (for the older 1994-2006 articles) I'll have to do on my own. :-( Well, I'm surprised it hasn't come up before but I guess I'll make the script available for others after I do it (more likely in awk and ksh than perl since that's what I know better, though I don't have a Unix system these days so who knows ...?). - Sending archives in segments and out of chronological order is not a problem and threading and user interface will not be confused by this but simply and automatically (or manually by support each time they add import old archives?) recalculated. E.g., if I send the mailman mbox first (since it's easy) and the earlier digests later (since I have to work on it). - You're willing to make an exception (or try ...) to have all posts indexed for my list, especially given that it's static, rather than just the last 3000 (but question on this below). - I can mirror the archive on my own site if I want (again, question on this below). Please let me know if any of the above is not correct. Two further questions: 1. Does mirroring to my own site involve installing cgi-bin or .php scripts and so on? In which case are there instructions for that? Or just a wget-like static copy? It seems like the search and email obfuscation features at least would require scripts, no? 2. I noticed though that the user interface requires clicking one page at a time to go back +/- 100 messages or so at a time and there's no other navigation method. This seems unwieldy--I can see people getting tired of clicking more than 30 times to go back 3000 messages. Is it not possible to have a year/month hyperlinked index instead like 2015 - Jan | Feb | Mar | Apr | May (final) 2014 - Jan | Feb | ... | Dec ... 1995 ... 1994 - Apr (inception) | May | Jun | ... | Dec on the side or top or bottom for direct access to the time frame of interest (plus of course Prev Page | Next Page to "scroll" within the month range in question? Of course I can do that with manually setting hyperlinks on my own backup version of the archive, especially given that it's static, but it would be great to have the mail-archive version do it directly. 3. Is threading based on subject-line matching only (and if so, what if the same subject happened to appear say 3 years later in a completely unrelated thread)? Or is it based on In-Reply-To: type parsing and linking? (The Digests have these "extraneous" headers stripped out, leaving only To/From/Date/Subject, so I need to know if splitting the Digests into their individual posts will break threading.) 4. Is thread view, is there a way to have the date of the past appear next to each item (e.g., after the author name)? E.g., Re: Search returning 404 Jeff Breidenbach 2013-05-31 since the date provides a useful additional context in the threads view. Regards, Shahrukh ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Porting digested new list archives to mail-archive
First, it is very common and super easy to directly import from a mailman (pipermail) archive. If the pipermail archive is publicly online, just supply the URL to the support team. The Mail Archive does not split digests back into individual messages. That's way too scary. If a digest is presented during import, it will be archived as a single large message. It might be possible to split a digest into a multi-message mbox, but I have no experience or advise to give. Consult your favorite internet search engine, the mailman-users community, or perhaps someone here can give guidance. I'd like to clarify some terminology in the FAQ. Cold storage means sitting on a disk in a closet somewhere, completely disconnected with the internet. The only thing in cold storage is some raw mail from years gone past. Anything we serve is in a processed format and very much online. Everything imported is very much live and online. The 3000 limit is simply how far back index pages go; people get tired clicking after a while and we also limit them for performance reasons. So on one hand The Mail Archive doesn't really offer what you are looking for, which is monthly indexes going back forever. But you can get something similar using the search engine. For extra fun, click on the expand button following the link. We might make such links more prominent in the user interface in the future, if there is demand. I've heard mixed feedback so far. http://www.mail-archive.com/search?q=date%3A200308*&l=gossip%40mail-archive.com While customization is possible, we tend to forget about them after enough time has passed (say 10 years) and then accidentally break them with some code change. So I wouldn't generally encourage that approach. If it did happen, no money would be involved. An inactive list is more likely to 'maintain' this type of exception over time than an active one. All right, fine, we can try it, on a best effort basis; mention to the support team during import. Regarding export, there's no problem for you to copy or mirror your archive's HTML. Some people do this as an extra backup, which is great. I haven't yet heard of folks doing this because of unhappiness with the user interface. ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Porting digested new list archives to mail-archive
On 04/13/2015 12:57 AM, Shahrukh Merchant wrote: I have two discussion lists on the Argentine Tango that are probably going to be suspended going forward owing to lack of activity in the face of many competing technologies in recent years, but that have a treasure of information dating back from 1994. Sounds very cool. I would like to get these onto mail-archive but there are some peculiarities of the existing archives that I have some questions on. Here are the questions: 1. First the easy one. From April 2006 to the present, the lists were hosted using mailman, so I have the complete raw mailman archives that I've downloaded. They are in one big mbox-format file (about 50 MB). (a) This is I suppose the most straightforward since I just send a pointer to these files and the mail-archive staff will do the rest, correct? (b) And am I correct that the single file is the best (rather than the monthly gzipped files? And (c) that the mail-archive software will recreate threads as necessary? In my experience, both mbox and monthly gzipped files work fine. Threads were recreated fine in both cases. 2. Now the harder one. From Sep 1994 (inception) to Apr 2006, the lists were hosted using L-Soft's LISTSERV software, which did not keep archives. However, I have a complete set of all traffic from that time period, but they are all in Daily Digest format, i.e., with a "Table of Contents" in the front and several emails afterwards. I have MOST (but not all) of these available as MIME digests with each message in a different MIME multipart segment. I also have ALL of them available as a non-MIME digest, with a fixed text separator (like a row of ) between messages. I would propose to send these as an mbox format of digest files but each email in each digest message would still need to be separated out. (a) Can mail-archive do this digest parsing, or do I need to find or write a script to do this myself? (b) If mail-archive can do it, do you have a preference for MIME vs. non-MIME digest? (c) And if MIME, can you handle the few for which I only have non-MIME digests? I can't help with this one; skipping. 3. Must these old archives be processed by mail-archive in chronological order in order for threading to work properly? Or if I provide older ones later are they automatically inserted and rethreaded appropriately? They will be inserted and rethreaded appropriately. 4. The FAQ says that only the latest 3000 messages are kept live and the rest are in "cold storage" and can be retrieved only via matching searches. Some questions on this: (a) Are the "latest" based on when they were processed by the archive software (e.g., old archives processed recently would count as new)? Or (b) Are the "latest" based on the Date: field of the post in question? (b) is correct. (c) Is there any way to get ALL messages live on mail-archive rather than only 3000 so they can be browsed for by month and year for example (e.g., by requesting an exception considering the list will be mothballed and won't be expanding, or by paying a donation/fee)? There is about 100 MB total of data per list, I'd guess. Mail-archive support, when I asked about the 3000, was willing to talk about exceptions. I didn't pursue it so I can't say more in detail. (d) If not, is there a way I can get a full mirror download that include the "cold storage" older archives (after processing by mail-archive's scripts) for me to install live on my own server (which may or may not disappear) while mail-archive still keeps it more permanently in their live+cold way? I have to imagine that some tricks with wget or httrack should be able to do this, despite the "cold storage" aspect, but I'm only guessing. I would pursue the first question with mail-archive support and see what happens. ___ Gossip mailing list https://www.mail-archive.com/[email protected] https://www.mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Temporary archive dysfunction
2014/1/6 Jeff Breidenbach : > After investigation, this turned out to be an issue with an "X-No-Archive: > Yes" header on the list itself. Thanks a lot Jeff for your answer. A point stays no clear (at least for us) : till the following message no problem with the archiving http://www.mail-archive.com/[email protected]/msg35805.html We haven't changed the parameters of our mailing list ( under Sympa and hosted by linuxfr.org ). In others words before the 16 of november 2013 our list-messages were also tagged with an "X-No-Archive" but the server of mail-archive.com has always accepted to archive our messages. Strange. -- All the best. Rene Mages ( GnuPG_key 1024D/2CC455D9 ) http://renemages.wordpress.com/debian http://nosoftwarepatents.wikidot.com/debian ___ Gossip mailing list https://www.mail-archive.com/[email protected] http://mail-archive.com/cgi-bin/mailman/options/gossip
Re: [Gossip] Temporary archive dysfunction
After investigation, this turned out to be an issue with an "X-No-Archive: Yes" header on the list itself. Cheers, Jeff ___ Gossip mailing list https://www.mail-archive.com/[email protected] http://mail-archive.com/cgi-bin/mailman/options/gossip
Re: Archived-At links - another non-working example
Hi Jeff, *, On Tue, Sep 3, 2013 at 6:15 AM, Jeff Breidenbach wrote: > I've now had some time to spruce up the search feature. Amazing what > progress Lucene has made in the last few years. Search is slightly > faster now, there is less code on our end, and I found and fixed a couple of > rare bugs involving HTML escaping. Ah, cool :-) > What I can't do is reproduce your problem; it works fine for me. We seem to > be calculating the link differently. Is something unclear in the > documentation? Hmm. Sorry for not checking whether the hash actually is correct - and no, the documentation is not lacking - we're basically using the exact same code. But I got what went wrong at our end: The mail was not only sent to the list, but also to another addressee, so it did not create the hash with the wrong email. Apparently something changed in the mailinglistmanager we use.. Thanks for investigation, and sorry for the false alarm. ciao Christian -- To unsubscribe, send mail to [email protected].
Re: Archived-At links - another non-working example
I've now had some time to spruce up the search feature. Amazing what progress Lucene has made in the last few years. Search is slightly faster now, there is less code on our end, and I found and fixed a couple of rare bugs involving HTML escaping. What I can't do is reproduce your problem; it works fine for me. We seem to be calculating the link differently. Is something unclear in the documentation? http://www.mail-archive.com/faq.html#listserver -Jeff >>> import hashlib >>> import base64 >>> message_id = "[email protected]" >>> list_post = "[email protected]" >>> sha = hashlib.sha1(message_id) >>> sha.update(list_post) >>> hash = base64.urlsafe_b64encode(sha.digest()) >>> url = "http://go.mail-archive.com/%s"; % hash >>> print url http://go.mail-archive.com/GNXPfUlFDrZhnUZ4SH7cDfXZSKQ= On Tue, Jul 30, 2013 at 3:47 AM, Christian Lohmaier wrote: > Hi Jeff, *, > > we stumbled across another non-working archive-link - the targeted > message is in the archive, and newer and older messages are accessible > using the hash-URLs. > > The message in question is: > http://www.mail-archive.com/[email protected]/msg15830.html > and the corresponding, non-working archived-at link is > http://go.mail-archive.com/c-LzIp2g0mD_PUzGjm4_-yBorXU= > > Contrary to the problems with the links in the past, searching by the > message-ID alone returns the result <[email protected]> > > Hope you can dig up what is wrong. > > ciao > Christian > > > -- > To unsubscribe, send mail to [email protected]. -- To unsubscribe, send mail to [email protected].
Re: Search returning 404
Thanks for the report. I found a stale lockfile in [email protected] that was gumming up the works (we update search indexes once a day, in alphabetical order). I've cleared the problem and resumed indexing, which should finish in a few hours. This error should have generated an alert, so I am checking to see why it didn't. -Jefff On Thu, Jun 6, 2013 at 12:31 PM, Bryan Alsdorf wrote: > Thanks Jeff, > > Search now does not return a 404 but it seems searching by date for > anything in June fails (unless I have the syntax wrong). > > > http://www.mail-archive.com/search?q=date:[20130601%20TO%2020130606][email protected] > > has no results, though the date view shoes messages. > > > http://www.mail-archive.com/[email protected]/maillist.html > > I have checked this on a few other lists as well. > > BR, > /bryan > > > On Fri, May 31, 2013 at 6:31 PM, Jeff Breidenbach wrote: > >> Individual list search is very important. Thank you for reporting >> the problem. This turned out to be a configuration mistake on the >> webserver, involving the MultiViews configuration directive. >> Search should be working now. Let us know if you see any >> anomalies, and in the meantime we're looking into how the >> mistake was introduced in order to prevent recurrence. >> >> -Jeff >> >> > -- Support The Mail Archive www.mail-archive.com
Re: Search returning 404
Thanks Jeff, Search now does not return a 404 but it seems searching by date for anything in June fails (unless I have the syntax wrong). http://www.mail-archive.com/search?q=date:[20130601%20TO%2020130606][email protected] has no results, though the date view shoes messages. http://www.mail-archive.com/[email protected]/maillist.html I have checked this on a few other lists as well. BR, /bryan On Fri, May 31, 2013 at 6:31 PM, Jeff Breidenbach wrote: > Individual list search is very important. Thank you for reporting > the problem. This turned out to be a configuration mistake on the > webserver, involving the MultiViews configuration directive. > Search should be working now. Let us know if you see any > anomalies, and in the meantime we're looking into how the > mistake was introduced in order to prevent recurrence. > > -Jeff > >
Re: Search returning 404
Individual list search is very important. Thank you for reporting the problem. This turned out to be a configuration mistake on the webserver, involving the MultiViews configuration directive. Search should be working now. Let us know if you see any anomalies, and in the meantime we're looking into how the mistake was introduced in order to prevent recurrence. -Jeff
Re: New look to Mail Archive message pages
An annoyance with the latest design is that hyperlinks to move to the next thread message are never in the same place. In the previous design, a message could be read and the key 'end' used to navigate to the end of the page. After moving the mouse the the hyperlink for the next message, never needed to move the mouse again! :) -- To unsubscribe, send mail to [email protected].
Re: New look to Mail Archive message pages
Okay, so here's a quick status update. There are have been suggestions about fonts. Font weight. Line spacing. Typeface. Line spacing is interesting, a big design goal was to make more information available with less scrolling. However, we've found several references that suggest 1.4 is good in terms of helping readability. There is probably some personal preference; for example I personally like Courier better than Monospace. We're going to let the current design ride for a few months then revisit. The left vs. center justification of the entire page seems similarly subjective. One thing that would make a difference - more quickly - is an extremely authoritative source. For example a paper by Donald Knuth explaining how and why some other line height is better. There have been users who like to read in date order who are disappointed that we dropped some of the navigation buttons. We continue thinking, but are not sure how to make them happy without increasing confusion for everyone else. The visited link color has been changed. That's all I have for feedback so far. We continue to find and work on small bugs, like certain pages not validating, or funny looking navigation buttons in several non-English languages. If you find more of these, that is also helpful. I don't have strong data for how happy people are overall, but guessing from tone of comments, I think it is overall positive so far. -Jeff -- To unsubscribe, send mail to [email protected].
Re: New look to Mail Archive message pages
Hi, Christian Lohmaier wrote: > Speaking of fonts: After reading a while in the archive I find the > line-spacing a little excessive - it is currently at 1.4 > > Personally I find 1.2 much more comfortable for longer posts. Deviating from the 1.2 norm also messes up glyphs that span lines, e.g. http://www.mail-archive.com/[email protected]/msg04946.html Altering it back to 1.2 by editing body's font using the browser makse them butt up normally again. Cheers, Ralph. -- To unsubscribe, send mail to [email protected].
Re: New look to Mail Archive message pages
Hi Christian, > Speaking of fonts: After reading a while in the archive I find the > line-spacing a little excessive - it is currently at 1.4 > > Personally I find 1.2 much more comfortable for longer posts. Thanks for pointing that out; I've just changed to 1.2, which I think is this browser's default, and consider it easier to read. The blank line between paragraphs now stands for something again now that everything isn't spaced. Cheers, Ralph. -- To unsubscribe, send mail to [email protected].
Re: New look to Mail Archive message pages
Hi Jeff, *, On Sun, Dec 2, 2012 at 7:50 AM, Jeff Breidenbach wrote: > Thank you for the feedback, keep it coming. > > Interesting screenshots. By the way, my everyday platform is > also Ubuntu (10.04 and 12.04). So far I can't reproduce font > problems with courier. Speaking of fonts: After reading a while in the archive I find the line-spacing a little excessive - it is currently at 1.4 Personally I find 1.2 much more comfortable for longer posts. ciao Christian -- To unsubscribe, send mail to [email protected].
Re: New look to Mail Archive message pages
>What I dislike is that visited links are indistinguishable from non >visited ones. The difference in color just is way too little. I didn't notice this until you mentioned it. Now it is driving me crazy. Thank you for the feedback. -- To unsubscribe, send mail to [email protected].
Re: New look to Mail Archive message pages
Thank you for the feedback, keep it coming. Interesting screenshots. By the way, my everyday platform is also Ubuntu (10.04 and 12.04). So far I can't reproduce font problems with courier. As for the ordering of font-family, that's a good question. Let me check with graphic designer. -Jeff -- To unsubscribe, send mail to [email protected].
Re: New look to Mail Archive message pages
Hi Jeff, *, On Sun, Nov 25, 2012 at 4:32 PM, Jeff Marshall wrote: > [...] > We've been finding and fixing bugs with the new design the last few weeks > but please alert us to all the edge cases we've neglected to find ourselves! > > Feedback and bug reports are desired. I like the new design Also like that I don't have to do horizontal scrolling to read the posts, as I hate having my browser maximized (only have 1280x800 screen, but still my browser ~never is maximized horizontally) What I dislike is that visited links are indistinguishable from non visited ones. The difference in color just is way too little. ciao Christian -- To unsubscribe, send mail to [email protected].
Re: New look to Mail Archive message pages
Hi Jeff, > Can you share your browser + operating system including > version numbers? If it is not too hard, a screenshot of > a message page as well? Do you know what your browser > zoom level is set to? Browser is Firefox 11.0+build1-0ubuntu0.10.10.2 on Ubuntu 10.10. Using http://www.mail-archive.com/[email protected]/msg04936.html PNG screenshot with browser maximised is http://derp.co.uk/52c55 That's with browser zoom zeroed. Shows the leftness of it. I got screenshots in a bunch of Firefox and Chrome browsers. http://browsershots.org/http://www.mail-archive.com/[email protected]/msg04936.html They all seem OK, including Firefox 11. Looking back at my one, pre's font-family is `courier,"courier new",monospace' and it's `courier' that looks bad. Either of the other two are OK, `monospace' is particularly nice. Why are they in that order? I'd expect the unusual but best first, with the fallback font available everywhere, `courier', last? Cheers, Ralph. -- To unsubscribe, send mail to [email protected].
Re: New look to Mail Archive message pages
Ralph: Can you share your browser + operating system including version numbers? If it is not too hard, a screenshot of a message page as well? Do you know what your browser zoom level is set to? Feel free to reply privately if you prefer. http://www.whatismybrowser.com/ http://www.smartsheet.com/help/browser-zoom Sherry: Thanks for the feedback. I think you are seeing the effects of a thin font, rather than font color. In any case, we'll think it over. Especially of others express similar concerns. Sarah: In the last round of feedback you suggested using ARIA for screen reader support. The new design includes basic ARIA roles. Are you able to test and tell us if this meets your needs? -- To unsubscribe, send mail to [email protected].
Re: New look to Mail Archive message pages
Looks great to me. The message takes up a full 2/3 of the page, not just 1/3. My only complaint, as one who has some vision issues, is that the font isn't dark enough. Personally, I *like* the white space. I *hate* clutter on my screen. But then that could be due to my vision issues - too much nonsense distracts from what I'm focusing on. I don't see any corrupted fonts. It just would be nice if they were darker though. Sherry On Tue, Nov 27, 2012 at 4:38 AM, Ralph Corderoy wrote: > Hi Jeff, > >> We have been working on a new design for The Mail Archive message >> pages. The goal has been to visually bring you to the message content >> faster. The subject and message are right there at the very top left >> of the page now. > > `left' being too true. :-) On a full HD monitor with maximised browser > the email is the left third of the screen. It's like Google+'s > `whitespace' problem, only slightly worse. Could not the whole page be > centred? > > Also, the fixed-width Courier is being corrupted. pre's `font-size: > 1em' is fine but the higher body's `font: 87.5%/1.4' is shrinking it > leading to hard-to read `a's and backticks are slight. Here's the > default and below with the 87.5% turned off. http://derp.co.uk/fc580 > > Cheers, Ralph. -- To unsubscribe, send mail to [email protected].
Re: New look to Mail Archive message pages
Hi Jeff, > We have been working on a new design for The Mail Archive message > pages. The goal has been to visually bring you to the message content > faster. The subject and message are right there at the very top left > of the page now. `left' being too true. :-) On a full HD monitor with maximised browser the email is the left third of the screen. It's like Google+'s `whitespace' problem, only slightly worse. Could not the whole page be centred? Also, the fixed-width Courier is being corrupted. pre's `font-size: 1em' is fine but the higher body's `font: 87.5%/1.4' is shrinking it leading to hard-to read `a's and backticks are slight. Here's the default and below with the 87.5% turned off. http://derp.co.uk/fc580 Cheers, Ralph. -- To unsubscribe, send mail to [email protected].
Re: site design
Thanks everyone for public and private feedback. Graphical summation here for the moment. Did I miss or misunderstand anything? http://mail-archive.com/feedback.png >> Access keys should >> also be defined to do similar. > >And that would be really nice. (but they should also be advertized, >maybe using a link/icon next to the navigation buttons. Christian, can you show me an example? We've had access keys for a very long time, they are listed in the FAQ. I doubt they get much use. Also is it better to do a javascript version where hitting a plain 'n' key takes you to the next message as well as the Alt-n access key? -Jeff -- To unsubscribe, send mail to [email protected].
Re: site design
Does this use aria which is a way of working with screen reading technology. I just arose out of bed so have not looked at it but that's my main concern. Take care all and be blessed. I love the service. Sarah Alawami: owner and founder of WICS Radio America. Check us out on the web at http://wics.cc and thanks for tuning in. On Aug 28, 2012, at 4:12 AM, Ralph Corderoy wrote: > Hi Jeff, > >> http://www.maxdesign.com.au/jobs/318-mail-archive/38.htm > > Generally, I like it. The "18-01-2012, 10:51PM -0800" date is > re-formatted compared to the original email so I'd like some say over > how it's displayed to me, e.g. preferences in a cookie, or else a better > default; "2012-01-18 22:51:42 -0800" ;-). > > How do I get to view the original email that arrived, headers, warts, > and all? > > I'd probably prefer the thread display at the bottom to be author first, > then subject. Both can use CSS to cut off their text at the edge of > their box, then fixed-width isn't required? Also, there doesn't seem > much point making the author italic as its position in a column shows > it's distinct from the surroundings? > > The Previous and Next buttons at the end are handy, though I'm not sure > they need to say "message" too. But the pair are also required at the > top of the page, though they could be more terse and smaller. What's > important is that their position is fixed from page to page. This > allows the mouse to stay in the same place and the user to click through > whilst seeing just the first page of each email. Access keys should > also be defined to do similar. > > Cheers, Ralph. > > > -- > To unsubscribe, send mail to [email protected]. -- To unsubscribe, send mail to [email protected].
Re: site design
Hi Jeff, *, On Tue, Aug 28, 2012 at 1:12 PM, Ralph Corderoy wrote: > >> http://www.maxdesign.com.au/jobs/318-mail-archive/38.htm Not much of a friend of displaying the ads within the message as if the poster had added the image (but that's not different compared to as it is now). Like the removal of deadspace at the top (less scrolling), but dislike the removal of the navigation from the top. > Generally, I like it. The "18-01-2012, 10:51PM -0800" date is > re-formatted compared to the original email so I'd like some say over > how it's displayed to me, e.g. preferences in a cookie, or else a better > default; "2012-01-18 22:51:42 -0800" ;-). Yea, ISO-Format please :-) > How do I get to view the original email that arrived, headers, warts, > and all? That isn't possible in the current design either, you see a the message-id in the source-code view though. > I'd probably prefer the thread display at the bottom to be author first, > then subject. Both can use CSS to cut off their text at the edge of > their box, then fixed-width isn't required? I prefer Subject, then Author, but I'd prefer if it wasn't truncated that much. Navigation/thread list should span across the whole browser window if possible. > The Previous and Next buttons at the end are handy, though I'm not sure > they need to say "message" too. But the pair are also required at the > top of the page, though they could be more terse and smaller. or plain links, no need for buttons at the top. > What's > important is that their position is fixed from page to page. This > allows the mouse to stay in the same place and the user to click through > whilst seeing just the first page of each email. Yes, that's mainly why I dislike the removal of the buttons at the top. > Access keys should > also be defined to do similar. And that would be really nice. (but they should also be advertized, maybe using a link/icon next to the navigation buttons. ciao Christian -- To unsubscribe, send mail to [email protected].
Re: site design
Please - don't place ads in the middle of an archived email! They're so annoying. I hate it when I see them in the middle of articles on the web. Yes, I realize advertising is necessary for revenue to keep a service free, but there has to be a better way than breaking the train of thought for the reader. Other than that, the new design is really nice. Sherry On Mon, Aug 27, 2012 at 11:12 PM, Jeff Breidenbach wrote: > Hello all, > > The Mail Archive is now 14 years old (that's a long time in dog > years) and we've been thinking about some design updates. > The mockup below is intended for visitors from global search > engines. Direct visitors will continue to have no advertisements. > > I hope that the proposed design is an improvement. We have > already done some formal user testing, and now want to get > thoughts from expert users, including folks who currently entrust > data to the service. Any opinions or thoughts are appreciated, > especially specific suggestions. > > Also don't get too excited; even if everything goes smoothly it will > probably be several months from deployment. Thank you for > your time. > > Cheers, > Jeff > > http://www.maxdesign.com.au/jobs/318-mail-archive/38.htm > > > -- > To unsubscribe, send mail to [email protected]. -- To unsubscribe, send mail to [email protected].
Re: site design
Hi Jeff, > http://www.maxdesign.com.au/jobs/318-mail-archive/38.htm Generally, I like it. The "18-01-2012, 10:51PM -0800" date is re-formatted compared to the original email so I'd like some say over how it's displayed to me, e.g. preferences in a cookie, or else a better default; "2012-01-18 22:51:42 -0800" ;-). How do I get to view the original email that arrived, headers, warts, and all? I'd probably prefer the thread display at the bottom to be author first, then subject. Both can use CSS to cut off their text at the edge of their box, then fixed-width isn't required? Also, there doesn't seem much point making the author italic as its position in a column shows it's distinct from the surroundings? The Previous and Next buttons at the end are handy, though I'm not sure they need to say "message" too. But the pair are also required at the top of the page, though they could be more terse and smaller. What's important is that their position is fixed from page to page. This allows the mouse to stay in the same place and the user to click through whilst seeing just the first page of each email. Access keys should also be defined to do similar. Cheers, Ralph. -- To unsubscribe, send mail to [email protected].
Re: Archived-At links for new mails not working anymore (since June-10)
Hi Jeff, On Tue, Jul 3, 2012 at 2:33 AM, Jeff Breidenbach wrote: > Okay, found the bug. Great :-) & thanks for sharing the reason. > [...] I have hopefully corrected the > code, so there should be good data going forward. yes, confirmed. Works again for new messages. > Can you remind me which lists are actively using the Archived-At feature? It is added to all public lists managed by TDF, i.e. to all @*.libreoffice.org and all @documentfoundation.org mailinglists. see http://go.mail-archive.com/YDDU2NX9f8BkG1iXDzJPWzrrgrY= for a more or less recent list. ciao Christian -- To unsubscribe, send mail to [email protected].
Re: Archived-At links for new mails not working anymore (since June-10)
Okay, found the bug. On June 10th I made a change to deal with archives containing more than one million messages. A piece of code had decided that one million was a really big number and was starting to write scientific notation to some internal log files. Unfortunately my change was flawed and I've disrupted both the Archived-At database and sitemap entries for the last 20 days or so. I have hopefully corrected the code, so there should be good data going forward. Can you remind me which lists are actively using the Archived-At feature? -Jeff -- To unsubscribe, send mail to [email protected].
Re: [email protected] Slow to List New Posts?
Hi Jeff, > > Fair enough, I found how to have http://cr.yp.to/ezmlm.html > > subscribe something other than the envelope or header from address. > > If you think this would be useful for others, please consider sharing > either here, or we can put in the http://mail-archive.com/faq.html if > appropriate. Well, it's not rocket science but http://cr.yp.to/ezmlm.html didn't mention it and doesn't provide further links to online documentation. Mailing the list's help address for the auto-reply made clear that for list foo-bar at example.com one emails [email protected] instead of the normal [email protected] IOW, append the email address with @ turned into =. Cheers, Ralph. -- To unsubscribe, send mail to [email protected].
Re: [email protected] Slow to List New Posts?
> Fair enough, I found how to have http://cr.yp.to/ezmlm.html subscribe > something other than the envelope or header from address. If you think this would be useful for others, please consider sharing either here, or we can put in the http://mail-archive.com/faq.html if appropriate. > I was a bit surprised to see some of the "confirm"s go directly to the > new list's page though, e.g. > http://www.mail-archive.com/[email protected]/, rather than > http://www.mail-archive.com/[email protected]/ where some of the > others appeared. The automatic sorting algorithm noticed the List-Post header pointing to [email protected] and decided that the message was list traffic. Sorry for the confusion. -- To unsubscribe, send mail to [email protected].
Re: [email protected] Slow to List New Posts?
Hi, > I'm waiting for some subscription confirmations to turn up at > http://www.mail-archive.com/[email protected]/. OK, I think it was the SPF softfail that's making the mailing list discard my subscribe attempt. $ dig +short mail-archive.com txt "v=spf1 a ptr a:sea.gmane.org a:ciao.gmane.org a:deer.gmane.org ~all" $ Fair enough, I found how to have http://cr.yp.to/ezmlm.html subscribe something other than the envelope or header from address. I was a bit surprised to see some of the "confirm"s go directly to the new list's page though, e.g. http://www.mail-archive.com/[email protected]/, rather than http://www.mail-archive.com/[email protected]/ where some of the others appeared. Cheers, Ralph. -- To unsubscribe, send mail to [email protected].
Re: Archived-At links for new mails not working anymore (since June-10)
Hi Jeff, *, On Tue, Jun 26, 2012 at 6:10 AM, Jeff Breidenbach wrote: > Thanks for the note, we'll take a look. By the way, there's a discussion > about using a shorter URL. Would that be useful to you? When shorter URLs will be possible, we'll adopt them, but it is not critical for us. Most important for us is the gain in comfort. People have the message-thread in their local archives and want to point others to it. Now all they need is to copy the Archived-At Link, previously they had to go to the archive and spend time on searching/browsing the archive for the desired message (and often didn't bother to do so, and instead just wrote "has been discussed already, look it up in the archives" :-)). ciao Christian -- To unsubscribe, send mail to [email protected].
Re: Archived-At links for new mails not working anymore (since June-10)
Thanks for the note, we'll take a look. By the way, there's a discussion about using a shorter URL. Would that be useful to you? http://www.mail-archive.com/[email protected]/msg12770.html
Re: Dark for 24 hours, starting now
And a follow-up to let everyone know the blackout is complete. The web site is back to normal, and all messages were processed today as usual. Thanks to everyone that supported our decision to black out the website for the day. Reading all the activity around SOPA/PIPA protests online today confirmed it was a good move. Thanks Jeff On Tue, Jan 17, 2012 at 9:25 PM, Butch Evans wrote: > On Tue, 2012-01-17 at 21:20 -0800, Jeff Breidenbach wrote: > > The only change is all web pages are serving HTTP 503 (Service > > Temporarily Unavailable) for the next 24 hours. There is no disruption > > to email archival. > > Thanks for the clarification. As a consultant to ISPs, I can assure you > that I fully support your actions, along with the other participants in > the blackout. Along with a number of folks from my industry, I have > written to a large number of Senators and Congressmen requesting that > these bills be defeated. These are VERY BAD for the internet at large > and the bills (in general) are way too vague. Good for you for standing > up (or standing down, as it were) to be heard. > > -- > > * Butch Evans* Professional Network Consultation * > * http://www.butchevans.com/ * Network Engineering * > * http://store.wispgear.net/ * Wired or Wireless Networks * > * http://blog.butchevans.com/ * ImageStream, Mikrotik and MORE!* > * NOTE THE NEW PHONE NUMBER: 702-537-0979 * > > > > > > > -- > To unsubscribe, send mail to [email protected]. >
Re: Dark for 24 hours, starting now
On Tue, 2012-01-17 at 21:20 -0800, Jeff Breidenbach wrote: > The only change is all web pages are serving HTTP 503 (Service > Temporarily Unavailable) for the next 24 hours. There is no disruption > to email archival. Thanks for the clarification. As a consultant to ISPs, I can assure you that I fully support your actions, along with the other participants in the blackout. Along with a number of folks from my industry, I have written to a large number of Senators and Congressmen requesting that these bills be defeated. These are VERY BAD for the internet at large and the bills (in general) are way too vague. Good for you for standing up (or standing down, as it were) to be heard. -- * Butch Evans* Professional Network Consultation * * http://www.butchevans.com/ * Network Engineering * * http://store.wispgear.net/ * Wired or Wireless Networks * * http://blog.butchevans.com/ * ImageStream, Mikrotik and MORE!* * NOTE THE NEW PHONE NUMBER: 702-537-0979 * -- To unsubscribe, send mail to [email protected].
Re: Dark for 24 hours, starting now
The only change is all web pages are serving HTTP 503 (Service Temporarily Unavailable) for the next 24 hours. There is no disruption to email archival. We noticed at least one other email archival service (marc.info) is also participating. -Jeff
Re: Dark for 24 hours, starting now
On Tue, 2012-01-17 at 21:05 -0800, Jeff Breidenbach wrote: > The Mail Archive is now dark. > > > We will be offline for 24 hours in protest of proposed US censorship > laws. While I absolutely agree with your decision to do so, I just wanted to double check. Is the mail still being archived during this dark period? -- * Butch Evans* Professional Network Consultation * * http://www.butchevans.com/ * Network Engineering * * http://store.wispgear.net/ * Wired or Wireless Networks * * http://blog.butchevans.com/ * ImageStream, Mikrotik and MORE!* * NOTE THE NEW PHONE NUMBER: 702-537-0979 * -- To unsubscribe, send mail to [email protected].
Re: SOPA blackout Jan 18, 2012
A short follow-up: all incoming messages will still be received and processed. Only web page serving will be affected during that period. Thanks Jeff On Jan 16, 2012, at 1:06 PM, Jeff Breidenbach wrote: > The Mail Archive will be participating in SOPA Blackout Day. On January 18th, > 2012 we will be dark. > > The Stop Online Piracy Act H.R.3261 (and PIPA, its sister bill S.968) is a > proposed United States law, please read it yourself. The basic goal of the > bills is to censor all access to non-US websites involved with copyright > violation. We feel there are some fundamental flaws with the proposed > legislation. > > Lawrence Tribe, a Harvard Constitutional Law Professor points out > > 1) "Although SOPA's supporters have described the bill as directed at > "foreign rogue websites," the definitions in the bill are not in fact limited > to foreign sites or to sites engaged in egregious piracy." > > 2) "To compound the problem, SOPA provides that a complaining party can file > a notice alleging that it is harmed by the activities occurring on the site > "or portion thereof." Conceivably, an entire website containing tens of > thousands of pages could be targeted if only a single page were accused of > infringement." > > 3) "In effect, the bill would impose the very monitoring obligation that > existing law (in the form of the Digital Millennium Copyright Act of 1998) > expressly does not require. SOPA would undo the statutory framework that has > created the foundation for many web-based businesses." > > As a public email archival service, we are very aware and appreciative of > America's long history of free speech. We don't usually feel like a cog in a > censorship machine. Except for the 153 deletion requests from list > administrators, 4 DMCA takedown notices, and 36 suppression actions by global > internet search engines in 2011. That's on a corpus of 100+ million messages. > Now imagine getting sued or criminally prosecuted for a message that links to > some shady portion of the internet? Or when someone forwards a copyrighted > article to a mailing list? The Mail Archive has proudly provided archival > service for 14 years. But in the end, we are a three person, part-time small > business. If SOPA passes, each of us will have to think: We have families. > The risk looks enormous. -- To unsubscribe, send mail to [email protected].
Re: Happy 2012
> Finally, one of the charter goals of Mail Archive, Inc. is to have fun Mission accomplished. http://www.airshipventures.com/sightings/1290/2012/01/08 -- To unsubscribe, send mail to [email protected].
Re: tinyurl filtering
Hello Horace, thanks for pointing that out. It's entirely possibly (and likely) you are right about Postini's aggressiveness on the tinyurls. I attempted to add a whitelist rule for the [email protected] recipient address to bypass the Postini filtering; can you please send a test message to your list, or let me know when you make your next post that contains a tinyurl? Also, let me know if you see any odd behavior because of the whitelist rule I added. Thank you Jeff On Sun, Sep 18, 2011 at 11:56 PM, Horace Heffner wrote: > Hello, > > I today discovered that many of my posts to the vortex-l%40eskimo.com > newslist have not been archived since the beginning of the year. I narrowed > the problem down to one thing; any posts using www.tin yurl.com (remove > space between tin and yurl) references were filtered. These posts have > possibly been filtered as spam by Postini? > > I post tinyurls in addition to the long URLs as a courtesy to readers. This > avoids problems with line wrap etc. for long URLs, and has been requested by > members of the list that I do this. > > Filtering such a useful feature seems a bit draconian, even though it can be > used to hide spam. I have used this facility for list posting for years. It > was a surprise to find it has been unavailable to list users for months now. > > Any suggestions for a work-around appreciated. > > I hope this message is not filtered. > > Thank you for your consideration. > > Best regards, > > Horace Heffner > > > > > > > > -- > To unsubscribe, send mail to [email protected]. > -- To unsubscribe, send mail to [email protected].
Re: Re: [libreoffice-website] Archived-At: links not working since May 31th?
Hi Jeff, On Mon, Jun 27, 2011 at 3:02 AM, Jeff Breidenbach wrote: >> [hash-URLs and search by message-ID not working] >> > I assume the indexing is not running at their end for some reason. > > This should be completely resolved as of June 20th. Yes, can confirm that it's fixed. Thanks a lot! ciao Christian -- To unsubscribe, send mail to [email protected].
Re: Re: [libreoffice-website] Archived-At: links not working since May 31th?
On Sun, Jun 5, 2011 at 9:27 PM, Jeff Breidenbach wrote: > > I assume the indexing is not running at their end for some reason. > > That is exactly correct. If I run by hand it works fine, and that go > link will resolve now. Still looking into why the cron job that kicks > off indexing had trouble. Thanks for problem report. > This should be completely resolved as of June 20th. Cheers, Jeff
Re: search failure
Hi e-letter, > > http://www.mail-archive.com/search?q=merge&l=users%40global.libreoffice.org > > > > is more helpful. It didn't find > > > > http://www.mail-archive.com/[email protected]/msg00181.html > > > > which contains "The problem I'm having with the merge cell function". > > Do not understand; the search function does not work. Yes. We agree. The search function does not work for the [email protected] list when searching for the word "merge" as an example. Thank you for the report. Cheers, Ralph. -- To unsubscribe, send mail to [email protected].
Re: search failure
On 13/06/2011, Ralph Corderoy wrote: > e-letter wrote: >> On 13/06/2011, Jeff Breidenbach wrote: >> > On Sun, Jun 12, 2011 at 3:11 PM, e-letter wrote: >> > > Unable to use the search feature, e.g. search for "text" or "a" >> > > returns 0 results, clearly incorrect. >> > >> > Works for me, from both the home page and in an individual archive. >> > Can you please supply the exact search URL that is giving trouble? >> >> libreoffice mail archives > > Odd looking URL. :-( Perhaps > > > http://www.mail-archive.com/search?q=merge&l=users%40global.libreoffice.org > > is more helpful. It didn't find > > http://www.mail-archive.com/[email protected]/msg00181.html > > which contains "The problem I'm having with the merge cell function". Do not understand; the search function does not work. -- To unsubscribe, send mail to [email protected].
Re: search failure
e-letter wrote: > On 13/06/2011, Jeff Breidenbach wrote: > > On Sun, Jun 12, 2011 at 3:11 PM, e-letter wrote: > > > Unable to use the search feature, e.g. search for "text" or "a" > > > returns 0 results, clearly incorrect. > > > > Works for me, from both the home page and in an individual archive. > > Can you please supply the exact search URL that is giving trouble? > > libreoffice mail archives Odd looking URL. :-( Perhaps http://www.mail-archive.com/search?q=merge&l=users%40global.libreoffice.org is more helpful. It didn't find http://www.mail-archive.com/[email protected]/msg00181.html which contains "The problem I'm having with the merge cell function". Cheers, Ralph. -- To unsubscribe, send mail to [email protected].
Re: search failure
On 13/06/2011, Jeff Breidenbach wrote: > On Sun, Jun 12, 2011 at 3:11 PM, e-letter wrote: >> Unable to use the search feature, e.g. search for "text" or "a" >> returns 0 results, clearly incorrect. > > Works for me, from both the home page and in an individual archive. > Can you please supply the exact search URL that is giving trouble? > libreoffice mail archives -- To unsubscribe, send mail to [email protected].
Re: search failure
On Sun, Jun 12, 2011 at 3:11 PM, e-letter wrote: > Unable to use the search feature, e.g. search for "text" or "a" > returns 0 results, clearly incorrect. Works for me, from both the home page and in an individual archive. Can you please supply the exact search URL that is giving trouble? http://www.mail-archive.com/search?q=text&l=gossip%40jab.org http://www.mail-archive.com/find.php?cx=partner-pub-7266757337600734%3A2228981072&cof=FORID%3A9&ie=UTF-8&q=text&sa=Search -- To unsubscribe, send mail to [email protected].
