pe...@easthope.ca writes:
* From: Reco recovery...@enotuniq.net
* Date: Mon, 22 Jul 2019 17:35:27 +0300
> You're breaking threading. Just a friendly note.
I've been adding References manually. By "breaking" do you refer to
omission of older references (For example,
On Tue 23 Jul 2019 at 08:56:36 (-0700), pe...@easthope.ca wrote:
> In future I'll make more effort with the references. Beyond 3 or 4 it
> can be tedious.
If you're typing (or pasting) the references, I would just add
the In-Reply-To instead. That way, you can Cut/Copy the original's
On Tue, 23 Jul 2019 12:28:50 -0400
Greg Wooledge wrote:
Hello Greg,
>We may be seeing different symptoms as a result of *whatever* Peter is
>doing, depending on how each individual mail transport agent and each
>mail user agent deals with the incoming mess.
Indeed.
I looked up his MUA
On Tue, Jul 23, 2019 at 05:22:44PM +0100, Brad Rogers wrote:
> On Tue, 23 Jul 2019 12:16:31 -0400
> Greg Wooledge wrote:
>
> Hello Greg,
>
> >You need to add "In-Reply-To:" as well. And stop doing whatever it is
> >you're doing that puts NUL bytes in your "* From:" lines. Or simply
>
Hi.
On Tue, Jul 23, 2019 at 08:56:36AM -0700, pe...@easthope.ca wrote:
> * From: Reco ?recovery...@enotuniq.net?
> * Date: Mon, 22 Jul 2019 17:35:27 +0300
> > You're breaking threading. Just a friendly note.
>
> I've been adding References manually. By "breaking" do you refer
On Tue, 23 Jul 2019 12:16:31 -0400
Greg Wooledge wrote:
Hello Greg,
>You need to add "In-Reply-To:" as well. And stop doing whatever it is
>you're doing that puts NUL bytes in your "* From:" lines. Or simply
>drop those lines altogethe
I /think/ they're tab characters. At least, that
On Tue, Jul 23, 2019 at 08:56:36AM -0700, pe...@easthope.ca wrote:
> * From: Reco
> > You're breaking threading. Just a friendly note.
>
> I've been adding References manually.
You need to add "In-Reply-To:" as well. And stop doing whatever it is
you're doing that puts NUL bytes in your "*
* From: Reco
he email address (which
> is presumably disabling all further rendering in this version of kmail
> (1.13.7, on kde 4.8.4), and a 0x09 in the byte after the email address.
>
> So, I guess I have a way to send secret messages (to, at least, myself ;-)
Here's what I see in mutt:
Date: Mo
On Monday 22 July 2019 15:48:08 rhkra...@gmail.com wrote:
> On Monday, July 22, 2019 11:52:59 AM Greg Wooledge wrote:
> > On Mon, Jul 22, 2019 at 11:40:59AM -0400, rhkra...@gmail.com wrote:
> > >* but when I view source in my email client (kmail 3.n), I see
> > > just the "*
> > >
> > > From:
On 7/22/19, Gene Heskett wrote:
> I've also never seen this header line before:
>
> X-Mailer: Oberon Mail (ejz) on LinuxA2 Gen. 32-bit, rev.8586
I've been following this partially in between some other things. A
super quick search that led to a few more where pieces of that were
DELETED... kept
On Monday, July 22, 2019 11:52:59 AM Greg Wooledge wrote:
> On Mon, Jul 22, 2019 at 11:40:59AM -0400, rhkra...@gmail.com wrote:
> >* but when I view source in my email client (kmail 3.n), I see just
> >the "*
> >
> > From: Reco" that I see when viewing the email "normally".
> >
> > So,
Gene, on 2019-07-22 :
> I don't think so, the only pdp-11, I ever tangled with crashed a dozen
> times a day so I refuse to even capitalize the model name.
Hi Gene,
That is a bit off-topic, but in my (somewhat small) world,
lowercase are glorifying in themselves, see dmr, or rms.
Uppercase is
On Monday 22 July 2019 12:43:43 Reco wrote:
> On Mon, Jul 22, 2019 at 05:50:30PM +0200, to...@tuxteam.de wrote:
> > > And this:
> > > > X-Mailer: Oberon Mail (ejz) on LinuxA2 Gen. 32-bit, rev.8586
> >
> > Wow. This [1] one? The elder among us stand in awe. Oberon still
> > alive...
> >
> > >
On Mon, Jul 22, 2019 at 01:04:29PM -0400, Gene Heskett wrote:
> I'm using kmail from TDE. R14.0.7. It has a view raw message mode. And
> the msg ends with "From Reco"
>
> But the barracuda spam report just above it says there's a null byte in
> the body. That might be being taken as "EOF" by
On Monday 22 July 2019 11:52:59 Greg Wooledge wrote:
> On Mon, Jul 22, 2019 at 11:40:59AM -0400, rhkra...@gmail.com wrote:
> >* but when I view source in my email client (kmail 3.n), I see
> > just the "* From: Reco" that I see when viewing the email
> > "normally".
> >
> > So, it seems,
On Mon, Jul 22, 2019 at 05:50:30PM +0200, to...@tuxteam.de wrote:
> > And this:
> >
> > > X-Mailer: Oberon Mail (ejz) on LinuxA2 Gen. 32-bit, rev.8586
>
> Wow. This [1] one? The elder among us stand in awe. Oberon still
> alive...
>
> > Looks rather unusual to me.
>
> Yes, but of historical
On Mon, Jul 22, 2019 at 11:40:59AM -0400, rhkra...@gmail.com wrote:
>* but when I view source in my email client (kmail 3.n), I see just the "*
>
> From: Reco" that I see when viewing the email "normally".
>
> So, it seems, something is filtering out a lot of the content of the email
On Mon, Jul 22, 2019 at 06:08:32PM +0300, Reco wrote:
> Hi.
>
> On Mon, Jul 22, 2019 at 11:00:20AM -0400, rhkra...@gmail.com wrote:
> > Anybody know what these no content messagess are about? Just spam?
>
> Mutt does show the contents to me. A text/plain with an unconventional
> quoting
On Monday, July 22, 2019 11:11:42 AM Andy Smith wrote:
> Hello,
>
> On Mon, Jul 22, 2019 at 11:00:20AM -0400, rhkra...@gmail.com wrote:
> > Anybody know what these no content messagess are about? Just spam?
>
> I haven't seen one without content, but I haven't read them as the
> quoting is so
Hi.
On Mon, Jul 22, 2019 at 11:00:20AM -0400, rhkra...@gmail.com wrote:
> Anybody know what these no content messagess are about? Just spam?
Mutt does show the contents to me. A text/plain with an unconventional
quoting style.
Threading is borken, though.
And this:
> X-Mailer: Oberon
Hello,
On Mon, Jul 22, 2019 at 11:00:20AM -0400, rhkra...@gmail.com wrote:
> Anybody know what these no content messagess are about? Just spam?
I haven't seen one without content, but I haven't read them as the
quoting is so broken it's too hard to read. Maybe check with the archives
and see if
Anybody know what these no content messagess are about? Just spam?
On Monday, July 22, 2019 09:32:36 AM pe...@easthope.ca wrote:
> * From: Reco
Hi.
You're breaking threading. Just a friendly note.
> On Mon, Jul 22, 2019 at 06:32:36AM -0700, pe...@easthope.ca wrote:
> Anything remarkable?
Nope, but that's expected.
Squid never logged served connections into the syslog.
Also note you either need to configure Squid as a
* From: Reco ptors available
Jul 22 06:11:14 dalton squid[3050]: Initializing IP Cache...
Jul 22 06:11:14 dalton squid[3050]: DNS Socket created at [::], FD 5
Jul 22 06:11:14 dalton squid[3050]: DNS Socket created at 0.0.0.0, FD 9
Jul 22 06:11:14 dalton squid[3050]: Adding domain
On Sat, Jul 20, 2019 at 12:23:47PM -0700, pe...@easthope.ca wrote:
> Is there a simple way to demonstrate something reported to a log?
> Similar to "telnet a.smtp.server 587".
wget -O - http://
curl -vL http:// >/dev/null
nmap -sT -p 80
Reco
* From: Reco
Hi.
On Sat, Jul 20, 2019 at 08:28:30AM -0700, pe...@easthope.ca wrote:
> * From: Reco �recovery...@enotuniq.net�
> * Date: Thu, 18 Jul 2019 10:13:58 +0300
> > For the whole Internet - *maybe* (and that's a big one) squid can do
> > the job.
>
> The story here is a different case
* From: Reco
On Wed, Jul 17, 2019 at 02:32:28PM -0700, pe...@easthope.ca wrote:
> > stunnel(1) mentions helpfully that you're required to have a certain
> > netfilter setup (mainly involving DNAT in your case), ...
> > If you need to transform outbound HTTP requests to HTTPS to multiple
> > hosts ...
>
>
Hi.
On Wed, Jul 17, 2019 at 08:55:39PM -0700, pe...@easthope.ca wrote:
> * From: "D. R. Evans" �doc.ev...@gmail.com�
> * Date: Wed, 17 Jul 2019 17:01:22 -0600
> > That doesn't seem to be correct. The original e-mail said:
> >> Jul 16 11:25:16 joule stunnel: LOG5[4]: Service
On 18/07/19 3:55 PM, pe...@easthope.ca wrote:
> * From: "D. R. Evans" €doc.ev...@gmail.com€
> * Date: Wed, 17 Jul 2019 17:01:22 -0600
>> That doesn't seem to be correct. The original e-mail said:
>>> Jul 16 11:25:16 joule stunnel: LOG5[4]: Service [https] accepted connection
>>> from
* From: "D. R. Evans"
pe...@easthope.ca wrote on 7/17/19 3:32 PM:
> Jul 16 11:25:16 joule stunnel: LOG5[4]: Service [https] accepted connection
> from 127.0.0.1:36140
>
> * From: Reco recovery...@enotuniq.net
> * Date: Wed, 17 Jul 2019 11:01:32 +0300
>> No, you're incorrect. A client application has
Jul 16 11:25:16 joule stunnel: LOG5[4]: Service [https] accepted connection
from 127.0.0.1:36140
* From: Reco ... Peter E.
--
https://en.wikibooks.org/wiki/Oberon
Tel: +1 604 670 0140Bcc: peter at easthope. ca
35 matches
Mail list logo
