Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #247493 > unrolled thread

email lacks sender address

Started byHaines Brown <haines@histomat.net>
First post2022-04-24 22:10 +0200
Last post2022-05-09 04:40 +0200
Articles 14 on this page of 74 — 13 participants

Back to article view | Back to linux.debian.user

Contents

  email lacks sender address Haines Brown <haines@histomat.net> - 2022-04-24 22:10 +0200
    Re: email lacks sender address Jonathan Dowland <jon+debian-user@dow.land> - 2022-04-24 23:40 +0200
    Re: email lacks sender address David Wright <deblis@lionunicorn.co.uk> - 2022-04-25 00:40 +0200
      Re: email lacks sender address Haines Brown <haines@histomat.net> - 2022-04-25 05:40 +0200
        Re: email lacks sender address David Wright <deblis@lionunicorn.co.uk> - 2022-04-25 06:40 +0200
          Re: email lacks sender address Haines Brown <haines@histomat.net> - 2022-04-25 17:50 +0200
            Re: email lacks sender address David Wright <deblis@lionunicorn.co.uk> - 2022-04-25 18:50 +0200
            Re: email lacks sender address Brian <ad44@cityscape.co.uk> - 2022-04-25 19:00 +0200
              Re: email lacks sender address Haines Brown <haines@histomat.net> - 2022-04-25 21:10 +0200
            Re: email lacks sender address Jonathan Dowland <jon+debian-user@dow.land> - 2022-04-26 11:20 +0200
              Re: email lacks sender address Haines Brown <haines@histomat.net> - 2022-04-26 15:30 +0200
                Re: email lacks sender address Vincent Lefevre <vincent@vinc17.net> - 2022-04-26 17:10 +0200
                Re: email lacks sender address David Wright <deblis@lionunicorn.co.uk> - 2022-04-26 22:30 +0200
                  Re: email lacks sender address Curt <curty@free.fr> - 2022-04-27 11:30 +0200
                    Re: email lacks sender address Vincent Lefevre <vincent@vinc17.net> - 2022-04-27 11:50 +0200
                  Re: email lacks sender address Haines Brown <haines@histomat.net> - 2022-04-27 14:10 +0200
                    Re: email lacks sender address Greg Wooledge <greg@wooledge.org> - 2022-04-27 14:30 +0200
                      Re: email lacks sender address Haines Brown <haines@histomat.net> - 2022-04-27 16:40 +0200
                        Re: email lacks sender address Jonathan Dowland <jon+debian-user@dow.land> - 2022-04-27 18:20 +0200
                          Re: email lacks sender address Haines Brown <haines@histomat.net> - 2022-04-27 23:00 +0200
                    Re: email lacks sender address Brian <ad44@cityscape.co.uk> - 2022-04-27 14:50 +0200
                      Re: email lacks sender address Haines Brown <haines@histomat.net> - 2022-04-27 15:40 +0200
                        Re: email lacks sender address Vincent Lefevre <vincent@vinc17.net> - 2022-04-27 16:30 +0200
                          Re: email lacks sender address Haines Brown <haines@histomat.net> - 2022-04-27 16:50 +0200
                            Re: email lacks sender address Greg Wooledge <greg@wooledge.org> - 2022-04-27 17:00 +0200
                              Re: email lacks sender address Haines Brown <haines@histomat.net> - 2022-04-27 17:30 +0200
                      Re: email lacks sender address <tomas@tuxteam.de> - 2022-04-27 15:40 +0200
                        Re: email lacks sender address Brian <ad44@cityscape.co.uk> - 2022-04-27 16:40 +0200
                          Re: email lacks sender address Haines Brown <haines@histomat.net> - 2022-04-27 17:10 +0200
                            Re: email lacks sender address Greg Wooledge <greg@wooledge.org> - 2022-04-27 17:30 +0200
                              Re: email lacks sender address Brian <ad44@cityscape.co.uk> - 2022-04-27 18:10 +0200
                              Re: email lacks sender address Haines Brown <haines@histomat.net> - 2022-04-27 19:50 +0200
                                Re: email lacks sender address Greg Wooledge <greg@wooledge.org> - 2022-04-27 20:40 +0200
                                  Re: email lacks sender address Vincent Lefevre <vincent@vinc17.net> - 2022-04-27 23:50 +0200
                                Re: email lacks sender address Brian <ad44@cityscape.co.uk> - 2022-04-27 21:10 +0200
                                Re: email lacks sender address Vincent Lefevre <vincent@vinc17.net> - 2022-04-27 23:00 +0200
                              Re: email lacks sender address Vincent Lefevre <vincent@vinc17.net> - 2022-04-27 22:50 +0200
                                Re: email lacks sender address <tomas@tuxteam.de> - 2022-04-28 07:00 +0200
                    Re: email lacks sender address Vincent Lefevre <vincent@vinc17.net> - 2022-04-27 16:20 +0200
                    Re: email lacks sender address Brian <ad44@cityscape.co.uk> - 2022-04-27 20:30 +0200
                      Re: email lacks sender address Greg Wooledge <greg@wooledge.org> - 2022-04-27 21:40 +0200
                        Re: email lacks sender address Vincent Lefevre <vincent@vinc17.net> - 2022-04-27 23:30 +0200
                    Re: email lacks sender address David Wright <deblis@lionunicorn.co.uk> - 2022-04-27 22:00 +0200
                      Re: email lacks sender address Greg Wooledge <greg@wooledge.org> - 2022-04-27 22:30 +0200
                      Re: email lacks sender address Brian <ad44@cityscape.co.uk> - 2022-04-28 17:00 +0200
                        Re: email lacks sender address David Wright <deblis@lionunicorn.co.uk> - 2022-04-28 19:10 +0200
                          Re: email lacks sender address Greg Wooledge <greg@wooledge.org> - 2022-04-28 19:20 +0200
                            Re: email lacks sender address David Wright <deblis@lionunicorn.co.uk> - 2022-04-29 01:50 +0200
            Re: email lacks sender address Vincent Lefevre <vincent@vinc17.net> - 2022-04-27 17:20 +0200
              Re: email lacks sender address Haines Brown <haines@histomat.net> - 2022-04-27 17:30 +0200
        Re: email lacks sender address Curt <curty@free.fr> - 2022-04-25 14:10 +0200
          Re: email lacks sender address David Wright <deblis@lionunicorn.co.uk> - 2022-04-25 16:20 +0200
            Re: email lacks sender address Greg Wooledge <greg@wooledge.org> - 2022-04-25 16:30 +0200
              Re: email lacks sender address David Wright <deblis@lionunicorn.co.uk> - 2022-04-25 17:10 +0200
            Re: email lacks sender address Haines Brown <haines@histomat.net> - 2022-04-25 16:40 +0200
        Re: email lacks sender address Vincent Lefevre <vincent@vinc17.net> - 2022-04-26 17:20 +0200
          Re: email lacks sender address Curt <curty@free.fr> - 2022-04-26 17:40 +0200
    Re: email lacks sender address 황병희 <soyeomul@doraji.xyz> - 2022-04-25 03:20 +0200
      Re: email lacks sender address Jim Popovitch <jim@k4vqc.com> - 2022-04-25 03:50 +0200
        Re: email lacks sender address 황병희 <soyeomul@doraji.xyz> - 2022-04-25 06:50 +0200
      Re: email lacks sender address Haines Brown <haines@histomat.net> - 2022-04-25 05:40 +0200
        Re: email lacks sender address 황병희 <soyeomul@doraji.xyz> - 2022-04-25 07:00 +0200
        Re: email lacks sender address Greg Wooledge <greg@wooledge.org> - 2022-04-25 14:50 +0200
          Re: email lacks sender address 황병희 <soyeomul@doraji.xyz> - 2022-04-26 02:50 +0200
            Re: email lacks sender address Celejar <celejar@gmail.com> - 2022-04-26 18:10 +0200
              Re: email lacks sender address Byung-Hee HWANG <soyeomul@doraji.xyz>  - 2022-04-27 03:10 +0200
                Re: email lacks sender address Byung-Hee HWANG <soyeomul@doraji.xyz>  - 2022-04-27 03:20 +0200
                Re: email lacks sender address Celejar <celejar@gmail.com> - 2022-04-27 17:30 +0200
                  Re: email lacks sender address Byung-Hee HWANG <soyeomul@doraji.xyz>  - 2022-04-27 20:40 +0200
                    Re: email lacks sender address (SOLVED) Haines Brown <haines@histomat.net> - 2022-05-08 18:10 +0200
                      Re: email lacks sender address (SOLVED) Charles Curley <charlescurley@charlescurley.com> - 2022-05-08 19:10 +0200
                        Re: email lacks sender address (SOLVED) David Wright <deblis@lionunicorn.co.uk> - 2022-05-09 02:50 +0200
                          Re: email lacks sender address (SOLVED) Charles Curley <charlescurley@charlescurley.com> - 2022-05-09 03:30 +0200
                            Re: email lacks sender address (SOLVED) David Wright <deblis@lionunicorn.co.uk> - 2022-05-09 04:40 +0200

