From: ron minnich <rminnich@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Re: sending mail ... so close ...
Date: Fri, 20 Dec 2024 15:24:41 -0800 [thread overview]
Message-ID: <CAP6exYJZB7RvfyXDSONn2V8MsO2q_2GgjFq2epU0=OaYgHTq7A@mail.gmail.com> (raw)
In-Reply-To: <A7FB7E56-5542-4DCA-9312-DE07E5FAE758@stanleylieber.com>
[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]
Thanks, that did it. I had messed up the format of upasname.
On Fri, Dec 20, 2024 at 2:24 PM Stanley Lieber <sl@stanleylieber.com> wrote:
>
>
> On Dec 20, 2024, at 4:51 PM, ron minnich <rminnich@gmail.com> wrote:
>
>
> oops, I think I meant remotemail did that. I've modified it per the
> FQA but somehow 'from glenda' is in there.
>
> On Fri, Dec 20, 2024 at 1:47 PM ron minnich <rminnich@gmail.com> wrote:
>
>> and sys/log/mail shows it is "From glenda" -- any way to make that
>> something else?
>>
>> I thought rewrite did that, but I guess not?
>>
>> On Fri, Dec 20, 2024 at 1:45 PM ron minnich <rminnich@gmail.com> wrote:
>>
>>> I'm pretty close to being able to use icloud as my mail server. It's
>>> preferred for me b/c I hate running these things ...
>>>
>>> anyway, acme Mail works great, and smtp, following the FQA, *almost*
>>> works, with one last little error:
>>> From address is not one of your addresses
>>>
>>> Now, my hostuser on this t420 is glenda, for old times sake.
>>>
>>> But my rewrite rules should be rewriting it all to rminnich@me.com, or
>>> so I think.
>>>
>>> But the reply comes to glenda ...
>>>
>>> what simple thing might I be missing?
>>>
>>
> upasname=rminnich@me.com echo test | mail -s test remote@host.tld
>
> sl
>
>
[-- Attachment #2: Type: text/html, Size: 2831 bytes --]
prev parent reply other threads:[~2024-12-20 23:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 21:45 [9front] " ron minnich
2024-12-20 21:47 ` [9front] " ron minnich
2024-12-20 21:48 ` ron minnich
2024-12-20 22:22 ` Stanley Lieber
2024-12-20 23:24 ` ron minnich [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAP6exYJZB7RvfyXDSONn2V8MsO2q_2GgjFq2epU0=OaYgHTq7A@mail.gmail.com' \
--to=rminnich@gmail.com \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).