I am in contract with a webhoster, having webserver, email and a few
other things.
But, there is no way to backup my emails stored on their imap
server.
I am in contract with a webhoster, having webserver, email and a few other things.
But, there is no way to backup my emails stored on their imap server. Meaning, when anything happens to that infrastructure (or they go broke) then all my emails are gone.
So, I'd like to mirror them via imapsync to a local instance of some
imap server, and then pack them together as a tgz archive.
Now I see, that there are several solutions out, see subject, and I
don't know which one fits best and what component is needed.
Does anyone have some experience here? Do I need an mta (exim for
instance) to just sync emails from external imap server to local?
Hi everyone
and happy new year!
I am in contract with a webhoster, having webserver, email and a few other things.
But, there is no way to backup my emails stored on their imap server. Meaning, when anything happens to that infrastructure (or they go broke) then all my emails are gone.
So, I'd like to mirror them via imapsync to a local instance of some imap server, and then pack them together as a tgz archive.
Now I see, that there are several solutions out, see subject, and I don't know which one fits best and what component is needed.
Dovecot is fairly easy to set up. I’ve not tried the other IMAP servers.
So, I'd like to mirror them via imapsync to a local instance of some
imap server, and then pack them together as a tgz archive.
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
Hi everyone
and happy new year!
I am in contract with a webhoster, having webserver, email and a few
other things.
But, there is no way to backup my emails stored on their imap server.
Meaning, when anything happens to that infrastructure (or they go
broke) then all my emails are gone.
So, I'd like to mirror them via imapsync to a local instance of some
imap server, and then pack them together as a tgz archive.
Now I see, that there are several solutions out, see subject, and I
don't know which one fits best and what component is needed.
Personally I'd ignore all those "solutions" as overkill and use movemail
from GNU Mailutils:
movemail -v imaps://no_reply@dipl-ing-kessler.de mh:///home/[user]/Mail
If you have special characters like '@' in the username, you may need to percent-encode them, eg. "%40".
https://www.mailutils.org/wiki/Fetching_Mail_with_Movemail
I use MH format for storing the mail, check what format/s your email
client understands and change "mh://" to suit.
https://www.mailutils.org/manual/html_node/Local-Mailboxes.html
I actually use POP to get mail using movemail myself, but it works with
IMAP too.
movemail -v imaps://no_reply@dipl-ing-kessler.de mh:///home/[user]/Mail
If you have special characters like '@' in the username, you may need to
percent-encode them, eg. "%40".
https://www.mailutils.org/wiki/Fetching_Mail_with_Movemail
I use MH format for storing the mail, check what format/s your email
client understands and change "mh://" to suit.
https://www.mailutils.org/manual/html_node/Local-Mailboxes.html
I actually use POP to get mail using movemail myself, but it works with
IMAP too.
Anyway, is there an option to automatically transmit content of more than
1 folder, i.e. inbox, draft and sent... at once?
On 2 Jan 2026 07:43:14 +1000 Computer Nerd Kev wrote:
movemail -v imaps://no_reply@dipl-ing-kessler.de
mh:///home/[user]/Mail
If you have special characters like '@' in the username, you may need
to percent-encode them, eg. "%40".
https://www.mailutils.org/wiki/Fetching_Mail_with_Movemail
On 2026-01-03, Markus Robert Kessler <no_reply@dipl-ing-kessler.de>
wrote:
I use MH format for storing the mail, check what format/s your email
client understands and change "mh://" to suit.
https://www.mailutils.org/manual/html_node/Local-Mailboxes.html
I actually use POP to get mail using movemail myself, but it works
with IMAP too.
Anyway, is there an option to automatically transmit content of more
than 1 folder, i.e. inbox, draft and sent... at once?
What is this "mh:" in a URL? Never saw that before. Is that part of the generic URL specification? Or is this a quirk of the "movemail" program?
I guess I need to get out "man movemail" or see what's in
/usr/share/docs ...
On 01.01.2026 20:19 Uhr Markus Robert Kessler wrote:
So, I'd like to mirror them via imapsync to a local instance of some
imap server, and then pack them together as a tgz archive.
I use Cyrus and like it.
It saves the mail as text files. The metadata information (folder permissions, read status etc.) is saved in local databases.
On 2 Jan 2026 07:43:14 +1000 Computer Nerd Kev wrote:
movemail -v imaps://no_reply@dipl-ing-kessler.de mh:///home/[user]/Mail
If you have special characters like '@' in the username, you may need to >>> percent-encode them, eg. "%40".
https://www.mailutils.org/wiki/Fetching_Mail_with_Movemail
On 2026-01-03, Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
I use MH format for storing the mail, check what format/s your email
client understands and change "mh://" to suit.
https://www.mailutils.org/manual/html_node/Local-Mailboxes.html
I actually use POP to get mail using movemail myself, but it works with
IMAP too.
Anyway, is there an option to automatically transmit content of more than >> 1 folder, i.e. inbox, draft and sent... at once?
What is this "mh:" in a URL? Never saw that before. Is that part of
the generic URL specification? Or is this a quirk of the "movemail"
program?
I guess I need to get out "man movemail" or see what's in
/usr/share/docs ...
On 2026-01-03, Lars Poulsen <lars@beagle-ears.com> wrote:
On 2 Jan 2026 07:43:14 +1000 Computer Nerd Kev wrote:
movemail -v imaps://no_reply@dipl-ing-kessler.de
mh:///home/[user]/Mail
If you have special characters like '@' in the username, you may need
to percent-encode them, eg. "%40".
https://www.mailutils.org/wiki/Fetching_Mail_with_Movemail
On 2026-01-03, Markus Robert Kessler <no_reply@dipl-ing-kessler.de>
wrote:
I use MH format for storing the mail, check what format/s your email
client understands and change "mh://" to suit.
https://www.mailutils.org/manual/html_node/Local-Mailboxes.html
I actually use POP to get mail using movemail myself, but it works
with IMAP too.
Anyway, is there an option to automatically transmit content of more
than 1 folder, i.e. inbox, draft and sent... at once?
What is this "mh:" in a URL? Never saw that before. Is that part of the
generic URL specification? Or is this a quirk of the "movemail"
program?
I guess I need to get out "man movemail" or see what's in
/usr/share/docs ...
Apparently, GNU-Mailutils is not in the Fedora distribution. There are
RPMs for it in SuSE, but I am reluctant to mix "foreign"
RPMs into my Fedora; I have seen that greate small messes in
dependencies. And I really don't like to compile from sources.
movemail seems to work, thanks!
Well, in the document mh was misspelled as
'mh://Mail' instead of
'mh:///Mail', so it took a while until I got it to work.
Anyway, is there an option to automatically transmit content of more than
1 folder, i.e. inbox, draft and sent... at once?
Apparently, GNU-Mailutils is not in the Fedora distribution. There
are RPMs for it in SuSE, but I am reluctant to mix "foreign" RPMs
into my Fedora; I have seen that greate small messes in
dependencies. And I really don't like to compile from sources.
On Sat, 3 Jan 2026 18:40:16 -0000 (UTC) Lars Poulsen wrote:
On 2026-01-03, Lars Poulsen <lars@beagle-ears.com> wrote:
On 2 Jan 2026 07:43:14 +1000 Computer Nerd Kev wrote:
movemail -v imaps://no_reply@dipl-ing-kessler.de
mh:///home/[user]/Mail
If you have special characters like '@' in the username, you may need >>>>> to percent-encode them, eg. "%40".
https://www.mailutils.org/wiki/Fetching_Mail_with_Movemail
On 2026-01-03, Markus Robert Kessler <no_reply@dipl-ing-kessler.de>
wrote:
I use MH format for storing the mail, check what format/s your email >>>>> client understands and change "mh://" to suit.
https://www.mailutils.org/manual/html_node/Local-Mailboxes.html
I actually use POP to get mail using movemail myself, but it works
with IMAP too.
Anyway, is there an option to automatically transmit content of more
than 1 folder, i.e. inbox, draft and sent... at once?
What is this "mh:" in a URL? Never saw that before. Is that part of the
generic URL specification? Or is this a quirk of the "movemail"
program?
I guess I need to get out "man movemail" or see what's in
/usr/share/docs ...
Apparently, GNU-Mailutils is not in the Fedora distribution. There are
RPMs for it in SuSE, but I am reluctant to mix "foreign"
RPMs into my Fedora; I have seen that greate small messes in
dependencies. And I really don't like to compile from sources.
Besides this, it looks like movemail can only transmit 'Inbox' but no
other folders?
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
movemail seems to work, thanks!
Well, in the document mh was misspelled as
'mh://Mail' instead of
'mh:///Mail', so it took a while until I got it to work.
Anyway, is there an option to automatically transmit content of more than
1 folder, i.e. inbox, draft and sent... at once?
I think you have to run a separate movemail command for each
folder (and pointing to each destination folder). But you could put
them in a script and have it add the password or set it in
~/.mu-tickets so you don't have to enter it manually multiple
times.
On 03/01/2026 21:56, Computer Nerd Kev wrote:
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:..and use & to background each folder transfer to spawn many shells to
movemail seems to work, thanks!
Well, in the document mh was misspelled as
'mh://Mail' instead of
'mh:///Mail', so it took a while until I got it to work.
Anyway, is there an option to automatically transmit content of more than >>> 1 folder, i.e. inbox, draft and sent... at once?
I think you have to run a separate movemail command for each
folder (and pointing to each destination folder). But you could put
them in a script and have it add the password or set it in
~/.mu-tickets so you don't have to enter it manually multiple
times.
move it sorta concurrently...
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
On Sat, 3 Jan 2026 18:40:16 -0000 (UTC) Lars Poulsen wrote:
On 2026-01-03, Lars Poulsen <lars@beagle-ears.com> wrote:
On 2 Jan 2026 07:43:14 +1000 Computer Nerd Kev wrote:
movemail -v imaps://no_reply@dipl-ing-kessler.de
mh:///home/[user]/Mail
If you have special characters like '@' in the username, you may
need to percent-encode them, eg. "%40".
https://www.mailutils.org/wiki/Fetching_Mail_with_Movemail
On 2026-01-03, Markus Robert Kessler <no_reply@dipl-ing-kessler.de>
wrote:
I use MH format for storing the mail, check what format/s your
email client understands and change "mh://" to suit.
https://www.mailutils.org/manual/html_node/Local-Mailboxes.html
I actually use POP to get mail using movemail myself, but it works >>>>>> with IMAP too.
Anyway, is there an option to automatically transmit content of more >>>>> than 1 folder, i.e. inbox, draft and sent... at once?
What is this "mh:" in a URL? Never saw that before. Is that part of
the generic URL specification? Or is this a quirk of the "movemail"
program?
I guess I need to get out "man movemail" or see what's in
/usr/share/docs ...
Apparently, GNU-Mailutils is not in the Fedora distribution. There are
RPMs for it in SuSE, but I am reluctant to mix "foreign"
RPMs into my Fedora; I have seen that greate small messes in
dependencies. And I really don't like to compile from sources.
Besides this, it looks like movemail can only transmit 'Inbox' but no
other folders?
No, just add the folder to the URL, such as:
movemail imaps://foo@example.com/draft mh:///tmp/Mail/draft
I just tested that and it works for me. I can't see any way to download
all the folders with one command like you asked before though.
By the way, if you want to keep the messages on the server, you probably
want to use the "--sync=uidnext" option:
https://www.mailutils.org/manual/html_node/Sync.html
On 4 Jan 2026 08:05:59 +1000 Computer Nerd Kev wrote:
movemail imaps://foo@example.com/draft mh:///tmp/Mail/draft
I just tested that and it works for me. I can't see any way to download
all the folders with one command like you asked before though.
By the way, if you want to keep the messages on the server, you probably
want to use the "--sync=uidnext" option:
https://www.mailutils.org/manual/html_node/Sync.html
Yes, this way, download by foldername works, thanks!
When wanting the emails to remain on the server, flag '-p' (keep messages) can be used. What does "--sync=uidnext" differently?
B.t.w., just trying to download folders with special characters in them, like "Entwurfe" (drafts). I did not make it yet to get this encoded (for instance "u" in html: ü)
On Fri, 2 Jan 2026 21:10:32 +0100 Marco Moock wrote:
On 01.01.2026 20:19 Uhr Markus Robert Kessler wrote:
So, I'd like to mirror them via imapsync to a local instance of
some imap server, and then pack them together as a tgz archive.
I use Cyrus and like it.
It saves the mail as text files. The metadata information (folder permissions, read status etc.) is saved in local databases.
Is there a sample configuration out, to not having to start from
scratch by "trial and error"?
I use Cyrus and like it.
On Sat, 3 Jan 2026 18:40:16 -0000 (UTC), Lars Poulsen wrote:
Apparently, GNU-Mailutils is not in the Fedora distribution. There are
RPMs for it in SuSE, but I am reluctant to mix "foreign" RPMs into my
Fedora; I have seen that greate small messes in dependencies. And I
really don't like to compile from sources.
Maybe you should switch to a more comprehensive distro?
<https://packages.debian.org/trixie/mailutils>
And what’s with this reluctance to compile from source, anyway? It’s
part of the bread and butter of running any Linux distro.
On Sat, 3 Jan 2026 21:57:23 -0000 (UTC) Lawrence D’Oliveiro wrote:
And what’s with this reluctance to compile from source, anyway?
It’s part of the bread and butter of running any Linux distro.
Yes, debian has it and openSuSE has it. And I can confirm that
compiling from scratch is not as easy as it looked like. I tried to
create a package for Mageia, based on the original tarball, but
there are plenty of dependencies not visible during configure/make/makeinstall.
I use Cyrus and like it.
It saves the mail as text files. The metadata information (folder
permissions, read status etc.) is saved in local databases.
Is there a sample configuration out, to not having to start from
scratch by "trial and error"?
The default config of Debian is reasonable. If you want mine, let me
know.
On Sat, 3 Jan 2026 21:57:23 -0000 (UTC) Lawrence D'Oliveiro wrote:
<https://packages.debian.org/trixie/mailutils>
And what's with this reluctance to compile from source, anyway? It's
part of the bread and butter of running any Linux distro.
Yes, debian has it and openSuSE has it.
And I can confirm that compiling from scratch is not as easy as it looked like. I tried to create a package for Mageia, based on the original
tarball, but there are plenty of dependencies not visible during configure/make/makeinstall. It compiled and built, but the result was not funtional. Creating a new rpm out of that failed as well.
Well I built GNU Mailutils 3.21 from source with all the functionality
you require and noted the following dependencies:
readline-dev, libunistring-dev, gnutls38-dev, tcp_wrappers-dev,
libltdl, libtool-dev, libgsasl-dev
At least libgsasl-dev probably isn't needed for your use since I only
added that to enable SMTP authentication using putmail. IMAP
authentication using movemail was working before that. Some others might
be surplus to requirements too.
On 01.01.2026 20:19 Uhr Markus Robert Kessler wrote:
So, I'd like to mirror them via imapsync to a local instance of some
imap server, and then pack them together as a tgz archive.
I use Cyrus and like it.
It saves the mail as text files. The metadata information (folder permissions, read status etc.) is saved in local databases.
I am asking this because I once got into big trouble when I had to
move multiple mysql databases to a new machine with new OS and new
version of mysqld. - Nothing worked and I had to use mysql-dump to
export the data as text-dump on the old system and import them into
the new one. After that, the permission system also had to be set up
from scratch because of different data format...
Well, these are the BUILD dependencies - are there RUNTIME requirements
also?
On 12/01/2026 06:36, Markus Robert Kessler wrote:
Well, these are the BUILD dependencies - are there RUNTIME requirements
also?
Generally (but I don't promise that it always works) if you have the dev
package installed in order to meet the build requirements you not need anything more at runtime.
There are non-dev packages that meet *only* the runtime requirements for people who don't need to meet the build requirements, but if you have
the dev packages you don't need those as well.
Meaning, do you let "make install" write directly to the filesystem
...
On 12 Jan 2026 07:20:47 +1000 Computer Nerd Kev wrote:
Well I built GNU Mailutils 3.21 from source with all the functionality
you require and noted the following dependencies:
readline-dev, libunistring-dev, gnutls38-dev, tcp_wrappers-dev,
libltdl, libtool-dev, libgsasl-dev
At least libgsasl-dev probably isn't needed for your use since I only
added that to enable SMTP authentication using putmail. IMAP
authentication using movemail was working before that. Some others might
be surplus to requirements too.
Interesting, thank you!
Well, these are the BUILD dependencies - are there RUNTIME requirements also?
On Mon, 12 Jan 2026 12:45:29 +0000 Daniel James wrote:
On 12/01/2026 06:36, Markus Robert Kessler wrote:
Well, these are the BUILD dependencies - are there RUNTIME requirements
also?
Generally (but I don't promise that it always works) if you have the dev
package installed in order to meet the build requirements you not need
anything more at runtime.
There are non-dev packages that meet *only* the runtime requirements for
people who don't need to meet the build requirements, but if you have
the dev packages you don't need those as well.
B.t.w.,
how do you install all the files retrieved from compiling the tarball from scratch, if you want to avoid building a deb or rpm?
Meaning, do you let "make install" write directly to the filesystem, or do you pack all that files in one tar.gz and then use "alien" to transform it into a deb or rpm?
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
On 12 Jan 2026 07:20:47 +1000 Computer Nerd Kev wrote:
Well I built GNU Mailutils 3.21 from source with all the functionality
you require and noted the following dependencies:
readline-dev, libunistring-dev, gnutls38-dev, tcp_wrappers-dev,
libltdl, libtool-dev, libgsasl-dev
At least libgsasl-dev probably isn't needed for your use since I only
added that to enable SMTP authentication using putmail. IMAP
authentication using movemail was working before that. Some others
might be surplus to requirements too.
Interesting, thank you!
Well, these are the BUILD dependencies - are there RUNTIME requirements
also?
Sure, all of those with "-dev" removed, except libtool. You can probably
use whatever version of the gnutls package for your distro is the
latest.
readline, libunistring, gnutls, tcp_wrappers, libltdl, libgsasl
Although you can build it without some of those, such as libgsasl as mentioned before. Of course exact package names will differ between
distros, especially with the "lib" prefixes.
"ldd `which movemail`" is a quick way to see all the libraries used by
the executable, however it will show additional libraries used by the
direct dependenies, without distinction. Another way is using "readelf
-d `which movemail` | grep NEEDED", which just gives you the immediate dependencies, but then in this case you get a bunch of "libmu_*"
Mailutils libraries which then also need to be checked with "ldd" or "readelf", and that gets confusing. Also those tools won't show any
libraries or executables that are loaded after the program has started.
Then you have to work out which packages the libraries belong to, for
which the method is specific to your distro or package format.
Anyway in this case you can just go from the list I gave you above.
Richard Kettlewell wrote:
Dovecot is fairly easy to set up. I’ve not tried the other IMAP
servers.
I would echo that.
On 13 Jan 2026 08:01:52 +1000 Computer Nerd Kev wrote:[snip]
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
On 12 Jan 2026 07:20:47 +1000 Computer Nerd Kev wrote:
Well I built GNU Mailutils 3.21 from source with all the functionality >>>> you require and noted the following dependencies:
readline-dev, libunistring-dev, gnutls38-dev, tcp_wrappers-dev,
libltdl, libtool-dev, libgsasl-dev
Hi, regarding Mageia Linux I am working on, I get
needed: available in distro:
readline lib64readline-devel
libunistring lib64unistring-devel
gnutls lib64gnutls-devel
tcp_wrappers tcp_wrappers
(no devel, executables in /usr/sbin:
safe_finger; tcpd; tcpdchk; tcpdmatch; try-from)
libltdl lib64ltdl-devel
libgsasl lib64gsasl-devel
So, except "tcp_wrappers", the package seems to be builable?
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:statement.html
On 13 Jan 2026 08:01:52 +1000 Computer Nerd Kev wrote:[snip]
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
On 12 Jan 2026 07:20:47 +1000 Computer Nerd Kev wrote:
Well I built GNU Mailutils 3.21 from source with all the
functionality you require and noted the following dependencies:
readline-dev, libunistring-dev, gnutls38-dev, tcp_wrappers-dev,
libltdl, libtool-dev, libgsasl-dev
Hi, regarding Mageia Linux I am working on, I get
needed: available in distro:
readline lib64readline-devel libunistring
lib64unistring-devel gnutls lib64gnutls-devel
tcp_wrappers tcp_wrappers
(no devel, executables in /usr/sbin: safe_finger;
tcpd; tcpdchk; tcpdmatch; try-from)
libltdl lib64ltdl-devel libgsasl
lib64gsasl-devel
So, except "tcp_wrappers", the package seems to be builable?
Yep, and tcp_wrappers looks to be optional, so you can probably ignore
that:
"The tcp-wrappers statements provides an alternative way to control
accesses to the resources served by GNU Mailutils. This statement is
enabled if Mailutils is compiled with TCP wrappers library libwrap." https://www.mailutils.org/manual/html_node/tcp_002dwrappers-
On 16 Jan 2026 08:19:25 +1000 Computer Nerd Kev wrote:
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:statement.html
So, except "tcp_wrappers", the package seems to be builable?
Yep, and tcp_wrappers looks to be optional, so you can probably ignore
that:
"The tcp-wrappers statements provides an alternative way to control
accesses to the resources served by GNU Mailutils. This statement is
enabled if Mailutils is compiled with TCP wrappers library libwrap."
https://www.mailutils.org/manual/html_node/tcp_002dwrappers-
OK, thanks. I see that
lib64wrap-devel and libwrap-devel
are there. Do you think it is sufficient to just install one of them as dependency?
And I can confirm that compiling from scratch is not as easy as it looked like. I tried to create a package for Mageia, based on the original
tarball, but there are plenty of dependencies not visible during configure/make/makeinstall. It compiled and built, but the result was not funtional. Creating a new rpm out of that failed as well.
When I try to log into Dovecot, it asks for password (based on /etc/shadowsearch for how to use sasl with pam and dovecot, I can't remember the
as it looks like), but then Dovecot asks for some imap password:
[502 root@rpi-inst ~]# cyradm -u cyrus localhost
Password:
IMAP Password:
Login failed: authentication failure at /usr/lib/arm-linux- gnueabihf/perl5/5.32/Cyrus/IMAP/Admin.pm line 134.
cyradm: cannot authenticate to server as cyrus
Can anyone please give some advice how to get a mailbox set up, so that I
can test with?
When I try to log into Dovecot, it asks for password (based on
/etc/shadow as it looks like), but then Dovecot asks for some imap
password:
[502 root@rpi-inst ~]# cyradm -u cyrus localhost
Password:
IMAP Password:
Login failed: authentication failure at /usr/lib/arm-linux-gnueabihf/perl5/5.32/Cyrus/IMAP/Admin.pm line 134.
cyradm: cannot authenticate to server as cyrus
I try to set up a simple Dovecot instance on a raspberry where I can
create one mailbox and use this for testing purposes with GNU Mailutils
and ImapSync.
On Sat, 17 Jan 2026 13:51:22 -0000 (UTC), Markus Robert Kessler wrote:Admin.pm
When I try to log into Dovecot, it asks for password (based on
/etc/shadow as it looks like), but then Dovecot asks for some imap
password:
[502 root@rpi-inst ~]# cyradm -u cyrus localhost Password:
IMAP Password:
Login failed: authentication failure at
/usr/lib/arm-linux-gnueabihf/perl5/5.32/Cyrus/IMAP/
line 134.
cyradm: cannot authenticate to server as cyrus
Seems to be saying it’s trying to authenticate as user “cyrus”. Is this valid?
Another thing to check is, is it trying to connect via the imap port
(143) or imaps (993)?
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
I try to set up a simple Dovecot instance on a raspberry where I can
create one mailbox and use this for testing purposes with GNU Mailutils
and ImapSync.
FWIW GNU Mailutils comes with an IMAP server too, which I use for about
the same purpose as what you seem to be doing. It seemed like a good
idea but in practice I rarely use it and read the mailbox movemail
writes to directly with an email client instead.
On Sat, 17 Jan 2026 13:51:22 -0000 (UTC), Markus Robert Kessler wrote:Admin.pm
When I try to log into Dovecot, it asks for password (based on
/etc/shadow as it looks like), but then Dovecot asks for some imap
password:
[502 root@rpi-inst ~]# cyradm -u cyrus localhost Password:
IMAP Password:
Login failed: authentication failure at
/usr/lib/arm-linux-gnueabihf/perl5/5.32/Cyrus/IMAP/
line 134.
cyradm: cannot authenticate to server as cyrus
Seems to be saying it’s trying to authenticate as user “cyrus”. Is this valid?
Another thing to check is, is it trying to connect via the imap port
(143) or imaps (993)?
At the moment I am stuck because any attempt to log in ends by returning
to commandline instantly:
[592 root@rpi-inst /tmp]# doveadm auth login dov
Password:
passdb: dov auth succeeded
extra fields:
user=dov
userdb extra fields:
dov
system_groups_user=dov
uid=1010
gid=1010
home=/home/dov
auth_mech=PLAIN
[593 root@rpi-inst /tmp]#
No chance to create a mailbox here.
On 18 Jan 2026 07:21:23 +1000 Computer Nerd Kev wrote:
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
I try to set up a simple Dovecot instance on a raspberry where I can
create one mailbox and use this for testing purposes with GNU Mailutils
and ImapSync.
FWIW GNU Mailutils comes with an IMAP server too, which I use for about
the same purpose as what you seem to be doing. It seemed like a good
idea but in practice I rarely use it and read the mailbox movemail
writes to directly with an email client instead.
[..]
Thanks! Yes, I see imapd is also created when installing from GNU
Mailutils tarball.
Confusingly, Raspbian has each a separate package for
imapd, pop3, etc. Maybe, they consider this to be easier to just install what's needed, rather than do a 'systemctl disable ...' for all unwanted services.
B.t.w., does GNU Mailutils imapd need mysql to store email details, or is there everything stored in plain text?
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
On 16 Jan 2026 08:19:25 +1000 Computer Nerd Kev wrote:
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:statement.html
So, except "tcp_wrappers", the package seems to be builable?
Yep, and tcp_wrappers looks to be optional, so you can probably ignore
that:
"The tcp-wrappers statements provides an alternative way to control
accesses to the resources served by GNU Mailutils. This statement is
enabled if Mailutils is compiled with TCP wrappers library libwrap."
https://www.mailutils.org/manual/html_node/tcp_002dwrappers-
OK, thanks. I see that lib64wrap-devel and libwrap-devel are there. Do
you think it is sufficient to just install one of them as dependency?
Probably the lib64 one. The configure script shows the features enabled
like I posted before. So if it's found tcp_wrappers/libwrap then you'll
get the same as me:
"Use TCP wrappers .............. yes"
If not:
"Use TCP wrappers .............. no"
Either way I expect it'll do everything you need, since I think it's
just for the IMAP and POP servers that are also part of Mailutils.
Wrappers (64bit) is ok, and all services like pop and imap are building. Somehow strange, that it complains about 'C++:no', though gcc is there.
On 16 Jan 2026 11:57:08 +1000 Computer Nerd Kev wrote:
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
On 16 Jan 2026 08:19:25 +1000 Computer Nerd Kev wrote:
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:statement.html
So, except "tcp_wrappers", the package seems to be builable?
Yep, and tcp_wrappers looks to be optional, so you can probably
ignore that:
"The tcp-wrappers statements provides an alternative way to control
accesses to the resources served by GNU Mailutils. This statement is
enabled if Mailutils is compiled with TCP wrappers library libwrap."
https://www.mailutils.org/manual/html_node/tcp_002dwrappers-
OK, thanks. I see that lib64wrap-devel and libwrap-devel are there. Do
you think it is sufficient to just install one of them as dependency?
Probably the lib64 one. The configure script shows the features enabled
like I posted before. So if it's found tcp_wrappers/libwrap then you'll
get the same as me:
"Use TCP wrappers .............. yes"
If not:
"Use TCP wrappers .............. no"
Either way I expect it'll do everything you need, since I think it's
just for the IMAP and POP servers that are also part of Mailutils.
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> writes:
Wrappers (64bit) is ok, and all services like pop and imap are
building.
Somehow strange, that it complains about 'C++:no', though gcc is there.
You have probably installed gcc but not g++.
On Sun, 18 Jan 2026 16:06:48 +0000 Richard Kettlewell wrote:
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> writes:
Wrappers (64bit) is ok, and all services like pop and imap are
building.
Somehow strange, that it complains about 'C++:no', though gcc is there.
You have probably installed gcc but not g++.
On Raspbian there is a package 'g++' to cover the c++ things.
While, on Mageia I cannot find such package. Instead there is 'gcc-c++', which claims 'This package adds C++ support to the GNU C compiler'.
I have installed 'gcc-c++', so, maybe GNU-mailutil's './configure' is
being confused here?
after a 'make install' to some DESTDIR, I took the created 'usr' dir, chown-ed everything to root:root and verified that the rights are correct.
Then I created a tar.gz archive out of this 'usr' dir.
From this I took alien to convert to rpm:
alien --target=`arch` -r gnu-mailutils-3.21.tar.gz
All worked, but when trying to install the rpm I get
[1040 root@mga9x64-lb1 /tmp]# rpm -i gnu-mailutils-3.21-2.x86_64.rpm
error: Failed dependencies:
devel(libgnutls(64bit)) is needed by gnu-mailutils-3.21-2.x86_64
devel(libgsasl(64bit)) is needed by gnu-mailutils-3.21-2.x86_64
devel(libltdl(64bit)) is needed by gnu-mailutils-3.21-2.x86_64
libgsasl.so.7()(64bit) is needed by gnu-mailutils-3.21-2.x86_64
libgsasl.so.7(LIBGSASL_1.1)(64bit) is needed by gnu- mailutils-3.21-2.x86_64
This is strange because './configure' said
From this I took alien to convert to rpm:
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
after a 'make install' to some DESTDIR, I took the created 'usr' dir,
chown-ed everything to root:root and verified that the rights are
correct.
Then I created a tar.gz archive out of this 'usr' dir.
From this I took alien to convert to rpm:
alien --target=`arch` -r gnu-mailutils-3.21.tar.gz
All worked, but when trying to install the rpm I get
[1040 root@mga9x64-lb1 /tmp]# rpm -i gnu-mailutils-3.21-2.x86_64.rpm
error: Failed dependencies:
devel(libgnutls(64bit)) is needed by
gnu-mailutils-3.21-2.x86_64 devel(libgsasl(64bit)) is needed by
gnu-mailutils-3.21-2.x86_64 devel(libltdl(64bit)) is needed by
gnu-mailutils-3.21-2.x86_64 libgsasl.so.7()(64bit) is needed by
gnu-mailutils-3.21-2.x86_64 libgsasl.so.7(LIBGSASL_1.1)(64bit)
is needed by gnu-
mailutils-3.21-2.x86_64
x86_64? This is in the Raspberry Pi Group. Did you pick the wrong
newsgroup to discuss this or are you trying to complile on a PC but run Mailutils on a RPi? That's possible, but difficult, and for this you'd
be much better compiling Mailutils on the RPi instead.
This is strange because './configure' said
The configure script worked if you got the mailutils binaries built,
which it sounds like you did (otherwise DESTDIR will be empty). I've
never used "alien" and don't know how it goes about making packages, but
it looks like something must be going wrong there. If you're trying to install to RPi (ARM) a package built for x86_64, then that's definitely what's going wrong.
On debian for intel, there is version 3.20 - but it is not complete.
imap4d and pop3d are missing and other stuff. Just left away.
On 19 Jan 2026 07:23:39 +1000 Computer Nerd Kev wrote:
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
[1040 root@mga9x64-lb1 /tmp]# rpm -i gnu-mailutils-3.21-2.x86_64.rpm
error: Failed dependencies:
devel(libgnutls(64bit)) is needed by
gnu-mailutils-3.21-2.x86_64 devel(libgsasl(64bit)) is needed by
gnu-mailutils-3.21-2.x86_64 devel(libltdl(64bit)) is needed by
gnu-mailutils-3.21-2.x86_64 libgsasl.so.7()(64bit) is needed by
gnu-mailutils-3.21-2.x86_64 libgsasl.so.7(LIBGSASL_1.1)(64bit)
is needed by gnu-
mailutils-3.21-2.x86_64
x86_64? This is in the Raspberry Pi Group. Did you pick the wrong
newsgroup to discuss this or are you trying to complile on a PC but run
Mailutils on a RPi? That's possible, but difficult, and for this you'd
be much better compiling Mailutils on the RPi instead.
This is strange because './configure' said
The configure script worked if you got the mailutils binaries built,
which it sounds like you did (otherwise DESTDIR will be empty). I've
never used "alien" and don't know how it goes about making packages, but
it looks like something must be going wrong there. If you're trying to
install to RPi (ARM) a package built for x86_64, then that's definitely
what's going wrong.
Hello, thanks! And, no, I did not click onto the wrong group.
Instead, the desperate situation is like that:
On latest raspbian, debian for ARM, there is only an ancient version 3.10. Good to play with, but that's all.
On debian for intel, there is version 3.20 - but it is not complete.
imap4d and pop3d are missing and other stuff. Just left away.
On Redhat / Mageia for intel, which I am also running, there is even no
such package like GNU mailutils at all.
Besides this:
Looking at the 'Failed dependencies' message above, this looks as if the devel packages have to be linked statically, otherwise movemail and others cannot access them and are asking for them again.
On 19 Jan 2026 07:23:39 +1000 Computer Nerd Kev wrote:[...]
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
after a 'make install' to some DESTDIR, I took the created 'usr' dir,
chown-ed everything to root:root and verified that the rights are
correct.
Then I created a tar.gz archive out of this 'usr' dir.
From this I took alien to convert to rpm:
alien --target=`arch` -r gnu-mailutils-3.21.tar.gz
All worked, but when trying to install the rpm I get
[1040 root@mga9x64-lb1 /tmp]# rpm -i gnu-mailutils-3.21-2.x86_64.rpm
error: Failed dependencies:
devel(libgnutls(64bit)) is needed by
gnu-mailutils-3.21-2.x86_64 devel(libgsasl(64bit)) is needed by
gnu-mailutils-3.21-2.x86_64 devel(libltdl(64bit)) is needed by
gnu-mailutils-3.21-2.x86_64 libgsasl.so.7()(64bit) is needed by
gnu-mailutils-3.21-2.x86_64 libgsasl.so.7(LIBGSASL_1.1)(64bit)
is needed by gnu-
mailutils-3.21-2.x86_64
Looking at the 'Failed dependencies' message above, this looks as if
the devel packages have to be linked statically, otherwise movemail
and others cannot access them and are asking for them again. Do you
dispose this to be so?
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> writes:
On 19 Jan 2026 07:23:39 +1000 Computer Nerd Kev wrote:[...]
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
after a 'make install' to some DESTDIR, I took the created 'usr' dir,
chown-ed everything to root:root and verified that the rights are
correct.
Then I created a tar.gz archive out of this 'usr' dir.
From this I took alien to convert to rpm:
alien --target=`arch` -r gnu-mailutils-3.21.tar.gz
All worked, but when trying to install the rpm I get
[1040 root@mga9x64-lb1 /tmp]# rpm -i gnu-mailutils-3.21-2.x86_64.rpm
error: Failed dependencies:
devel(libgnutls(64bit)) is needed by
gnu-mailutils-3.21-2.x86_64 devel(libgsasl(64bit)) is needed
by gnu-mailutils-3.21-2.x86_64 devel(libltdl(64bit)) is
needed by gnu-mailutils-3.21-2.x86_64 libgsasl.so.7()(64bit)
is needed by gnu-mailutils-3.21-2.x86_64
libgsasl.so.7(LIBGSASL_1.1)(64bit) is needed by gnu-
mailutils-3.21-2.x86_64
Looking at the 'Failed dependencies' message above, this looks as if
the devel packages have to be linked statically, otherwise movemail and
others cannot access them and are asking for them again. Do you
dispose this to be so?
I don’t know RPM well but for most packaging systems, if it says you’re missing a dependency then it just means you need to install the package containing that dependency.
Certainly within Debian the norm is for executables to be dynamically
linked and the package containing then to have a dependency on the
runtime packages for each shared library. Static executables are rare at best.
In your case, I thought you were trying to do a local build and install.
So I don’t see why RPM is involved at all.
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
On 19 Jan 2026 07:23:39 +1000 Computer Nerd Kev wrote:
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
[1040 root@mga9x64-lb1 /tmp]# rpm -i gnu-mailutils-3.21-2.x86_64.rpm
error: Failed dependencies:
devel(libgnutls(64bit)) is needed by
gnu-mailutils-3.21-2.x86_64 devel(libgsasl(64bit)) is needed
by gnu-mailutils-3.21-2.x86_64 devel(libltdl(64bit)) is
needed by gnu-mailutils-3.21-2.x86_64 libgsasl.so.7()(64bit)
is needed by gnu-mailutils-3.21-2.x86_64
libgsasl.so.7(LIBGSASL_1.1)(64bit) is needed by gnu-
mailutils-3.21-2.x86_64
x86_64? This is in the Raspberry Pi Group. Did you pick the wrong
newsgroup to discuss this or are you trying to complile on a PC but
run Mailutils on a RPi? That's possible, but difficult, and for this
you'd be much better compiling Mailutils on the RPi instead.
This is strange because './configure' said
The configure script worked if you got the mailutils binaries built,
which it sounds like you did (otherwise DESTDIR will be empty). I've
never used "alien" and don't know how it goes about making packages,
but it looks like something must be going wrong there. If you're
trying to install to RPi (ARM) a package built for x86_64, then that's
definitely what's going wrong.
Hello, thanks! And, no, I did not click onto the wrong group.
Instead, the desperate situation is like that:
On latest raspbian, debian for ARM, there is only an ancient version
3.10.
Good to play with, but that's all.
On debian for intel, there is version 3.20 - but it is not complete.
imap4d and pop3d are missing and other stuff. Just left away.
On Redhat / Mageia for intel, which I am also running, there is even no
such package like GNU mailutils at all.
Just note that nothing you do "on intel" will just work on ARM. If you
want Mailutils on both ARM and "intel", you need to build it twice. If
you just want it on one ARM system, then repeat everything on the ARM
system and just do "sudo make install" without the DESTDIR and package
stuff which only matters if you want to install easily to other RPis
(and even then I'd personally just make a tarball and unpack that to "/" after installing the dependencies manually, rather than making an RPM package).
Besides this:
Looking at the 'Failed dependencies' message above, this looks as if
the devel packages have to be linked statically, otherwise movemail and
others cannot access them and are asking for them again.
Static linking should avoid any dependency problem when it's built on
ARM. Building on x86_64 "intel", nothing will work on ARM unless you
install and use a cross-compiling environment. But don't do that unless you're desperate for a challenge, just build on ARM in the first place,
since any RPi is capable of compiling Mailutils.
If you want the same build to run on Debian and "Redhat / Mageia", then static linking can achieve that more reliably. Note that it will prevent security updates to gnutls being applied when running Mailutils with encrypted connections, until you rebuild the static binary. You should
be able to use the Debian x86_64 Mailutils packages at least, so you
probably don't need to try running the Mageia build on there. Just
compile and install Mailutils normally on "Redhat / Mageia for intel"
and "debian for ARM" as two separate processes.
If you want the same build to run on Debian and "Redhat / Mageia", then static linking can achieve that more reliably. Note that it will prevent security updates to gnutls being applied when running Mailutils with encrypted connections, until you rebuild the static binary. You should
be able to use the Debian x86_64 Mailutils packages at least, so you
probably don't need to try running the Mageia build on there. Just
compile and install Mailutils normally on "Redhat / Mageia for intel"
and "debian for ARM" as two separate processes.
On 20 Jan 2026 07:41:06 +1000 Computer Nerd Kev wrote:
[..]
If you want the same build to run on Debian and "Redhat / Mageia", then
static linking can achieve that more reliably. Note that it will prevent
security updates to gnutls being applied when running Mailutils with
encrypted connections, until you rebuild the static binary. You should
be able to use the Debian x86_64 Mailutils packages at least, so you
probably don't need to try running the Mageia build on there. Just
compile and install Mailutils normally on "Redhat / Mageia for intel"
and "debian for ARM" as two separate processes.
Yes, and now I try to install the GNU Mailutils source package on a Pi3B with Bullseye OS. Meaning, try to rebuild the (ancient) package as is, and as next steps, to replace the source tgz, do some adaptations and try to
By some reason, Synaptic install GUI does only show the sources for a few packages, and Mailutils is not among them.
/etc/apt/sources.list contains^^^^^^^^^^^^^^
deb http://raspbian.raspberrypi.org/raspbian/ bullseye main contrib non-
free rpi
# Uncomment line below then 'apt-get update' to enable 'apt-get source'
deb-src http://raspbian.raspberrypi.org/raspbian/ bullseye main contrib non-free rpi--
Is there one more repo to activate, so that it shows up for downloading?
By some reason, Synaptic install GUI does only show the sources for a few packages, and Mailutils is not among them.
/etc/apt/sources.list contains
deb http://raspbian.raspberrypi.org/raspbian/ bullseye main contrib non-
free rpi
On 20 Jan 2026 07:41:06 +1000 Computer Nerd Kev wrote:
[..]
If you want the same build to run on Debian and "Redhat / Mageia", then
static linking can achieve that more reliably. Note that it will prevent
security updates to gnutls being applied when running Mailutils with
encrypted connections, until you rebuild the static binary. You should
be able to use the Debian x86_64 Mailutils packages at least, so you
probably don't need to try running the Mageia build on there. Just
compile and install Mailutils normally on "Redhat / Mageia for intel"
and "debian for ARM" as two separate processes.
Yes, and now I try to install the GNU Mailutils source package on a Pi3B with Bullseye OS. Meaning, try to rebuild the (ancient) package as is, and as next steps, to replace the source tgz, do some adaptations and try to
get this built, also.
By some reason, Synaptic install GUI does only show the sources for a few packages, and Mailutils is not among them.
/etc/apt/sources.list contains
deb http://raspbian.raspberrypi.org/raspbian/ bullseye main contrib non-
free rpi
# Uncomment line below then 'apt-get update' to enable 'apt-get source' deb-src http://raspbian.raspberrypi.org/raspbian/ bullseye main contrib non-free rpi
Is there one more repo to activate, so that it shows up for downloading?
You could look at the Debian package info/downloads
on the web like LDO suggested.
As a guess: maybe the Raspbian package repo doesn't have sources
for packages they copied from Debian instead of rebuilding
themselves?
On 24/01/2026 01:25, Computer Nerd Kev wrote:
As a guess: maybe the Raspbian package repo doesn't have sources for
packages they copied from Debian instead of rebuilding themselves?
Raspbian doesn't copy packages from Debian, it just uses the Debian
repos. The Raspberry Pi's own repo doesn't contain userspace packages
unless they're pi-specific.
The issue is probably that /etc/apt/sources.list only has a line for
"deb" packages and not "deb-src" packages, by default.
Such a line is easy to add.
(If the OP were using Trixie it would be a matter of adding "deb-src"
after "deb" on the line starting "Types:" in /etc/apt/sources.list.d/debian.sources).
On 24/01/2026 01:25, Computer Nerd Kev wrote:
As a guess: maybe the Raspbian package repo doesn't have sources
for packages they copied from Debian instead of rebuilding
themselves?
Raspbian doesn't copy packages from Debian, it just uses the Debian
repos. The Raspberry Pi's own repo doesn't contain userspace packages
unless they're pi-specific.
The issue is probably that /etc/apt/sources.list only has a line for
"deb" packages and not "deb-src" packages, by default.
Daniel James <daniel@me.invalid> wrote:
On 24/01/2026 01:25, Computer Nerd Kev wrote:
As a guess: maybe the Raspbian package repo doesn't have sources
for packages they copied from Debian instead of rebuilding
themselves?
Raspbian doesn't copy packages from Debian, it just uses the Debian
repos. The Raspberry Pi's own repo doesn't contain userspace packages
unless they're pi-specific.
This is evidently untrue simply from looking at the Raspbian repo's
contents. I found out the hard way that some packages like Firefox
there are built only for Debian's target ARM architectures, not the
early Raspberry Pi boards.
Also I haven't seen the Debian repo used in Raspbian sources.list,
though I haven't used the more recent RPi OS versions.
Would this even work seeing as there'd be conflicting packages for the
same programs? In my experience with Debian on PC, it wouldn't since
Apt doesn't favour one repo over another - it just selects whichever
package versions look latest.
The issue is probably that /etc/apt/sources.list only has a line for
"deb" packages and not "deb-src" packages, by default.
He posted that there was a "deb-src" line already.
Anyway it still won't build him the latest Mailutils which would be
easy to do the same way he already did it on PC (providing the
dependency package names are changed to Debian ones), so I think I
give up at this point.
Raspbian doesn't copy packages from Debian, it just uses the
Debian repos. The Raspberry Pi's own repo doesn't contain
userspace packages unless they're pi-specific.
This is evidently untrue simply from looking at the Raspbian repo's contents. I found out the hard way that some packages like Firefox
there are built only for Debian's target ARM architectures, not the
early Raspberry Pi boards.
Also I haven't seen the Debian repo used in Raspbian sources.list,
though I haven't used the more recent RPi OS versions.
Would this even work seeing as there'd be conflicting packages for
the same programs? In my experience with Debian on PC, it wouldn't
since Apt doesn't favour one repo over another - it just selects
whichever package versions look latest.
not@telling.you.invalid (Computer Nerd Kev) writes:
Daniel James <daniel@me.invalid> wrote:
On 24/01/2026 01:25, Computer Nerd Kev wrote:
As a guess: maybe the Raspbian package repo doesn't have sources
for packages they copied from Debian instead of rebuilding
themselves?
Raspbian doesn't copy packages from Debian, it just uses the Debian
repos. The Raspberry Pi's own repo doesn't contain userspace packages
unless they're pi-specific.
This is evidently untrue simply from looking at the Raspbian repo's
contents. I found out the hard way that some packages like Firefox
there are built only for Debian's target ARM architectures, not the
early Raspberry Pi boards.
Also I haven't seen the Debian repo used in Raspbian sources.list,
though I haven't used the more recent RPi OS versions.
It uses both debian.org (or mirrors thereof) and raspberrypi.org. The
latter has RPi-specific packages (e.g. raspi-config) and RPi-specific rebuilds of standard packages (e.g. vlc), but excludes packages where
the binaries are shared with Debian (e.g. coreutils).
Would this even work seeing as there'd be conflicting packages for the
same programs? In my experience with Debian on PC, it wouldn't since
Apt doesn't favour one repo over another - it just selects whichever
package versions look latest.
It works fine...
The issue is probably that /etc/apt/sources.list only has a line for
"deb" packages and not "deb-src" packages, by default.
He posted that there was a "deb-src" line already.
Anyway it still won't build him the latest Mailutils which would be
easy to do the same way he already did it on PC (providing the
dependency package names are changed to Debian ones), so I think I
give up at this point.
The answer was clear from the original post: OP didn't know how to get
source packages.
Richard Kettlewell <invalid@invalid.invalid> wrote:
It uses both debian.org (or mirrors thereof) and raspberrypi.org. The
latter has RPi-specific packages (e.g. raspi-config) and RPi-specific
rebuilds of standard packages (e.g. vlc), but excludes packages where
the binaries are shared with Debian (e.g. coreutils).
OK, maybe the sources.list has changed in newer versions, but
coreutils _is_ there the RPi repo, and updated in 2025:
http://raspbian.raspberrypi.org/raspbian/pool/main/c/coreutils/
OP won't get source packages for the newer Mailutils version he wants
that way, just the old version used for the package, which he's not
happy with. But OP already has the sources he used for building the
latest version on PC, minus the Debian patches (which might not work
on the latest version anyway).
Computer Nerd Kev <not@telling.you.invalid> writes:
Richard Kettlewell <invalid@invalid.invalid> wrote:
It uses both debian.org (or mirrors thereof) and raspberrypi.org. The
latter has RPi-specific packages (e.g. raspi-config) and RPi-specific
rebuilds of standard packages (e.g. vlc), but excludes packages where
the binaries are shared with Debian (e.g. coreutils).
OK, maybe the sources.list has changed in newer versions, but
coreutils _is_ there the RPi repo, and updated in 2025:
http://raspbian.raspberrypi.org/raspbian/pool/main/c/coreutils/
Not in arm64 trixie.
$ curl -s https://archive.raspberrypi.org/debian/dists/trixie/main/binary-arm64/Packages | grep 'Package: coreutils'
$
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 1,096 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 398:59:34 |
| Calls: | 14,036 |
| Calls today: | 2 |
| Files: | 187,082 |
| D/L today: |
2,640 files (1,646M bytes) |
| Messages: | 2,479,108 |