Re: Has gmail SMTP authentication changed recently?

On 16.07.2025 16:20 Frank Bures wrote: > Mailertable is empty (default). Nothing has been specified, but it > has been like that since the beginning and relaying via gmail worked > for almost two years. I have NOT changed anything in any relevant > config in the meantime. Then it will use port

Re: Has gmail SMTP authentication changed recently?

On 16.07.2025 21:59 Sam Varshavchik wrote: > In most cases nobody wanted to waste their time figuring out what the > "something" of the "something is faulty" actually is, and just asked > for a configuration switch to always use IPv4, or always use IPv6. So > that's what I did. > > I'm not famil

Re: Has gmail SMTP authentication changed recently?

On 16.07.2025 15:50 Frank Bures wrote: > mtr --tcp -P 587 smtp.gmail.com > > I get > > 1. (no route to host) Then something on your system is faulty. Show ip a ip -6 r s -- kind regards Marco Send spam to abfall1752673...@stinkedores.dorfdsl.de -- _

Re: Working with secureboot

On Wed, 2025-07-16 at 13:39 -0400, Robert McBroom via users wrote: > My understanding was that it was a new password entry Todd Zullinger's earlier post said: >> You should already have the key, which is stored at >> /etc/pki/akmods/certs/public_key.der. The "code" that >> GNOME provides is the

Re: Emergency mode - maybe OT

Paolo Galtieri writes: Folks,  during the night there was a power failure. When I powered up one of my systems it booted into emergency mode.  I'm not sure what to do to get it out of this.  Nothing I've tried works. Both root and home are mounted.  The default target is graphical.target.

Re: Has gmail SMTP authentication changed recently? - SOLVED

Frank Bures writes: On 2025-07-16 16:21, Chris Adams wrote: Out of desperation I changed my DNS from 1.1.1.1 etc. to 8.8.8.8 etc. That required EERO reboot and after the reboot everything is back to normal. Thank you all for the help This was in the news. 1.1.1.1 is Cloudflare, and they crap

Re: Has gmail SMTP authentication changed recently?

Marco Moock writes: Am 16.07.2025 um 15:18:28 Uhr schrieb Frank Bures: > mtr --tcp -P 587 -6 smtp.gmail.com > > returns: > > mtr: udp socket connect failed: Network is unreachable Indicates that something is faulty. Leave -6 out, it will default to IPv6. If not, something other is faulty. I'

Re: Problem accessing lvm on nvme drive

On 7/15/25 1:22 AM, Samuel Sieb wrote: On 7/13/25 1:31 PM, Robert McBroom via users wrote: During boot I get the message block nvme0n1: No UUID available providing old NGUID When I try to mount the lvm I get the message ~# mount /dev/mapper/fedora /sd1 mount: /sd1: fsconfig system call faile

Re: Has gmail SMTP authentication changed recently?

> On 16 Jul 2025, at 21:16, Frank Bures wrote: > > I tried to add the default route to the IPv6 with > > ip -6 route add default via fe80::::: dev enp42s0 That should not be required if you ipv6 router and isp are working correctly. Can you confirm that your isp is providing

Re: multiboot 2 HD

On 7/16/25 2:55 PM, Patrick Dupre via users wrote: On 7/15/25 2:45 PM, Patrick Dupre via users wrote: Sent: Sunday, July 13, 2025 at 1:06 PM From: "Steven I Usdansky via users" To: "users@lists.fedoraproject.org" Cc: "Steven I Usdansky" Subject: Re: multiboot 2 HD Each of my three drive

Re: multiboot 2 HD

> > On 7/15/25 2:45 PM, Patrick Dupre via users wrote: > > > >> Sent: Sunday, July 13, 2025 at 1:06 PM > >> From: "Steven I Usdansky via users" > >> To: "users@lists.fedoraproject.org" > >> Cc: "Steven I Usdansky" > >> Subject: Re: multiboot 2 HD > >> > >> Each of my three drives is bootable h

Re: Has gmail SMTP authentication changed recently? - SOLVED

On 2025-07-16 16:21, Chris Adams wrote: Out of desperation I changed my DNS from 1.1.1.1 etc. to 8.8.8.8 etc. That required EERO reboot and after the reboot everything is back to normal. Thank you all for the help Frank -- -- ___ users mailing list

Re: Emergency mode - maybe OT

On 7/16/25 10:07 AM, Paolo Galtieri wrote:  during the night there was a power failure. When I powered up one of my systems it booted into emergency mode.  I'm not sure what to do to get it out of this.  Nothing I've tried works. Both root and home are mounted.  The default target is graphical