Page 4 of 4 — ← Prev page 1 2 3 [4]

#247505

FromHaines Brown <haines@histomat.net>
Date2022-04-25 05:40 +0200
Message-ID<EfXJU-b0tf-5@gated-at.bofh.it>
In reply to#247502
On Mon, Apr 25, 2022 at 10:16:09AM +0900, 황병희 wrote:
> Haines Brown <haines@histomat.net> writes:
> 
> > (... thanks ...)
> > 521 5.5.1 Protocol error (154.24 ms)
> > Unverified address
> >
> > I reconfigured exim4 and it has no problem.
> >
> 
> Or you try with sSMTP, very easy!
> 
> Sincerely, Linux fan Byung-Hee

Thanks for the suggestion, but I have same problem with ssmtp as I 
do with swaks: what does "test-server.example.net" refer to? Sorry
for my ignorance.

[toc] | [prev] | [next] | [standalone]

#247508

From황병희 <soyeomul@doraji.xyz>
Date2022-04-25 07:00 +0200
Message-ID<EfYZk-b1cY-1@gated-at.bofh.it>
In reply to#247505
Haines Brown <haines@histomat.net> writes:

> (... thanks ...)
> Thanks for the suggestion, but I have same problem with ssmtp as I 
> do with swaks: what does "test-server.example.net" refer to?

