Gil,
Contact me off-list if you haven't heard from me already (I have an email
address for you but it may be old).
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with t
On Wed, 9 Aug 2017 09:02:25 -0400, zMan wrote:
>OK, fair 'nuff! I'm on a horrible connection, wasn't inclined to dig.
>Has anyone asked them? Just wondering. They at least used to be a great
>company.
>
They won't talk to me, or even let me subscribe to their own LISTSERV unless
I have a customer
OK, fair 'nuff! I'm on a horrible connection, wasn't inclined to dig.
Has anyone asked them? Just wondering. They at least used to be a great
company.
On Wed, Aug 9, 2017 at 9:00 AM, Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> On Wed, 9 Aug 2017 08:29:39 -0400, zMan
On Wed, 9 Aug 2017 08:29:39 -0400, zMan wrote:
>Before blaming L-Soft, it probably makes sense to be sure the list is
>running current software. I know many lists are way backlevel...
>
The logo at the top of this page shows "LISTSERV 16.0". The page at
http://www.lsoft.com/products/listserv_os.
SHA1
>
> On Tue, 8 Aug 2017 12:36:00 -0500, Elardus Engelbrecht
> (elardus.engelbre...@sita.co.za) wrote about "Curse you, L-Soft!" (in
> <8733075135946583.wa.elardus.engelbrechtsita.co...@listserv.ua.edu>):
>
> > David W Noon wrote:
> [snip]
> >> Hash
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 8 Aug 2017 12:36:00 -0500, Elardus Engelbrecht
(elardus.engelbre...@sita.co.za) wrote about "Curse you, L-Soft!" (in
<8733075135946583.wa.elardus.engelbrechtsita.co...@listserv.ua.edu>):
> David W Noon wrote:
[snip]
>&g
On Tue, 8 Aug 2017 18:24:29 +0100, David W Noon wrote:
>
>Mutt has always been very RFC-compliant.
>
Meaning both that it obeys the rules in the RFCs and doesn't invent any
of its own.
>Microsoft sets the standards.
>
I'm mad as hell, and I'm not going to take it anymore!
>Another problem with
David W Noon wrote:
>-BEGIN PGP SIGNED MESSAGE-
First time I see this prefix message with PGP and word MESSAGE. Hmmm,
interesting. I really need to do drink coffee and then RTFM...
>Hash: SHA1
You're using SHA1, not SHA256? Ok, what e-mail software are you using. If you
don't wan
On Tue, 8 Aug 2017 09:16:18 -0500, Paul Gilmartin (Paul Gilmartin) wrote
about Curse you, L-Soft!:
[snip]
> According to various experiments and headers of off-list messages:
>
> MacOS Mail.app sends utf-8 as quoted-printable but deals corectly with
> incoming 8-bit/
>
> Fr
(off-list)
On 2017-08-08, at 10:50, David W Noon wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Tue, 8 Aug 2017 01:45:22 -0500, Elardus Engelbrecht (Elardus
> Engelbrecht ) wrote about Re: Curse
> you, L-Soft!:
>
>> David W Noon wrote:
>>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 8 Aug 2017 01:45:22 -0500, Elardus Engelbrecht (Elardus
Engelbrecht ) wrote about Re: Curse
you, L-Soft!:
> David W Noon wrote:
>
> >Sometimes Base64 or other binary-safe encoding is required by RFC.
>
> So I see. Than
(sent via web interface)
On Tue, 8 Aug 2017 01:45:22 -0500, Elardus Engelbrecht wrote:
>David W Noon wrote:
>
>>Sometimes Base64 or other binary-safe encoding is required by RFC.
>
>So I see. Thanks. Wish Shmuel is here, he certainly has something to say about
>all these RFC requirements...
>
Acc
David W Noon wrote:
>Sometimes Base64 or other binary-safe encoding is required by RFC.
So I see. Thanks. Wish Shmuel is here, he certainly has something to say about
all these RFC requirements...
>MTA = Mail Transfer Agent
>This is/are the SMTP server(s) used to move email around.
>Using a fu
On Mon, Aug 07, 2017 at 03:45:08PM -0500, Joel C. Ewing wrote:
>
> As an experiment, I will try adding some "unusual" characters (like
> degree ° and check__✔) to force Content-Transfer-Encoding: 8bit and see
> what the list does to this message.__
>
(antiquated) MacOS Mail.app seems to force Q-
On Mon, 7 Aug 2017 15:45:08 -0500, Joel C. Ewing wrote:
>
> As an experiment, I will try adding some "unusual" characters (like
>degree ° and check__✔) to force Content-Transfer-Encoding: 8bit and see
>what the list does to this message.__
>
It came to me as:
Content-Type: text/plain; charse
On 08/07/2017 01:54 PM, David W Noon wrote:
> On Mon, 7 Aug 2017 13:08:20 -0500, Elardus Engelbrecht
> (elardus.engelbre...@sita.co.za) wrote about "Re: Curse you, L-Soft!"
> (in <6156763411207138.wa.elardus.engelbrechtsita.co...@listserv.ua.edu>):
>
>> Paul Gil
On Mon, 7 Aug 2017 13:08:20 -0500, Elardus Engelbrecht
(elardus.engelbre...@sita.co.za) wrote about "Re: Curse you, L-Soft!"
(in <6156763411207138.wa.elardus.engelbrechtsita.co...@listserv.ua.edu>):
> Paul Gilmartin wrote:
>
>> I can neither submit an SR to L-Soft no
Paul Gilmartin wrote:
>I can neither submit an SR to L-Soft nor rant on the L-Soft mailing list
>because I'm not a registered L-Soft customer.
I feel your pain. I also wanted to moan and b*tch about base 64 encoding
amongst other things, but ...
>o When I attempt to reply to a submitter rathe
I can neither submit an SR to L-Soft nor rant on the L-Soft
mailing list because I'm not a registered L-Soft customer.
And no owner of a LISTSERV to which I subscribe seems interested
in championing my cause. So, I'll vent here (again).
Mostly about composing or replying via the Web interface.
o
19 matches
Mail list logo