Re: Has gmail SMTP authentication changed recently?

Frank Bures composed on 2025-07-16 12:04 (UTC-0400): > On 2025-07-16 11:51, Frank Bures wrote: >> Recently I have not been able to send root system mail from my Fedora 42 >> machine using Sendmail via gmail SMTP relay.  It worked reliably since I >> built this machine more than a year ago. >>

Re: Has gmail SMTP authentication changed recently?

Once upon a time, Frank Bures said: > ip -6 route > > does not have "default" entry. > > ip -6 neigh > > returns all entries "STALE", no "REACHABLE". Either your router dropped the IPv6 ball or your service provider did. Your issues starting the other way around (v4 broke, v6 work) points even

Re: Has gmail SMTP authentication changed recently?

On 2025-07-16 15:29, Marco Moock wrote: How does the smarthost/mailertable config look? Mailertable is empty (default). Nothing has been specified, but it has been like that since the beginning and relaying via gmail worked for almost two years. I have NOT changed anything in any relevant

Re: Has gmail SMTP authentication changed recently?

On 2025-07-16 15:38, Chris Adams wrote: Once upon a time, Frank Bures said: mtr --tcp -P 587 -4 smtp.gmail.com works OK. mtr --tcp -P 587 -6 smtp.gmail.com returns: mtr: udp socket connect failed: Network is unreachable So you've flipped from v4 not working to v6 not working? Do you have

Re: Has gmail SMTP authentication changed recently?

On 2025-07-16 15:27, Marco Moock wrote: Am 16.07.2025 um 15:18:28 Uhr schrieb Frank Bures: mtr --tcp -P 587 -6 smtp.gmail.com returns: mtr: udp socket connect failed: Network is unreachable Indicates that something is faulty. Leave -6 out, it will default to IPv6. If not, something other is

Re: Has gmail SMTP authentication changed recently?

Once upon a time, Frank Bures said: > mtr --tcp -P 587 -4 smtp.gmail.com > > works OK. > > mtr --tcp -P 587 -6 smtp.gmail.com > > returns: > > mtr: udp socket connect failed: Network is unreachable So you've flipped from v4 not working to v6 not working? Do you have working IPv6 for other se

Re: Has gmail SMTP authentication changed recently?

Am 16.07.2025 um 15:07:30 Uhr schrieb Frank Bures: > bures@ryzen:~$ openssl s_client -starttls smtp -connect > smtp.gmail.com:587 Connecting to 192.178.157.108 > CONNECTED(0003) > depth=2 C=US, O=Google Trust Services LLC, CN=GTS Root R1 > > Seems to be working fine. On port 587. Did you ch

Re: Has gmail SMTP authentication changed recently?

Am 16.07.2025 um 15:18:28 Uhr schrieb Frank Bures: > mtr --tcp -P 587 -6 smtp.gmail.com > > returns: > > mtr: udp socket connect failed: Network is unreachable Indicates that something is faulty. Leave -6 out, it will default to IPv6. If not, something other is faulty. -- Gruß Marco Send uns

Re: Has gmail SMTP authentication changed recently?

On 2025-07-16 14:54, Chris Adams wrote: Once upon a time, Frank Bures said: More info: openssl s_client -connect smtp.gmail.com:587 -6 That is incorrect. I know. I corrected it already. Thanks. You should probably check your Internet path with mtr, like: $ mtr --tcp -P 587 -6 smtp.g

Re: Has gmail SMTP authentication changed recently?

On 2025-07-16 13:54, Marco Moock wrote: Am 16.07.2025 um 12:04:16 Uhr schrieb Frank Bures: If smtp.gmail.com resolves to an IPv6 address, relaying works. If it resolves into IPv4 address, the above error ensues. I checked my firewall, there is nothing relevant to the smtp.gmail.com IPv4 addre

Re: Has gmail SMTP authentication changed recently?

Once upon a time, Frank Bures said: > More info: > > openssl s_client -connect smtp.gmail.com:587 -6 That is incorrect. Port 587 will require SMTP+STARTTLS, not SSL-wrapped SMTP (which is port 465). You'd want to add "-starttls smtp" to your openssl test command. However... > returns: > > C

Re: Problem accessing lvm on nvme drive

