Re: test

[Rémi Demarthe]

Bonjour,

Le lundi 25 avril 2022 à 19:01 +0200, awache...@gmail.com a écrit :
> On Monday 25 April 2022 17:56:36 Rémi Demarthe wrote:
> > Le lundi 25 avril 2022 à 11:13 +0200, ajh-valmer a écrit :
> > > test ml
> 
> > Chez moi sur evolution le message est considéré comme spam.
> > Dans les sources :
> > X-Spam-Flag: yes
> > X-Spam-Level: ***
> > X-GND-Spam-Score: 290
> > X-GND-Status: SPAM
> > En espérant que cela puisse aider.
> 
> Oui, ça m'aide, merci.
> 
> Déjà, je n'ai pas reçu mon propre message depuis la liste,
> alors que c'est un nouveau mail créé ce matin...
> Donc à peine créé il est déjà bloqué.
> 
> Quel serveur de mails indique que mon mail est un spam ?
> 
Le mail est mis en spam côté client par évolution.
Il ajoute les X-Spam-Flag et X-Spam-Level.

Pour X-GND-Spam-Score et X-GND-Status, cela serait lié à un filtrage
sieve qui si je ne m'abuse à lieu lors de la réception du serveur IMAP.
Je n'arrive pas à comprendre pourquoi tu atteri dans les spam au regard
des sources du message.


> J'utilise smtp.bbox.fr, immédiatement je reçois ce message :
> "Le serveur a répondu : «5.7.1 Rejected for policy reason»
> Avec d'autres smtp, le destinataire ne reçoit rien,
> sinon une déclaration de spam.
> Bref, ça devient inquétiant, je ne sais quoi faire.
> Bonne soirée
> 

As-tu essayé les testeur de spam comme https://www.mail-tester.com/ ?

Bonne journée,
Crodialement,
--
Rémi Demarthe

Re: zwart op wit, constrastrijk

[Geert Stappers]

On Mon, Apr 25, 2022 at 11:35:04AM +0200, Sijmen J. Mulder wrote:
> Geert Stappers wrote:
> }... witte achtergrond  met zwarte tekst ...
> > Aanname: Er zijn hier mensen die dat ook hebben.
> 
> Zeker! Ik doe dat ook.
> 
> > Programmas die lichte kleuren als geel en lichtblauw gebruiken
> > om tekst te laten opvallen.
> 
> Er zjn een aantal dingen die je kunt doen:
> 
>  1. Als je eigenlijk helemaal niet zo'n behoefte hebt kun je
> programma's configurareren om geen kleur te gebruiken. Dat doe ik
> meestal. In het bijzonder heeft de standaard Debian ~/.bashrc een
> hele sectie die kleur configureert. Ik heb dat er allemaal
> uitgehaald. Je kunt ook NO_COLOR=1 in de omgeving definieren, een
> aantal programma's respecteren dat.
 
Inmiddels http://no-color.org/ gevonden. Van die stoere website:

  , an informal standard is hereby proposed:

Command-line software which adds ANSI color to its output by default
should check for the presence of a NO_COLOR environment variable
that, when present (regardless of its value), prevents the addition
of ANSI color.

  By adopting this standard, users that prefer to have plain, non-colored
  text output can set one environment variable in their shell to have
  it automatically affect all supported software.


>  2. Veel programma's gebruiken het basispallet van 16 kleuren. Dit
> pallet kun je aanpassen in de voorkeuren van de terminal, dan kun je
> bijvoorbeeld een andere, leesbare, tint aangeven voor 'lichtblauw'.
> (In MATE Terminal vond ik het standaardkleurenschema al aardig.)

Daarmee word nu ge-experimenteerd. Dank voor de tip.

 
>  3. Andere programma's die 256 of 'ware kleuren' gebruiken moet je soms
> handmatig configureren.

Misschien dat ik van TERM=xterm-256color naar TERM=xterm ga ...
 

> Hopelijk heb je hier wat aan.

Jawel.

 
> Sijmen
> 

 
Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: No puedo imprimir en impresora en red

[Camaleón]

El 2022-04-26 a las 16:13 -0300, Marcelo Eduardo Giordano escribió:

> Amigos:
> 
> Acabo de instalar debian en mi nueva notebook e instalo mis dos impresoras y
> en ambas no puedo imprimir
> 
> una impresora es una impresora XEROX B215 que se conecta directamente a la
> red y que me el sistema me la detectó automaticamente. Sin embargo al
> imprimir me dice "No suitable destinacion host found by cups browsed"

Seguramente se trata de este bug:

CUPS fails to print to autodetected printers because of cups-browsed 
error 
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1855595

Mira a ver si lo que sugieren para resolverlo te sirve.
 
> Tampoco puedo imprimir en una Epson L3110 que esta conectada en red en otra
> pc con debian y me dice "la configuracion de la impresora es incorrecta o la
> impresora ya no existe"

Esta parece más complicada de instalar. Mira a ver si has instalado los 
drivers correctamente y si en el equipo donde está instalada 
físicamente imprimime bien.

Si no es un problema de controladores, revisa la configuración de CUPS, 
tanto en el equipo cliente como en el servidor, relacionada con la 
compartición de la impresora.

CUPS/Printer sharing
https://wiki.archlinux.org/title/CUPS/Printer_sharing

> Ambas impresoras puedo imprimir perfectamente desde otra pc con Arch

Saludos,

-- 
Camaleón 

Re: file born 30 seconds after its creation on ext4 - bug?

[Thomas Schmitt]

Hi,

i wrote:
> > So if it got created by the script, maybe it was deleted or renamed
> > shortly afterwards and created again 30 seconds later ?

Vincent Lefevre wrote:
> The script doesn't do that. The file is created with
>   echo "* $fqdn ($(${1:-.}/config.guess) / ${line#PROC:})" > "$out"
> [...]
> Note that if the file were created again, the first line with the FQDN
> would no longer be in the file, but the line is still there.

This is indeed a riddle. But is there a hard reason not to insert

  stat "$out" >/tmp/stat_out_after_creation 2>&1

after that line and to compare /tmp/stat_out_after_creation with the
stat(1) result when the expected file appears 30 seconds later ?


> https://gitlab.inria.fr/mpfr/misc/-/blob/fed7770cf5f712871bd116ef80d93ea5885fc3f7/vl-tests/mpfrtests.sh
> # Written in 2011-2021 by Vincent Lefevre .

So you are supposed to really know what it does. :))

Whatever, it is fewly plausible that the file would not show up in stat(1)
or ls(1) but the script can happily do
  ... >> "$out"
Each of these lines is supposed to do a name lookup of the file.

Maybe another stat(1) should be placed between
  printf "OK, output in %s\n" "$out"
and
  exit 0


Have a nice day :)

Thomas

Re: file born 30 seconds after its creation on ext4 - bug?

[Vincent Lefevre]

Hi,

On 2022-04-27 09:07:37 +0200, Thomas Schmitt wrote:
> i wrote:
> > > So if it got created by the script, maybe it was deleted or renamed
> > > shortly afterwards and created again 30 seconds later ?
> 
> Vincent Lefevre wrote:
> > The script doesn't do that. The file is created with
> >   echo "* $fqdn ($(${1:-.}/config.guess) / ${line#PROC:})" > "$out"
> > [...]
> > Note that if the file were created again, the first line with the FQDN
> > would no longer be in the file, but the line is still there.
> 
> This is indeed a riddle. But is there a hard reason not to insert
> 
>   stat "$out" >/tmp/stat_out_after_creation 2>&1
> 
> after that line and to compare /tmp/stat_out_after_creation with the
> stat(1) result when the expected file appears 30 seconds later ?

Because the issue was unexpected (this was the first time it occurred
after 11 years of testing: I wrote the first version of the script in
2011, and I typically look at the output file just after starting the
script) and is probably unlikely to occur again.

Moreover I don't see why this behavior would be allowed with a local
filesystem. If one has in a script with "set -e" (to detect errors,
like in my script)

  something > out
  something else

and if in an interactive shell, one can see the side effect of
"something else", then one should expect file "out" to be visible
in the directory. (This is/was not necessarily the case with NFS
due to caching, even on the same machine.)

> > https://gitlab.inria.fr/mpfr/misc/-/blob/fed7770cf5f712871bd116ef80d93ea5885fc3f7/vl-tests/mpfrtests.sh
> > # Written in 2011-2021 by Vincent Lefevre .
> 
> So you are supposed to really know what it does. :))

Yes, I'm the only author of the script, and I've been working on
it for 11 years. It was much simpler 11 years ago, but there was
already the same kind of code concerning the output file.

> Whatever, it is fewly plausible that the file would not show up in stat(1)
> or ls(1) but the script can happily do
>   ... >> "$out"
> Each of these lines is supposed to do a name lookup of the file.

unless there is some caching bug. The script is likely to run on
the same CPU core, so that the file would still be visible along
the script, possibly via a cache. But some process running on a
different core might not see it for some time.

However, there's also the fact that the birth time was 30 seconds
ahead of the actual file creation, while there was no lockup.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: [HS] Recherche spécialiste PHP-7

[Daniel Caillibaud]

Le 26/04/22 à 15:40, "ajh.valmer"  a écrit :
> Les différences importantes se situent au passage de php5 vers php7.
> Après, les différences de php7 vers php8 sont minimes.

Certes, mais minime ne veut pas dire inexistantes ;-)
Il y a par ex des fonctions qui étaient deprecated depuis un bon moment et qui 
ont disparu
entre 7.3 et 7.4, ou bien des syntaxes qui lançaient un warning et se mettent à 
planter.

> Je l'ai vu entre les versions php5.1 à php5.6.
> 
> https://www.php.net/eol.php guides migration 5.6 vers 7.0.
> ne donnent pas les modifications essentielles, 
> telles, la nouvelle syntaxe d'appel à une base de données
> et les nouveaux scripts php7 à englober dans le SQL.

Tu penses à quoi ?

Car il y a pourtant la liste des nouvelles fonctionnalités pour chaque version.

Si tu parles de PDO, ça n'est pas mentionné dans les nouvelles fonctionnalités 
php7 parce que
ça existait déjà en php5.

Mais pour migrer, tu n'es pas obligé de passer tout le code aux nouvelles 
syntaxes tant que les
anciennes fonctionnent et ne sont pas deprecated, il faut surtout se concentrer 
sur les
"breaking changes" qu'il faut absolument modifier si ça te concerne, par ex 
pour le passage 5.6
=> 7.0
https://www.php.net/manual/fr/migration70.incompatible.php

-- 
Daniel

Il  est impossible de faire 1 000 pompes par jour... 
sauf si vous êtes un  enfant chinois dans une usine Nike.

Re: email lacks sender address

[Curt]

On 2022-04-26, David Wright  wrote:
>
> Well, the simple way, which is why I use it, is to put:
>
>   set envelope_from_address="someuser@somedomain"
>   set use_envelope_from

The OP sent me an email off-list in which he informed me he was doing
his best and that he'd changed *both* of the following parameters to
booleans (yes!). I guess he misunderstood our proofreading. 


 set envelope_from_address
 set use_envelope_from

Re: file born 30 seconds after its creation on ext4 - bug?

[Thomas Schmitt]

Hi,

Vincent Lefevre wrote:
> the issue [...] is probably unlikely to occur again.

In this case we will hardly be able to find an explanation.


> However, there's also the fact that the birth time was 30 seconds
> ahead of the actual file creation, while there was no lockup.

Yes, your observations are not yet consistently explainable.
So some of the normal assumptions about your situation must be wrong.
Question is which ones.

The file times which you showed are consistent with a file that was indeed
created and written 30 seconds after your script was supposed to have
created it and to have written to it with repeated name lookups.

> > -rw-r--r--  1 878 2022-04-26 14:43:45 
> > mpfrtests.cventin.lip.ens-lyon.fr.out
> >  Birth: 2022-04-26 14:43:45.537241731 +0200

On the other hand the content looks like the normal work result of your
script which already had ended half a minute ago.

It is normal that data get onto the physical storage medium only quite a
long time after a program wrote them. But this is supposed to be kept
consistent by the VFS and virtual memory of the Linux kernel.


> The script is likely to run on
> the same CPU core, so that the file would still be visible along
> the script, possibly via a cache.

A connection to the CPU cache would be a strange low level problem of
kernel or hardware.
I understand that the filesystem driver writes to memory pages which
are associated to storage device memory. The pages and their association
are managed by the virtual memory facility of the kernel.
  
https://www.kernel.org/doc/html/latest/filesystems/vfs.html#the-address-space-object
Any attempt to access the associated to storage device memory of a not
yet written page is supposed to be directed to the cached page in RAM.

If it has indeed to do with the CPU cache then a particular cache would have
delayed its writing to RAM for 30 seconds but would have served its own CPU
with the full results of file system driver and virtual memory activities
around the new file. No inconsistent partial results would have been written
to page cache in RAM which would have caused protests during your attempts
to see the file.

But i deem it unlikely that the kernel threads which operated filesystem and
virtual memory are (nearly) always running on the same CPU cache which is
not shared with all other CPU cores.
Further, if the memory operations were just pending in some secluded cache
why does the inode then bear the time when that cache would finally have
released its content to the wider accessible RAM.


If i was in your situation, i'd add diagnostic messages to the script in the
hope (or fear) that the glitch happens again.
Especially the inode numbers during and after the script run would be
interesting.


Have a nice day :)

Thomas

Re: email lacks sender address

[Vincent Lefevre]

On 2022-04-27 09:19:38 -, Curt wrote:
> On 2022-04-26, David Wright  wrote:
> > Well, the simple way, which is why I use it, is to put:
> >
> >   set envelope_from_address="someuser@somedomain"
> >   set use_envelope_from
> 
> The OP sent me an email off-list in which he informed me he was doing
> his best and that he'd changed *both* of the following parameters to
> booleans (yes!). I guess he misunderstood our proofreading. 
> 
>  set envelope_from_address
>  set use_envelope_from

Unfortunately, Mutt doesn't output an error when one uses
"set variable" for non-boolean variables.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: Unwanted route appears at every reboot...

[Jeremy Ardley]

On 28/4/22 4:49 am, nimrod wrote:

default dev eno1 scope link src 169.254.30.62 metric 202


the 169.254 address is Used for link-local addresses between two hosts 
on a single link when no IP address is otherwise specified, such as 
would have normally been retrieved from a DHCP server.


So something is stopping your system from assigning the static address.

When it is booted and in  the bad state what does 'ip a' show?

What does it show in syslog?

One suspicion is that another host on the LAN has  the same address?


--
Jeremy



OpenPGP_signature
Description: OpenPGP digital signature

Re: email lacks sender address

[Vincent Lefevre]

On 2022-04-27 13:46:01 -0400, Haines Brown wrote:
> On Wed, Apr 27, 2022 at 11:29:17AM -0400, Greg Wooledge wrote:
> > If what you WANT is for your outgoing mail to appear to come from
> > j...@histomat.net then you should have histomat.net in that file instead.
> 
> Thanks for the clarifation. I changed it to histomat because I want 
> outgoing mail to appear to come from hai...@histomat.net.

Only if you send mail with just a username in "From:", e.g.

  From: haines

In general, one prefers to handle the "From:" address at the
MUA level.

The only advantage or disadvantage is that if you send a mail to
hai...@histomat.net, I think that it will be sent locally instead
of remotely (that is, going to the smarthost). The local mailbox
and the remote mailbox are generally different. So this depends
on what you prefer.

