Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

Avoid strange women and temporary variables.


computers / comp.mail.pine / IMAP E-Mail sending question.

SubjectAuthor
* IMAP E-Mail sending question.Bud Spencer
+* Re: IMAP E-Mail sending question.Eduardo Chappa
|`* Re: IMAP E-Mail sending question.Bud Spencer
| `* Re: IMAP E-Mail sending question.Eduardo Chappa
|  `- Re: IMAP E-Mail sending question.Bud Spencer
+* Re: IMAP E-Mail sending question.Henning Hucke
|`* Re: IMAP E-Mail sending question.Bud Spencer
| `* Re: IMAP E-Mail sending question.Henning Hucke
|  `- Re: IMAP E-Mail sending question.Bud Spencer
`* Re: IMAP E-Mail sending question.Adam H. Kerman
 +* Re: IMAP E-Mail sending question.Bud Spencer
 |`* Re: IMAP E-Mail sending question.Adam H. Kerman
 | `- Re: IMAP E-Mail sending question.Bud Spencer
 `* Re: IMAP E-Mail sending question.Eduardo Chappa
  +- Re: IMAP E-Mail sending question.Bud Spencer
  +* Re: IMAP E-Mail sending question.Adam H. Kerman
  |`- Re: IMAP E-Mail sending question.Adam H. Kerman
  `* Re: IMAP E-Mail sending question.Adam H. Kerman
   `* Re: IMAP E-Mail sending question.Bud Spencer
    `* Re: IMAP E-Mail sending question.Bud Spencer
     `* Re: IMAP E-Mail sending question.Eduardo Chappa
      +* Re: IMAP E-Mail sending question.Bud Spencer
      |`- Re: IMAP E-Mail sending question.Adam H. Kerman
      `* Re: IMAP E-Mail sending question.Adam H. Kerman
       `* Re: IMAP E-Mail sending question.Henning Hucke
        `- Re: IMAP E-Mail sending question.Adam H. Kerman

Pages:12
IMAP E-Mail sending question.

<alpine.BSF.2.21.9999.2208032027080.11738@cerebro.liukuma.net>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=422&group=comp.mail.pine#422

 copy link   Newsgroups: comp.mail.pine
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx08.iad.POSTED!not-for-mail
Newsgroups: comp.mail.pine
From: bud...@campo.verano.it (Bud Spencer)
Reply-To: Bud Spencer <bud@campo.verano.it>
Subject: IMAP E-Mail sending question.
Message-ID: <alpine.BSF.2.21.9999.2208032027080.11738@cerebro.liukuma.net>
User-Agent: Alpine 2.21.9999 (BSF 287 2018-06-16)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="2739015498-468396953-1659547978=:11738"
Lines: 29
X-Complaints-To: abuse@usenetserver.com
NNTP-Posting-Date: Wed, 03 Aug 2022 17:33:00 UTC
Organization: UsenetServer - www.usenetserver.com
Date: Wed, 3 Aug 2022 20:32:56 +0300
X-Received-Bytes: 1614
 by: Bud Spencer - Wed, 3 Aug 2022 17:32 UTC

Hi there.

I'm wondering about the following thing:

There is a server A and Alpine is running on that server and is configured
to talk with mail.server.a and there is user@server.a account.

Then I'll set up Alpine to use IMAP to get E-Mails from server B,
user@server.b ... now when I send E-Mails as user@server.b using
mail.server.b, does Alpine include some indentifying things into header of
those E-Mails that can point out to server.a?

I'd like to keep these two separated, yet use Alpine on server.a to
send/receive both ...

Hope my question made some sense :)

--
₪ BUD ₪

Re: IMAP E-Mail sending question.

<9c3c9df0-0846-f260-a5bd-a815810325fc@washington.edu>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=423&group=comp.mail.pine#423

 copy link   Newsgroups: comp.mail.pine
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: cha...@washington.edu (Eduardo Chappa)
Newsgroups: comp.mail.pine
Subject: Re: IMAP E-Mail sending question.
Date: Wed, 3 Aug 2022 13:06:16 -0600
Organization: A noiseless patient Spider
Lines: 21
Message-ID: <9c3c9df0-0846-f260-a5bd-a815810325fc@washington.edu>
References: <alpine.BSF.2.21.9999.2208032027080.11738@cerebro.liukuma.net>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
Injection-Info: reader01.eternal-september.org; posting-host="123f5ba1ee5c355ecf5adab349adfdca";
logging-data="2548181"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/l0dTV6uZE3bv6xdlUmMWT"
Cancel-Lock: sha1:fcYC2aCYvXxngkBF2MTllu1tlAo=
In-Reply-To: <alpine.BSF.2.21.9999.2208032027080.11738@cerebro.liukuma.net>
 by: Eduardo Chappa - Wed, 3 Aug 2022 19:06 UTC

On Wed, 3 Aug 2022, Bud Spencer wrote:

> There is a server A and Alpine is running on that server and is
> configured to talk with mail.server.a and there is user@server.a
> account.
>
> Then I'll set up Alpine to use IMAP to get E-Mails from server B,
> user@server.b ... now when I send E-Mails as user@server.b using
> mail.server.b, does Alpine include some indentifying things into header
> of those E-Mails that can point out to server.a?

Alpine will not add anything that is not requested by protocols. SMTP
asks that computers identify themselves (by their IP address) so the IP
address of server.a will be available to the smtp server.b, which will be
included in the Received: headers.

Other than that, everything can be set up and kept separately.

--
Eduardo
https://alpineapp.email

Re: IMAP E-Mail sending question.

<alpine.BSF.2.21.9999.2208032224460.67262@cerebro.liukuma.net>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=424&group=comp.mail.pine#424

 copy link   Newsgroups: comp.mail.pine
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx01.iad.POSTED!not-for-mail
Newsgroups: comp.mail.pine
From: bud...@campo.verano.it (Bud Spencer)
Reply-To: Bud Spencer <bud@campo.verano.it>
Subject: Re: IMAP E-Mail sending question.
In-Reply-To: <9c3c9df0-0846-f260-a5bd-a815810325fc@washington.edu>
Message-ID: <alpine.BSF.2.21.9999.2208032224460.67262@cerebro.liukuma.net>
References: <alpine.BSF.2.21.9999.2208032027080.11738@cerebro.liukuma.net> <9c3c9df0-0846-f260-a5bd-a815810325fc@washington.edu>
User-Agent: Alpine 2.21.9999 (BSF 287 2018-06-16)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="2739015498-1344332946-1659554792=:67262"
Lines: 42
X-Complaints-To: abuse@usenetserver.com
NNTP-Posting-Date: Wed, 03 Aug 2022 19:26:34 UTC
Organization: UsenetServer - www.usenetserver.com
Date: Wed, 3 Aug 2022 22:26:31 +0300
X-Received-Bytes: 2302
 by: Bud Spencer - Wed, 3 Aug 2022 19:26 UTC

On Wed, 3 Aug 2022, Eduardo Chappa wrote:

> On Wed, 3 Aug 2022, Bud Spencer wrote:
>
>> There is a server A and Alpine is running on that server and is configured
>> to talk with mail.server.a and there is user@server.a account.
>>
>> Then I'll set up Alpine to use IMAP to get E-Mails from server B,
>> user@server.b ... now when I send E-Mails as user@server.b using
>> mail.server.b, does Alpine include some indentifying things into header of
>> those E-Mails that can point out to server.a?
>
> Alpine will not add anything that is not requested by protocols. SMTP
> asks that computers identify themselves (by their IP address) so the IP
> address of server.a will be available to the smtp server.b, which will be
> included in the Received: headers.
>
> Other than that, everything can be set up and kept separately.

Thanks for your answer Eduardo!

So, if I understod this correctly. If server.b doesn't strip these things
from header, then it will be shown that particular E-MAil is sent from
server.a?

Correct?

--
₪ BUD ₪

Re: IMAP E-Mail sending question.

<0de08a8e-e3af-8b33-3865-2f4d63904a50@washington.edu>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=425&group=comp.mail.pine#425

 copy link   Newsgroups: comp.mail.pine
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: cha...@washington.edu (Eduardo Chappa)
Newsgroups: comp.mail.pine
Subject: Re: IMAP E-Mail sending question.
Date: Wed, 3 Aug 2022 13:28:58 -0600
Organization: A noiseless patient Spider
Lines: 15
Message-ID: <0de08a8e-e3af-8b33-3865-2f4d63904a50@washington.edu>
References: <alpine.BSF.2.21.9999.2208032027080.11738@cerebro.liukuma.net> <9c3c9df0-0846-f260-a5bd-a815810325fc@washington.edu> <alpine.BSF.2.21.9999.2208032224460.67262@cerebro.liukuma.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Injection-Info: reader01.eternal-september.org; posting-host="123f5ba1ee5c355ecf5adab349adfdca";
logging-data="2559952"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/P1y1o/cfkPXmu7yDS+v+S"
Cancel-Lock: sha1:lxO/yXIH9KuZSpS51ZSk048mLAY=
In-Reply-To: <alpine.BSF.2.21.9999.2208032224460.67262@cerebro.liukuma.net>
 by: Eduardo Chappa - Wed, 3 Aug 2022 19:28 UTC

On Wed, 3 Aug 2022, Bud Spencer wrote:

> So, if I understod this correctly. If server.b doesn't strip these
> things from header, then it will be shown that particular E-MAil is sent
> from server.a?
>
> Correct?

Yes, and server.b will add a header to show the message came from
server.a.

--
Eduardo
https://alpineapp.email (web)
http://repo.or.cz/alpine.git (Git)

Re: IMAP E-Mail sending question.

<alpine.BSF.2.21.9999.2208032236050.67262@cerebro.liukuma.net>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=426&group=comp.mail.pine#426

 copy link   Newsgroups: comp.mail.pine
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!newsreader4.netcologne.de!news.netcologne.de!peer01.ams1!peer.ams1.xlned.com!news.xlned.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx14.iad.POSTED!not-for-mail
Newsgroups: comp.mail.pine
From: bud...@campo.verano.it (Bud Spencer)
Reply-To: Bud Spencer <bud@campo.verano.it>
Subject: Re: IMAP E-Mail sending question.
In-Reply-To: <0de08a8e-e3af-8b33-3865-2f4d63904a50@washington.edu>
Message-ID: <alpine.BSF.2.21.9999.2208032236050.67262@cerebro.liukuma.net>
References: <alpine.BSF.2.21.9999.2208032027080.11738@cerebro.liukuma.net> <9c3c9df0-0846-f260-a5bd-a815810325fc@washington.edu> <alpine.BSF.2.21.9999.2208032224460.67262@cerebro.liukuma.net> <0de08a8e-e3af-8b33-3865-2f4d63904a50@washington.edu>
User-Agent: Alpine 2.21.9999 (BSF 287 2018-06-16)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="2739015498-396370151-1659555411=:67262"
Lines: 27
X-Complaints-To: abuse@usenetserver.com
NNTP-Posting-Date: Wed, 03 Aug 2022 19:36:53 UTC
Organization: UsenetServer - www.usenetserver.com
Date: Wed, 3 Aug 2022 22:36:49 +0300
X-Received-Bytes: 1832
 by: Bud Spencer - Wed, 3 Aug 2022 19:36 UTC

On Wed, 3 Aug 2022, Eduardo Chappa wrote:

> On Wed, 3 Aug 2022, Bud Spencer wrote:
>
>> So, if I understod this correctly. If server.b doesn't strip these things
>> from header, then it will be shown that particular E-MAil is sent from
>> server.a?
>>
>> Correct?
>
> Yes, and server.b will add a header to show the message came from server.a.

Thanks for clearing this up! Much obliged!

--
₪ BUD ₪

Re: IMAP E-Mail sending question.

<tcfobh$t9k$1@sirius.aeon.icebear.cloud>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=427&group=comp.mail.pine#427

 copy link   Newsgroups: comp.mail.pine
Path: i2pn2.org!i2pn.org!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: h_hucke+...@newsmail.aeon.icebear.org (Henning Hucke)
Newsgroups: comp.mail.pine
Subject: Re: IMAP E-Mail sending question.
Date: Thu, 4 Aug 2022 06:18:25 -0000 (UTC)
Organization: aeon: think longer than you thought before
Lines: 40
Distribution: world
Message-ID: <tcfobh$t9k$1@sirius.aeon.icebear.cloud>
References: <alpine.BSF.2.21.9999.2208032027080.11738@cerebro.liukuma.net>
Reply-To: Henning Hucke <h_hucke+news.reply@newsmail.aeon.icebear.org>
X-Trace: individual.net 7iQCMmyZg9q4rUGOiO8pEQw298Yn6f1FegYlZ5gjErV83f16vU
X-Orig-Path: news.aeon.icebear.cloud!news1.aeon.icebear.cloud!.POSTED.romulus.aeon.icebear.cloud!not-for-mail
Cancel-Lock: sha1:MTYFY0HK3+dcpxej7D2cbk4Qc5I= sha1:6BlK+cX0sSfxPiWT/LTJqjYYmBE=
Injection-Date: Thu, 4 Aug 2022 06:18:25 -0000 (UTC)
Injection-Info: sirius.aeon.icebear.cloud; posting-host="romulus.aeon.icebear.cloud:fd09:afca:b044:1:4ecc:6aff:fecf:5c8f";
logging-data="30004"; mail-complaints-to="abuse+news@aeon.icebear.cloud"
User-Agent: tin/2.4.1-20161224 ("Daill") (UNIX) (Linux/4.9.0-15-amd64 (x86_64))
 by: Henning Hucke - Thu, 4 Aug 2022 06:18 UTC

Bud Spencer <bud@campo.verano.it> wrote:
> Hi there.

Hi Mr. Spencer,

I tought that you died recently (for a suitable definition of
"recently"). Wondering how you can write postings as a dead being.

Read: It seems to me that you are asking how to - some kind of - fake
mails.

> [...]
> There is a server A and Alpine is running on that server and is configured
> to talk with mail.server.a and there is user@server.a account.
>
> Then I'll set up Alpine to use IMAP to get E-Mails from server B,
> user@server.b ... now when I send E-Mails as user@server.b using
> mail.server.b, does Alpine include some indentifying things into header of
> those E-Mails that can point out to server.a?
>
> I'd like to keep these two separated, yet use Alpine on server.a to
> send/receive both ...
>
> Hope my question made some sense :)

It does.

You'll not be able to hide this setup. At least not to people who are
able to read mail headers and know how mail systems function.

Beside of that: You are talking about where you get your mails from but
asking how to hide things if you send mails...
Strange combination!

Regards,
Henning
--
In the first place, God made idiots;
this was for practice; then he made school boards.
-- Mark Twain

Re: IMAP E-Mail sending question.

<alpine.BSF.2.21.9999.2208041259580.56503@cerebro.liukuma.net>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=428&group=comp.mail.pine#428

 copy link   Newsgroups: comp.mail.pine
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx07.iad.POSTED!not-for-mail
Newsgroups: comp.mail.pine
From: bud...@campo.verano.it (Bud Spencer)
Reply-To: Bud Spencer <bud@campo.verano.it>
Subject: Re: IMAP E-Mail sending question.
In-Reply-To: <tcfobh$t9k$1@sirius.aeon.icebear.cloud>
Message-ID: <alpine.BSF.2.21.9999.2208041259580.56503@cerebro.liukuma.net>
References: <alpine.BSF.2.21.9999.2208032027080.11738@cerebro.liukuma.net> <tcfobh$t9k$1@sirius.aeon.icebear.cloud>
User-Agent: Alpine 2.21.9999 (BSF 287 2018-06-16)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="2739015498-1578621276-1659607526=:56503"
Lines: 58
X-Complaints-To: abuse@usenetserver.com
NNTP-Posting-Date: Thu, 04 Aug 2022 10:05:28 UTC
Organization: UsenetServer - www.usenetserver.com
Date: Thu, 4 Aug 2022 13:05:23 +0300
X-Received-Bytes: 2863
 by: Bud Spencer - Thu, 4 Aug 2022 10:05 UTC

On Thu, 4 Aug 2022, Henning Hucke wrote:

> Bud Spencer <bud@campo.verano.it> wrote:
>
> I tought that you died recently (for a suitable definition of
> "recently"). Wondering how you can write postings as a dead being.

It's a kind of magic.

> Read: It seems to me that you are asking how to - some kind of - fake
> mails.

No. Not at all. Both E-Mail addresses are real, nothing to fake here.

>> [...]
>> There is a server A and Alpine is running on that server and is configured
>> to talk with mail.server.a and there is user@server.a account.
>>
>> Then I'll set up Alpine to use IMAP to get E-Mails from server B,
>> user@server.b ... now when I send E-Mails as user@server.b using
>> mail.server.b, does Alpine include some indentifying things into header of
>> those E-Mails that can point out to server.a?
>>
>> I'd like to keep these two separated, yet use Alpine on server.a to
>> send/receive both ...
>>
>> Hope my question made some sense :)
>
> It does.
>
> You'll not be able to hide this setup. At least not to people who are
> able to read mail headers and know how mail systems function.

Except if server.b strips this any mention of server.a from the headers
and send it as it would have sent from the server.b

> Beside of that: You are talking about where you get your mails from but
> asking how to hide things if you send mails...
> Strange combination!

Not really. It would just be more convenient to use both E-Mail addresses
with same client. But undisclosed reasons server.a should not be visible
in E-Mails sent from server.b ... I see nothing strange about this. At
least for me.

--
₪ BUD ₪

Re: IMAP E-Mail sending question.

<tci9oq$qpq$1@sirius.aeon.icebear.cloud>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=429&group=comp.mail.pine#429

 copy link   Newsgroups: comp.mail.pine
Path: i2pn2.org!i2pn.org!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: h_hucke+...@newsmail.aeon.icebear.org (Henning Hucke)
Newsgroups: comp.mail.pine
Subject: Re: IMAP E-Mail sending question.
Date: Fri, 5 Aug 2022 05:27:54 -0000 (UTC)
Organization: aeon: think longer than you thought before
Lines: 51
Distribution: world
Message-ID: <tci9oq$qpq$1@sirius.aeon.icebear.cloud>
References: <alpine.BSF.2.21.9999.2208032027080.11738@cerebro.liukuma.net> <tcfobh$t9k$1@sirius.aeon.icebear.cloud> <alpine.BSF.2.21.9999.2208041259580.56503@cerebro.liukuma.net>
Reply-To: Henning Hucke <h_hucke+news.reply@newsmail.aeon.icebear.org>
X-Trace: individual.net 70hoKKnTeHu8tKvHPouoAgHCXl5gHqOTPTflmhJFfJeU0Uvq6X
X-Orig-Path: news.aeon.icebear.cloud!news1.aeon.icebear.cloud!.POSTED.romulus.aeon.icebear.cloud!not-for-mail
Cancel-Lock: sha1:nZhreqO3I+TfBY11/01ONKqcC0Y= sha1:QL83fOdaGQtyt2TxL4PSMaeOKHQ=
Injection-Date: Fri, 5 Aug 2022 05:27:54 -0000 (UTC)
Injection-Info: sirius.aeon.icebear.cloud; posting-host="romulus.aeon.icebear.cloud:fd09:afca:b044:1:4ecc:6aff:fecf:5c8f";
logging-data="27450"; mail-complaints-to="abuse+news@aeon.icebear.cloud"
User-Agent: tin/2.4.1-20161224 ("Daill") (UNIX) (Linux/4.9.0-15-amd64 (x86_64))
 by: Henning Hucke - Fri, 5 Aug 2022 05:27 UTC

Bud Spencer <bud@campo.verano.it> wrote:
> [-- text/plain, encoding quoted-printable, charset: UTF-8, 50 lines --]

Stange information line.

>
> On Thu, 4 Aug 2022, Henning Hucke wrote:
>[...]
>> You'll not be able to hide this setup. At least not to people who are
>> able to read mail headers and know how mail systems function.
>
> Except if server.b strips this any mention of server.a from the headers
> and send it as it would have sent from the server.b

Of course as ever: If you've got a server under your control you can
manipulate everything which happened before (and at) this server. So
far so true. But you didn't tell that you've control over server.b.

>
>> Beside of that: You are talking about where you get your mails from but
>> asking how to hide things if you send mails...
>> Strange combination!
>
> Not really. It would just be more convenient to use both E-Mail addresses
> with same client. But undisclosed reasons server.a should not be visible
> in E-Mails sent from server.b ... I see nothing strange about this. At
> least for me.

Please enlighten me: why?

For security reasons? This would be so called security by obscurity
which is known to be no security.

It's a little bit like blocking ICMP echo/reply messages. This indeed
closes a hole which can be used to tunnel malicious data through a
firewall but on the other hand you can minimize the risk by also
filtering "oversized" ICMP echo/reply messages and other things.
But if you block ICMP you harm others which not so seldom need this
"tool" to troubleshoot thing. And these others are your partner "in the
internet".

So carefully think about whether or not this really helps you and also
think about how this personal measurement harms other participants of
the internet.

Regards
Henning
--
In theory there is no difference between theory and practise.
In practise there is.
Yogi Beer

Re: IMAP E-Mail sending question.

<alpine.BSF.2.21.9999.2208051340010.4210@cerebro.liukuma.net>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=430&group=comp.mail.pine#430

 copy link   Newsgroups: comp.mail.pine
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx11.iad.POSTED!not-for-mail
Newsgroups: comp.mail.pine
From: bud...@campo.verano.it (Bud Spencer)
Reply-To: Bud Spencer <bud@campo.verano.it>
Subject: Re: IMAP E-Mail sending question.
In-Reply-To: <tci9oq$qpq$1@sirius.aeon.icebear.cloud>
Message-ID: <alpine.BSF.2.21.9999.2208051340010.4210@cerebro.liukuma.net>
References: <alpine.BSF.2.21.9999.2208032027080.11738@cerebro.liukuma.net> <tcfobh$t9k$1@sirius.aeon.icebear.cloud> <alpine.BSF.2.21.9999.2208041259580.56503@cerebro.liukuma.net> <tci9oq$qpq$1@sirius.aeon.icebear.cloud>
User-Agent: Alpine 2.21.9999 (BSF 287 2018-06-16)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="2739015498-731397538-1659696166=:4210"
Lines: 47
X-Complaints-To: abuse@usenetserver.com
NNTP-Posting-Date: Fri, 05 Aug 2022 10:42:48 UTC
Organization: UsenetServer - www.usenetserver.com
Date: Fri, 5 Aug 2022 13:42:45 +0300
X-Received-Bytes: 2547
 by: Bud Spencer - Fri, 5 Aug 2022 10:42 UTC

On Fri, 5 Aug 2022, Henning Hucke wrote:

> Bud Spencer <bud@campo.verano.it> wrote:
>> [-- text/plain, encoding quoted-printable, charset: UTF-8, 50 lines --]
>
> Stange information line.

Innit?

>> On Thu, 4 Aug 2022, Henning Hucke wrote:
>> [...]
>>> You'll not be able to hide this setup. At least not to people who are
>>> able to read mail headers and know how mail systems function.
>>
>> Except if server.b strips this any mention of server.a from the headers
>> and send it as it would have sent from the server.b
>
> Of course as ever: If you've got a server under your control you can
> manipulate everything which happened before (and at) this server. So
> far so true. But you didn't tell that you've control over server.b.

I don't.

>>> Beside of that: You are talking about where you get your mails from but
>>> asking how to hide things if you send mails...
>>> Strange combination!
>>
>> Not really. It would just be more convenient to use both E-Mail addresses
>> with same client. But undisclosed reasons server.a should not be visible
>> in E-Mails sent from server.b ... I see nothing strange about this. At
>> least for me.
>
> Please enlighten me: why?

You are smart man, you figure out possibilities.

--
₪ BUD ₪

Re: IMAP E-Mail sending question.

<tcjf0h$37a70$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=431&group=comp.mail.pine#431

 copy link   Newsgroups: comp.mail.pine
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: ahk...@chinet.com (Adam H. Kerman)
Newsgroups: comp.mail.pine
Subject: Re: IMAP E-Mail sending question.
Date: Fri, 5 Aug 2022 16:03:29 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 38
Message-ID: <tcjf0h$37a70$1@dont-email.me>
References: <alpine.BSF.2.21.9999.2208032027080.11738@cerebro.liukuma.net>
Injection-Date: Fri, 5 Aug 2022 16:03:29 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="1ca8d308b8ec7886e270ceae3387b0de";
logging-data="3385568"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1//ybwv2lh1Egnj8K3cAVcFjr87iikRHsA="
Cancel-Lock: sha1:Aify/TRSQTAOPFDsTYruTfm2lQQ=
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
 by: Adam H. Kerman - Fri, 5 Aug 2022 16:03 UTC

Bud Spencer <bud@campo.verano.it> wrote:

> This message is in MIME format. The first part should be readable text,
> while the remaining parts are likely unreadable without MIME-aware tools.

>--2739015498-468396953-1659547978=:11738
>Content-Type: text/plain; format=flowed; charset=UTF-8
>Content-Transfer-Encoding: QUOTED-PRINTABLE

>Hi there.

>I'm wondering about the following thing:

>There is a server A and Alpine is running on that server and is configured=
>=20
>to talk with mail.server.a and there is user@server.a account.

>Then I'll set up Alpine to use IMAP to get E-Mails from server B,=20
>user@server.b ... now when I send E-Mails as user@server.b using=20
>mail.server.b, does Alpine include some indentifying things into header of=
>=20
>those E-Mails that can point out to server.a?

>I'd like to keep these two separated, yet use Alpine on server.a to=20
>send/receive both ...

>Hope my question made some sense :)

>--=20
>=E2=82=AA BUD =E2=82=AA
>--2739015498-468396953-1659547978=:11738--

Could I please request that you not post articles to plain text Usenet
that are attachments with QUOTED-PRINTABLE encoding? There's no plain
text alternative part and there's no reason to encode.

I don't even know how you set alpine to create the intended main part
to be an attachment with no alternative plain text part.

Re: IMAP E-Mail sending question.

<alpine.BSF.2.21.9999.2208060010110.87688@cerebro.liukuma.net>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=432&group=comp.mail.pine#432

 copy link   Newsgroups: comp.mail.pine
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx09.iad.POSTED!not-for-mail
Newsgroups: comp.mail.pine
From: bud...@campo.verano.it (Bud Spencer)
Reply-To: Bud Spencer <bud@campo.verano.it>
Subject: Re: IMAP E-Mail sending question.
In-Reply-To: <tcjf0h$37a70$1@dont-email.me>
Message-ID: <alpine.BSF.2.21.9999.2208060010110.87688@cerebro.liukuma.net>
References: <alpine.BSF.2.21.9999.2208032027080.11738@cerebro.liukuma.net> <tcjf0h$37a70$1@dont-email.me>
User-Agent: Alpine 2.21.9999 (BSF 287 2018-06-16)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="2739015498-288430170-1659733859=:87688"
Lines: 17
X-Complaints-To: abuse@usenetserver.com
NNTP-Posting-Date: Fri, 05 Aug 2022 21:11:01 UTC
Organization: UsenetServer - www.usenetserver.com
Date: Sat, 6 Aug 2022 00:10:57 +0300
X-Received-Bytes: 1401
 by: Bud Spencer - Fri, 5 Aug 2022 21:10 UTC

On Fri, 5 Aug 2022, Adam H. Kerman wrote:

> I don't even know how you set alpine to create the intended main part
> to be an attachment with no alternative plain text part.

Then there are two of us. I haven't done such settings ...

--
₪ BUD ₪

Re: IMAP E-Mail sending question.

<tcm2ai$3u82d$2@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=433&group=comp.mail.pine#433

 copy link   Newsgroups: comp.mail.pine
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: ahk...@chinet.com (Adam H. Kerman)
Newsgroups: comp.mail.pine
Subject: Re: IMAP E-Mail sending question.
Date: Sat, 6 Aug 2022 15:45:22 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 39
Message-ID: <tcm2ai$3u82d$2@dont-email.me>
References: <alpine.BSF.2.21.9999.2208032027080.11738@cerebro.liukuma.net> <tcjf0h$37a70$1@dont-email.me> <alpine.BSF.2.21.9999.2208060010110.87688@cerebro.liukuma.net>
Injection-Date: Sat, 6 Aug 2022 15:45:22 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="be3153fc1b3ec393fbedf4e2f7a4e7a9";
logging-data="4137037"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+oWY+RQ8gm6UXbcW39+zVTHdCNBFzKQkI="
Cancel-Lock: sha1:ABCXDVI/SqHr9U8jbMIr7bL0ZYs=
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
 by: Adam H. Kerman - Sat, 6 Aug 2022 15:45 UTC

Bud Spencer <bud@campo.verano.it> wrote:

I don't know what your alpine settings are, but this is what you are
producing. There are two parts to your article.

This is part one. It's boilerplate. I've seen other clients add this.
I had no idea alpine would ever add it. This is undesireable behavior.

> This message is in MIME format. The first part should be readable text,
> while the remaining parts are likely unreadable without MIME-aware tools.

Here is the second part.

>--2739015498-288430170-1659733859=:87688
>Content-Type: text/plain; charset=UTF-8; format=flowed
>Content-Transfer-Encoding: QUOTED-PRINTABLE

>On Fri, 5 Aug 2022, Adam H. Kerman wrote:

>>I don't even know how you set alpine to create the intended main part
>>to be an attachment with no alternative plain text part.

>Then there are two of us. I haven't done such settings ...

>--=20
>=E2=82=AA BUD =E2=82=AA
>--2739015498-288430170-1659733859=:87688--

Usenet is 8-bit clean. Never post with QP encoding. alpine has a setting
"Enable 8bit ESMTP Negotiation" which I have set but I don't think it's
set by default. I think that generally prevents alpine creating QP in
email but that shouldn't effect Usenet since SMTP is irrelevant.

As far as how you keep posting with your intended main body part of the
article as an attachment instead, I cannot possibly guess. I've never
had alpine create an email message of mine like that nor would it create
a Usenet article like that. Generally, I don't use alpine as a
newsreader but I have the option to do so as I follow pine naming
convention for my .newsrc so that alpine may use it.

Re: IMAP E-Mail sending question.

<fbe4551f-8c49-0b88-6763-d4c8489aecf3@washington.edu>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=434&group=comp.mail.pine#434

 copy link   Newsgroups: comp.mail.pine
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: cha...@washington.edu (Eduardo Chappa)
Newsgroups: comp.mail.pine
Subject: Re: IMAP E-Mail sending question.
Date: Sat, 6 Aug 2022 10:26:24 -0600
Organization: A noiseless patient Spider
Lines: 15
Message-ID: <fbe4551f-8c49-0b88-6763-d4c8489aecf3@washington.edu>
References: <alpine.BSF.2.21.9999.2208032027080.11738@cerebro.liukuma.net> <tcjf0h$37a70$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Injection-Info: reader01.eternal-september.org; posting-host="d6feb58f902e09e808f027c6143444dd";
logging-data="4166244"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18GRkf3/esHktaQGSwuH+Tg"
Cancel-Lock: sha1:5fnlA8f7yfSCSkWo2CYRHzsPeZI=
In-Reply-To: <tcjf0h$37a70$1@dont-email.me>
 by: Eduardo Chappa - Sat, 6 Aug 2022 16:26 UTC

On Fri, 5 Aug 2022, Adam H. Kerman wrote:

> Could I please request that you not post articles to plain text Usenet
> that are attachments with QUOTED-PRINTABLE encoding? There's no plain
> text alternative part and there's no reason to encode.

Adam, please take a look at RFC 5536, which effectively allows for
quoted-printable in news articles. I understand you will never like it,
but it is perfectly legal, and there is no reason to create noise about
it.

--
Eduardo
https://alpineapp.email (web)
http://repo.or.cz/alpine.git (Git)

Re: IMAP E-Mail sending question.

<alpine.BSF.2.21.9999.2208070011470.95900@cerebro.liukuma.net>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=435&group=comp.mail.pine#435

 copy link   Newsgroups: comp.mail.pine
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx15.iad.POSTED!not-for-mail
Newsgroups: comp.mail.pine
From: bud...@campo.verano.it (Bud Spencer)
Reply-To: Bud Spencer <bud@campo.verano.it>
Subject: Re: IMAP E-Mail sending question.
In-Reply-To: <tcm2ai$3u82d$2@dont-email.me>
Message-ID: <alpine.BSF.2.21.9999.2208070011470.95900@cerebro.liukuma.net>
References: <alpine.BSF.2.21.9999.2208032027080.11738@cerebro.liukuma.net> <tcjf0h$37a70$1@dont-email.me> <alpine.BSF.2.21.9999.2208060010110.87688@cerebro.liukuma.net> <tcm2ai$3u82d$2@dont-email.me>
User-Agent: Alpine 2.21.9999 (BSF 287 2018-06-16)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="2739015498-159663268-1659820520=:95900"
Lines: 64
X-Complaints-To: abuse@usenetserver.com
NNTP-Posting-Date: Sat, 06 Aug 2022 21:15:22 UTC
Organization: UsenetServer - www.usenetserver.com
Date: Sun, 7 Aug 2022 00:15:11 +0300
X-Received-Bytes: 3351
 by: Bud Spencer - Sat, 6 Aug 2022 21:15 UTC

On Sat, 6 Aug 2022, Adam H. Kerman wrote:

> Bud Spencer <bud@campo.verano.it> wrote:
>
> I don't know what your alpine settings are, but this is what you are
> producing. There are two parts to your article.
>
> This is part one. It's boilerplate. I've seen other clients add this.
> I had no idea alpine would ever add it. This is undesireable behavior.
>
>> This message is in MIME format. The first part should be readable text,
>> while the remaining parts are likely unreadable without MIME-aware tools.
>
> Here is the second part.
>
>> --2739015498-288430170-1659733859=:87688
>> Content-Type: text/plain; charset=UTF-8; format=flowed
>> Content-Transfer-Encoding: QUOTED-PRINTABLE
>
>> On Fri, 5 Aug 2022, Adam H. Kerman wrote:
>
>>> I don't even know how you set alpine to create the intended main part
>>> to be an attachment with no alternative plain text part.
>
>> Then there are two of us. I haven't done such settings ...
>
>> --=20
>> =E2=82=AA BUD =E2=82=AA
>> --2739015498-288430170-1659733859=:87688--
>
> Usenet is 8-bit clean. Never post with QP encoding. alpine has a setting
> "Enable 8bit ESMTP Negotiation" which I have set but I don't think it's
> set by default. I think that generally prevents alpine creating QP in
> email but that shouldn't effect Usenet since SMTP is irrelevant.
>
> As far as how you keep posting with your intended main body part of the
> article as an attachment instead, I cannot possibly guess. I've never
> had alpine create an email message of mine like that nor would it create
> a Usenet article like that. Generally, I don't use alpine as a
> newsreader but I have the option to do so as I follow pine naming
> convention for my .newsrc so that alpine may use it.

Breath.

I never knew this kind of thing is going on, no need to foam all over.

Also what you are doing has nothing to do with anything. You do you.

Anyway thank you to bring this up, now I know the issue and can correct it
.. only I didn't find anything like that in the configs.

--
₪ BUD ₪

Re: IMAP E-Mail sending question.

<alpine.BSF.2.21.9999.2208070015471.95900@cerebro.liukuma.net>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=436&group=comp.mail.pine#436

 copy link   Newsgroups: comp.mail.pine
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx02.iad.POSTED!not-for-mail
Newsgroups: comp.mail.pine
From: bud...@campo.verano.it (Bud Spencer)
Reply-To: Bud Spencer <bud@campo.verano.it>
Subject: Re: IMAP E-Mail sending question.
In-Reply-To: <fbe4551f-8c49-0b88-6763-d4c8489aecf3@washington.edu>
Message-ID: <alpine.BSF.2.21.9999.2208070015471.95900@cerebro.liukuma.net>
References: <alpine.BSF.2.21.9999.2208032027080.11738@cerebro.liukuma.net> <tcjf0h$37a70$1@dont-email.me> <fbe4551f-8c49-0b88-6763-d4c8489aecf3@washington.edu>
User-Agent: Alpine 2.21.9999 (BSF 287 2018-06-16)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="2739015498-1157977665-1659820659=:95900"
Lines: 30
X-Complaints-To: abuse@usenetserver.com
NNTP-Posting-Date: Sat, 06 Aug 2022 21:17:41 UTC
Organization: UsenetServer - www.usenetserver.com
Date: Sun, 7 Aug 2022 00:17:37 +0300
X-Received-Bytes: 1980
 by: Bud Spencer - Sat, 6 Aug 2022 21:17 UTC

On Sat, 6 Aug 2022, Eduardo Chappa wrote:

> On Fri, 5 Aug 2022, Adam H. Kerman wrote:
>
>> Could I please request that you not post articles to plain text Usenet that
>> are attachments with QUOTED-PRINTABLE encoding? There's no plain text
>> alternative part and there's no reason to encode.
>
> Adam, please take a look at RFC 5536, which effectively allows for
> quoted-printable in news articles. I understand you will never like it, but
> it is perfectly legal, and there is no reason to create noise about it.

Oh. So I didn't accidentally do anything wrong then.

Anyway, could you please point out where I can set this off anyway? Since
I haven't set such thing ... at least not knowingly.

--
₪ BUD ₪

Re: IMAP E-Mail sending question.

<298156o1-s4o4-9654-5o0-337s83n5p5sn@puvarg.pbz>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=437&group=comp.mail.pine#437

 copy link   Newsgroups: comp.mail.pine
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: ahk...@chinet.com (Adam H. Kerman)
Newsgroups: comp.mail.pine
Subject: Re: IMAP E-Mail sending question.
Date: Sat, 6 Aug 2022 20:01:21 -0500
Organization: A noiseless patient Spider
Lines: 18
Message-ID: <298156o1-s4o4-9654-5o0-337s83n5p5sn@puvarg.pbz>
References: <alpine.BSF.2.21.9999.2208032027080.11738@cerebro.liukuma.net> <tcjf0h$37a70$1@dont-email.me> <fbe4551f-8c49-0b88-6763-d4c8489aecf3@washington.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-7
Content-Transfer-Encoding: 8BIT
Injection-Info: reader01.eternal-september.org; posting-host="b6c7598e228a520d7e9c52d62b0f7a25";
logging-data="220272"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19aSJrkX26DNkCnVhl+pTegiWKx+DoDFJY="
Cancel-Lock: sha1:+b0qLxaTSPge8m8MJWo5DwTaqyo=
In-Reply-To: <fbe4551f-8c49-0b88-6763-d4c8489aecf3@washington.edu>
 by: Adam H. Kerman - Sun, 7 Aug 2022 01:01 UTC

At 11:26am -0000, 08/06/22, Eduardo Chappa <chappa@washington.edu> wrote:
>On Fri, 5 Aug 2022, Adam H. Kerman wrote:

>>Could I please request that you not post articles to plain text Usenet that
>>are attachments with QUOTED-PRINTABLE encoding? There's no plain text
>>alternative part and there's no reason to encode.

>Adam, please take a look at RFC 5536, which effectively allows for
>quoted-printable in news articles. I understand you will never like it, but
>it is perfectly legal, and there is no reason to create noise about it.

I'm posting a followup with alpine. Here's a non-ASCII character.

Let's see if I get quoted-printable encoding and if the main body of the
article ends up in a second attachment, with the boilerplate nag about
MIME-aware tools in the first part.

Re: IMAP E-Mail sending question.

<r7102prr-p855-6s1r-763-q29qo8q84qro@puvarg.pbz>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=438&group=comp.mail.pine#438

 copy link   Newsgroups: comp.mail.pine
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: ahk...@chinet.com (Adam H. Kerman)
Newsgroups: comp.mail.pine
Subject: Re: IMAP E-Mail sending question.
Date: Sat, 6 Aug 2022 20:14:37 -0500
Organization: A noiseless patient Spider
Lines: 33
Message-ID: <r7102prr-p855-6s1r-763-q29qo8q84qro@puvarg.pbz>
References: <alpine.BSF.2.21.9999.2208032027080.11738@cerebro.liukuma.net> <tcjf0h$37a70$1@dont-email.me> <fbe4551f-8c49-0b88-6763-d4c8489aecf3@washington.edu> <298156o1-s4o4-9654-5o0-337s83n5p5sn@puvarg.pbz>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Injection-Info: reader01.eternal-september.org; posting-host="b6c7598e228a520d7e9c52d62b0f7a25";
logging-data="226457"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/PMZP7pjlTmbeEwxOl09uwRG4PCPUTAc4="
Cancel-Lock: sha1:N+P1MKIo2vBWzOVBh2Xl9sMuhrE=
In-Reply-To: <298156o1-s4o4-9654-5o0-337s83n5p5sn@puvarg.pbz>
 by: Adam H. Kerman - Sun, 7 Aug 2022 01:14 UTC

At 8:01pm -0000, 08/06/22, Adam H. Kerman <ahk@chinet.com> wrote:

>MIME-Version: 1.0
>Content-Type: text/plain; charset=ISO-8859-7
>Content-Transfer-Encoding: 8BIT

>At 11:26am -0000, 08/06/22, Eduardo Chappa <chappa@washington.edu> wrote:
>>On Fri, 5 Aug 2022, Adam H. Kerman wrote:

>>>Could I please request that you not post articles to plain text Usenet that
>>>are attachments with QUOTED-PRINTABLE encoding? There's no plain text
>>>alternative part and there's no reason to encode.

>>Adam, please take a look at RFC 5536, which effectively allows for
>>quoted-printable in news articles. I understand you will never like it, but
>>it is perfectly legal, and there is no reason to create noise about it.

>I'm posting a followup with alpine. Here's a non-ASCII character.

>?

In UTF-8, that was supposed to be an apostrophe.

>Let's see if I get quoted-printable encoding and if the main body of the
>article ends up in a second attachment, with the boilerplate nag about
>MIME-aware tools in the first part.

Huh

I was not expecting the MIME header to declare ISO-8859-7 since my shell's
environment has character set to UTF-8, and my terminal emulation matches.

In any event, I didn't get a multipart.

Re: IMAP E-Mail sending question.

<tcn3rv$6ti0$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=439&group=comp.mail.pine#439

 copy link   Newsgroups: comp.mail.pine
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: ahk...@chinet.com (Adam H. Kerman)
Newsgroups: comp.mail.pine
Subject: Re: IMAP E-Mail sending question.
Date: Sun, 7 Aug 2022 01:17:51 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 15
Message-ID: <tcn3rv$6ti0$1@dont-email.me>
References: <alpine.BSF.2.21.9999.2208032027080.11738@cerebro.liukuma.net> <tcjf0h$37a70$1@dont-email.me> <fbe4551f-8c49-0b88-6763-d4c8489aecf3@washington.edu>
Injection-Date: Sun, 7 Aug 2022 01:17:51 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="b6c7598e228a520d7e9c52d62b0f7a25";
logging-data="226880"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+WmxK8VTj1uOsGMlfMwW9DhXyyaiE5//I="
Cancel-Lock: sha1:Q/ckxH0xw78Zwe828qcIkHfSZ4g=
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
 by: Adam H. Kerman - Sun, 7 Aug 2022 01:17 UTC

Eduardo Chappa <chappa@washington.edu> wrote:
>On Fri, 5 Aug 2022, Adam H. Kerman wrote:

>>Could I please request that you not post articles to plain text Usenet
>>that are attachments with QUOTED-PRINTABLE encoding? There's no plain
>>text alternative part and there's no reason to encode.

>Adam, please take a look at RFC 5536, which effectively allows for
>quoted-printable in news articles. I understand you will never like it,
>but it is perfectly legal, and there is no reason to create noise about
>it.

I don't agree that attachments are part of plain-text Usenet either.
I've just never seen alpine do that before and I have no idea how
to recreate it.

Re: IMAP E-Mail sending question.

<alpine.BSF.2.21.9999.2208071930170.53077@cerebro.liukuma.net>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=440&group=comp.mail.pine#440

 copy link   Newsgroups: comp.mail.pine
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx15.iad.POSTED!not-for-mail
Newsgroups: comp.mail.pine
From: bud...@campo.verano.it (Bud Spencer)
Reply-To: Bud Spencer <bud@campo.verano.it>
Subject: Re: IMAP E-Mail sending question.
In-Reply-To: <tcn3rv$6ti0$1@dont-email.me>
Message-ID: <alpine.BSF.2.21.9999.2208071930170.53077@cerebro.liukuma.net>
References: <alpine.BSF.2.21.9999.2208032027080.11738@cerebro.liukuma.net> <tcjf0h$37a70$1@dont-email.me> <fbe4551f-8c49-0b88-6763-d4c8489aecf3@washington.edu> <tcn3rv$6ti0$1@dont-email.me>
User-Agent: Alpine 2.21.9999 (BSF 287 2018-06-16)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="2739015498-1355159910-1659889921=:53077"
Lines: 35
X-Complaints-To: abuse@usenetserver.com
NNTP-Posting-Date: Sun, 07 Aug 2022 16:32:03 UTC
Organization: UsenetServer - www.usenetserver.com
Date: Sun, 7 Aug 2022 19:31:59 +0300
X-Received-Bytes: 2219
 by: Bud Spencer - Sun, 7 Aug 2022 16:31 UTC

On Sun, 7 Aug 2022, Adam H. Kerman wrote:

> Eduardo Chappa <chappa@washington.edu> wrote:
>> On Fri, 5 Aug 2022, Adam H. Kerman wrote:
>
>>> Could I please request that you not post articles to plain text Usenet
>>> that are attachments with QUOTED-PRINTABLE encoding? There's no plain
>>> text alternative part and there's no reason to encode.
>
>> Adam, please take a look at RFC 5536, which effectively allows for
>> quoted-printable in news articles. I understand you will never like it,
>> but it is perfectly legal, and there is no reason to create noise about
>> it.
>
> I don't agree that attachments are part of plain-text Usenet either.
> I've just never seen alpine do that before and I have no idea how
> to recreate it.

If you figure that out let me know how I turn that thing off ... so far I
have no idea what is going on.

Like I said. I haven't done any setting of that sort. So I'm completely
clueless why this happens.

--
₪ BUD ₪

Re: IMAP E-Mail sending question.

<alpine.BSF.2.21.9999.2208080744540.9738@cerebro.liukuma.net>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=442&group=comp.mail.pine#442

 copy link   Newsgroups: comp.mail.pine
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx18.iad.POSTED!not-for-mail
Newsgroups: comp.mail.pine
From: bud...@campo.verano.it (Bud Spencer)
Reply-To: Bud Spencer <bud@campo.verano.it>
Subject: Re: IMAP E-Mail sending question.
In-Reply-To: <alpine.BSF.2.21.9999.2208071930170.53077@cerebro.liukuma.net>
Message-ID: <alpine.BSF.2.21.9999.2208080744540.9738@cerebro.liukuma.net>
References: <alpine.BSF.2.21.9999.2208032027080.11738@cerebro.liukuma.net> <tcjf0h$37a70$1@dont-email.me> <fbe4551f-8c49-0b88-6763-d4c8489aecf3@washington.edu> <tcn3rv$6ti0$1@dont-email.me> <alpine.BSF.2.21.9999.2208071930170.53077@cerebro.liukuma.net>
User-Agent: Alpine 2.21.9999 (BSF 287 2018-06-16)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="2739015498-1164100211-1659933957=:9738"
Lines: 41
X-Complaints-To: abuse@usenetserver.com
NNTP-Posting-Date: Mon, 08 Aug 2022 04:45:59 UTC
Organization: UsenetServer - www.usenetserver.com
Date: Mon, 8 Aug 2022 07:45:55 +0300
X-Received-Bytes: 2527
 by: Bud Spencer - Mon, 8 Aug 2022 04:45 UTC

On Sun, 7 Aug 2022, Bud Spencer wrote:

> On Sun, 7 Aug 2022, Adam H. Kerman wrote:
>
>> Eduardo Chappa <chappa@washington.edu> wrote:
>>> On Fri, 5 Aug 2022, Adam H. Kerman wrote:
>>
>>>> Could I please request that you not post articles to plain text Usenet
>>>> that are attachments with QUOTED-PRINTABLE encoding? There's no plain
>>>> text alternative part and there's no reason to encode.
>>
>>> Adam, please take a look at RFC 5536, which effectively allows for
>>> quoted-printable in news articles. I understand you will never like it,
>>> but it is perfectly legal, and there is no reason to create noise about
>>> it.
>>
>> I don't agree that attachments are part of plain-text Usenet either.
>> I've just never seen alpine do that before and I have no idea how
>> to recreate it.
>
> If you figure that out let me know how I turn that thing off ... so far I
> have no idea what is going on.
>
> Like I said. I haven't done any setting of that sort. So I'm completely
> clueless why this happens.

Could you help Eduardo? I still have no idea how to set Alpine not to do
such thing. Or I'm just missing something big time :)

--
₪ BUD ₪

Re: IMAP E-Mail sending question.

<25a43316-e391-cb2b-93c5-a11da48954b0@washington.edu>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=444&group=comp.mail.pine#444

 copy link   Newsgroups: comp.mail.pine
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: cha...@washington.edu (Eduardo Chappa)
Newsgroups: comp.mail.pine
Subject: Re: IMAP E-Mail sending question.
Date: Mon, 8 Aug 2022 11:17:54 -0600
Organization: A noiseless patient Spider
Lines: 15
Message-ID: <25a43316-e391-cb2b-93c5-a11da48954b0@washington.edu>
References: <alpine.BSF.2.21.9999.2208032027080.11738@cerebro.liukuma.net> <tcjf0h$37a70$1@dont-email.me> <fbe4551f-8c49-0b88-6763-d4c8489aecf3@washington.edu> <tcn3rv$6ti0$1@dont-email.me> <alpine.BSF.2.21.9999.2208071930170.53077@cerebro.liukuma.net>
<alpine.BSF.2.21.9999.2208080744540.9738@cerebro.liukuma.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Injection-Info: reader01.eternal-september.org; posting-host="d0f4edd57887e78334eadc97e82625cf";
logging-data="1051776"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19Mn0DJgSo9+0Sr2ylA6rxN"
Cancel-Lock: sha1:BQ/oLosz8RTCfAOxF3stWxU5s7A=
In-Reply-To: <alpine.BSF.2.21.9999.2208080744540.9738@cerebro.liukuma.net>
 by: Eduardo Chappa - Mon, 8 Aug 2022 17:17 UTC

On Mon, 8 Aug 2022, Bud Spencer wrote:

> Could you help Eduardo? I still have no idea how to set Alpine not to do
> such thing. Or I'm just missing something big time :)

Bud, there is nothing to do here. You cannot configure Alpine so that it
will not do something that Adam will not like.

The point is: There are 8-bits in your message, Alpine will encode them
somehow (meaning they will not be sent as 8-bit). That is the standard.

--
Eduardo
https://alpineapp.email (web)
http://repo.or.cz/alpine.git (Git)

Re: IMAP E-Mail sending question.

<alpine.BSF.2.21.9999.2208082154480.22649@cerebro.liukuma.net>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=445&group=comp.mail.pine#445

 copy link   Newsgroups: comp.mail.pine
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx14.iad.POSTED!not-for-mail
Newsgroups: comp.mail.pine
From: bud...@campo.verano.it (Bud Spencer)
Reply-To: Bud Spencer <bud@campo.verano.it>
Subject: Re: IMAP E-Mail sending question.
In-Reply-To: <25a43316-e391-cb2b-93c5-a11da48954b0@washington.edu>
Message-ID: <alpine.BSF.2.21.9999.2208082154480.22649@cerebro.liukuma.net>
References: <alpine.BSF.2.21.9999.2208032027080.11738@cerebro.liukuma.net> <tcjf0h$37a70$1@dont-email.me> <fbe4551f-8c49-0b88-6763-d4c8489aecf3@washington.edu> <tcn3rv$6ti0$1@dont-email.me> <alpine.BSF.2.21.9999.2208071930170.53077@cerebro.liukuma.net>
<alpine.BSF.2.21.9999.2208080744540.9738@cerebro.liukuma.net> <25a43316-e391-cb2b-93c5-a11da48954b0@washington.edu>
User-Agent: Alpine 2.21.9999 (BSF 287 2018-06-16)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="2739015498-1322974694-1659985100=:22649"
Lines: 33
X-Complaints-To: abuse@usenetserver.com
NNTP-Posting-Date: Mon, 08 Aug 2022 18:58:22 UTC
Organization: UsenetServer - www.usenetserver.com
Date: Mon, 8 Aug 2022 21:58:18 +0300
X-Received-Bytes: 2233
 by: Bud Spencer - Mon, 8 Aug 2022 18:58 UTC

On Mon, 8 Aug 2022, Eduardo Chappa wrote:

> On Mon, 8 Aug 2022, Bud Spencer wrote:
>
>> Could you help Eduardo? I still have no idea how to set Alpine not to do
>> such thing. Or I'm just missing something big time :)
>
> Bud, there is nothing to do here. You cannot configure Alpine so that it will
> not do something that Adam will not like.

I wasn't thinking of this because of him. Just out of interest and if,
which is doubtful, I did have made something in mistake.

> The point is: There are 8-bits in your message, Alpine will encode them
> somehow (meaning they will not be sent as 8-bit). That is the standard.

So nothing is broken then. I'm fine with that.

Thanks for taking time to elaborate this more to my autistic mind :)

--
₪ BUD ₪

Re: IMAP E-Mail sending question.

<tcrp7k$10svi$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=446&group=comp.mail.pine#446

 copy link   Newsgroups: comp.mail.pine
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: ahk...@chinet.com (Adam H. Kerman)
Newsgroups: comp.mail.pine
Subject: Re: IMAP E-Mail sending question.
Date: Mon, 8 Aug 2022 19:47:00 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 33
Message-ID: <tcrp7k$10svi$1@dont-email.me>
References: <alpine.BSF.2.21.9999.2208032027080.11738@cerebro.liukuma.net> <alpine.BSF.2.21.9999.2208071930170.53077@cerebro.liukuma.net> <alpine.BSF.2.21.9999.2208080744540.9738@cerebro.liukuma.net> <25a43316-e391-cb2b-93c5-a11da48954b0@washington.edu>
Injection-Date: Mon, 8 Aug 2022 19:47:00 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="600aed0d72ea0311613a835c25960613";
logging-data="1078258"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/6c+IOArN/PpJltetyMPOWFLk5+9rRLrI="
Cancel-Lock: sha1:GHBLPlyTPMMUE9mV31m7VFCYzRM=
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
 by: Adam H. Kerman - Mon, 8 Aug 2022 19:47 UTC

Eduardo Chappa <chappa@washington.edu> wrote:
>On Mon, 8 Aug 2022, Bud Spencer wrote:

>>Could you help Eduardo? I still have no idea how to set Alpine not to do
>>such thing. Or I'm just missing something big time :)

>Bud, there is nothing to do here. You cannot configure Alpine so that it
>will not do something that Adam will not like.

>The point is: There are 8-bits in your message, Alpine will encode them
>somehow (meaning they will not be sent as 8-bit). That is the standard.

You're being unfair, Eduardo. I raised the issue because of the fact that
alpine created an article as a two-part multipart with one of the two
parts blank (except for the nag boilerplate about using MIME-aware
tools) with his intended main body of the article in the second
attachment.

Multiparts aren't plain text Usenet. That's undesireable.

The quoted-printable encoding was a separate matter. Yes, there is a
quoted-printable encoding standard that alpine implements. Nevertheless,
unencoded text should be prefered over encoded text in an almost entirely
8-bit clean environment like Usenet.

The issue of attachments is of greater concern than the issue of
quoted-printable.

I wasn't able to figure out what settings he used to get that result.

I understand that you disagree with everything I've written.
Nevertheless, I'm not alone in caring that text Usenet remains a plain
text medium of communication.

Re: IMAP E-Mail sending question.

<tcrpeu$10svi$2@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=447&group=comp.mail.pine#447

 copy link   Newsgroups: comp.mail.pine
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: ahk...@chinet.com (Adam H. Kerman)
Newsgroups: comp.mail.pine
Subject: Re: IMAP E-Mail sending question.
Date: Mon, 8 Aug 2022 19:50:54 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 33
Message-ID: <tcrpeu$10svi$2@dont-email.me>
References: <alpine.BSF.2.21.9999.2208032027080.11738@cerebro.liukuma.net> <alpine.BSF.2.21.9999.2208080744540.9738@cerebro.liukuma.net> <25a43316-e391-cb2b-93c5-a11da48954b0@washington.edu> <alpine.BSF.2.21.9999.2208082154480.22649@cerebro.liukuma.net>
Injection-Date: Mon, 8 Aug 2022 19:50:54 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="600aed0d72ea0311613a835c25960613";
logging-data="1078258"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+mpg7hCcWM+nYLOk9ymN71jAdbssBqMt8="
Cancel-Lock: sha1:/HViub5AwP1ws6MQPVT2tI01AKQ=
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
 by: Adam H. Kerman - Mon, 8 Aug 2022 19:50 UTC

Bud Spencer <bud@campo.verano.it> wrote:

> This message is in MIME format. The first part should be readable text,
> while the remaining parts are likely unreadable without MIME-aware tools.

>--2739015498-1322974694-1659985100=:22649
>Content-Type: text/plain; charset=UTF-8; format=flowed
>Content-Transfer-Encoding: QUOTED-PRINTABLE

>On Mon, 8 Aug 2022, Eduardo Chappa wrote:
>>On Mon, 8 Aug 2022, Bud Spencer wrote:

>>>Could you help Eduardo? I still have no idea how to set Alpine not to do=
>=20
>>>such thing. Or I'm just missing something big time :)

>>Bud, there is nothing to do here. You cannot configure Alpine so that it =
>will=20
>>not do something that Adam will not like.

>I wasn't thinking of this because of him. Just out of interest and if,=20
>which is doubtful, I did have made something in mistake.

>>The point is: There are 8-bits in your message, Alpine will encode them=
>=20
>>somehow (meaning they will not be sent as 8-bit). That is the standard.

>So nothing is broken then. I'm fine with that.

Broken behavior is non-standards compliance. That's not the issue here.
Eduardo makes sure alpine remains standards compliant.

>Thanks for taking time to elaborate this more to my autistic mind :)

Re: IMAP E-Mail sending question.

<tcsptc$t7j$1@sirius.aeon.icebear.cloud>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=448&group=comp.mail.pine#448

 copy link   Newsgroups: comp.mail.pine
Path: i2pn2.org!i2pn.org!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: h_hucke+...@newsmail.aeon.icebear.org (Henning Hucke)
Newsgroups: comp.mail.pine
Subject: Re: IMAP E-Mail sending question.
Date: Tue, 9 Aug 2022 05:04:44 -0000 (UTC)
Organization: aeon: think longer than you thought before
Lines: 36
Distribution: world
Message-ID: <tcsptc$t7j$1@sirius.aeon.icebear.cloud>
References: <alpine.BSF.2.21.9999.2208032027080.11738@cerebro.liukuma.net> <alpine.BSF.2.21.9999.2208071930170.53077@cerebro.liukuma.net> <alpine.BSF.2.21.9999.2208080744540.9738@cerebro.liukuma.net> <25a43316-e391-cb2b-93c5-a11da48954b0@washington.edu> <tcrp7k$10svi$1@dont-email.me>
Reply-To: Henning Hucke <h_hucke+news.reply@newsmail.aeon.icebear.org>
X-Trace: individual.net H8+IWpuybdI+EtpzOg17EwOoqL+ruPn8fFrA/VbZmuEHejni/7
X-Orig-Path: news.aeon.icebear.cloud!news1.aeon.icebear.cloud!.POSTED.romulus.aeon.icebear.cloud!not-for-mail
Cancel-Lock: sha1:3s8Ln0L/9qJsCwSJFkUvsuan/lc= sha1:KT/o0O9pSAdf2vOMYp4ZebWRocE=
Injection-Date: Tue, 9 Aug 2022 05:04:44 -0000 (UTC)
Injection-Info: sirius.aeon.icebear.cloud; posting-host="romulus.aeon.icebear.cloud:fd09:afca:b044:1:4ecc:6aff:fecf:5c8f";
logging-data="29939"; mail-complaints-to="abuse+news@aeon.icebear.cloud"
User-Agent: tin/2.4.1-20161224 ("Daill") (UNIX) (Linux/4.9.0-15-amd64 (x86_64))
 by: Henning Hucke - Tue, 9 Aug 2022 05:04 UTC

Adam H. Kerman <ahk@chinet.com> wrote:

Hi Adam,

> Eduardo Chappa <chappa@washington.edu> wrote:
> [...]
>>The point is: There are 8-bits in your message, Alpine will encode them
>>somehow (meaning they will not be sent as 8-bit). That is the standard.
> [...]
> The quoted-printable encoding was a separate matter. Yes, there is a
> quoted-printable encoding standard that alpine implements. Nevertheless,
> unencoded text should be prefered over encoded text in an almost entirely
> 8-bit clean environment like Usenet.

I beg your pardon! In newsgroups text should get uuencoded in preference
to for instance quoted printable encoding?

Especially in newsgroups exactly this should be the case at all. They
should stay as close to us ascii text as possible so that they are as
readable as possible even if the raw article is presented to you.

And I think this is what you'll read if you read all RFCs relevant for
newsgroup articles.

> The issue of attachments is of greater concern than the issue of
> quoted-printable.

Here I'm totally with you.

> [...]

Best regards,
Henning
--
Zero Mostel: That's it baby! When you got it, flaunt it! Flaunt it!
-- Mel Brooks, "The Producers"

Pages:12
server_pubkey.txt

rocksolid light 0.9.7
clearnet tor