On 7/16/25 11:05 AM, Barry Scott wrote: On 15 Jul 2025, at 05:51, Robert McBroom via users wrote: ├─nvme0n1p5 │ LVM2_mem LVM2 001 v1gXoi-sKLO-fS0t-oKxo-en1J-7vOu-BH8Hal └─nvme0n1p6 LVM2_mem LVM2 001 lQ45eA-ARYv-JiVX-JRjR-eyHl-NCXO-vkB2m0 Why are there two LVM2 partitions? That is not

Re: Has gmail SMTP authentication changed recently?

On 2025-07-16 12:21, Barry Scott wrote: You should always get both IPv4 and IPv6 addresses back. $ host smtp.gmail.com smtp.gmail.com has address 66.102.1.109 smtp.gmail.com has IPv6 address 2a00:1450:400c:c06::6d I see this: root@ryzen:/var# host smtp.gmail.com smtp.gmail.com has address 19

Re: Emergency mode - maybe OT

Am 16.07.2025 um 10:07:00 Uhr schrieb Paolo Galtieri: >  during the night there was a power failure. When I powered up one > of my systems it booted into emergency mode.  I'm not sure what to do > to get it out of this.  Nothing I've tried works. Both root and home > are mounted.  The default tar

Re: Has gmail SMTP authentication changed recently?

Am 16.07.2025 um 12:04:16 Uhr schrieb Frank Bures: > If smtp.gmail.com resolves to an IPv6 address, relaying works. If it > resolves into IPv4 address, the above error ensues. > > I checked my firewall, there is nothing relevant to the > smtp.gmail.com IPv4 addresses. Can you contact the serve

Re: Working with secureboot

On 7/15/25 4:32 AM, Tim via users wrote: On Tue, 2025-07-15 at 01:00 -0400, Robert McBroom via users wrote: Didn't get very far :~# mokutil --import /etc/pki/akmods/certs/public_key.der input password: input password again: Failed to enroll new keys Just in general, and WITHOUT (!) telling us

Re: Working with secureboot

On 7/15/25 1:48 AM, Todd Zullinger wrote: Robert McBroom via users wrote: Didn't get very far :~# mokutil --import /etc/pki/akmods/certs/public_key.der input password: input password again: Failed to enroll new keys What does `mokutil --sb-state` (with root privileges) report? It should say

Emergency mode - maybe OT

Folks,  during the night there was a power failure. When I powered up one of my systems it booted into emergency mode.  I'm not sure what to do to get it out of this.  Nothing I've tried works. Both root and home are mounted.  The default target is graphical.target. In the past making sure th

Re: Has gmail SMTP authentication changed recently?

On 2025-07-16 12:04, Frank Bures wrote: On 2025-07-16 11:51, Frank Bures wrote: Recently I have not been able to send root system mail from my Fedora 42 machine using Sendmail via gmail SMTP relay.  It worked reliably since I built this machine more than a year ago. Any attempt to send mail e

Re: Has gmail SMTP authentication changed recently?

> On 16 Jul 2025, at 17:04, Frank Bures wrote: > > If smtp.gmail.com resolves to an IPv6 address, > relaying works. If it resolves into IPv4 address, the above error ensues. You should always get both IPv4 and IPv6 addresses back. $ host smtp.gmail.com smtp.gmail.co

Re: Has gmail SMTP authentication changed recently?

On 2025-07-16 11:51, Frank Bures wrote: Recently I have not been able to send root system mail from my Fedora 42 machine using Sendmail via gmail SMTP relay.  It worked reliably since I built this machine more than a year ago. Any attempt to send mail either from cron or from CLI returns: rel

Has gmail SMTP authentication changed recently?

Recently I have not been able to send root system mail from my Fedora 42 machine using Sendmail via gmail SMTP relay. It worked reliably since I built this machine more than a year ago. Any attempt to send mail either from cron or from CLI returns: relay=smtp.gmail.com. [142.251.185.109], dsn

Re: Problem accessing lvm on nvme drive

> On 15 Jul 2025, at 05:51, Robert McBroom via users > wrote: > > ├─nvme0n1p5 > │ LVM2_mem LVM2 001 > v1gXoi-sKLO-fS0t-oKxo-en1J-7vOu-BH8Hal > └─nvme0n1p6 > LVM2_mem LVM2 001 > lQ45eA-ARYv-JiVX-JRjR-eyHl-NCXO-vkB2m0

Re: Problem accessing lvm on nvme drive

What does /etc/fstab look like? See if "vgchange -ay" activates fedora, if so then rebuild the initramfs. Use dracut to rebuild the initial ramdisk and see if that changes anything something like; dracut -f /boot/initramfs-$(uname -r).img $(uname -r) You would need to manually substitute the kern