sieve scripts
by Tim
Hi,
I've just gotten around to using sieve with Dovecot, and trying to work
out how scripts should be written has been a bit of a headache. There
doesn't seem to be coherent documentation, just various people's
cobbled together notes. So I'm wondering if anybody can see anything
glaringly wrong, or missing, that I haven't noticed in this script. It
seems to be working, but I don't know if that's by accident, or I've
done it right.
require ["fileinto"];
##### mail test 1 #####
#if header :contains "subject" "mailtest"
#{
# fileinto "tests";
# stop;
#}
##### Fedora list #####
if header :contains "List-Id" "users.lists.fedoraproject.org"
{
fileinto "lists.Fedora 2021";
stop;
}
###### Fedora 32 updates #####
if allof
(
header :contains "List-Id" "package-announce.lists.fedoraproject.org",
header :contains "subject" "Fedora 32 update"
)
{
fileinto "announcements.Fedora 32";
stop;
}
##### Fedora 33 updates #####
if allof
(
header :contains "List-Id" "package-announce.lists.fedoraproject.org",
header :contains "subject" "Fedora 33 update"
)
{
fileinto "announcements.Fedora 33";
stop;
}
--
uname -rsvp
Linux 5.11.15-100.fc32.x86_64 #1 SMP Fri Apr 16 14:19:43 UTC 2021 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
3 years, 1 month
ifcfg scripts?
by Tom Horsley
I just built a fedora 34 virtual machine. Networking clearly
works in it since I downloaded updates. But inside the virtual
machine there are no /etc/sysconfig/network-scripts/ifcfg-* files.
Has NetworkManager completely moved where it stores network
information now? I used to be able to copy all the ifcfg scripts
to get the network setup the same as the old fedora had.
Do I have to recreate my network setup with a bunch of nmcli commands
for fedora 34?
3 years, 1 month
Installation on externnal SSD
by Patrick Dupre
Hello,
I planed to install fedora on an external SSD.
Because the internal disk of the laptop is currently not visible by fedora
live, I planed to make the external SSD bootable.
I guess that it can be done via grub2.
Is there any thing special that I need to be warmed up?
Thanks
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire interdisciplinaire Carnot de Bourgogne
9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
Tel: +33 (0)380395988 | | Room# D114A
===========================================================================
3 years, 1 month
External SSD not recognized
by Patrick Dupre
Hello,
A Latitude 3410 BIOS does not recognize an external SSD
(in USAB-A or USB-C).
I see only one reason, it is not UEFI.
How can I fix this?
Thanks
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire interdisciplinaire Carnot de Bourgogne
9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
Tel: +33 (0)380395988 | | Room# D114A
===========================================================================
3 years, 1 month
Audio on F34 -- dead
by SternData
Zoom, Amarok, and other apps that were happy with PulseAudio on F33 are
soundless on F34. How do I either re-enable pulseaudio or get them to
work with the new audio system?
--
-- Steve
3 years, 1 month
UniFi Public Key Authentication
by Kevin Becker
I'm at a bit of a loss on this one so I thought I'd see if anyone has
any other suggestions.
My home network is all Ubiquity UniFi gear. I have a USG-3P router, a
few switches and one AP. There is a UniFi controller app that
centrally handles the configuration of the devices, including managing
SSH access. You enter a public key in the controller software and it
distributes it to all the devices automatically. I rarely actually SSH
into any of the devices so I don't know when this stopped working but
at some point it did work. I have the public keys for my desktop and
laptop, both running Fedora 33, in the controller but when I attempt to
SSH I am prompted for the UniFi admin password rather than my private
key password. I don't get any sort of cipher mismatch or any other
error, it just prompts for the account password.
Things I've tried:
* Verified permissions on ~/.ssh
* I can still SSH into many other hosts and they all accept my RSA key
just fine
* I removed and re-added the keys in the USG controller
* The fingerprint of the keys, as displaying in the controller
software, matches the fingerprint in seahorse (Passwords and Keys)
* Verified public key auth works to the UniFi gear from several other
devices I have, including a Macbook, iPhone, Raspberry Pi, and an
Ubuntu VM
* I built a fresh Fedora 33 virtual machine, added its public key, and
it has the same issue
* I verified the keys are actually being copied to the authorized_keys
on several different UniFi boxes
* Comparing keys to my MacBook, both are RSA and have a length of 3072
Essentially any Fedora box I've tried won't do public key auth to any
of the UniFi gear but they all authenticate fine everywhere else, and
every non-Fedora device I've tried can authenticate to the UniFi stuff.
The UniFi gear doesn't even all run the same OS, the USG runs EdgeOS
and has the keys in .ssh/authorized_keys but the switches have a
busybox shell and use dropbear for ssh with the keys at
/etc/dropbear/authorized_keys
I can just use the password for SSH, it's very rare that I actually
have any reason to do it at all, it's just the puzzle that is driving
me crazy.
3 years, 1 month
machine will not boot after moving root
by Michael Hennebry
I'm trying to move my root directory from sda5 to sda3.
After running grub2-install and grub2-mkconfig,
my machine will not boot.
I performed the changes using a F33 live DVD which also fails to boot.
After plugging in a USB-connected SD card with Centos 7 on it,
the F33 live DVD decided to boot.
It is what I am running now.
The complaint is UUID 2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a not found.
While running F33 live DVD I get
blkid | grep 2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a
/dev/loop1: LABEL="Anaconda" UUID="2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a"
BLOCK_SIZE="4096" TYPE="ext4"
/dev/mapper/live-rw: LABEL="Anaconda"
UUID="2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a" BLOCK_SIZE="4096" TYPE="ext4"
/dev/mapper/live-base: LABEL="Anaconda"
UUID="2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a" BLOCK_SIZE="4096" TYPE="ext4"
I backed up sda5 with rsync -auHAXUUx .
I copied from the backup with the same flags.
I edited the new etc/fstab to point at sda3,
actually LABEL=local3slash .
As root:
grupb2-install
grub2-mkconfig -o .../local3slash/boot/grub2/grub/cfg
Reboot failed and sent me to grub rewscue mode, about which I know nothing.
From .../local3slash/boot ,
grep -r -F 2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a .
./grub2/grub.cfg: search --no-floppy --fs-uuid --set=root
2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a
./grub2/grub.cfg: search --no-floppy --fs-uuid --set=root
2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a
./grub2/grub.cfg: search --no-floppy --fs-uuid --set=root
2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a
./grub2/grub.cfg: search --no-floppy --fs-uuid --set=root
2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a
./grub2/grub.cfg: search --no-floppy --fs-uuid --set=boot
2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a
./grub2/grub.cfg: search --no-floppy --fs-uuid --set=boot
2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a
./grub2/grub.cfg: set
kernelopts="root=UUID=2b82edc2-4eb2-44a0-8b5b-c71da0de9b3a ro "
What is going on and what can I do about it?
--
Michael hennebry(a)web.cs.ndsu.NoDak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
-- someeecards
3 years, 1 month
NOKEY warning from yum update
by Michael Hennebry
On F33, yum update gives me
...
(195/196): vim-common-8.2.2787-1.fc33.x86_64.rp 3.6 MB/s | 6.7 MB 00:01
(196/196): java-11-openjdk-headless-11.0.11.0.9 2.4 MB/s | 38 MB 00:15
[DRPM] libburn-1.5.4-1.fc33_1.5.4-2.fc33.x86_64.drpm: done
--------------------------------------------------------------------------------
Total 8.5 MB/s | 258 MB 00:30
Delta RPMs reduced 511.0 MB of updates to 510.8 MB (0.1% saved)
warning:
/var/cache/dnf/rpmfusion-nonfree-237dcb74312e3130/packages/rpmfusion-nonfree-appstream-data-33-2.fc33.noarch.rpm:
Header V3 RSA/SHA1 Signature, key ID 94843c65: NOKEY
RPM Fusion for Fedora 33 - Nonfree 1.6 MB/s | 1.7 kB 00:00
Importing GPG key 0x94843C65:
Userid : "RPM Fusion nonfree repository for Fedora (2020)
<rpmfusion-buildsys(a)lists.rpmfusion.org>"
Fingerprint: 79BD B88F 9BBF 7391 0FD4 095B 6A2A F961 9484 3C65
From : /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-fedora-33
Is this ok [y/N]:
From google, I know approximately what it means.
Also from google:
rpmfusion-nonfree-appstream-data - Appstream metadata for the RPM Fusion nonfree
repository
The message seems to be aganst the
repository rather than an individual package.
Huh?
Why would an update reach out to a previously unused repository?
For that matter I'm not all that sure it did.
I'm pretty sure I've used rpmfusion nonfreee before.
Why would it be balking now?
What do I do about it?
This problem predates the root change mentioned in another thread
(... won't boot after moving ...).
I'd suspected, clearly incorrectly, that it had something
to do with the fullness of my root partition.
Until I have a solution,
is there a way to tell yum to update everything
that does not involve rpmfusion non-free?
--
Michael hennebry(a)web.cs.ndsu.NoDak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
-- someeecards
3 years, 1 month
Announcements for manual configuration intervention?
by Matti Pulkkinen
Hello!
TL;DR is there a list where announcements are made regarding
configuration changes requiring manual intervention?
Today I noticed that the clock in my Fedora 33 workstation install was
about five minutes fast. Some examination revealed that none of the
sources chrony was using for NTP were working. There was, however, a
new configuration file, /etc/chrony.conf.rpmnew, which changed the
sources from specific IP addresses to a pool URL. It would have been
nice if there was some kind of notification that the current chrony
configuration is broken, and it can't be fixed automatically. Is there
a list, or some other method, by which I could be notified of these
sorts of things? Not for specific packages necessarily, but just in
general, even if it is high-traffic?
--
Terveisin / Regards,
Matti Pulkkinen
3 years, 1 month
dangling symlinks and upgrades (was "invisible application after
upgrade").
by home user
(context)
In the "invisible application after upgrade" thread, Ed did not know how
I did my upgrade to f33. I responded that I mostly followed the Fedora
upgrade instructions from here:
"https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/",
and listed the sequence of commands that I did. That included the steps
symlinks -r /usr | grep dangling
symlinks -r -d /usr
from the "Clean-Up Old Symlinks" section. Andras responded that
> This isn't necessarily a good idea, because those dangling symlinks
> may belong to their respective packages. If so, removing them will
> compromise the integrity of the package they belong to.
If Andras is correct, then the upgrade instructions need to be changed.
Based on past experience, when a bug is submitted against Fedora
documentation, the Fedora documentation team will want suggestions on
how the document should be worded.
(question 1)
What should the instructions say? Is there a better yet easy and safe
way to find and clean out dangling symlinks? Maybe more detail should
accompany "After you verify the list of broken symlinks"?
(question 2)
In a later post, Andras provided and example of a dangling symlink (in
the "hunspell" package) that should not be deleted. When I was a C/C++
programmer (a long long time ago, in a galaxy far far away), dangling
pointers (and memory leaks) were naughty; they can cause serious
problems. Isn't a dangling symlink a file system parallel to a dangling
pointer in a C/C++ program? What good, valid purpose is there for a
package to have a dangling symlink? Or maybe "hunspell" needs a little
clean-up?
3 years, 1 month