Sorry i don't know that <<test-server.example.net>>.

> Sorry for my ignorance. 

Don't worry! Always email stuff are not easy, i think...


Sincerely, Linux fan Byung-Hee

-- 
^고맙습니다 _布德天下_ 감사합니다_^))//

[toc] | [prev] | [next] | [standalone]

#247517

FromGreg Wooledge <greg@wooledge.org>
Date2022-04-25 14:50 +0200
Message-ID<Eg6k9-b5Tv-5@gated-at.bofh.it>
In reply to#247505
On Sun, Apr 24, 2022 at 11:37:00PM -0400, Haines Brown wrote:
> On Mon, Apr 25, 2022 at 10:16:09AM +0900, 황병희 wrote:
> > Haines Brown <haines@histomat.net> writes:
> > 
> > > (... thanks ...)
> > > 521 5.5.1 Protocol error (154.24 ms)
> > > Unverified address
> > >
> > > I reconfigured exim4 and it has no problem.
> > >
> > 
> > Or you try with sSMTP, very easy!
> > 
> > Sincerely, Linux fan Byung-Hee
> 
> Thanks for the suggestion, but I have same problem with ssmtp as I 
> do with swaks: what does "test-server.example.net" refer to? Sorry
> for my ignorance. 

unicorn:~$ apt-cache show ssmtp
[...]
Description-en: extremely simple MTA to get mail off the system to a mail hub
 A secure, effective and simple way of getting mail off a system to your
 mail hub. It contains no suid-binaries or other dangerous things - no mail
 spool to poke around in, and no daemons running in the background. Mail is
 simply forwarded to the configured mailhost. Extremely easy configuration.

The entire point of this package is that it's meant to be used on a
"dumb client" which does not wish to have its own outgoing mail queue.
Instead, it forwards all of your mail to your "smart host" -- the MTA
that has been set up for your organization's dumb clients to use.

So, the single piece of information you need in order to use ssmtp is
the hostname of your smart host.  Also known as your mail relay.  Or many
other names.  It's where you want your outgoing mail to be handled.

[toc] | [prev] | [next] | [standalone]

#247555

From황병희 <soyeomul@doraji.xyz>
Date2022-04-26 02:50 +0200
Message-ID<EghyV-bcKd-1@gated-at.bofh.it>
In reply to#247517
Dear Greg,