> However just changing it does not fix my problem.

Not surprising.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Unwanted route appears at every reboot...

[nimrod]

Hi,

yesterday afternoon, after working all day at office without any
(network) problem, I decided to reboot my machine. Suddenly I could not
navigate on the web. But I could ping the gateway, I could resolve
names... just cannot reach the network (most commands just issued the
classic "network is unreachable" message).

thinking it was a route problem, I issued "ip route" on the terminal
and got this default route:

default dev eno1 scope link src 169.254.30.62 metric 202

I deleted it and add the good one:

ip route add default via 192.168.1.113 dev eno1

and I could navigate again immediately. Nevertheless, after every
reboot the wrong default route is there again. I couldn't find any file
or directory in which this could be configured, nor I found a command
that could create somehow implicitly such a default route.

How can prevent it to come back after reboot? I could add some kind of
/etc/rc.local or a systemd target to remove the wrong one and add the
right one at every boot, but i would prefer to understand why it
happens. At least, since a 169.254 route is always on, I wish to
undestand why it becomes the default one, preventing me from reach the
internet.

Please note that I only use Network Manager from the Gnome GUI with a
static address, and I didn't modify the configuration in several
months. Never touched /etc/network* dirs and files, nor
/etc/systemd/network.

Any hint will be much appreciated.

Best regards.

Re: Debian 10 and also 11 installation fails, because grub fails - please fix

[Jaroslav Fojtík]

Hi,




>Looks like your partition is full.
>Check if there are old and unneeded kernels installed. If so, uninstall 
these
>and try again.

133GigaBytes free space on the partition should be sufficient enough.



>Please could you install pastebininit, maybe and put all the details into a
>pastebin rather than on your machine?

>I suspect that there is something odd with the partition numbering and

>logical partitions, possibly.


>All the very best, as ever,

I suspect mail size limit on this discussion. That is why mail cannot be 
delivered

and waits for moderation. And then the mail is trashed in recycle bin
because moderator


does not allow oversized mail.





Pastebin only wraps XML that I cannot attach to this mail either.

Files on my machine are visible on whole internet 24/7 to anybody.


    http://78.108.103.11/~fojtik/debian11/



regards

   Jara

Re: email lacks sender address

[Haines Brown]

On Wed, Apr 27, 2022 at 05:14:34PM +0100, Jonathan Dowland wrote:
> On Wed, Apr 27, 2022 at 10:37:28AM -0400, Haines Brown wrote:
> > Don't my headers show that I'm using Devuan? Devuan is simply Debian
> > without systemd.
> 
> And any bugs they have introduced. We cannot handle support for Devuan
> because we are not responsible for what they release.

Understood

Re: file born 30 seconds after its creation on ext4 - bug?

[Greg Wooledge]

On Wed, Apr 27, 2022 at 10:45:09PM -0400, Stefan Monnier wrote:
> Another option might be that your system's time was "reset".
> This shouldn't happen, but it can happen if your NTP was down, the
> machine got out-of-sync over time and you restart the NTP server at
> which point it may(!) decide to jump the clock if the difference is
> large enough (i.e. too large to catch up gradually).
> Can't remember how large is "large enough".

It would depend on which NTP implementation is in use.  The traditonal
"ntp" package should not do a large jump like that, except at boot.  It
should just make the clock drift toward the correct time.

Other implementations may be more aggressive about it.  Debian 11 uses
systemd-timesyncd by default, but I don't know how it behaves.  I've
not used chrony either.  I did experiment with openntpd for a while, but
it was many years ago when it was pretty new, so it might have changed
a lot.

In any case, that's a clever theory.  The OP could look for evidence of
an NTP time jump in whatever logs survive from the offending time
period.

Re: Recommendations for a home server running Debian Bullseye (11)?

[David Christensen]

On 4/27/22 05:24, Will Mengarini wrote:

* Tom Browder  [22-04/27=We 05:50 -0500]:

I really appreciate all the advice, but I am
not going to build from scratch again [...].


Just in case anybody's discouraged that the OP won't build from
scratch, I just want to say /I/ found this thread valuable too.

Where do you all buy parts?  Alternatives to Newegg?



For new items, mostly Amazon just because we are paying for Prime.  I 
prefer B when they have what I need.  And, Newegg and other companies 
have a presence on eBay.



For used items, mostly eBay.  But, I did get my Dell PowerEdge T30 from 
a local seller via Craig's List.



David

Re: Recommendations for a home server running Debian Bullseye (11)?

[David Christensen]

On 4/27/22 03:50, Tom Browder wrote:

On Tue, Apr 26, 2022 at 08:49 Christian Britz  wrote:
...

I really appreciate all the advice, but I am not going to build from
scratch again (but I will encourage my grandchildren if they ever get
interested).  In that vein, the link on the modern build-your-own case
(Fractal Design) from David was very helpful--thanks!



YW



So, if I need a new in-home server, I think I will go the Dell route. The
multiple easy in/out drives capability is just what I need for my
redundancy case (and ease of use) and assume I can add SSDs from my own
sources instead.



If your COTS server has spare internal or hot-plug drive bays, 
backplanes, cables, PSU capacity, etc., and you have the appropriate 
drive carriers, then you can install additional standard drives and they 
should work.  But, beware of warranty entanglements.



Going the other way, when you remove a drive in a COTS server, you may 
need to install a filler so that cooling works as engineered.



I have been using SATA 2.5" SSD's as OS drives for many years.  I 
install 2.5" SATA trayless drive racks in all of my desktop and server 
machines (including the Fractal Design):


https://www.startech.com/en-us/hdd/hsb220sat25b


For machines without an available external drive bay (including the Dell 
PowerEdge T30), I install a PCI slot version:


https://www.startech.com/en-us/hdd/s25slotr


