[gentoo-user] install bug
install-amd64-minimal-20220403T220339Z.iso when gentoo-nofb got used for kernel selection and speakup.synth=soft as boot parameter I got as far as setting a root password then speakup crashed. The other thing I didn't see that happened was two returns were needed to get speakup talking at all once the boot line got keyed in. I'll try the standard gentoo kernel next and see if I can duplicate behavior.
Re: [gentoo-user] Fully-Defined-Domain-Name for nullmailer
On 4/13/22 3:40 PM, Grant Taylor wrote: I don't know what name Thunderbird uses in it's HELO / EHLO command(s). Though it shouldn't matter much which name is used. The important thing should be that the SMTP client, be it Thunderbird or nullmailer or something else, should authenticate to the outbound relay / MSA. The MSA should then use that authentication as a control for what is and is not allowed to be relayed. Okay, that's a good tip. From tcpdump on my work machine (nullmailer runs on my home machine, though), I have: EHLO.[10.0 0x0040: 2e32 2e31 355d 0d0a .2.15].. so the argument to EHLO supplied by /thunderbird/ is my ip address. So, the hypothesis is, if I can coerce nullmailer to use that, it should work?
Re: [gentoo-user] Fully-Defined-Domain-Name for nullmailer
On 4/13/22 6:31 AM, n952162 wrote: Unfortunately, I get a 550 from my network provider for all of these: 1. me 2. localdomain 3. net 4. web.de So, how does thunderbird do it? I don't know what name Thunderbird uses in it's HELO / EHLO command(s). Though it shouldn't matter much which name is used. The important thing should be that the SMTP client, be it Thunderbird or nullmailer or something else, should authenticate to the outbound relay / MSA. The MSA should then use that authentication as a control for what is and is not allowed to be relayed. Nominally, the name used has little effect on the SMTP session. However there is more and more sanity checking being applied for server to server SMTP connections. Mostly the sanity checking is around that a sender isn't obviously lying or trying to get around security checks. These attempts usually take the form of pretending to be the destination or another known / easily identifiable lie. Mail servers that send server to server traffic actually SHOULD use proper names that validate. Clients shouldn't need to adhere to as high a standard. I consider nullmailer to be a client in this case. -- Grant. . . . unix || die
Re: [gentoo-user] Fully-Defined-Domain-Name for nullmailer
On 4/13/22 11:53 AM, n952162 wrote: Hello, What would this be for the 99% of all linux users who are connected to the internet via DSL? Is "localdomain" sufficient for nullmailer? (I tried it, temporarily, in /etc/conf.d/hostname), but it didn't help. And, is there anyway that I can set it without putting it in my /etc/conf.d/hostname file? That will require changes to any script that uses $(uname -n). I discovered that if I set (apparently, both of ) these to some value, that value will be used as the domain. 1. /etc/nullmailer/defaultname 2. /etc/nullmailer/me That answers the second part of the question. Unfortunately, I get a 550 from my network provider for all of these: 1. me 2. localdomain 3. net 4. web.de So, how does thunderbird do it?
[gentoo-user] Fully-Defined-Domain-Name for nullmailer
Hello, What would this be for the 99% of all linux users who are connected to the internet via DSL? Is "localdomain" sufficient for nullmailer? (I tried it, temporarily, in /etc/conf.d/hostname), but it didn't help. And, is there anyway that I can set it without putting it in my /etc/conf.d/hostname file? That will require changes to any script that uses $(uname -n).