Greg Wooledge <greg@wooledge.org> writes:

> (... thanks ...)
> unicorn:~$ apt-cache show ssmtp
> [...]
> Description-en: extremely simple MTA to get mail off the system to a mail hub
>  A secure, effective and simple way of getting mail off a system to your
>  mail hub. It contains no suid-binaries or other dangerous things - no mail
>  spool to poke around in, and no daemons running in the background. Mail is
>  simply forwarded to the configured mailhost. Extremely easy configuration.
>
> The entire point of this package is that it's meant to be used on a
> "dumb client" which does not wish to have its own outgoing mail queue.
> Instead, it forwards all of your mail to your "smart host" -- the MTA
> that has been set up for your organization's dumb clients to use.
>
> So, the single piece of information you need in order to use ssmtp is
> the hostname of your smart host.  Also known as your mail relay.  Or many
> other names.  It's where you want your outgoing mail to be handled.
>

Thanks for your time and your life!

Really i love sSMTP so much!!!

Thanks again ^^^

Sincerely, Linux fan Byung-Hee

-- 
^고맙습니다 _布德天下_ 감사합니다_^))//

[toc] | [prev] | [next] | [standalone]

#247579

FromCelejar <celejar@gmail.com>
Date2022-04-26 18:10 +0200
Message-ID<EgvVf-bmbJ-5@gated-at.bofh.it>
In reply to#247555
On Tue, 26 Apr 2022 09:42:38 +0900
황병희 <soyeomul@doraji.xyz> wrote:

> Dear Greg,
> 
> Greg Wooledge <greg@wooledge.org> writes:
> 
> > (... thanks ...)
> > unicorn:~$ apt-cache show ssmtp
> > [...]
> > Description-en: extremely simple MTA to get mail off the system to a mail hub
> >  A secure, effective and simple way of getting mail off a system to your
> >  mail hub. It contains no suid-binaries or other dangerous things - no mail
> >  spool to poke around in, and no daemons running in the background. Mail is
> >  simply forwarded to the configured mailhost. Extremely easy configuration.
> >
> > The entire point of this package is that it's meant to be used on a
> > "dumb client" which does not wish to have its own outgoing mail queue.
> > Instead, it forwards all of your mail to your "smart host" -- the MTA
> > that has been set up for your organization's dumb clients to use.
> >
> > So, the single piece of information you need in order to use ssmtp is
> > the hostname of your smart host.  Also known as your mail relay.  Or many
> > other names.  It's where you want your outgoing mail to be handled.
> >
> 
> Thanks for your time and your life!
> 
> Really i love sSMTP so much!!!

FWIW, there's an outstanding ten year old bug against sSMTP pointing
out that it doesn't bother to validate server TLS certificates. You'll
have to decide whether this bothers you or not:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662960

-- 
Celejar

[toc] | [prev] | [next] | [standalone]

#247588

FromByung-Hee HWANG <soyeomul@doraji.xyz>
Date2022-04-27 03:10 +0200
Message-ID<EgElP-br7J-1@gated-at.bofh.it>
In reply to#247579
Dear Celejar,

Celejar <celejar@gmail.com> writes:

> On Tue, 26 Apr 2022 09:42:38 +0900
> 황병희 <soyeomul@doraji.xyz> wrote:
>
>> Dear Greg,
>> 
>> Greg Wooledge <greg@wooledge.org> writes:
>> 
>> > (... thanks ...)
>> > unicorn:~$ apt-cache show ssmtp
>> > [...]
>> > Description-en: extremely simple MTA to get mail off the system to
>> > a mail hub
>> >  A secure, effective and simple way of getting mail off a system to your
>> >  mail hub. It contains no suid-binaries or other dangerous things - no mail
>> >  spool to poke around in, and no daemons running in the background. Mail is
>> >  simply forwarded to the configured mailhost. Extremely easy configuration.
>> >
>> > The entire point of this package is that it's meant to be used on a
>> > "dumb client" which does not wish to have its own outgoing mail queue.
>> > Instead, it forwards all of your mail to your "smart host" -- the MTA
>> > that has been set up for your organization's dumb clients to use.
>> >
>> > So, the single piece of information you need in order to use ssmtp is
>> > the hostname of your smart host.  Also known as your mail relay.  Or many
>> > other names.  It's where you want your outgoing mail to be handled.
>> >
>> 
>> Thanks for your time and your life!
>> 
>> Really i love sSMTP so much!!!
>
> FWIW, there's an outstanding ten year old bug against sSMTP pointing
> out that it doesn't bother to validate server TLS certificates. You'll
> have to decide whether this bothers you or not:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662960

