From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.corp.redhat.com (int-mx16.intmail.prod.int.phx2.redhat.com [10.5.11.28]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id v0KEESHE006296 for ; Fri, 20 Jan 2017 09:14:28 -0500 Received: by smtp.corp.redhat.com (Postfix) id E714B1D98C0; Fri, 20 Jan 2017 14:14:28 +0000 (UTC) Received: from mx1.redhat.com (ext-mx06.extmail.prod.ext.phx2.redhat.com [10.5.110.30]) by smtp.corp.redhat.com (Postfix) with ESMTPS id E16F91D98C1 for ; Fri, 20 Jan 2017 14:14:28 +0000 (UTC) Received: from mail-ua0-f194.google.com (mail-ua0-f194.google.com [209.85.217.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id A1E1C3DBC2 for ; Fri, 20 Jan 2017 14:14:27 +0000 (UTC) Received: by mail-ua0-f194.google.com with SMTP id i68so7335638uad.1 for ; Fri, 20 Jan 2017 06:14:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:user-agent:mime-version; bh=dZHg8uO7tiwIHgEMC6YNWrfeYPG+uzVgFDVqSqzYNPA=; b=MN5LM3P3QZqazCI4wxtrQK4nFljQJ73B1khbv0sk+atskt9EAH8KYpJMEhrbjbkDiB JtF+sXSz7exLJW7C8FWG+uV7Ng/uKR6gHZMmwV5RM2uk+QcVI47GK95pOWPpMaG/vY9g BoHO+ZMEujHWdVerkbIQTOjn4VbtPx86dCeRbLQwoAdsGWjz9tGtiXbFYR5UMK1Bd4BH Z43DC70X/xxOg8Ojspz0RebwTWJO6/U1i6dLZYcaOuEH2IfntzYsxVpUqVixqnfk02d0 77otw+ny6oG7p0sgH2L6Qx7gczkHdiID5ouapKeaO2dOmDtxLCZp+/YFUjc22li2Dj5l JVXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:user-agent :mime-version; bh=dZHg8uO7tiwIHgEMC6YNWrfeYPG+uzVgFDVqSqzYNPA=; b=JRdzQD4aNtR/kMkD4D2FpXYV5pg4+j6srW+5jAZTfQRc3GNsuSlfv1Sd/pcpmtmZZa IiNQXFb8xAxfifIxAn6JqPojjfTDlDx7jbuvxI61Ih2tOa/8oh3p9CcTtWsGc+aX95xp cQ5y9QOK7weTkPNKnM3uVUsWHAKJ+Dflxn7HgvGEoWZSAUbnxQKKt2qdrICbBhPkx/4r ZRN4p/dsNeLyfW6/aqj5fjwDXbEO8qb6O34DmolIYBQOTVew0UAs1p1urgEXZWmL8miI p7olL0WMDIzr9lLSjSHntSItG9hs8c2hOHan763nxfuczAD4s+Ni22fI3tEpQDy3Egbi wiBQ== X-Gm-Message-State: AIkVDXK0HyPwYcNYLDN01q8M8Zqa14+MXu5RNvfbXvlOD47jGC1FFHNiB8Y4Yl98ikbTzA== X-Received: by 10.200.50.97 with SMTP id y30mr12501561qta.194.1484921665746; Fri, 20 Jan 2017 06:14:25 -0800 (PST) Received: from ds-mac-mini.home (pool-96-236-145-55.pitbpa.ftas.verizon.net. [96.236.145.55]) by smtp.googlemail.com with ESMTPSA id 37sm6008746qto.43.2017.01.20.06.14.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 20 Jan 2017 06:14:25 -0800 (PST) Date: Fri, 20 Jan 2017 09:14:23 -0500 (EST) From: "Dan D." X-X-Sender: dandunfee@ds-mac-mini.home To: Karen Lewellen Subject: Re: A challenging question? Message-ID: User-Agent: Alpine 2.20 (OSX 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Fri, 20 Jan 2017 14:14:27 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Fri, 20 Jan 2017 14:14:27 +0000 (UTC) for IP:'209.85.217.194' DOMAIN:'mail-ua0-f194.google.com' HELO:'mail-ua0-f194.google.com' FROM:'dandunfee@gmail.com' RCPT:'' X-RedHat-Spam-Score: 1.17 * (BAYES_50, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, RCVD_IN_SORBS_SPAM, SPF_PASS) 209.85.217.194 mail-ua0-f194.google.com 209.85.217.194 mail-ua0-f194.google.com X-Scanned-By: MIMEDefang 2.78 on 10.5.110.30 X-Scanned-By: MIMEDefang 2.74 on 10.5.11.28 X-loop: blinux-list@redhat.com Cc: Linux for blind general discussion X-BeenThere: blinux-list@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk Reply-To: Linux for blind general discussion List-Id: Linux for blind general discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2017 14:14:29 -0000 Iuse alpine with a gmail account with no problems recieving or sending. Pine would work in your case also. The only real issue for someone is to link gmail to a local alpine mail account, its just a matter of simple configuration entries to do it. If I were you I would set up an alpine filter to automatically grab those messages of interesst into one mail folder. Then the entire contents of each message can be exported as individual plain texts with one command. On Fri, 20 Jan 2017, Karen Lewellen wrote: > Fine, but logging into gmail is not the problem. It is gathering in a > fashion that reflects how these e-mails appear in a low graphics > environment. That and the volume. > Whatever the program is, does it exist at shellworld? I have no other > access to Linux at all, save for my office shell with dreamhost. > > > On Fri, 20 Jan 2017, Jude DaShiell wrote: > >> tmux, not tmox. >> >> On Thu, 19 Jan 2017, Karen Lewellen wrote: >> >>> Date: Thu, 19 Jan 2017 23:42:30 >>> From: Karen Lewellen >>> Reply-To: Linux for blind general discussion >>> To: Linux for blind general discussion >>> Subject: Re: A challenging question? >>> >>> Hi folks, >>> I do wonder if we have tmox at shellworld. >>> Actually, the printer friendly edition of emails at google will produce >>> fine text, and yes I can save the file with the p function. >>> The challenge is, since this is court evidence, I must gather likely a >>> couple hundred of them. >>> Something to petition the judge regarding. >>> Thanks for the ideas, >>> Kare >>> >>> >>> On Thu, 19 Jan 2017, Tim Chase wrote: >>> >>>> On January 19, 2017, Karen Lewellen wrote: >>>>> Asking just in case there is a simple tool for this process. >>>>> I need to capture several emails from my gmail account. It is >>>>> critical that the e-mails appear, as they do for me, not how they >>>>> might in standard view, i. e. with alt tags visible for anyone. >>>>> Lynx, links, and e-links are the browsers I wish to use for this, I >>>>> would imagine the alt tag would be different even if I had access >>>>> to say Firefox. >>>> >>>> Depending on the target audience, a couple ways come to mind: >>>> >>>> 1) In lynx-the-cat, use the "p" command to print to a file. This is >>>> basically the same thing as doing a "lynx -dump" on a page. In >>>> links-the-chain and elinks, you can use "File, Save formatted >>>> document" to get the same sort of results. >>>> >>>> 2) use your terminal emulator's copy/paste functionality to select >>>> the content of the gmail session in lynx/links/elinks session >>>> >>>> 3) fire up GNU screen or tmux, launch Lynx inside, browse to your >>>> email, and then use the "scrollback" functionality in screen/tmux to >>>> copy text off the screen into a buffer, then use the screen/tmux >>>> scrollback-paste functionality to dump it into a file. >>>> >>>> 4) use the "script" program to record the entire session with >>>> timings: >>>> >>>> $ script --timing=gmail.timings gmail.script >>>> $ lynx https://gmail.com >>>> (do your thing) >>>> $ exit # leaves the "script" recording session >>>> >>>> this will give you two files "gmail.timings" and "gmail.script" which >>>> you can then play back with >>>> >>>> $ scriptreplay gmail.timings gmail.script >>>> >>>> Now on to comparing: >>>> >>>> #1 is easiest choice with some of the best results for the use-case >>>> you are describing. >>>> >>>> #2 & #3 are basically a screen capture of the text that you can dump >>>> into a text file, but don't include any coloration or playback (like >>>> #1). Also, these usually end up being one screen at a time with >>>> full-screen curses applications like lynx/links/elinks, so if your >>>> text is more than one page, it's a bit annoying to capture, save, >>>> scroll, capture, save, repeat. But they do work for any terminal >>>> application, not just relying on browser-specific functionality. >>>> >>>> #4 gives an exact replay of the options, but requires a terminal that >>>> understands it. If you're playing back on the same terminal where >>>> you recorded, this has no issues. But if you're trying to share it, >>>> there may be hurdles involved. Also, while a quick test here >>>> suggests that script doesn't capture passwords in certain modes, it >>>> might if recording a lynx/links session, so I'd either only share it >>>> with someone you trust with your gmail password, or redact the file >>>> before sharing it. >>>> >>>> And if you haven't had a chance to play with screen/tmux, they're >>>> incredibly powerful and well worth the investment of time (I >>>> personally prefer and recommend tmux, but both are substantially >>>> similar to the end user). >>>> >>>> As usual, my verbose replies are likely overkill, but hopefully give >>>> you some options to explore. (grins) >>>> >>>> -tim >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Blinux-list mailing list >>>> Blinux-list@redhat.com >>>> https://www.redhat.com/mailman/listinfo/blinux-list >>>> >>>> >>> >>> _______________________________________________ >>> Blinux-list mailing list >>> Blinux-list@redhat.com >>> https://www.redhat.com/mailman/listinfo/blinux-list >>> >> >> -- >> >> _______________________________________________ >> Blinux-list mailing list >> Blinux-list@redhat.com >> https://www.redhat.com/mailman/listinfo/blinux-list >> >> >> > > _______________________________________________ > Blinux-list mailing list > Blinux-list@redhat.com > https://www.redhat.com/mailman/listinfo/blinux-list > XB