(My older laptops have externally accessible 2.5" SATA drive bays.)


My SSD's do not get heavy use, so passive cooling is enough.  If your 
SSD's get heavy use, pay attention to cooling.



For backup disks, I have experienced numerous issues with external disk 
drives; primarily disconnects, but also overheating.  I install 3.5" 
SATA drive racks in appropriate machines (including the Fractal Design) 
and put 3.5" SATA drives in drawers with fans:


https://www.startech.com/en-us/hdd/drw150satbk


(I tried 3.5" SATA trayless bays, but cooling was inadequate.)


That said, racks, backplanes, etc., add more opportunities for failure. 
 The most reliable approach is internal drives with good quality 
cables.  This is how my data drives are connected.



When shopping, be sure to look at barebone NAS products that are 
designed for a home environment -- e.g. small, energy efficient, quiet, 
etc..



David

/etc/resolv.conf en Debian Bookworm

[Guillermo Sosa]

Buenas tardes aquí en Argentina.
Desde hace años, mas precisamente desde Stretch, construyo mi distribución (con 
lb build) personalizada; hoy uso la "estable" Bullseye, pero ya estoy 
experimentando con Bookworm. De hecho hace un mes mas o menos que estoy 
probandola con escritorios Cinnamon, Mate y Xfce. Hasta 10 ó 12 días atrás 
todas funcionaban perfecto, pero de repente, con cualquier DE, comenzaron a 
tener problemas con /etc/resolv.conf tanto en live-system como instaladas a 
disco. De hecho ese archivo, que en la jaula chroot se activa (ustedes lo deben 
saber) con el comando; cp /etc/resolv.conf chroot/etc/resolv.conf, o sea 
copiando el resolv.conf del sistema anfitrión al sistema en construcción en la 
carpeta chroot. El mismo es un archivo de texto plano con el siguiente 
contenido:

# Generated by NetworkManager
search fibertel.com.arnameserver 192.168.0.1

Donde fibertel.com.ar es mi proovedor de internet, y el nameserver calculo que 
se asigna de acuerdo a mi dirección IP

/etc/resolv.conf al salir de la jaula chroot o al salir del sistema en modo 
live, se borra y cada vez que iniciamos "network-manager" como dice mas arriba 
vuelve a generarlo.
Y acá viene el tema, desde hace diez días ocurre que una vez terminado el 
sistema, hacer la imágen ISO y correrla se genera un /etc/resolv.conf que en 
realidad es un enlace a:
/run/systemd/resolve/resolv.conf, pero es un enlace vacío, ya que en 
/run/systemd/ el directorio "resolve" y por lo tanto el archivo "resolv.conf" 
NO EXISTEN. Lo mismo ocurre si se instala el sistema en disco duro. Como 
consecuencia no se encuentran los DNS y lógicamente no se puede acceder a la 
web.
Cabe aclarar que si instalo a disco, y luego reemplazo el /etc/resolv.conf 
enlace por el un resolv.conf con el contenido que dejé mas arriba, arranca la 
conexión.

Esperando no haber sido demasiado extenso y que se aya entendido me quedo a la 
espera de una respuesta, ya sea porque le haya ocurrido a alguien o bien sepa 
de donde se genera el error/problema.
He buscado mucho en internet (y lo sigo haciendo) pero hasta ahora no encuentro 
nada.

Muchas gracias y saludos

Guillermo E. Sosa
San Nicolás de los Arroyos
Bs. As. - Argentina

Enviado con [ProtonMail](https://protonmail.com/) correo seguro.

Re: Debian 10 and also 11 installation fails, because grub fails - please fix

[Andrew M.A. Cater]

On Wed, Apr 27, 2022 at 08:34:25PM +0200, Jaroslav Fojtík wrote:
> 
> Dears,
> 
> 
> 
> 
> Please fix an issue in Debian installer that blocks automatic installation.
> 
> It affects all known Debian distributions on my machine.
> 
> 
> 
> 
> 
> http://78.108.103.11/~fojtik/debian11/DebianInstallFail.jpg
> 
> 
> 
> 
> Debian could be hacked to finish installation and then works.
> 
> 
> 
> 
> 
> This does not look sane:
> http://78.108.103.11/~fojtik/debian11/update_grub.txt
> ***
> Generating grub configuration file ...
> Found linux image: /boot/vmlinuz-5.15.0-3-amd64
> Found initrd image: /boot/initrd.img-5.15.0-3-amd64
> Found linux image: /boot/vmlinuz-5.14.0-4-amd64
> Found initrd image: /boot/initrd.img-5.14.0-4-amd64
> Found Windows 7 on /dev/sda1
> Found Slackware Linux (Slackware 8.1) on /dev/sda9
> Found Windows 7 on /dev/sdb1
> Found Slackware 14.2 on /dev/sdb3
> error: out of memory.
> error: syntax error.
> error: Incorrect command.
> error: syntax error.
> Syntax error at line 447
> Syntax errors are detected in generated GRUB config file.
> Ensure that there are no errors in /etc/default/grub
> and /etc/grub.d/* files or please file a bug report with
> /boot/grub/grub.cfg.new file attached.
> ***
> 
> 
> 
> 
> All neccessary information about my Debian are published here:
> 
>   http://78.108.103.11/~fojtik/debian11/
> 
> I cannot attach them directly into Email, mail will be dropped.
> 
> 
> 
> 
> best regards
> 
>    Jara
> 
> 
>

Hello Jara,

Please could you install pastebininit, maybe and put all the details into a
pastebin rather than on your machine?

I suspect that there is something odd with the partition numbering and
logical partitions, possibly.

All the very best, as ever,

Andy Cater 

Re: email lacks sender address

[Vincent Lefevre]

On 2022-04-27 15:30:33 -0400, Greg Wooledge wrote:
> On Wed, Apr 27, 2022 at 07:26:31PM +0100, Brian wrote:
> > On Wed 27 Apr 2022 at 08:05:46 -0400, Haines Brown wrote:
> > >   A message that you sent could not be delivered to one or more of its
> > >   recipients. This is a permanent error. The following address(es) failed:
> > 
> > This message is from your smarthost, mail.guardedhost.com.
> 
> It doesn't look like it to me.

Agreed. The mail was rejected by the smarthost, and the user's
machine lenin.histomat.net reported this error back to the user
as a mailer-daemon message.

> > > sur...@popcon.devuan.org
> > > host mail.guardedhost.com [216.239.133.245]
> > > SMTP error from remote mail server after pipelined sending data block:
> > > 553 5.7.1 : Sender address rejected:
> > > not owned by user bro...@historicalmaterialism.info
> 
> > > Reporting-MTA: dns; lenin.histomat.net
> 
> > However, the devuan server apparently decides to look at what is in
> > the mail being sent. At least, that is what I surmise from
> > 
> >   ...after pipelined sending data block
> > 
> > It decides to reject the mail on what it sees, not on guardedhost.com
> > being an inappropriate sender.
> 
> That's a very interesting conclusion, but it's not what I'm seeing.
> 
> First, I'm just ignoring the "after pipelined sending data block" part,
> because I don't know what that means.

I think that the data block was sent at the same time that the
sender address was inspected (hence the word "pipelined", which
just means that several operations overlap, which is common in
SMTP to speed up things: the client doesn't have to wait for
the server reply to send the next data).

> The clearest part is ": Sender address rejected".
> That sounds very much like it rejected the message specifically because
> it didn't like the sender address.  The "not owned by user" part
> is supporting detail.  There's nothing here to indicate that it inspected
> the body in order to make its rejection decision.
> 
> So, what I'm seeing here:
> 
> 1) The "Reporting-MTA: dns; lenin.histomat.net" tells us which MTA is
>actually writing this error message.
> 
> 2) "sur...@popcon.devuan.org" is the intended recipient address.
> 
> 3) "host mail.guardedhost.com [216.239.133.245]" is the remote host the
>MTA was talking to when the error occurred.
> 
> 4) The "SMTP error ..." line is gibberish to me, except that it tells us
>that the remote mail server (the smarthost) is who generated the error.
> 
> 5) The two lines starting with "553 5.7.1 ..." were generated by the
>smarthost, and reported here by the local MTA.
> 
> As I've said, I don't use exim myself, so I might be mistaken about some
> or all of these conclusions.  But that's my interpretation.

I entirely agree with this interpretation.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: email lacks sender address

[Vincent Lefevre]

On 2022-04-27 14:31:51 -0400, Greg Wooledge wrote:
> Funny thing, though... I'm not sure that /etc/mailname actually does
> anything other than sit there looking cute.  Reading farther along in
> , it says:
> 
>   Exim (i.e. exim 3.x) doesn't read /etc/mailname at all. When you
>   configure it, it prompts you for what it calls the "visible name"
>   of the system. This is stored in /etc/mailname, and also used in a
>   few places in the exim config file.
> 
> But also:
> 
>   Failing to come up with something better exim4 (and mutt) use mailname
>   to qualify recipients and therefore exim4 makes mailname a local
>   domain. If people don't want that, they delete it from the list in
>   the debconf dialog.
> 
> I'm honestly not sure how to interpret that paragraph about exim4.

This means that if you send a mail to "foo" (without a @ followed
by a domain), then "foo" will be qualified with the mailname, i.e.
adding "@" followed by the contents of /etc/mailname.

So, if you have two machines host1.domain.tld and host2.domain.tld,
since their users may be different (typically, root), I think that
it is better to have mailname = FQDN of the machine. Otherwise,
mailname = domain.tld may be fine.

> They're using "local domain" as a technical term with a highly
> specific meaning, but it's something unique to exim4, and I don't
> use exim4 myself.

No, "local domain" just means that the mail is received locally.
If domain.tld is a local domain, then mail sent to f...@domain.tld
will be sent to the mailbox foo on the local machine instead of
being sent through the smarthost (or directly to a MX). This is
not specific to exim.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: "Disabling IRQ #9" - how to check for impact

[IL Ka]

Hi.

Short answer:
This is a known kernel bug:
https://bugzilla.kernel.org/show_bug.cgi?id=207749

Long answer:
This message means some hardware generates an interrupt request, but the
interrupt handler (kernel driver) failed to process it.
See:
https://stackoverflow.com/questions/13861282/understanding-kernel-message-nobody-cared-try-booting-with-the-irqpoll-optio

As we see from stacktrace, this handler is "acpi_irq" (you can also check
it by reading /proc/interrupts):
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/deployment_guide/s2-proc-interrupts

Many hardware things in laptops use ACPI: Brightness buttons, FN buttons,
volume buttons, lid etc.

It seems that your latest firmware (or BIOS as you called it) is
incompatible with your kernel (either kernel or firmware should be fixed)

This situation is common with Lenovo hardware:
https://support.lenovo.com/at/en/solutions/ht505228
https://bugzilla.kernel.org/show_bug.cgi?id=207749 (I suggest you to write
to this issue and to follow it)
https://www.reddit.com/r/linuxquestions/comments/jhxlia/rip_acpi_irq_disabling_irq_9_any_way_to_figure/

If everything works as expected (you see no problem with lid, buttons etc)
simply ignore it.
If no, try to install the latest kernel and file a bug to Debian (I think
it should be forwarded upstream and handled by the kernel developer,
probably duplicating 207749
).

You can also add "irqpoll" kernel param which will ask the kernel to check
all IRQ handlers to find the one which can process it, but I am 99% sure
this wouldn't help since
we know it should be processed by ACPI.
https://www.linuxtopia.org/online_books/linux_kernel/kernel_configuration/re17.html




On Tue, Apr 26, 2022 at 10:21 AM Christian Britz  wrote:

> Hello Debianists,
>
> some days ago I updated the BIOS of my Lenovo IdeaPad S145-15IIL (had to
> boot a certain proprietary OS for this). I think since then there is a
> new error in the kernel log. I never noticed it before.
>
> [9.967601] irq 9: nobody cared (try booting with the "irqpoll" option)
> [9.967607] CPU: 1 PID: 981 Comm: sddm-greeter Tainted: G
> OE 5.10.0-13-amd64 #1 Debian 5.10.106-1
> [9.967608] Hardware name: LENOVO 81W8/LNVNB161216, BIOS DKCN54WW
> 01/27/2022
> [9.967608] Call Trace:
> [9.967615]  dump_stack+0x6b/0x83
> [...]
> [9.967636] handlers:
> [9.967639] [<872fa119>] acpi_irq
> [9.967640] Disabling IRQ #9
>
> This IRQ seems to be related to ACPI on this machine. I am unsure, what
> exactly gets diabled and what might be the impact. So far I notice no
> problems with performance or overheating, compiling a small tool went as
> always I would say.
>
> Do you have any hints for me about what I should/could check?
>
> Regards,
> Christian
>
> --
> http://www.cb-fraggle.de
>
>

Re: email lacks sender address

[Greg Wooledge]

On Wed, Apr 27, 2022 at 02:57:19PM -0500, David Wright wrote:
> 4) The MAIL FROM address, which is the one that you're having trouble
> with.

Just to keep everything clear, the MAIL FROM address and the envelope
sender address are the same thing.  The colloquial use of "sender" (with
lowercase s, and no colon) in some diagnostic messages may refer to
this address.  Or not.  Interpreting diagnostic messages is an art, not
a science.

The original purpose of the MAIL FROM address is "where to send bounces".
Back in the old days, before spam became so prevalent, a typical email
followed a path something like this:

1) User composes the email using their MUA.

2) The MUA injects the email into the local queue using /usr/sbin/sendmail
   (or /usr/lib/sendmail back then).  At this point, the envelope sender
   (MAIL FROM) and envelope recipient (RCPT TO) addresses are established,
   either by the MUA or by the local MTA.

3) The local MTA attempts delivery of the message to the envelope recipient.

4) The recipient's MTA receives the message and injects it into its own
   local queue.

5) The recipient's MTA attempts local delivery of the message.  If this
   fails, a bounce message is created, and sent back to the sender's
   MAIL FROM address, with an empty MAIL FROM.  The empty MAIL FROM on
   the bounce message prevents infinite bounce loops.  The bounce cannot
   be bounced again.

Step 4 is where a lot of changes have occurred in recent decades.  Back in
the original days of email, the receiving MTA typically did not check
things like "is this address actually deliverable".  It would simply
check whether the "@domain" part was "one of mine", or if the message
would have to be relayed.  Checks for the validity of the full receipient
address, including the left-hand side, were delayed until local delivery
processes took over.

This worked well enough until spam took over the Internet.

Spammers began sending messages with two targets -- the actual recipient,
and a second recipient listed in the MAIL FROM.  If the message was
delivered to the actual recipient, then they got a reader that way.  If
the message wasn't delivered to the actual recipient, it might be
bounced back to the MAIL FROM address, and the second recipient would
see it (along with an error message).

Also, if the first recipient happens to be clever enough to read the email
headers, it would appear that the spam was written by the second
recipient, who is also a victim.

This is known as "joe-jobbing".

Modern MTA strategy is to reject the message during the SMTP transaction
if at all possible, and avoid sending bounces -- because the MAIL FROM
is not reliable.

So, the original purpose of the MAIL FROM (destination for bounces) is
mostly obsolete at this point.  Instead, people are using MAIL FROM as
an identifier for authentication purposes.  It's incredibly weak, and
you can spoof it to anything you like, so it's not really a form of
authentication so much as a "way of preventing simple accidents".

A mail relay (smarthost) might decide that it will only accept your
messages if your MAIL FROM is in a special allowed-list.  This is in
addition to whatever other authentication checks the smarthost may perform,
such as checking that the client's IP is in an allowed-list, or SMTP AUTH
which involves using a username and password, or POP-before-SMTP, which
means that it only permits relaying for clients who have accessed the POP3
service on the same machine within the last n minutes.

Isn't email *fun*?

So anyway, configuring your MAIL FROM (envelope sender) address correctly
is really important.

Re: Graphics::Magick

[IL Ka]

Rectangle should be transparent by default (unless you provide `fill`
argument explicitly).
'false' is not a valid color, so providing it shouldn't make any difference.
I suggest to provide color explicitly:
https://imagemagick.org/script/color.php


Here is red:
$bg->Draw(primitive=>'rectangle',stroke=>'red',points=>"100,100,980,980",
fill=>'#FF');
Black:
$bg->Draw(primitive=>'rectangle',stroke=>'red',points=>"100,100,980,980",
fill=>'#FF');
While
$bg->Draw(primitive=>'rectangle',stroke=>'red',points=>"100,100,980,980",
fill=>'#00');


See hex color converter:
https://www.rapidtables.com/convert/color/rgb-to-hex.html



On Wed, Apr 27, 2022 at 3:55 PM mick crane  wrote:

> with bullseye previous Perl script
>
> use Graphics::Magick;
>
> my $bg=Graphics::Magick->new;
> $bg->Set(size=>"1000"."x"."1000");
> $bg->ReadImage('xc:white');
> $bg->Draw(primitive=>'rectangle',stroke=>'red',points=>"100,100
> 980,980");
> $bg->Draw(primitive=>'rectangle',stroke=>'blue',points=>"20,20
> 400,400");
> my $filename = "test.png";
> $bg->Write(filename=>$filename);
> $bg=undef;
>
> would result in outlines of 2 rectangles overlaid on white.
> but with bookworm same thing results in 2 rectangles filled with black.
> to get same result have to change to
> $bg->Draw(primitive=>'rectangle',stroke=>'red',points=>"100,100
> 980,980",fill=>'false');
>
> Is this because bookworm is work in progress ?
>
> regards
>
> mick
> --
> Key ID4BFEBB31
>
>

Re: Thunderbird importeren

[hanbenes]

De gebruiker die Thunderbird opstart is vm01

vm01@debian:~/.thunderbird/6x3rus8f.default-default-1$ ls -ld
drwxr-xr-x 8 vm01 vm01 4096 27 apr 21:48 .
vm01@debian:~/.thunderbird/6x3rus8f.default-default-1$

Er lijkt mij hier geen probleem, toch ziet Thunderbird het niet.

Han




Verzonden met ProtonMail beveiligde e-mail.
--- Original Message ---
Op woensdag 27 april 2022 om 21:13 schreef Geert Stappers 
:


> On Wed, Apr 27, 2022 at 04:29:42PM +, hanbenes wrote:
>
> > Ik wil de email mappen uit een eerdere Linux Thunderbird installatie
> > importeren in de huidige Debian Thunderbird installatie. Daarvoor heb ik
> > de hele directory .thunderbird gecopieerd naar de plek waar deze hoort
> > te staan. Deze methode werkte in eerdere situaties prima, bij de eerste
> > keer openen van de nieuwe Thunderbird werd het meteen al goed ingelezen
> > en stond alles al goed. Nu echter negeert Thunderbird de hele directory
> > alsof deze helemaal niet bestaat.
> > Iemand een idee wat er hier mis gaat?
>
>
> Misschien is de directory inhoud van een andere gebruiker
> dan de gebruiker die thunderbird opstart.
>
>
>
> Groeten
> Geert Stappers
> --
> Silence is hard to parse

Re: HTTP Proxy

[David Wright]

On Wed 27 Apr 2022 at 14:24:51 (-0400), gene heskett wrote:
> On Wednesday, 27 April 2022 14:04:43 EDT Larry Martin wrote:

> > >> Thank you for the prompt reply.  I am still having problems.  I
> > >> enter my IP address as 192.168.1.45 and all appears to go ok. When
> > >> it gets to the point of connecting to a mirror site it fails.  I
> > >> have left the proxy blank.  Any suggestions?> 
> 
> That address will not go thru a router, it is an assigned private block 
> (192.168.xx.zz) that you can set up for your home networks, so you will 
> need to setup a NAT scheme in the router and let it handle the details. I 
> do that here for 6 machines full time, and they all have free run of the 
> net. And with the router running dd-wrt or one of its ilk, it stands 
> guard, allowing nothing coming in that wasn't asked for. And its been 
> standng guard here for 20 years now with no penetrators.

>From the OP's original post, I see no evidence that they have
configured an internet connection.

Is the router connected to their computer by ethernet, or wired?
What does   ip a   print? After all, everything up to the proxy
can be installed off the DVD; IIRC the next step is scanning the
Debian mirror, the first involving outside communication.

Notice that I wrote DVD. Question zero might be: CD, or DVD?

Disclaimer: If it's a DVD, then honestly, I'm not familiar with
/exactly/ when you configure the network.

Cheers,
David.

Re: email lacks sender address

[Vincent Lefevre]

On 2022-04-27 11:29:17 -0400, Greg Wooledge wrote:
> So if your /etc/mailname contains lenin.histomat.net then mail sent by
> john on your system may(!) have a default(!) from/sender address of
> j...@lenin.histomat.net.  Unless it's overridden.
> 
> If what you WANT is for your outgoing mail to appear to come from
> j...@histomat.net then you should have histomat.net in that file instead.
> 
> The fact that lenin.histomat.net has no MX or A records in global DNS
> means it's completely unsuitable for being the right-hand side of an
> email address.  So, what you have now is clearly not correct.

No, this is not necessarily incorrect. If mail is sent locally,
this is fine. For mail sent to other machines, 2 things can be
done in such a case:

1. Provide a fully qualified e-mail address when sending the mail.
   This is what one usually does.

2. Configure the local mail server (here, exim) to do address
   rewriting.

(You can also do both.)

For instance, on my laptop, I use

zira:~> cat /etc/mailname
zira.vinc17.org

which is the FQDN of the machine, and it is resolvable locally only.
This is fine for local mail, e.g. sent by cron.

And with Mutt, I provide the correct e-mail address with my_hdr
(to set the "From:" header, which will be used for the envelope),
e.g. vinc...@vinc17.net for this mail message.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: Unwanted route appears at every reboot...

[Charles Curley]

On Wed, 27 Apr 2022 22:49:59 +0200
nimrod  wrote:

> Please note that I only use Network Manager from the Gnome GUI with a
> static address, and I didn't modify the configuration in several
> months. Never touched /etc/network* dirs and files, nor
> /etc/systemd/network.

Check that NM didn't somehow acquire a spurious route. Edit Connections
-> Your connection, little gear wheel in the lower left. IPv4 Settings
-> Routes.

Are you sure you aren't getting that spurious route from the DHCP
server? To check on that, add a short script to
/etc/NetworkManager/dispatcher.d, called, say, 50environment. It should
look something like

--
#!/bin/bash
LOG=/var/log/NetworkManager

{
  echo "Environment is:"
  printenv
  route -n
} >> "${LOG}" 2>&1
--

Somewhere in that log file you should find a variable that specifies
extra routes, if any.

You can also check to be sure you are getting the correct
address. That should be in $IP4_ADDRESS. Mine looks like:

IP4_ADDRESS_0=192.168.100.44/24 192.168.100.31

I think the second address is either the DHCP server, or the DNS server.

The variables NM uses are detailed in man 8 networkmanager.

-- 
Does anybody read signatures any more?

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

Re: email lacks sender address

[tomas]

On Wed, Apr 27, 2022 at 10:43:33PM +0200, Vincent Lefevre wrote:
> On 2022-04-27 11:29:17 -0400, Greg Wooledge wrote:
> > So if your /etc/mailname contains lenin.histomat.net then mail sent by
> > john on your system may(!) have a default(!) from/sender address of
> > j...@lenin.histomat.net.  Unless it's overridden.
> > 
> > If what you WANT is for your outgoing mail to appear to come from
> > j...@histomat.net then you should have histomat.net in that file instead.
> > 
> > The fact that lenin.histomat.net has no MX or A records in global DNS
> > means it's completely unsuitable for being the right-hand side of an
> > email address.  So, what you have now is clearly not correct.
> 
> No, this is not necessarily incorrect. If mail is sent locally,
> this is fine. For mail sent to other machines, 2 things can be
> done in such a case:

Agreed. The receiving MTA has to be convinced that the one sending
the stuff is supposed to. What that takes is up to that MTA's admin.

For example, the sender could provide a cerrtificate for the SMTPS
session (I've set up systems like that).

Of course, a random MTA contacting "me" with no MX record is either
misconfigured or (more probably) a low-cost spammer, so I'll tend
to reject that.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: HTTP Proxy

[Tim Woodall]

On Wed, 27 Apr 2022, Larry Martin wrote:


I am using my home router IP address 192.168.1.0 device number 45.


This doesn't make sense.

Are you sure it's not one of:
192.168.1.1
192.168.1.254
192.168.1.45

(if it's the latter then you do not want to use the same address on the
machine you're installing.)

Re: Thunderbird content importeren

[Geert Stappers]

On Wed, Apr 27, 2022 at 08:14:17PM +, hanbenes wrote:
> Op woensdag 27 april 2022 om 21:13 schreef Geert Stappers:
> > On Wed, Apr 27, 2022 at 04:29:42PM +, hanbenes wrote:
> >
> > > Ik wil de email mappen uit een eerdere Linux Thunderbird installatie
> > > importeren in de huidige Debian Thunderbird installatie. Daarvoor heb ik
> > > de hele directory .thunderbird gecopieerd naar de plek waar deze hoort
> > > te staan. Deze methode werkte in eerdere situaties prima, bij de eerste
> > > keer openen van de nieuwe Thunderbird werd het meteen al goed ingelezen
> > > en stond alles al goed. Nu echter negeert Thunderbird de hele directory
> > > alsof deze helemaal niet bestaat.
> > > Iemand een idee wat er hier mis gaat?
> >
> >
> > Misschien is de directory inhoud van een andere gebruiker
> > dan de gebruiker die thunderbird opstart.
> >
> De gebruiker die Thunderbird opstart is vm01
> 
> vm01@debian:~/.thunderbird/6x3rus8f.default-default-1$ ls -ld
> drwxr-xr-x 8 vm01 vm01 4096 27 apr 21:48 .
> vm01@debian:~/.thunderbird/6x3rus8f.default-default-1$
> 
> Er lijkt mij hier geen probleem, toch ziet Thunderbird het niet.
> 

En toen waren we nog even ver als in het begin. [1]

Terug naar
} Misschien is de directory inhoud van een andere gebruiker
} dan de gebruiker die thunderbird opstart.

Ik had iets verwacht als UserID en dat ID **in** de directory: 
|bert@myhost:~
|$ id
|UID=1009(bert) GID=1009(bert) groepen=1009(bert)
|bert@myhost:~
|$ ls -ln .thunderbird/
|totaal 24
|drwx-- 12 1009 1009 4096 28 apr 06:49  6qyi7lwk.default-default
|drwx--  3 1009 1009 4096 14 dec 15:23 'Crash Reports'
|-rw-r--r--  1 1009 1009   62 21 mrt  2021  installs.ini
|drwx--  2 1009 1009 4096 20 mrt  2021 'Pending Pings'
|-rw-r--r--  1 1009 1009  259 21 mrt  2021  profiles.ini
|drwx--  2 1009 1009 4096  9 jul  2021  v7v8z28x.default
|bert@myhost:~
|$ 


We gaan zien wat het vervolg wordt.

Bijvoorbeeld:
* Kopieren doe ik op deze manier
* Als ik de -1 achter default-default weghaal gaat het goed
* Door middel van ...  het gewenste doel bereikt


Groeten
Geert Stappers

[1] Kleine vooruitgang: We weten weer dat reactie onder het eerdere
bericht komt.
-- 
Silence is hard to parse

Re: file born 30 seconds after its creation on ext4 - bug?

[Greg Wooledge]

On Wed, Apr 27, 2022 at 03:11:22PM +0200, Vincent Lefevre wrote:
> So, perhaps there were no issues with openat, but when reading
> the directory, the file could not be found because some internal
> structures might have been incomplete.

If so, this is a bug at the kernel level, perhaps in the VFS code
or a file system driver.  I'm no expert on such things.

> To the question why this doesn't occur every time or at least more
> often: there might have been an interrupt at the wrong place, or
> something like that.

It's going to be extremely hard to make any progress on your issue if
you can't reliably reproduce the outcome.  Frustrating as that may be.

Are you able to reproduce the issue at all, even like 1% of the time?
If so, you could set up a script that sometimes reproduces, and run it
in a loop until you get the erroneous behavior.  Of course, the script
would have to generate enough debugging output to be useful for
diagnosing the underlying problem, and you'd probably have a second
script controlling the loop which runs the first script, and then looks
for the anomalous output in the logs, to stop the loop.

Re: Crucial SSDs and Debian Bullseye

[Alexander V. Makartsev]

On 27.04.2022 17:17, Tom Browder wrote:
On Wed, Apr 27, 2022 at 07:08 Alexander V. Makartsev 
 wrote:

...

The laptop is a Toshiba C655D-S5136 Satellite.
The SSD is a Crucial MX500 1000GB 2.5 inch SSD.

Thanks, Alexander.

-Tom

Crucial MX500 is based on SM2258 controller IC from Silicon Motion.
In general, I usually select SSDs based on controller ICs from Phison. 
They are in my experience have better backward-compatibility with older 
hardware.
The make\brand of the SSD itself doesn't really matter, if you choose 
appropriately the rest of SSD parts (i.e. NAND type, bits per cell, etc)


There is an one workaround you should try:
Inside BIOS of the laptop, check if there is an option to switch between 
protocols in HDD or Chipset sections. They could be called "Legacy", 
"Native" and "AHCI".

Make sure to set it to "AHCI", which should be default for any SSDs.
Some SSDs will still work in "Legacy" mode, but it could cause a 
compatibility issues.


--
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀https://www.debian.org
⠈⠳⣄

Re: how are the dlbd images created?

[Thomas Schmitt]

Hi,

majid hussain wrote:
> was just curious, how are the debian dlbd images created?

By a package named debian-cd:

  https://tracker.debian.org/pkg/debian-cd


> and what percentage of the debian archive is used to gennerate them?

You may estimate from the .jigdo files which describe them.

  gunzip 

Re: email lacks sender address

[Haines Brown]

On Wed, Apr 27, 2022 at 01:42:05PM +0100, Brian wrote:
> On Wed 27 Apr 2022 at 08:05:46 -0400, Haines Brown wrote:

> > If I understand correctly, which is always in serious doubt, it is 
> > exim that constructs the Sender: line by combining /etc/mailname and 
> > $LOCALHOST. Is this so?
> 
> No. exim4 uses what is in /etec/mailname as the MAI FROM: (the envelope
> from).

Thanks for the clarification. 

> > These values are present:
> > 
> >   $ nano /etec/mailname
> >   lenin.histomat.net
> 
> lenin.histomat.net appears to be unrouteable. How a remote system would
> deal with that is anyone's guess.

I do not understand. What should /etc/mailname look like? I suspect it 
should simply be histomat.net and wonder how the host name got in 
there. I changed it to the latter value but still get 5.5.1 Protocol 
error from online email tester. Perhaps I need to restart networking.

Re: email lacks sender address

[Vincent Lefevre]

On 2022-04-27 09:36:22 -0400, Haines Brown wrote:
> On Wed, Apr 27, 2022 at 01:42:05PM +0100, Brian wrote:
> > On Wed 27 Apr 2022 at 08:05:46 -0400, Haines Brown wrote:
> 
> > > If I understand correctly, which is always in serious doubt, it is 
> > > exim that constructs the Sender: line by combining /etc/mailname and 
> > > $LOCALHOST. Is this so?
> > 
> > No. exim4 uses what is in /etec/mailname as the MAI FROM: (the envelope
> > from).
> 
> Thanks for the clarification. 
> 
> > > These values are present:
> > > 
> > >   $ nano /etec/mailname
> > >   lenin.histomat.net
> > 
> > lenin.histomat.net appears to be unrouteable. How a remote system would
> > deal with that is anyone's guess.
> 
> I do not understand. What should /etc/mailname look like?

In general, the FQDN of your machine. It does not need to be
resolvable, but if it isn't, you will probably need to use a
smarthost.

> I suspect it should simply be histomat.net

You may use it if you own the domain. Otherwise, I think that
this could lead to problems, with mail sent to the wrong place
(think of mail sent to root and mail sent to some external
histomat.net user).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: exim4 and oAuth

[Dan Ritter]

mike.junk...@att.net wrote: 
> I recently switch ISPs to Frontier.com and find that my emails aren't
> going out due to Frontier's insistence on using oAuth which as far as
> I can tell is beyond Exim4's capabilities.
> Feel free to contradict me if you know otherwise.
> I've seen one note suggesting that Mutt can do oAuth but find
> nothing in the docs confirming this nor how to make it so.
> Any pointers would be appreciated.

Not quite what you're asking for, but the voice of my experience
says: don't use any email service bundled with your ISP. Sooner
or later your ISP will change, and then you need to tell a
thousand friends and a dozen mailing lists to change to your new
address -- often without recourse to your old address.

Buy a domain name and use a third-party email service, or
(advanced case) run your own email servers. (Debian is great for
that.)

-dsr-

multiple systemd-nspawn container name resolution

[basti]

Hello,

i have setup multiple systemd-nspawn container with virtualEthernet=yes.
Inside the container systemd-networkd and systemd-resolved are enabled.
So far so good.

Is there a way to disable the 169.254... networking for systemd?
The problem is as followed:

ip r

169.254.0.0/16 dev ve-test3 proto kernel scope link src 169.254.144.44
169.254.0.0/16 dev ve-test2 proto kernel scope link src 169.254.38.46
169.254.0.0/16 dev ve-test proto kernel scope link src 169.254.80.104

So I only can ping test3.
The same problem is with name resolution.

best regards

Re: email lacks sender address

[Haines Brown]

On Wed, Apr 27, 2022 at 10:52:07AM -0400, Greg Wooledge wrote:
> On Wed, Apr 27, 2022 at 10:46:53AM -0400, Haines Brown wrote:
> > In exim4 condiguration I select smarthost.
> 
> Is your smarthost "mail.guardedhost.com"?

I don't understand. I thought the question in exim configuration 
referred to my own set up. I tell exim to use smart host for my 
outcgoing mail. The address mail.guardedhost.com is simply the mail 
serrver address to which I send outgoing mail.
 
> > So did you mean the 
> > recipient mail server must use smarthost?
> 
> That's total nonsense.  A smarthost is for relaying your outgoing mail.

My understanding is that the mail server to which I send mail 
understands SMTP.

Re: email lacks sender address

[Celejar]

On Wed, 27 Apr 2022 10:04:06 +0900
Byung-Hee HWANG   wrote:

> Dear Celejar,
> 
> Celejar  writes:
> 
> > On Tue, 26 Apr 2022 09:42:38 +0900
> > 황병희  wrote:
> >
> >> Dear Greg,
> >> 
> >> Greg Wooledge  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

Re: email lacks sender address

[Greg Wooledge]

On Wed, Apr 27, 2022 at 11:05:20AM -0400, Haines Brown wrote:
> If mailname (the value of /etc/mailname) is supposed to be my FQDN, 
> then that would be lenin.histomat.net
> 
>   $ hostname -f
>   lenin.histomat.net 
> 
>   $ nano /etc/mailname
>   lenin.histomat.net

 says:

  If your package needs to know what hostname to use on (for example)
  outgoing news and mail messages which are generated locally, you should
  use the file /etc/mailname. It will contain the portion after the
  username and @ (at) sign for email addresses of users on the machine
  (followed by a newline).

So if your /etc/mailname contains lenin.histomat.net then mail sent by
john on your system may(!) have a default(!) from/sender address of
j...@lenin.histomat.net.  Unless it's overridden.

If what you WANT is for your outgoing mail to appear to come from
j...@histomat.net then you should have histomat.net in that file instead.

The fact that lenin.histomat.net has no MX or A records in global DNS
means it's completely unsuitable for being the right-hand side of an
email address.  So, what you have now is clearly not correct.

> So should the value of /etc/mailname be a FQDN or simply a domain 
> name?

It should be what you WANT TO SEE on the right hand side of the @ sign
in auto-generated from/sender-type addresses in outgoing email.

In this entire thread I have yet to see you simply state what it is
that you WANT or EXPECT.

> If the latter, then the question is how my installion of the operating 
> system managed to get it wrong.

YOU ARE NOT USING DEBIAN SO WE DON'T KNOW!

As a *guess*, it probably used your hostname, which you gave it, as
the value of /etc/mailname.  There is no way it could know what you
want without asking, and there has been a recent trend among OS
installers to ask fewer questions, and to assume more things.

Of course, since we HAVE NO IDEA HOW YOUR OS'S INSTALLER WORKS, all
we can do is guess.

> During network setup I entered the 
> hostname lenin and domain name histomat.net. Or at least that was
> my intention. 

It probably decided to use that as your /etc/mailname.

If that's NOT WHAT YOU WANT, then CHANGE IT.

(Caveat: you can also override the enveloper sender address, the From:
header address, and so on, so that /etc/mailname becomes irrelevant.)

> In /etc/hosts I have the line:
> 
>   127.0.1.1   lenin.histomat.net  lenin

Irrelevant, except insofar as it verifies that you correctly typed your
desired hostname at some point.  Email certainly will not care.

Now, let's look at this domain name for a moment.

unicorn:~$ host histomat.net
histomat.net has address 216.239.138.216
histomat.net mail is handled by 10 postoffice.omnis.com.

unicorn:~$ host postoffice.omnis.com.
postoffice.omnis.com has address 216.239.133.242
postoffice.omnis.com has IPv6 address 2607:fe90:1:1::1c

The similarity in the two IPv4 addresses catches my attention.  It looks
like this histomat.net domain name is "owned by" (or at least handled by)
the same people who own/handle postoffice.omnis.com.

I'm guessing that person isn't you.  You don't seem to know enough to be
running an Internet domain.

So, that begs the question of why you think it's appropriate to announce
yourself as histomat.net in your outgoing communications.

Furthermore, we've seen evidence that you're using an outgoing mail relay
(not under your own control) which rejects your outgoing email if you
try to identify yourself as r...@lenin.histomat.net.  Would it also have
rejected r...@histomat.net?  Who knows.  Certainly not us, because you
haven't performed that test and told us the result.

This makes me wonder what envelope sender address(es) it WILL accept.
Knowing that would be incredibly useful.  It may be the single most
important piece of data you could possibly possess in this entire
scenario, as it will probably dictate everything there is to be dictated
about how you should configure your outgoing email.

Do you have any actual *instructions* or *documentation* that was
given to you by the histomat.net / postoffice.omnis.com administrators?
Something that could guide you toward setting up your outgoing email in
a way they will tolerate?  Or is it going to be 100% guesswork?

(Also, what is mail.guardedhost.com?  I still never saw an answer to that.)

Re: email lacks sender address

[Haines Brown]

On Wed, Apr 27, 2022 at 05:13:51PM +0200, Vincent Lefevre wrote:
> On 2022-04-25 11:39:01 -0400, Haines Brown wrote:
> > Incidentally, I get 
> > 
> >   $ hostname -A
> >   lenin-16.home
> > 
> > that's strange. Should be lenin.histomat.net
> 
> About this point, you should not use "hostname -A", but
> "hostname -f" (or "hostname --fqdn").
> 
> The -A option will just give you the FQDNs associated with
> configured network interfaces, if any; this isn't much useful.

Aha. Thanks
> 

Re: Crucial SSDs and Debian Bullseye

[Tom Browder]

On Wed, Apr 27, 2022 at 10:11 Keith Bainbridge 
wrote:

> Tom
>
> Did you remove the old drive and try the SSD using the installer?
>

I removed the old drive, installed the new SSD, then booted off a Debian
live dvd.

It never found the drive, so I may have killed it. I am twiddling my thumbs
until I can leave the house, drive to my storage unit and find my USB/SATA
external cable, drive to my church, get the laptop, bring it home,
uninstall the SSD, then try it hanging off my main Linux laptop (or my
Windows host ) just to see.

If either of those fail to see it, I’m afraid I toasted it. I don’t think
that will qualify for a return.

BTW, my last four SSDs have been Samsung—no issues at all.

-Tom

Re: Crucial SSDs and Debian Bullseye

[Vincent Lefevre]

On 2022-04-27 17:08:04 +0500, Alexander V. Makartsev wrote:
> I've never heard anything like that and I've worked with many
> consumer-grade SSDs.
> Usually all SSDs "just work". They may come pre-partitioned and
> pre-formatted, but this could be reconfigured with any standard utility
> programs.

Yes. FYI, when I had to change the SSD disk of my laptop,
I connected it via a SATA-USB adapter to repartition the
new disk and copy the data.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: Crucial SSDs and Debian Bullseye

[Vincent Lefevre]

On 2022-04-27 07:46:27 -0500, Tom Browder wrote:
> And for future reference, what brand of SSDs (and memory) do you use?

A few months ago, when I looked at what was recommended to change
the SSD disk of my laptop, I found that the Samsung 870 EVO 1TB
was generally recommended. So this is what I chose, and it works
perfectly. And I got around 10× to 200× raw speedups!

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: file born 30 seconds after its creation on ext4 - bug?

[Vincent Lefevre]

On 2022-04-27 09:26:50 -0400, Greg Wooledge wrote:
> Are you able to reproduce the issue at all, even like 1% of the time?

In the past 11 years, I may have ran the script (and looked at the
output just after that) hundreds or thousands of times; the commands
to look at the output have been in my shell history for 6 years.

This was the first time I noticed such an issue. But if this is a
kernel bug, it may be a new bug.

> If so, you could set up a script that sometimes reproduces, and run it
> in a loop until you get the erroneous behavior.

I'll try to do that.

> Of course, the script would have to generate enough debugging output
> to be useful for diagnosing the underlying problem, and you'd
> probably have a second script controlling the loop which runs the
> first script, and then looks for the anomalous output in the logs,
> to stop the loop.

The first thing would be to try to reproduce the issue without
much debug info (in order to get the same system calls as the ones
generated by my normal script).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: how are the dlbd images created?

[majid hussain]

hi sir Thomas,

thank you for responding so promptly :)
may you have a great day :)
Majid Hussain

On 27/04/2022 14:29, Thomas Schmitt wrote:

Hi,

majid hussain wrote:

was just curious, how are the debian dlbd images created?

By a package named debian-cd:

   https://tracker.debian.org/pkg/debian-cd



and what percentage of the debian archive is used to gennerate them?

You may estimate from the .jigdo files which describe them.

   gunzip 

Re: email lacks sender address

[Haines Brown]

On Wed, Apr 27, 2022 at 08:28:27AM -0400, Greg Wooledge wrote:
> On Wed, Apr 27, 2022 at 08:05:46AM -0400, Haines Brown wrote:
> > If I understand correctly, which is always in serious doubt, it is 
> > exim that constructs the Sender: line by combining /etc/mailname and 
> > $LOCALHOST. Is this so?
> > 
> > These values are present:
> > 
> >   $ nano /etec/mailname
> >   lenin.histomat.net
> 
> Obvious typo.  This means you are not pasting results directly from a
> terminal into an email.  Instead, you're re-typing them, and making
> tons of errors in the process.  That makes it super hard to know what
> is actually real.

I apologize for the errors. I had just arisen and not yet had my 
coffe. Also as I approach 90 I make more typos. My eyesight is not so 
sharp and my fingerwork don't behave as well.

> > However I'm not clear whether the field is empthy or that what us 
> > in it field is not owned by me. I have popcorn installed, and it has 
>
> popcon, not popcorn.
> 
> > root send a priodidic message. The mail server does not recognize 
> > the r...@histomats.net address. It sends me this message:
> 
> *Which* mail server?  Who is "it"?

A company named Omnis provides me with an email account. I presume it 
fumctions as a mail server and does my own machine. The error message 
below came from the former. I simply pasted it.

> >   A message that you sent could not be delivered to one or more 
> >   of >   its
> >   recipients. This is a permanent error. The following address(es) failed:
> > 
> > sur...@popcon.devuan.org
> > host mail.guardedhost.com [216.239.133.245]
> > SMTP error from remote mail server after pipelined sending data block:
> > 553 5.7.1 : Sender address rejected:
> > not owned by user bro...@historicalmaterialism.info
> > 
> > Reporting-MTA: dns; lenin.histomat.net

> So, this message was generated by your own MTA running on your own
> computer, after the message was rejected by the receiving MTA.

No. This the mesage sent by the receiving MTA, Omnis.

> There are many things I do not understand in this error message.  For
> starters, who or what is "host mail.guardedhost.com [216.239.133.245]"
> and what do they have to do with anything?

That is the address, less a port number, required by the Omnis server 
for incoming email messages.

> It sounds like something on *your* end.  Maybe you've configured your
> MTA to use a smarthost,

Yes, I did. In exim4 confguration I selected "mail sent by smarthost; 
received via SMTP or fetchmail". I assume the Omnis mail server 
accepts mail using the SMTP protocol.

> and mail.guardedhost.com is your smarthost?

No, that is recipient address provided by Omnis less a port 
number. I send outgoing email to it.
 
> And if so, it's refusing to relay mail from you as long as you claim
> to be r...@histomat.net instead of bro...@historicalmaterialism.info
> or something.

Yes, so it appears. However, popcon has always sent periodic mail 
presumably from root without this problem.

> Also, you appear not to be using Debian, so... all bets are off.

Don't my headers show that I'm using Devuan? Devuan is simply Debian 
without systemd.

Re: email lacks sender address

[Greg Wooledge]

On Wed, Apr 27, 2022 at 10:46:53AM -0400, Haines Brown wrote:
> In exim4 condiguration I select smarthost.

Is your smarthost "mail.guardedhost.com"?

> So did you mean the 
> recipient mail server must use smarthost?

That's total nonsense.  A smarthost is for relaying your outgoing mail.

Re: Crucial SSDs and Debian Bullseye

[Dan Ritter]

Tom Browder wrote: 
> On Wed, Apr 27, 2022 at 06:42 Christian Britz  wrote:
> ...
> 
> I have seem some indications on the web though, which suggest there
> > might be an ISO image for updating the drive too. What is the exact
> > model name?
> >
> 
> Crucial MX500 1000GB 2.5-INCH SOLID STATE DRIVE


I have dozens of these in service as SATA disks, no special
firmware has ever been used. Completely plug and play.

-dsr-

Re: email lacks sender address

[Haines Brown]

On Wed, Apr 27, 2022 at 03:31:05PM +0100, Brian wrote:
> On Wed 27 Apr 2022 at 15:38:21 +0200, to...@tuxteam.de wrote:
> 
> > On Wed, Apr 27, 2022 at 01:42:05PM +0100, Brian wrote:
> > 
> > [...]
> > 
> > > lenin.histomat.net appears to be unrouteable. How a remote system would
> >^^^
> > > deal with that is anyone's guess.
> > 
> > unresolvable (i.e. there's no (MX) DNS record "out there" for it) is what
> > you want to say?
> 
> I did mean that. Thanks. OTOH, histomat.net is resolvable.

If mailname (the value of /etc/mailname) is supposed to be my FQDN, 
then that would be lenin.histomat.net

  $ hostname -f
  lenin.histomat.net 

  $ nano /etc/mailname
  lenin.histomat.net

True, an MX record refers to a domain name and so I suppose can make 
no sense of a domain prepended with a hostname. 

So should the value of /etc/mailname be a FQDN or simply a domain 
name?

If the latter, then the question is how my installion of the operating 
system managed to get it wrong. During network setup I entered the 
hostname lenin and domain name histomat.net. Or at least that was
my intention. 

In /etc/hosts I have the line:

  127.0.1.1   lenin.histomat.net  lenin

Re: multiple systemd-nspawn container name resolution

[john doe]

On 4/27/2022 4:29 PM, basti wrote:


Hello,

i have setup multiple systemd-nspawn container with virtualEthernet=yes.
Inside the container systemd-networkd and systemd-resolved are enabled.
So far so good.

Is there a way to disable the 169.254... networking for systemd?
The problem is as followed:

ip r

169.254.0.0/16 dev ve-test3 proto kernel scope link src 169.254.144.44
169.254.0.0/16 dev ve-test2 proto kernel scope link src 169.254.38.46
169.254.0.0/16 dev ve-test proto kernel scope link src 169.254.80.104

So I only can ping test3.
The same problem is with name resolution.



Not realy an answer, Systemd has also a mailing list! :)

--
John Doe

Re: Crucial SSDs and Debian Bullseye

[Christian Britz]

On 2022-04-27 14:46 UTC+0200, Tom Browder wrote:

> And for future reference, what brand of SSDs (and memory) do you use?

Currently I use what is built in to my laptop, a SK Hynix SSD. The Raspi
home server is connected to a traditional hard disk.

In the past I had a Samsung EVO SSD for home use. It worked out of the
box. I do not know if fit your needs for the commercial grade server
which you want to install.

I can not give any current recommendations for memory, sorry.

-- 
http://www.cb-fraggle.de

Re: email lacks sender address

[tomas]

On Wed, Apr 27, 2022 at 01:42:05PM +0100, Brian wrote:

[...]

> lenin.histomat.net appears to be unrouteable. How a remote system would
   ^^^
> deal with that is anyone's guess.

unresolvable (i.e. there's no (MX) DNS record "out there" for it) is what
you want to say?

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: Crucial SSDs and Debian Bullseye

[Thomas Schmitt]

Hi,

Christian Britz wrote:
> I found it. https://www.crucial.com/support/ssd-support/mx500-support,
> there seem to be two versions. Click on the appropriate blue button, a
> zip file will be downloaded which contains the ISO. Apparently this can
> not be written to USB.

Both of them look like they shall boot where Debian ISOs can boot.

Boot equipment for legacy BIOS is ISOLINUX. For EFI it is GRUB2.
Both are exposed for optical media and for hard-disk-like media like in
Debian's layout for i386 or amd64. (Once invented for Fedora.)

Besides the boot equipment i see only two significant files
  -r--r--r--1 0011019792 Oct 30  2018 '/boot/corepure64.gz'
  -r--r--r--1 00 4491536 Oct 30  2018 '/boot/vmlinuz64'
or in the younger ISO
  -r--r--r--1 0011821309 Aug 17  2020 '/boot/corepure64.gz'
  -r--r--r--1 00 4491536 Aug 17  2020 '/boot/vmlinuz64'
A kernel and its initrd ?

Whatever one might think about their firmware installation demands,
at least they seem to be not locked into MS-Windows. :))


Have a nice day :)

Thomas

Re: Crucial SSDs and Debian Bullseye

[Anssi Saari]

Tom Browder  writes:

> On Wed, Apr 27, 2022 at 07:08 Alexander V. Makartsev  
> wrote:
> ...
>
> The laptop is a Toshiba C655D-S5136 Satellite.
> The SSD is a Crucial MX500 1000GB 2.5 inch SSD.

Some quick specs from
https://www.cnet.com/reviews/toshiba-satellite-c655d-review/:

Price as reviewed   $398
Processor   1.5 GHz AMD Fusion E-240 Dual Core
Memory  3GB, 667MHz DDR3 RAM
Hard drive  250GB 5,400rpm
Chipset ID1510 + SB800
GraphicsAMD Radeon HD 6310
Operating systemWindows 7 Home Premium (64-bit)
Dimensions (WD) 15 x 9.8 inches
Height  1.1-1.5 inches
Screen size (diagonal)  15.6 inches
System weight / Weight  5.1 / 5.8 pounds
with AC adapter

Looks like the SB800 south bridge supports SATA 3.0 6Gb/s interfaces so
it doesn't seem like it's the problem here. But I have no idea what the
problem could be, other than a faulty drive.

Re: Crucial SSDs and Debian Bullseye

[Tom Browder]

On Wed, Apr 27, 2022 at 8:48 AM Anssi Saari  wrote:
> Tom Browder  writes:
...
> Looks like the SB800 south bridge supports SATA 3.0 6Gb/s interfaces so
> it doesn't seem like it's the problem here. But I have no idea what the
> problem could be, other than a faulty drive.

Well, as I said originally, I could have fried it, but I hope not. I
think I will have to find my USB/SATA cable.

Thanks.

-Tom

Re: email lacks sender address

[Vincent Lefevre]

On 2022-04-27 08:05:46 -0400, Haines Brown wrote:
> If I understand correctly, which is always in serious doubt, it is 
> exim that constructs the Sender: line by combining /etc/mailname and 
> $LOCALHOST. Is this so?

On my machine that uses exim (used to send this mail), exim does not
add a "Sender:" line. The exim4(8) man page says for the -f option:

  Processes running  as  root  or  the  Exim  user  are  always
  trusted. Other trusted users are defined by the trusted_users
  or trusted_groups options. In the absence of -f,  or  if  the
  caller  is  not trusted, the sender of a local message is set
  to the caller's login name at the default qualify domain.

But if you set use_envelope_from in Mutt, the -f option will be
used (see OPTENVFROM in sendlib.c).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: email lacks sender address

[Brian]

On Wed 27 Apr 2022 at 15:38:21 +0200, to...@tuxteam.de wrote:

> On Wed, Apr 27, 2022 at 01:42:05PM +0100, Brian wrote:
> 
> [...]
> 
> > lenin.histomat.net appears to be unrouteable. How a remote system would
>^^^
> > deal with that is anyone's guess.
> 
> unresolvable (i.e. there's no (MX) DNS record "out there" for it) is what
> you want to say?

I did mean that. Thanks. OTOH, histomat.net is resolvable.

Re: email lacks sender address

[Haines Brown]

On Wed, Apr 27, 2022 at 04:26:09PM +0200, Vincent Lefevre wrote:
> On 2022-04-27 09:36:22 -0400, Haines Brown wrote:
> > On Wed, Apr 27, 2022 at 01:42:05PM +0100, Brian wrote:
> > > On Wed 27 Apr 2022 at 08:05:46 -0400, Haines Brown wrote:

> > Thanks for the clarification. 
> > 
> > > > These values are present:
> > > > 
> > > >   $ nano /etec/mailname
> > > >   lenin.histomat.net
> > > 
> > > lenin.histomat.net appears to be unrouteable. How a remote system would
> > > deal with that is anyone's guess.

> > I do not understand. What should /etc/mailname look like?

The reason for my question is that I believe this is the mailname that 
I've always used (except for changing hostname) without any problem.

  $ hostname -f
  lenin.histomat.net

> In general, the FQDN of your machine. It does not need to be
> resolvable, but if it isn't, you will probably need to use a
> smarthost.

In exim4 condiguration I select smarthost. So did you mean the 
recipient mail server must use smarthost?

Re: Crucial SSDs and Debian Bullseye

[Keith Bainbridge]

Tom

Did you remove the old drive and try the SSD using the installer?



On 27 April 2022 11:06:20 am UTC, Tom Browder  wrote:
>I am trying to replace the original hard drive on an old Toshiba laptop
>with a 1 TB SSD from Crucial. (I had recently successfully done that in an
>old Dell Latitude and had no problems.)
>
>I first did a clean install of Debian 11 on the old drive to ensure the
>laptop works okay. Then I installed the new SSD and it can't find the
>drive. From what I can find at Crucial, I need to install their Storage
>Executive program on a Windows host, hook up the SSD to a USB/SATA
>connector on that host, and configure or install the firmware onto the SSD.
>
>I was foolish not to have researched their SSD use on a Linux host, but I
>got lulled into their "upgrade your computer" site that told me the exact
>models that were hardware-compatible.
>
>Of course I may have fried the SSD, but I am fairly confident that the
>device is operable.
>
>Suggestions are greatly appreciated.
>
>Best regards,
>
>-Tom

Re: how are the dlbd images created?

[Andrew M.A. Cater]

On Wed, Apr 27, 2022 at 03:23:15PM +0100, majid hussain wrote:
> hi sir Thomas,
> 
> thank you for responding so promptly :)
> may you have a great day :)
> Majid Hussain
> 
> On 27/04/2022 14:29, Thomas Schmitt wrote:
> > Hi,
> > 
> > majid hussain wrote:
> > > was just curious, how are the debian dlbd images created?
> > By a package named debian-cd:
> > 
> >https://tracker.debian.org/pkg/debian-cd
> > 
> > 
> > > and what percentage of the debian archive is used to gennerate them?
> > You may estimate from the .jigdo files which describe them.
> > 
> >gunzip  > 
> > The total size of the ISO image and thus roughly of the included packages
> > is given by line
> ># Image size 48245475328 bytes
> > I.e. 45 GiB. The number of packages listed is a bit higher than 29,000.
> > 
> > In debian-11.3.0-amd64-DLBD-2.jigdo i see
> ># Image size 35798159360 bytes
> > 33 GiB and nearly 30,000 packages.
> > I guess that few packages are excluded from the installation media.
> > 
> > 
> > Have a nice day :)
> > 
> > Thomas
> > 

So: the size for the first DVD, for example, is calculated to be 4.0GB
and there's a script which puts as many packages as possible for a full
system with graphics to fit size exactly 4GB.

Thereafter, packages get assigned to DVD2, DVD3 etc. partly by popularity
and partly by "what fits" as far as I understand it. Most people will never
need more than the first 3 DVDs which is why we only supply the first three
as downloadable images, and the rest as .jigdo files.

This means that the size of the cdimages.debian.org mirror of media remains
manageable now.

dlbd - the same script from debian-cd makes the dlbd image. dlbd size allows
you many DVDs: dlbd1 and dlbd2 together probably contain >90% of what any
user would normally install at one time. Obviously - these are very large 
images - we don't store them on the mirrors for space reasons and only provide
.jigdo files go generate them.

Congratulations, however, you're the first person I've come across who actually
gains benefit from the dlbd and has reported such: I'm pleased because it 
makes the effort of generating them and (potentially) testing them worthwhile
because there is a real user out there who uses them.

I don't think we bother generating them locally and testing the dlbd images with
every point release so you may be one of the few people to ever report
installing from these iamges.

With every good wish,

Andy Cater

[Who works with Steve and Andy (and the other testers) of the Debian media/CD
images team for every point release.]

> 

Re: email lacks sender address

[Vincent Lefevre]

On 2022-04-25 11:39:01 -0400, Haines Brown wrote:
> Incidentally, I get 
> 
>   $ hostname -A
>   lenin-16.home
> 
> that's strange. Should be lenin.histomat.net

About this point, you should not use "hostname -A", but
"hostname -f" (or "hostname --fqdn").

The -A option will just give you the FQDNs associated with
configured network interfaces, if any; this isn't much useful.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: email lacks sender address

[Brian]

On Wed 27 Apr 2022 at 11:29:17 -0400, Greg Wooledge wrote:

> On Wed, Apr 27, 2022 at 11:05:20AM -0400, Haines Brown wrote:

[...]
 
> > In /etc/hosts I have the line:
> > 
> >   127.0.1.1   lenin.histomat.net  lenin
> 
> Irrelevant, except insofar as it verifies that you correctly typed your
> desired hostname at some point.  Email certainly will not care.

Not entirely. Exim would use lenin.histomat.net as the (E)HELO.
A smaarthost wouls probably not care as it has authenticated
the sender. So, nothing to worry about.

-- 
Brian.

Re: email lacks sender address

[Jonathan Dowland]

On Wed, Apr 27, 2022 at 10:37:28AM -0400, Haines Brown wrote:

Don't my headers show that I'm using Devuan? Devuan is simply Debian
without systemd.


And any bugs they have introduced. We cannot handle support for Devuan
because we are not responsible for what they release.

--
Please do not CC me for listmail.

  Jonathan Dowland
✎j...@debian.org
   https://jmtd.net

Re: Graphics::Magick

[Ulf Volmer]

On 27.04.22 14:54, mick crane wrote:


would result in outlines of 2 rectangles overlaid on white.
but with bookworm same thing results in 2 rectangles filled with black.
to get same result have to change to
$bg->Draw(primitive=>'rectangle',stroke=>'red',points=>"100,100 
980,980",fill=>'false');


Is this because bookworm is work in progress ?


No, I think there is a change upstream. I have the same behavior in my 
fedora box.


Best regards
Ulf

HTTP Proxy

[Larry Martin]

I am installing Debian 11 from a single CD.  My plan was to complete the 
install via the internet.  
I am using my home router IP address 192.168.1.0 device number 45.  
However I have no idea about what to specify as an HTTP proxy.  
I have tried a couple of options but when Debian tries to connect it fails.
Communications is my weak point, so basic advice would be appreciated.

Larry

Thunderbird importeren

[hanbenes]

Wie weet een oplossing voor het volgende:
Ik wil de email mappen uit een eerdere Linux Thunderbird installatie importeren 
in de huidige Debian Thunderbird installatie. Daarvoor heb ik de hele directory 
.thunderbird gecopieerd naar de plek waar deze hoort te staan. Deze methode 
werkte in eerdere situaties prima, bij de eerste keer openen van de nieuwe 
Thunderbird werd het meteen al goed ingelezen en stond alles al goed. Nu echter 
negeert Thunderbird de hele directory alsof deze helemaal niet bestaat. Iemand 
een idee wat er hier mis gaat?
Groeten,Han Benes

Verzonden met [ProtonMail](https://protonmail.com/) beveiligde e-mail.

Re: HTTP Proxy

[Brian]

On Wed 27 Apr 2022 at 12:23:12 -0400, Larry Martin wrote:

> I am installing Debian 11 from a single CD.  My plan was to complete the 
> install via the internet.  
> I am using my home router IP address 192.168.1.0 device number 45.  
> However I have no idea about what to specify as an HTTP proxy.  
> I have tried a couple of options but when Debian tries to connect it fails.
> Communications is my weak point, so basic advice would be appreciated.

I have always left the answer to that question as blank. Are you sure
you need a proxy?

-- 
Brian.

Re: HTTP Proxy

[Greg Wooledge]

On Wed, Apr 27, 2022 at 12:23:12PM -0400, Larry Martin wrote:
> I am installing Debian 11 from a single CD.  My plan was to complete the 
> install via the internet.  
> I am using my home router IP address 192.168.1.0 device number 45.  

I have no idea what "device number 45" means here.

> However I have no idea about what to specify as an HTTP proxy.  
> I have tried a couple of options but when Debian tries to connect it fails.
> Communications is my weak point, so basic advice would be appreciated.

Try without any kind of HTTP proxy first.  Most routers do not offer
an HTTP proxy.  If you haven't set one up yourself, and if you aren't
part of a company that has set one up, and you don't live in China
where the government has set one up, things should just work.

Even if you can't manage to get Internet connectivity during the
installation, you may still be able to install things using apt (or
similar commands) after the installation has finished.

If things don't work out, you'll need to provide more detail.  Are you
using ethernet, or wireless?  Which "single CD" image did you use --
the official netinst one, or the netinst with non-free firmware?  Some
network interfaces will require non-free firmware to work.  Adding
that to your system post-installation is possible, but it will require
some legwork.

Re: HTTP Proxy

[Dan Ritter]

Larry Martin wrote: 
> I am installing Debian 11 from a single CD.  My plan was to complete the 
> install via the internet.  
> I am using my home router IP address 192.168.1.0 device number 45.  
> However I have no idea about what to specify as an HTTP proxy.  
> I have tried a couple of options but when Debian tries to connect it fails.
> Communications is my weak point, so basic advice would be appreciated.


You almost certainly do not need an HTTP proxy. Leave it blank.

-dsr-

Re: Crucial SSDs and Debian Bullseye

[Felix Miata]

Tom Browder composed on 2022-04-27 10:37 (UTC-0500):

> I removed the old drive, installed the new SSD, then booted off a Debian
> live dvd.

> It never found the drive, so I may have killed it. 

Killed it how? My Linux-only 120G & 240G MX500s were mere PNP, the smaller
originally setup in a tower, then moved to a Toshiba Satellite A205-S5831 laptop
with no changes needed except for NIC MAC.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

how are the dlbd images created?

[majid hussain]

hi all,

was just curious, how are the debian dlbd images created?

I find them very useful my connection is not the most stablest of things
currently.

so having an option to install offline is most wonderful

and what percentage of the debian archive is used to gennerate them?

thank you for reading my questions.

sorry for spelling errors I am blind and use orca the assistive screen
reader.

Majid

Re: Crucial SSDs and Debian Bullseye

[Tom Browder]

On Wed, Apr 27, 2022 at 06:42 Christian Britz  wrote:
...

I have seem some indications on the web though, which suggest there
> might be an ISO image for updating the drive too. What is the exact
> model name?
>

Crucial MX500 1000GB 2.5-INCH SOLID STATE DRIVE

Thanks, Christian

-Tom

Re: Recommendations for a home server running Debian Bullseye (11)?

[Will Mengarini]

* Tom Browder  [22-04/27=We 05:50 -0500]:
> I really appreciate all the advice, but I am
> not going to build from scratch again [...].

Just in case anybody's discouraged that the OP won't build from
scratch, I just want to say /I/ found this thread valuable too.

Where do you all buy parts?  Alternatives to Newegg?

-- 
 Will Mengarini  
 Free software: the Source will be with you, always.

Re: file born 30 seconds after its creation on ext4 - bug?

[Vincent Lefevre]

On 2022-04-27 11:39:17 +0200, Thomas Schmitt wrote:
> If it has indeed to do with the CPU cache then a particular cache would have
> delayed its writing to RAM for 30 seconds but would have served its own CPU
> with the full results of file system driver and virtual memory activities
> around the new file. No inconsistent partial results would have been written
> to page cache in RAM which would have caused protests during your attempts
> to see the file.
> 
> But i deem it unlikely that the kernel threads which operated filesystem and
> virtual memory are (nearly) always running on the same CPU cache which is
> not shared with all other CPU cores.
> Further, if the memory operations were just pending in some secluded cache
> why does the inode then bear the time when that cache would finally have
> released its content to the wider accessible RAM.

I was thinking of a potentially specific FS cache. But perhaps this
is not related to the CPU at all. It could be that a potential bug
(either in the kernel code or in the compiler) would affect some
system calls but not others. So, the ">> $out" done in the script
would work, but not other kinds of operations on $out.

In the strace output of the script, I get

  openat(AT_FDCWD, "….out", O_WRONLY|O_CREAT|O_TRUNC, 0666) = 3

when the file is created, then

  openat(AT_FDCWD, "….out", O_WRONLY|O_CREAT|O_APPEND, 0666) = 3

for the commands that append to this file, and one with

  openat(AT_FDCWD, "….out", O_WRONLY|O_CREAT|O_APPEND, 0666 
  <... openat resumed>)  = 3

about 30 seconds later.

So, perhaps there were no issues with openat, but when reading
the directory, the file could not be found because some internal
structures might have been incomplete.

This doesn't explain why the birth time of the file was 30 seconds
late. But according to fs/ext4/inode.c, inode handling seems a bit
complex.

To the question why this doesn't occur every time or at least more
often: there might have been an interrupt at the wrong place, or
something like that.

> If i was in your situation, i'd add diagnostic messages to the script in the
> hope (or fear) that the glitch happens again.

I think that a better thing would be to write a specific test script
doing file creations and writes in append mode, that on many files,
and see at the end whether some birth times were unexpectedly late.

> Especially the inode numbers during and after the script run would be
> interesting.

But note that getting other information about the file during the
script could void the effects of a potential bug.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Crucial SSDs and Debian Bullseye

[Tom Browder]

I am trying to replace the original hard drive on an old Toshiba laptop
with a 1 TB SSD from Crucial. (I had recently successfully done that in an
old Dell Latitude and had no problems.)

I first did a clean install of Debian 11 on the old drive to ensure the
laptop works okay. Then I installed the new SSD and it can't find the
drive. From what I can find at Crucial, I need to install their Storage
Executive program on a Windows host, hook up the SSD to a USB/SATA
connector on that host, and configure or install the firmware onto the SSD.

I was foolish not to have researched their SSD use on a Linux host, but I
got lulled into their "upgrade your computer" site that told me the exact
models that were hardware-compatible.

Of course I may have fried the SSD, but I am fairly confident that the
device is operable.

Suggestions are greatly appreciated.

Best regards,

-Tom

Re: email lacks sender address

[Haines Brown]

David. thanks for hanging in with me!

On Tue, Apr 26, 2022 at 03:23:17PM -0500, David Wright wrote:

> Do you know why mutt is adding a Sender: line to your emails?
> Did you ask it to, or have you been asked to by someone else?

No, I didn't ask mutt to add a Sender: line and I do not know what 
evidence there it that it is doing so. 

If I understand correctly, which is always in serious doubt, it is 
exim that constructs the Sender: line by combining /etc/mailname and 
$LOCALHOST. Is this so?

These values are present:

  $ nano /etec/mailname
  lenin.histomat.net

  $ echo $LOGNAME
  haines

> But don't confuse the specific "Sender:" field in the header with the
> conversational use of "sender" to talk about the person/software/system
> that's sending the email. (The emails you send here do not contain
> a Sender: field.)

Understood. But my impression is not that there is no Sender: field, 
but that it is empty (<>).

However I'm not clear whether the field is empthy or that what us 
in it field is not owned by me. I have popcorn installed, and it has 
root send a priodidic message. The mail server does not recognize 
the r...@histomats.net address. It sends me this message:

  A message that you sent could not be delivered to one or more of its
  recipients. This is a permanent error. The following address(es) failed:

sur...@popcon.devuan.org
host mail.guardedhost.com [216.239.133.245]
SMTP error from remote mail server after pipelined sending data block:
553 5.7.1 : Sender address rejected:
not owned by user bro...@historicalmaterialism.info

Reporting-MTA: dns; lenin.histomat.net

Action: failed
Final-Recipient: rfc822;sur...@popcon.devuan.org
Status: 5.0.0
Remote-MTA: dns; mail.guardedhost.com
Diagnostic-Code: smtp; 553 5.7.1 : Sender
address rejected: not owned by user bro...@historicalmaterialism.info

The address hai...@histomat.net is owned by 
bro...@historicalmaterialism.info. Omnis mail server never had a 
problem with r...@histomat.net before.

> A typical, straightforward, email contains a From: field, which is the
> email address of the sender (not Sender), as opposed to the recipient
> (ie the To: field). Again, typically, straightforwardly, the From:
> and To: fields will be used to generate the envelope's MAIL FROM
> and RCPT TO addresses.

Are you saying that the envelope hss MAIL FROM and RCPT TO lines and a 
typical email has From: and To: lines? Does this leave it to mutt 
to construct the Sender: line?

> > First, the implication seems to be that an empty Sender: line means 
> > that mutt is falling down on the job and for some reason this past 
> > week ceasad to provide a value for the Sender: line in the header of 
> > the some mail it sent to exim. So is the obvious thing to do is fix 
> > mutt? Since I've been using the same mutt configuration for years, its 
> > not a configuration problem but samage to mutt. Looks like a reinstall 
> > and slow reconstruction of its confirturation. 
> 
> You have to tell mutt what to use. It can't assume that your $LOGNAME
> and /etc/mailname are, taken together, going to generate a satisfactory
> From: field for an email.

And yet it has access to those values. Or should /etc/mailname be 
histomat.net rather tnan lenin.histomat.net?

> What did Omnis actually say, literally?
> 
> In your OP, you wrote "554 5.7.1 Empty Sender Address
>   is prohibited through this server; from=<>"

> (Should I guess that that's Omnis speaking?)

Yes

> I have assumed that "554 5.7.1 Empty Sender Address" is the actual
> response, and it's capitalised, whereas "is prohibited through this
> server" is their gloss, uncapitalised. So I don't think it's saying
> anything about a Sender: field, rather, the MAIL FROM address.

Oh! This hadn't occurred to me. The MAIL FROM belongs to the envelope. 

> Well, the simple way, which is why I use it, is to put:
> 
>   set envelope_from_address="someuser@somedomain"
>   set use_envelope_from
> 
> into mutt's configuration file (always assuming it gets read!), as
> I wrote before. (At this point, I didn't have an inkling of Sender:
> being involved, and hope that is still true.)

I checked, and the muttrc does get read. I put these two lines into 
it:

  set envelope_from_address="hai...@histomat.net"
  set use_envelope_from

If these take immediae effect (without restarting mutt), then they did 
not help. The online email testing utility still returns:

  Unverified address: postoffice.omnis.com said: 521 5.5.1 Protocol error 
  Error in communication with postoffice.omnis.com

What happened to the objection raised by someone tnat the these lines 
should have a binary value?

It strikes me that the addition of these lines are just a work around 
for the problem that the envelopoe's MAIL FROM line is 
unacceptable.

> The reason /I/ have to do that is that submission to my ISP requires
> an email address belonging to them. I've never used my ISP's email
> system beyond 

Re: Crucial SSDs and Debian Bullseye

[Tom Browder]

On Wed, Apr 27, 2022 at 07:08 Alexander V. Makartsev 
wrote:
...

The laptop is a Toshiba C655D-S5136 Satellite.
The SSD is a Crucial MX500 1000GB 2.5 inch SSD.

Thanks, Alexander.

-Tom

Re: email lacks sender address

[Greg Wooledge]

On Wed, Apr 27, 2022 at 08:05:46AM -0400, Haines Brown wrote:
> If I understand correctly, which is always in serious doubt, it is 
> exim that constructs the Sender: line by combining /etc/mailname and 
> $LOCALHOST. Is this so?
> 
> These values are present:
> 
>   $ nano /etec/mailname
>   lenin.histomat.net

Obvious typo.  This means you are not pasting results directly from a
terminal into an email.  Instead, you're re-typing them, and making
tons of errors in the process.  That makes it super hard to know what
is actually real.

>   $ echo $LOGNAME
>   haines

You mentioned $LOCALHOST before, and now suddenly it's $LOGNAME.

> However I'm not clear whether the field is empthy or that what us 
> in it field is not owned by me. I have popcorn installed, and it has 

popcon, not popcorn.

> root send a priodidic message. The mail server does not recognize 
> the r...@histomats.net address. It sends me this message:

*Which* mail server?  Who is "it"?

>   A message that you sent could not be delivered to one or more of its
>   recipients. This is a permanent error. The following address(es) failed:
> 
> sur...@popcon.devuan.org
> host mail.guardedhost.com [216.239.133.245]
> SMTP error from remote mail server after pipelined sending data block:
> 553 5.7.1 : Sender address rejected:
> not owned by user bro...@historicalmaterialism.info
> 
> Reporting-MTA: dns; lenin.histomat.net

So, this message was generated by your own MTA running on your own
computer, after the message was rejected by the receiving MTA.

There are many things I do not understand in this error message.  For
starters, who or what is "host mail.guardedhost.com [216.239.133.245]"
and what do they have to do with anything?

unicorn:~$ host -t mx popcon.devuan.org
popcon.devuan.org mail is handled by 10 mx.devuan.org.
unicorn:~$ host mx.devuan.org
mx.devuan.org has address 141.95.83.167

There's no mention of mail.guardedhost.com or 216.239.133.245 in DNS
at all.

It sounds like something on *your* end.  Maybe you've configured your
MTA to use a smarthost, and mail.guardedhost.com is your smarthost?
And if so, it's refusing to relay mail from you as long as you claim
to be r...@histomat.net instead of bro...@historicalmaterialism.info
or something.

Also, you appear not to be using Debian, so... all bets are off.

Graphics::Magick

[mick crane]

with bullseye previous Perl script

use Graphics::Magick;

my $bg=Graphics::Magick->new;
$bg->Set(size=>"1000"."x"."1000");
$bg->ReadImage('xc:white');
$bg->Draw(primitive=>'rectangle',stroke=>'red',points=>"100,100 
980,980");
$bg->Draw(primitive=>'rectangle',stroke=>'blue',points=>"20,20 
400,400");

my $filename = "test.png";
$bg->Write(filename=>$filename);
$bg=undef;

would result in outlines of 2 rectangles overlaid on white.
but with bookworm same thing results in 2 rectangles filled with black.
to get same result have to change to
$bg->Draw(primitive=>'rectangle',stroke=>'red',points=>"100,100 
980,980",fill=>'false');


Is this because bookworm is work in progress ?

regards

mick
--
Key ID4BFEBB31

Re: Recommendations for a home server running Debian Bullseye (11)?

[Tom Browder]

On Tue, Apr 26, 2022 at 08:49 Christian Britz  wrote:
...

I really appreciate all the advice, but I am not going to build from
scratch again (but I will encourage my grandchildren if they ever get
interested).  In that vein, the link on the modern build-your-own case
(Fractal Design) from David was very helpful--thanks!

So, if I need a new in-home server, I think I will go the Dell route. The
multiple easy in/out drives capability is just what I need for my
redundancy case (and ease of use) and assume I can add SSDs from my own
sources instead.

Best regards, and thanks again to all of you,

-Tom

Re: Crucial SSDs and Debian Bullseye

[Alexander V. Makartsev]

On 27.04.2022 16:06, Tom Browder wrote:
I am trying to replace the original hard drive on an old Toshiba 
laptop with a 1 TB SSD from Crucial. (I had recently successfully done 
that in an old Dell Latitude and had no problems.)


I first did a clean install of Debian 11 on the old drive to ensure 
the laptop works okay. Then I installed the new SSD and it can't find 
the drive. From what I can find at Crucial, I need to install their 
Storage Executive program on a Windows host, look up the SSD to a 
USB/SATA connector on that host, and configure or install the firmware 
onto the SSD.


I've never heard anything like that and I've worked with many 
consumer-grade SSDs.
Usually all SSDs "just work". They may come pre-partitioned and 
pre-formatted, but this could be reconfigured with any standard utility 
programs.
The only thing I can think of, is that it could require usage of some 
vendor-specific proprietary software to setup hardware encryption and/or

to update currently flashed firmware to newer versions.

I think, you've encountered a hardware compatibility issue between an 
old ICH controller on the host and a SATA controller on the SSD drive.
Some Samsung SSDs with their custom drive controller ICs were affected 
by this issue, refusing to work with some older chipsets and at lower 
SATA speeds.
I suspect it could be done on purpose, because vendor doesn't want to 
look bad when people benchmark their new drive and post sub-par results 
online.


Can you provide exact model\make of your host and the SSD drive?

--
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄

Re: Crucial SSDs and Debian Bullseye

[Christian Britz]

On 2022-04-27 14:22 UTC+0200, Christian Britz wrote:
> 
> 
> On 2022-04-27 13:57 UTC+0200, Tom Browder wrote:
>> On Wed, Apr 27, 2022 at 06:42 Christian Britz > > wrote:
>> ...
>>
>> I have seem some indications on the web though, which suggest there
>> might be an ISO image for updating the drive too. What is the exact
>> model name?
>>
>>
>> Crucial MX500 1000GB 2.5-INCH SOLID STATE DRIVE
> 
> 
> They don't seem to offer the ISO image anymore, at least I did not find
> it on their support site, even though it is mentioned several times.
> What a shame! You should really get rid of that thing if possible.
> 


I found it. https://www.crucial.com/support/ssd-support/mx500-support,
there seem to be two versions. Click on the appropriate blue button, a
zip file will be downloaded which contains the ISO. Apparently this can
not be written to USB.

-- 
http://www.cb-fraggle.de

Re: Crucial SSDs and Debian Bullseye

[Tom Browder]

On Wed, Apr 27, 2022 at 07:30 Christian Britz  wrote:
…

> I found it. https://www.crucial.com/support/ssd-support/mx500-support,
> there seem to be two versions. Click on the appropriate blue button, a
> zip file will be downloaded which contains the ISO. Apparently this can
> not be written to USB.
>
> --
> http://www.cb-fraggle.de
>

Thank you, Christian!

And for future reference, what brand of SSDs (and memory) do you use?

Blessings,

-Tom

Re: Crucial SSDs and Debian Bullseye

[Christian Britz]

On 2022-04-27 13:06 UTC+0200, Tom Browder wrote:

> drive. From what I can find at Crucial, I need to install their Storage
> Executive program on a Windows host, hook up the SSD to a USB/SATA
> connector on that host, and configure or install the firmware onto the SSD.

Sounds really crappy. A drive which must be preconfigured by a
Windows-only tool before first use? If possible, return it to the dealer.

I have seem some indications on the web though, which suggest there
might be an ISO image for updating the drive too. What is the exact
model name?

-- 
http://www.cb-fraggle.de

Re: Crucial SSDs and Debian Bullseye

[Christian Britz]

On 2022-04-27 13:57 UTC+0200, Tom Browder wrote:
> On Wed, Apr 27, 2022 at 06:42 Christian Britz  > wrote:
> ...
> 
> I have seem some indications on the web though, which suggest there
> might be an ISO image for updating the drive too. What is the exact
> model name?
> 
> 
> Crucial MX500 1000GB 2.5-INCH SOLID STATE DRIVE


They don't seem to offer the ISO image anymore, at least I did not find
it on their support site, even though it is mentioned several times.
What a shame! You should really get rid of that thing if possible.

-- 
http://www.cb-fraggle.de

Re: email lacks sender address

[Brian]

On Wed 27 Apr 2022 at 08:05:46 -0400, Haines Brown wrote:

> David. thanks for hanging in with me!
> 
> On Tue, Apr 26, 2022 at 03:23:17PM -0500, David Wright wrote:
> 
> > Do you know why mutt is adding a Sender: line to your emails?
> > Did you ask it to, or have you been asked to by someone else?
> 
> No, I didn't ask mutt to add a Sender: line and I do not know what 
> evidence there it that it is doing so. 
> 
> If I understand correctly, which is always in serious doubt, it is 
> exim that constructs the Sender: line by combining /etc/mailname and 
> $LOCALHOST. Is this so?

No. exim4 uses what is in /etec/mailname as the MAI FROM: (the envelope
from).
 
> These values are present:
> 
>   $ nano /etec/mailname
>   lenin.histomat.net

lenin.histomat.net appears to be unrouteable. How a remote system would
deal with that is anyone's guess.

-- 
Brian.

Re: test

[antoine . valmer]

On Wednesday 27 April 2022 08:54:52 Rémi Demarthe wrote:
> Le lundi 25 avril 2022 à 19:01 +0200, awache...@gmail.com a écrit :
> > On Monday 25 April 2022 17:56:36 Rémi Demarthe wrote:
> > > Le lundi 25 avril 2022 à 11:13 +0200, ajh-valmer a écrit :
> > Quel serveur de mails indique que mon mail est un spam ?
> Le mail est mis en spam côté client par évolution.
> Il ajoute les X-Spam-Flag et X-Spam-Level.

> Pour X-GND-Spam-Score et X-GND-Status, cela serait lié à un filtrage
> sieve qui si je ne m'abuse à lieu lors de la réception du serveur IMAP.
> Je n'arrive pas à comprendre pourquoi tu atteri dans les spam au regard
> des sources du message :
Oui, c'est très curieux !

> As-tu essayé les testeur de spam comme https://www.mail-tester.com/ ? :
Oui, à l'instant, il répond systématiquement que mon mail n'a pas été reçu,
SMTP l'ayant refusé, quelquesoit le smtp utilisé.

Synthèse :
1) smtp.bbox.fr , smtp.free.fr : refus immédiat,
respectivement "policy reason" et "spam detected"

2) smtp.gmail.com : mail envoyé mais pas reçu au destinataire.

3) Envoi à la ML debian avec smtp.gmail.com, 
aucun mail en retour à moi mais mail reçu sur la ML.

Re: email lacks sender address

[Haines Brown]

On Wed, Apr 27, 2022 at 11:29:17AM -0400, Greg Wooledge wrote:

> If what you WANT is for your outgoing mail to appear to come from
> j...@histomat.net then you should have histomat.net in that file instead.

Thanks for the clarifation. I changed it to histomat because I want 
outgoing mail to appear to come from hai...@histomat.net. However just 
changing it does not fix my problem. I may have to restart networking. 
If this works I'll let the thread know.

> In this entire thread I have yet to see you simply state what it is
> that you WANT or EXPECT.

Sorry. I simply wanted to fix the problem that some of my outgoing 
mail was rejected because of a protocol error. I wanted mail to get 
to its intended recipient; I expected that to happen.  The problem 
seems to be that Sender: field is empty. 

> YOU ARE NOT USING DEBIAN SO WE DON'T KNOW!

I insist that the Devan operating system I use is identical to Debian 
except for its lack of systemd. Its installation is identical to 
that of Debian and all packages come from the Debian repository.

> As a *guess*, it probably used your hostname, which you gave it, as
> the value of /etc/mailname.  There is no way it could know what you
> want without asking, and there has been a recent trend among OS
> installers to ask fewer questions, and to assume more things.

In network setup during OS installation, if I recall 
correctly, I'm asked for a) my host name and seprately for b) my 
domain namer. It is entirely possible that when it asked for my domaiin name 
that I entered lenin.histomat.net. But this seems unlikelyi because 
my e-mail system has been working property until just a week ago. 

> Of course, since we HAVE NO IDEA HOW YOUR OS'S INSTALLER WORKS, all
> we can do is guess.

If the installer were any different from that of Debian I would have
addressed the difference. Devuan is imply Devian without systemd. The 
installers presumably work the same. 

> > During network setup I entered the 
> > hostname lenin and domain name histomat.net. Or at least that was
> > my intention. 
> 
> It probably decided to use that as your /etc/mailname.

No. The system worked until a week ago.

> Now, let's look at this domain name for a moment.
> 
> unicorn:~$ host histomat.net
> histomat.net has address 216.239.138.216
> histomat.net mail is handled by 10 postoffice.omnis.com.
> 
> unicorn:~$ host postoffice.omnis.com.
> postoffice.omnis.com has address 216.239.133.242
> postoffice.omnis.com has IPv6 address 2607:fe90:1:1::1c
> 
> The similarity in the two IPv4 addresses catches my attention.  It looks
> like this histomat.net domain name is "owned by" (or at least handled by)
> the same people who own/handle postoffice.omnis.com.
> 
> I'm guessing that person isn't you.  You don't seem to know enough to be
> running an Internet domain.

That is correct. I am not an IT person. My public IP address is indeed 
216.239.138.216. I assume it is assigned by my ISP. My ISP is Onnis. 
My mail service is also provided by Omnis. Would that explain the 
similarity of the IP addresses?

> So, that begs the question of why you think it's appropriate to announce
> yourself as histomat.net in your outgoing communications.

By "announce" do you refer to my domain name? Are you asking why I use 
histomat.net as my domain name? That is because it is my domain name. 
I had my ISP create a simple alias for the domain name 
historicalmateiralism.info. It has the same IP address as hstomat.net.

> Furthermore, we've seen evidence that you're using an outgoing mail relay
> (not under your own control) which rejects your outgoing email if you
> try to identify yourself as r...@lenin.histomat.net.  Would it also have
> rejected r...@histomat.net?  Who knows.  Certainly not us, because you
> haven't performed that test and told us the result.

I presume that by "outgoing mail relay" you refer to the mail service 
provided by my ISP. I understand that it will reject 
r...@lenin.histomat.net because my hostname is not part of my domain 
name. 

I have no idea off hand how to test if mail sent from 
r...@histomat.net will get through. All I can think of is telnet. I 
don't know whether mail has an option to define the sender. Perhaps I 
could log in as root and send mail

> This makes me wonder what envelope sender address(es) it WILL accept.
> Knowing that would be incredibly useful.  It may be the single most
> important piece of data you could possibly possess in this entire
> scenario, as it will probably dictate everything there is to be dictated
> about how you should configure your outgoing email.

I know from past success that it will accept mail from haines@histomat 
(and from bro...@historicalmaterialism.info)
 
> Do you have any actual *instructions* or *documentation* that was
> given to you by the histomat.net / postoffice.omnis.com administrators?
> Something that could guide you toward setting up your outgoing email in
> a way they will tolerate?  Or is it going to be 100% 

Re: email lacks sender address

[Brian]

On Wed 27 Apr 2022 at 08:05:46 -0400, Haines Brown wrote:

[...]

>   A message that you sent could not be delivered to one or more of its
>   recipients. This is a permanent error. The following address(es) failed:

This message is from your smarthost, mail.guardedhost.com. It has
attempted to send mail on your behalf to sur...@popcon.devuan.org.
It tell the server at devuan.org who it is and where the mail is
required to go to.  Those are the only two required items of info
the remote server needs to deliver the mail.
  
> sur...@popcon.devuan.org
> host mail.guardedhost.com [216.239.133.245]
> SMTP error from remote mail server after pipelined sending data block:
> 553 5.7.1 : Sender address rejected:
> not owned by user bro...@historicalmaterialism.info

However, the devuan server apparently decides to look at what is in
the mail being sent. At least, that is what I surmise from

  ...after pipelined sending data block

It decides to reject the mail on what it sees, not on guardedhost.com
being an inappropriate sender. It sees the sender as claiming to be
histomat.net but really being historicalmaterialism.info. This did
noy bother mail.guardedhost.com, but it puts popcon.devuan.org's
knickers in a twist. It rejects the mail.

(People would go beserk if Royal Mail or the US Postal System opend
every envelope and scrutnised its contents. But this is email and
invasion of privacy is all in a good cause).

> Reporting-MTA: dns; lenin.histomat.net
> 
> Action: failed
> Final-Recipient: rfc822;sur...@popcon.devuan.org
> Status: 5.0.0
> Remote-MTA: dns; mail.guardedhost.com
> Diagnostic-Code: smtp; 553 5.7.1 : Sender
> address rejected: not owned by user bro...@historicalmaterialism.info
> 
> The address hai...@histomat.net is owned by 
> bro...@historicalmaterialism.info. Omnis mail server never had a 
> problem with r...@histomat.net before.

The problem is not with the Omnis mail server. It did its job.

-- 
Brian.

Re: recherche équivalent à RT enterprise-grade ticketing system

[didier gaumet]

Le mercredi 27 avril 2022 à 19:30:03 UTC+2, Bernard Schoenacker a écrit :
[...]
> j'ai retrouvé le nom du paquet et il s'agit de OTRS 
[...]

Avertissement préalable: je n'y connais absolument rien...

... mais il y sur wikipedia un comparatif de ce genre de solutions avec 4 
alternatives libres (OTRS, Zammad, GPLI, et RT auquel tu fais allusion): 
https://en.wikipedia.org/wiki/Comparison_of_help_desk_issue_tracking_software

J'ai regardé en diagonale rapide: tous ces logiciels sont soit libres et 
gratuits téléchargeables directement sur le site de l'éditeur, soit il faut 
chercher un site community pour télécharger une version gratuite

Concernant OTRS en particulier,
https://en.wikipedia.org/wiki/OTRS
la version gratuite (v6, community, celle qui est empaquetée dans Debian) n'est 
plus maintenue depuis fin 2020, l'éditeur semble vouloir se passer de cette 
version gratuite.
https://otrs.com/release-notes/attention-security-risk-with-otrs-6/

recherche équivalent à RT enterprise-grade ticketing system

[Bernard Schoenacker]

Bonjour,

Je recherche une solution couplée à un asterisk et à
une messagerie pour réaliser un bug report ou une
aide par assistance technique de différents niveaux

La société qui avait mis n avant l'ensemble était Allemande
mais comme j'ai un trou de mémoire...

Pourriez-vous éclairer ma lanterne ?

Merci pour votre aimable attention

Bien à vous

Bernard

Re: Crucial SSDs and Debian Bullseye

[Alexander V. Makartsev]

On 27.04.2022 20:37, Tom Browder wrote:

...
If either of those fail to see it, I’m afraid I toasted it. I don’t 
think that will qualify for a return.

...


What makes you think that way?
It is next to impossible to actually mishandle and "toast" a device 
simply by unpacking it and connecting to a SATA port. (Even when PC is 
powered on¹).
SSDs are not fragile, they are electrically compatible with SATA 
standard, so both data and power port parts won't do any damage to a 
device, no matter how old or new the hardware is.
If you won't manage to get it working with another PC, then you simply 
got a faulty product and have a warranty to get it replaced.
I've seen a fair share of faulty brand new devices in my life, memory 
sticks, motherboards, HDDs.
This is rare nowadays and I don't handle large volumes of PC parts 
anymore, but it still happen here and there.



¹ It is still a risk and is not recommended at all. It is always safer 
to do any work with powered off computer and disconnected battery if it 
is a laptop.


--
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄

Re: recherche équivalent à RT enterprise-grade ticketing system

[Bernard Schoenacker]

- Mail original -
> De: "Bernard Schoenacker" 
> À: "Liste Debian" 
> Envoyé: Mercredi 27 Avril 2022 19:00:28
> Objet: recherche équivalent à RT  enterprise-grade ticketing system
> 
> Bonjour,
> 
> Je recherche une solution couplée à un asterisk et à
> une messagerie pour réaliser un bug report ou une
> aide par assistance technique de différents niveaux
> 
> La société qui avait mis n avant l'ensemble était Allemande
> mais comme j'ai un trou de mémoire...
> 
> Pourriez-vous éclairer ma lanterne ?
> 
> Merci pour votre aimable attention
> 
> Bien à vous
> 
> Bernard
> 

Re Bonjour,

j'ai retrouvé le nom du paquet et il s'agit de OTRS

Merci beaucoup pour les coups de pouce et à bientôt

Bien à vous

Bernard

Re: HTTP Proxy

[Larry Martin]

Dan,

Thank you.  That makes perfect sense.

> On Apr 27, 2022, at 2:02 PM, Dan Ritter  wrote:
> 
> Larry Martin wrote: 
>> Dan,
>> 
>> Thank you for the prompt reply.  I am still having problems.  I enter my IP 
>> address as 192.168.1.45 and all appears to go ok.
>> When it gets to the point of connecting to a mirror site it fails.  I have 
>> left the proxy blank.  Any suggestions?
> 
> 
> Hi, Larry.
> 
> The etiquette on open source user mailing lists is to always
> reply to the list, optionally copying the respondent. This is
> for several reasons:
> 
> - many people will see your reply and be able to help, not just
>  one
> 
> - many people in the future will see the archive and thus be
>  helped in turn
> 
> - it doesn't presume that the person who answered your question
>  is going to take responsibility for solving your whole
>  problem. We're not paid, we're your fellow users.
> 
> 
> -dsr-

Re: HTTP Proxy

[gene heskett]

On Wednesday, 27 April 2022 14:04:43 EDT Larry Martin wrote:
> Dan,
> 
> Thank you.  That makes perfect sense.
> 
> > On Apr 27, 2022, at 2:02 PM, Dan Ritter  wrote:
> > 
> > Larry Martin wrote:
> >> Dan,
> >> 
> >> Thank you for the prompt reply.  I am still having problems.  I
> >> enter my IP address as 192.168.1.45 and all appears to go ok. When
> >> it gets to the point of connecting to a mirror site it fails.  I
> >> have left the proxy blank.  Any suggestions?> 

That address will not go thru a router, it is an assigned private block 
(192.168.xx.zz) that you can set up for your home networks, so you will 
need to setup a NAT scheme in the router and let it handle the details. I 
do that here for 6 machines full time, and they all have free run of the 
net. And with the router running dd-wrt or one of its ilk, it stands 
guard, allowing nothing coming in that wasn't asked for. And its been 
standng guard here for 20 years now with no penetrators.

> > Hi, Larry.
> > 
> > The etiquette on open source user mailing lists is to always
> > reply to the list, optionally copying the respondent. This is
> > for several reasons:
> > 
> > - many people will see your reply and be able to help, not just
> > 
> >  one
> > 
> > - many people in the future will see the archive and thus be
> > 
> >  helped in turn
> > 
> > - it doesn't presume that the person who answered your question
> > 
> >  is going to take responsibility for solving your whole
> >  problem. We're not paid, we're your fellow users.
> > 
> > -dsr-
> 
> .


Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis

Re: email lacks sender address

[Byung-Hee HWANG]

Celejar  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

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

Re: email lacks sender address

[Greg Wooledge]

On Wed, Apr 27, 2022 at 01:46:01PM -0400, Haines Brown wrote:
> Thanks for the clarifation. I changed it to histomat because I want 
> outgoing mail to appear to come from hai...@histomat.net.

OK!  We're making progress now.

Funny thing, though... I'm not sure that /etc/mailname actually does
anything other than sit there looking cute.  Reading farther along in
, it says:

  Exim (i.e. exim 3.x) doesn't read /etc/mailname at all. When you
  configure it, it prompts you for what it calls the "visible name"
  of the system. This is stored in /etc/mailname, and also used in a
  few places in the exim config file.

But also:

  Failing to come up with something better exim4 (and mutt) use mailname
  to qualify recipients and therefore exim4 makes mailname a local
  domain. If people don't want that, they delete it from the list in
  the debconf dialog.

I'm honestly not sure how to interpret that paragraph about exim4.
They're using "local domain" as a technical term with a highly specific
meaning, but it's something unique to exim4, and I don't use exim4 myself.

What it *sounds* like is "the content of /etc/mailname will be used in the
configuration dialog as a default value".  In other words, changing the
content of /etc/mailname won't do anything unless you then go through the
next step of configuring exim4's "local domains", whatever those are.

> However just 
> changing it does not fix my problem.

*nod*

> I may have to restart networking. 
> If this works I'll let the thread know.

It won't.  Networking has nothing to do with MTA configuration.

> > YOU ARE NOT USING DEBIAN SO WE DON'T KNOW!
> 
> I insist that the Devan operating system I use is identical to Debian 
> except for its lack of systemd. Its installation is identical to 
> that of Debian and all packages come from the Debian repository.

You have already demonstrated that this is false.  Your popcon package
is sending its results to a different address than the Debian popcon
package uses.  This means the Devuan popcon package is different.  Which
means it's coming from a different repository.

Devuan has *changes*.  That's why you selected it.  That also means that
we, as users of Debian, may not know what all of those changes *are*.

> In network setup during OS installation, if I recall 
> correctly, I'm asked for a) my host name and seprately for b) my 
> domain namer. It is entirely possible that when it asked for my domaiin name 
> that I entered lenin.histomat.net.

None of that is important.

What's important is configuring your MTA correctly.  Which means you stop
relying on what the installer did for you, and just fix things that need
to be fixed.

> But this seems unlikelyi because 
> my e-mail system has been working property until just a week ago. 

So, something changed a week ago.

Did *you* change something?  If so, what?

If not, then perhaps your smarthost's configuration was changed.  Did
your smarthost administrator send you any notifications of changes?
Anything like that?

Or did they just pull the rug out from under you?

> > unicorn:~$ host histomat.net
> > histomat.net has address 216.239.138.216
> > histomat.net mail is handled by 10 postoffice.omnis.com.
> > 
> > unicorn:~$ host postoffice.omnis.com.
> > postoffice.omnis.com has address 216.239.133.242
> > postoffice.omnis.com has IPv6 address 2607:fe90:1:1::1c
> > 
> > The similarity in the two IPv4 addresses catches my attention.  It looks
> > like this histomat.net domain name is "owned by" (or at least handled by)
> > the same people who own/handle postoffice.omnis.com.
> > 
> > I'm guessing that person isn't you.  You don't seem to know enough to be
> > running an Internet domain.
> 
> That is correct. I am not an IT person. My public IP address is indeed 
> 216.239.138.216.

Oh, that's interesting.  So histomat.net points to your machine.

> I assume it is assigned by my ISP. My ISP is Onnis. 

Ah.

> My mail service is also provided by Omnis. Would that explain the 
> similarity of the IP addresses?

Yes.

> > So, that begs the question of why you think it's appropriate to announce
> > yourself as histomat.net in your outgoing communications.
> 
> By "announce" do you refer to my domain name?

I'm talking about the envelope sender address and the From: header address
of your outgoing emails.  (Brian also mentioned the HELO address, but
that usually isn't important.)

Re-read your original error message.  The one where your exim MTA reported
that your smarthost had rejected the message.

Keep staring at it until understanding occurs.

> Are you asking why I use 
> histomat.net as my domain name? That is because it is my domain name. 

It points to your machine, so that sounds correct.

What does it mean that the domain name points to your machine?  It means
that you can use it for *incoming* email.  Other people, trying to send
email to you, will be able to use that domain name to reach you.

Well, they *would* be 

Debian 10 and also 11 installation fails, because grub fails - please fix

[Jaroslav Fojtík]

Dears,




Please fix an issue in Debian installer that blocks automatic installation.

It affects all known Debian distributions on my machine.





http://78.108.103.11/~fojtik/debian11/DebianInstallFail.jpg




Debian could be hacked to finish installation and then works.





This does not look sane:
http://78.108.103.11/~fojtik/debian11/update_grub.txt
***
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.15.0-3-amd64
Found initrd image: /boot/initrd.img-5.15.0-3-amd64
Found linux image: /boot/vmlinuz-5.14.0-4-amd64
Found initrd image: /boot/initrd.img-5.14.0-4-amd64
Found Windows 7 on /dev/sda1
Found Slackware Linux (Slackware 8.1) on /dev/sda9
Found Windows 7 on /dev/sdb1
Found Slackware 14.2 on /dev/sdb3
error: out of memory.
error: syntax error.
error: Incorrect command.
error: syntax error.
Syntax error at line 447
Syntax errors are detected in generated GRUB config file.
Ensure that there are no errors in /etc/default/grub
and /etc/grub.d/* files or please file a bug report with
/boot/grub/grub.cfg.new file attached.
***




All neccessary information about my Debian are published here:

  http://78.108.103.11/~fojtik/debian11/

I cannot attach them directly into Email, mail will be dropped.




best regards

   Jara