That seems some technical issue. However i have no skills to repair that
C level program.

Actually i have no trouble with current sSMTP. Both Gmail and yw-1204
does not break about this matter (verify certificate). So for a while
i'll keep this state. It means that i will continue to use the sSMTP.

Sorry and thanks ^^^

Sincerely, Linux fan Byung-Hee

-- 
^고맙습니다 _布德天下_ 감사합니다_^))//

[toc] | [prev] | [next] | [standalone]

#247589

FromByung-Hee HWANG <soyeomul@doraji.xyz>
Date2022-04-27 03:20 +0200
Message-ID<EgEvv-brbi-1@gated-at.bofh.it>
In reply to#247588
> Both Gmail and yw-1204
> does not break about this matter (verify certificate).

Correction: Exactly, i did't see any problems. Because i have been using always
self-signed certficate with sSMTP.

Sorry for confusing statement. 

Sincerely, Linux fan Byung-Hee

-- 
^고맙습니다 _布德天下_ 감사합니다_^))//

[toc] | [prev] | [next] | [standalone]

#247643

FromCelejar <celejar@gmail.com>
Date2022-04-27 17:30 +0200
Message-ID<EgRM5-bzxu-7@gated-at.bofh.it>
In reply to#247588
On Wed, 27 Apr 2022 10:04:06 +0900
Byung-Hee HWANG <soyeomul@doraji.xyz>  wrote:

> Dear Celejar,
> 
> Celejar <celejar@gmail.com> writes:
> 
> > On Tue, 26 Apr 2022 09:42:38 +0900
> > 황병희 <soyeomul@doraji.xyz> wrote:
> >
> >> Dear Greg,
> >> 
> >> Greg Wooledge <greg@wooledge.org> writes:
> >> 
> >> > (... thanks ...)
> >> > unicorn:~$ apt-cache show ssmtp

...

> >> Really i love sSMTP so much!!!
> >
> > FWIW, there's an outstanding ten year old bug against sSMTP pointing
> > out that it doesn't bother to validate server TLS certificates. You'll
> > have to decide whether this bothers you or not:
> >
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662960
> 
> That seems some technical issue. However i have no skills to repair that
> C level program.
> 
> Actually i have no trouble with current sSMTP. Both Gmail and yw-1204
> does not break about this matter (verify certificate). So for a while
> i'll keep this state. It means that i will continue to use the sSMTP.


[From another email by Byung-Hee:]

> Correction: Exactly, i did't see any problems. Because i have been using always
> self-signed certficate with sSMTP.
> 
> Sorry for confusing statement. 

I'm not sure what you are saying here - are you possibly confusing
client and server certificates? - but the problem is not that sSMTP
doesn't work with Gmail - the problem is that it doesn't verify the
server's SSL certificate, so it's susceptible to a MITM attack by
someone impersonating Gmail. Again, you'll have to judge for yourself
whether this is something to worry about.

-- 
Celejar

[toc] | [prev] | [next] | [standalone]

#247660

FromByung-Hee HWANG <soyeomul@doraji.xyz>
Date2022-04-27 20:40 +0200
Message-ID<EgUJX-bBiA-5@gated-at.bofh.it>
In reply to#247643
Celejar <celejar@gmail.com> writes:

> (... thanks ...)
> the problem is that it doesn't verify the
> server's SSL certificate, so it's susceptible to a MITM attack by
> someone impersonating Gmail. Again, you'll have to judge for yourself
> whether this is something to worry about.

Now i understood correctly.
Thanks for the summary, Celejar!

Sincerely, Linux fan Byung-Hee

-- 
^고맙습니다 _布德天下_ 감사합니다_^))//

[toc] | [prev] | [next] | [standalone]

#247993 — Re: email lacks sender address (SOLVED)

FromHaines Brown <haines@histomat.net>
Date2022-05-08 18:10 +0200
SubjectRe: email lacks sender address (SOLVED)
Message-ID<EkRDP-e7Jc-3@gated-at.bofh.it>
In reply to#247660
I appreciate tbe rich reponses to my question. I  believe I found the 
answer. Not sure but at least the messages I've been sending now get 
to ter recipients

