Quoting Michael M Slusarz :
Quoting Robin Bankhead :
Quoting Michael J Rubinsky :
Quoting Robin Bankhead :
Quoting Michael M Slusarz :
I *really* think this is probably the issue though. My memory
is that there were bugs in the past relating to PHP variable
references that may ca
Quoting Robin Bankhead :
Quoting Michael J Rubinsky :
Quoting Robin Bankhead :
Quoting Michael M Slusarz :
I *really* think this is probably the issue though. My memory is
that there were bugs in the past relating to PHP variable
references that may cause this kind of behavior. And
Quoting Michael J Rubinsky :
Quoting Robin Bankhead :
Quoting Michael M Slusarz :
I *really* think this is probably the issue though. My memory is
that there were bugs in the past relating to PHP variable
references that may cause this kind of behavior. And I would also
classify P
Quoting Robin Bankhead :
Quoting Michael M Slusarz :
I *really* think this is probably the issue though. My memory is
that there were bugs in the past relating to PHP variable
references that may cause this kind of behavior. And I would also
classify PHP 5.3.1 as ancient ... it's ov
Quoting Robin Bankhead :
Quoting Michael M Slusarz :
Quoting Robin Bankhead :
Quoting Robin Bankhead :
Quoting Michael M Slusarz :
Quoting Robin Bankhead :
Didn't want to ticket this automatically in case it's put down
to bad message format (I'm no expert but this seems a common
re
Quoting Michael M Slusarz :
Quoting Robin Bankhead :
Quoting Robin Bankhead :
Quoting Michael M Slusarz :
Quoting Robin Bankhead :
Didn't want to ticket this automatically in case it's put down
to bad message format (I'm no expert but this seems a common
reply to such issues).
The
Quoting Robin Bankhead :
Quoting Robin Bankhead :
Quoting Michael M Slusarz :
Quoting Robin Bankhead :
Didn't want to ticket this automatically in case it's put down to
bad message format (I'm no expert but this seems a common reply
to such issues).
The (redacted) message below is all
Quoting Robin Bankhead :
Quoting Michael M Slusarz :
Quoting Robin Bankhead :
Didn't want to ticket this automatically in case it's put down to
bad message format (I'm no expert but this seems a common reply to
such issues).
The (redacted) message below is all base64-encoded text/plain
- Message from Robin Bankhead -
Date: Tue, 14 Jan 2014 14:21:09 +
From: Robin Bankhead
Subject: Re: [imp] Base64-only message not quoted in reply
To: imp@lists.horde.org
Quoting Michael M Slusarz :
Quoting Robin Bankhead :
Didn't want to ticket
Quoting Michael M Slusarz :
Quoting Robin Bankhead :
Didn't want to ticket this automatically in case it's put down to
bad message format (I'm no expert but this seems a common reply to
such issues).
The (redacted) message below is all base64-encoded text/plain and
has no plaintext par
Quoting Robin Bankhead :
Didn't want to ticket this automatically in case it's put down to
bad message format (I'm no expert but this seems a common reply to
such issues).
The (redacted) message below is all base64-encoded text/plain and
has no plaintext part. It views fine, but when rep
Hi,
Didn't want to ticket this automatically in case it's put down to bad
message format (I'm no expert but this seems a common reply to such
issues).
The (redacted) message below is all base64-encoded text/plain and has
no plaintext part. It views fine, but when replying to it, it is no
12 matches
Mail list logo