When I installed the operating systme, the host name some how at a 
numvber appended. I inteded to have nost name lenin, but it ended up 
lenin-16. When I discovred that afer installation I corrrected the
host name in /etc/hsots and /etc/hostname. 

Whats I didn't check  was what my router took to be my host name. 
It did not reponse to my changed host name and I had to do it manually 
in the router. Doing do seems to have solved my problem.

[toc] | [prev] | [next] | [standalone]

#247997 — Re: email lacks sender address (SOLVED)

FromCharles Curley <charlescurley@charlescurley.com>
Date2022-05-08 19:10 +0200
SubjectRe: email lacks sender address (SOLVED)
Message-ID<EkSzT-e8iB-11@gated-at.bofh.it>
In reply to#247993
On Sun, 8 May 2022 12:07:00 -0400
Haines Brown <haines@histomat.net> wrote:

> When I installed the operating systme, the host name some how at a 
> numvber appended. I inteded to have nost name lenin, but it ended up 
> lenin-16. When I discovred that afer installation I corrrected the
> host name in /etc/hsots and /etc/hostname. 

Systemd provides a program for setting the host name, called, oddly
enough, hostnamectl. It may do other things you might have missed.

I doubt it would have affected your router, though.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [next] | [standalone]

#248018 — Re: email lacks sender address (SOLVED)

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2022-05-09 02:50 +0200
SubjectRe: email lacks sender address (SOLVED)
Message-ID<EkZL3-ecvG-1@gated-at.bofh.it>
In reply to#247997
On Sun 08 May 2022 at 11:08:08 (-0600), Charles Curley wrote:
> On Sun, 8 May 2022 12:07:00 -0400
> Haines Brown <haines@histomat.net> wrote:
> 
> > When I installed the operating systme, the host name some how at a 
> > numvber appended. I inteded to have nost name lenin, but it ended up 
> > lenin-16. When I discovred that afer installation I corrrected the
> > host name in /etc/hsots and /etc/hostname. 
> 
> Systemd provides a program for setting the host name, called, oddly
> enough, hostnamectl. It may do other things you might have missed.
> 
> I doubt it would have affected your router, though.

I'm really not sure who, and under what circumstances,
hostnamectl is for. I ran:

# hostnamectl set-hostname acerx

and /etc/hostname was changed, but not /etc/hosts, which still had:

127.0.1.1       acer.corp       acer

and also not /etc/mailname. I'm not saying it should have affected
those occurrences, but that it's better to check you have the
correct, consistent name throughout the system.

It's also not clear to me either, where one might insert this command
so that it takes effect early enough to avoid polluting the system
with wrong names. (The logs, for one example.)

> > Whats I didn't check  was what my router took to be my host name. 
> > It did not reponse to my changed host name and I had to do it manually 
> > in the router. Doing do seems to have solved my problem.

It would seem then that you were letting DHCP in the router set your
hostname as well as the usual IP address, nameservers etc, which
could be unfortunate if it doesn't agree. How you avoid that depends ….

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#248023 — Re: email lacks sender address (SOLVED)

FromCharles Curley <charlescurley@charlescurley.com>
Date2022-05-09 03:30 +0200
SubjectRe: email lacks sender address (SOLVED)
Message-ID<El0nL-ecX5-3@gated-at.bofh.it>
In reply to#248018
On Sun, 8 May 2022 19:42:57 -0500
David Wright <deblis@lionunicorn.co.uk> wrote:

> I'm really not sure who, and under what circumstances,
> hostnamectl is for.

Nor am I, especially after this. According to apt-file, it is in the
package systemd.

> I ran:
> 
> # hostnamectl set-hostname acerx
> 
> and /etc/hostname was changed, but not /etc/hosts, which still had:
> 
> 127.0.1.1       acer.corp       acer

I confirm this. I guess I missed it due to rarely referring to a
computer by its hostname, but instead by localhost. Sigh. Thanks for
the catch. It looks like I shall have to adjust my installation scripts.

> 
> and also not /etc/mailname. I'm not saying it should have affected
> those occurrences, but that it's better to check you have the
> correct, consistent name throughout the system.

Odd. On the two boxes I used hostnamectl on, mailname is set correctly.
However, I ran it on installation, and may have fixed that manually
(but there's no backup file), or by installing postfix subsequently.

> 
> It's also not clear to me either, where one might insert this command
> so that it takes effect early enough to avoid polluting the system
> with wrong names. (The logs, for one example.)

I run it in a script that I run manually immediately after installation.

> 
> > > Whats I didn't check  was what my router took to be my host name. 
> > > It did not reponse to my changed host name and I had to do it
> > > manually in the router. Doing do seems to have solved my problem.
> > >  
> 
> It would seem then that you were letting DHCP in the router set your
> hostname as well as the usual IP address, nameservers etc, which
> could be unfortunate if it doesn't agree. How you avoid that depends
> ….

Yup. However I make sure they agree by assigning most hosts a "host"
statement in dhcpd.conf, and assigning a fixed IP address to a given MAC
address, and then having dhcpd feed that to bind9.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [next] | [standalone]

#248029 — Re: email lacks sender address (SOLVED)

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2022-05-09 04:40 +0200
SubjectRe: email lacks sender address (SOLVED)
Message-ID<El1tv-edI5-3@gated-at.bofh.it>
In reply to#248023
On Sun 08 May 2022 at 19:20:05 (-0600), Charles Curley wrote:
> On Sun, 8 May 2022 19:42:57 -0500 David Wright wrote:
> 
> > I'm really not sure who, and under what circumstances,
> > hostnamectl is for.
> 
> Nor am I, especially after this. According to apt-file, it is in the
> package systemd.
> 
> > I ran:
> > 
> > # hostnamectl set-hostname acerx
> > 
> > and /etc/hostname was changed, but not /etc/hosts, which still had:
> > 
> > 127.0.1.1       acer.corp       acer
> 
> I confirm this. I guess I missed it due to rarely referring to a
> computer by its hostname, but instead by localhost. Sigh. Thanks for
> the catch. It looks like I shall have to adjust my installation scripts.
> 
> > 
> > and also not /etc/mailname. I'm not saying it should have affected
> > those occurrences, but that it's better to check you have the
> > correct, consistent name throughout the system.
> 
> Odd. On the two boxes I used hostnamectl on, mailname is set correctly.
> However, I ran it on installation, and may have fixed that manually
> (but there's no backup file), or by installing postfix subsequently.

Well, I was running hostnamectl after the event, ie on an already
fully-configured system. In your case, you probably configured exim
after setting the hostname (or it's the same name anyway, or whatever).
OTOH I think dpkg-reconfigure reads the mailname from /etc/hosts,
rather than /etc/hostname, initially (ie when /etc/mailname is unset.
If it's already set, it just parrots it.).

> > It's also not clear to me either, where one might insert this command
> > so that it takes effect early enough to avoid polluting the system
> > with wrong names. (The logs, for one example.)
> 
> I run it in a script that I run manually immediately after installation.

I see. And it sets /etc/hostname for good. But I think the OP's
problem might have been that DHCP was overwriting /etc/hostname
each time it ran (or ran at boot time).

> > > > Whats I didn't check  was what my router took to be my host name. 
> > > > It did not reponse to my changed host name and I had to do it
> > > > manually in the router. Doing do seems to have solved my problem.
> > > >  
> > 
> > It would seem then that you were letting DHCP in the router set your
> > hostname as well as the usual IP address, nameservers etc, which
> > could be unfortunate if it doesn't agree. How you avoid that depends
> > ….
> 
> Yup. However I make sure they agree by assigning most hosts a "host"
> statement in dhcpd.conf, and assigning a fixed IP address to a given MAC
> address, and then having dhcpd feed that to bind9.

Similarly here, except that I don't have anything running a DNS
server. But the router's DHCP table's hostname agrees with
/etc/hostname, /etc/hosts, /etc/mailname, and any derived places
like update-exim4.conf.conf and the ssh keys.

BTW my "…" stood for "different with different configurations", and
I don't think I can even avoid it on my own preferred DHCP client,
iwd. (I think I have seen a post proferring a patch to allow it.)

Cheers,
David.

[toc] | [prev] | [standalone]

Page 4 of 4 — ← Prev page 1 2 3 [4]

Back to top | Article view | linux.debian.user

csiph-web