#StackBounty: #debian #email #smtp #exim Complete setup of Exim4 as SMTP to reach most inboxes as possible (correct configuration)

Bounty: 200

I have over the last days tried to setup Exim4 to handle all mails sent from a web application.

It seems to be working, but I haven’t found out how to hardcode the hostname which will be sent with EHLO? (I don’t want to set /etc/hostname)

Have found the variable MAIN_HARDCODE_PRIMARY_HOSTNAME mentioned in the config but havn’t found a way to set it. Is this variable the simplest way to set the hostname or is there a better way to do it?

Below is the complete install/config.. Am I missing something?

Exim version 4.92
Debian Buster 10

Install

apt-get install exim4-daemon-light

Configure Exim4

dpkg-reconfigure exim4-config

Type:           internet site
FQDN:           smtp.mydomain.com
SMTP listener:      (empty)
Mail destinations:  (empty)
Domain relay:       (empty)
Machine relay:      (empty)
DNS queries minimal:    No
Delivery method:    Maildir
Split conf files:   No

Enable TLS and generate certs

printf "MAIN_TLS_ENABLE = truen" >> /etc/exim4/exim4.conf.localmacros
/usr/share/doc/exim4-base/examples/exim-gencert

check reverse DNS (IP -> smtp.mydomain.com)

https://mxtoolbox.com/ReverseLookup.aspx

Get IPv6

ip -6 addr | grep inet6 | awk -F '[ t]+|/' '{print $3}' | grep -v ^::1 | grep -v ^fe80

/etc/hosts

[ipv4]  smtp.mydomain.com
[ipv6]  smtp.mydomain.com

uncomment in ‘/etc/exim4/exim4.conf.template’

# plain_server:
# driver = plaintext
# public_name = PLAIN
# server_condition = "${if crypteq{$3}{${extract{1}{:}{${lookup{$2}lsearch{CON$
# server_set_id = $2
# server_prompts = :
# .ifndef AUTH_SERVER_ALLOW_NOTLS_PASSWORDS
# server_advertise_condition = ${if eq{$tls_cipher}{}{}{*}}
# .endif

add user/pass -> ‘/etc/exim4/passwd’

/usr/share/doc/exim4-base/examples/exim-adduser

DKIM/SPF

I have setup DKIM keys on the server and DKIM/SPF on DNS and both works


Get this bounty!!!

#StackBounty: #ubuntu #debian #keyboard-shortcuts #gnome #xkb How to revert keyboard layout switching shortcuts after setting them with…

Bounty: 50

I wanted to have two keyboard layouts (one for english and one for spanish), and add a shortcut for switching between them.

The solution I chose was to set the following lines in my /etc/default/keyboard file:

XKBLAYOUT="us,es"
XKBOPTION="grp:ctrl_shift_toggle"

This has turned out to be a mistake because the ctrl_shift shortcut interfers and takes precedence over all other application level shortcuts like browser’s ctrl+shift+tab and vi’s ctrl+shift+insert.

I haven’t found a way to revert this change and have it persist in between shutdowns.

Here are the methods I have tried:
1) Removing the XKBOPTION line from /etc/default/keyboard
2) Running the command dpkg-reconfigure keyboard
3) Running the command setxkbmap -option. This works but is reset upon restarting.
4) Configuring one single layout by adding the line XKBLAYOUT and adding the alternative layout via GNOME and using the GNOME shortcut (Super space). The switch has no effect and is reset upon restarting.

I don’t know where these changes are stored in between installs, I have ran grep with searching for terms like XKBOPTION,ctrl_shift_toggle but I can’t seem to find it. All I can find is that the setxkbmap -print command shows the ctrl_shift_toggle option:

xkb_keymap {
    xkb_keycodes  { include "evdev+aliases(qwerty)" };
    xkb_types     { include "complete"  };
    xkb_compat    { include "complete"  };
    xkb_symbols   { include "pc+us+es:2+us:3+inet(evdev)+grp(ctrl_shift_toggle)"    };
    xkb_geometry  { include "pc(pc105)" };
};

However, as mentioned, I cannot find the file responsible for the ctrl_shift_toggle configuration.

Note: The question is looking for an answer that can revert the state of the keyboard setting either to the original setting, or to the desired configuration. Reinstalling the OS or a solution that starts from a clean install is not considered an optimal solution. The reason for this is that, as a superuser, I want to have deep control of my system.

Thank you for your time.


Get this bounty!!!

#StackBounty: #debian #password #chrome chrome does not save my passwords

Bounty: 100

When I had to login in a site, Chrome used to offer me a number of possible user names and later the password associated with the user I choose (provided that I saved the user-password association previously).

Now Chrome still offers the correct possible users but then offers no password, I have to enter the password (if I remember it, that is, otherwise it’s password resetting) and, after a successful login, Chrome ask for permission to save the password. I give permission, of course, but next time I login it’s again no password remembered.

If I open the Settings->Passwords screen I see (the equivalent of)

Offer to save passwords [YES]
Auto Sign-in            [YES]

and below

Saved Passwords
    Saved passwords will appear here

that is, no password is really saved.

Final consideration, the same page permits to View and manage saved passwords in your Google Account and if I go there I can see all my sites, my users and my passwords except, important exception! that some of these passwords are stale.

I’m on Debian Sid, Chrome is Version 76.0.3809.132 (Official Build) (64-bit)
from Google’s official .deb

What can I do to fix this annoying problem?

UPDATE

This is what I get when I launch Chrome from the shell

$ google-chrome
[18891:18891:0906/221132.855189:ERROR:sandbox_linux.cc(369)] InitializeSandbox() called with multiple threads in process gpu-process.
[18856:18990:0906/221136.514201:ERROR:object_proxy.cc(619)] Failed to call method: org.freedesktop.Notifications.GetCapabilities: object_path= /org/freedesktop/Notifications: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files
[18891:18891:0906/221143.906640:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command
[18856:18996:0906/221151.512723:ERROR:password_syncable_service.cc(191)] Passwords datatype error was encountered: Failed to get passwords from store.

In particular, Passwords datatype error was encountered: Failed to get passwords from store. seems relevant wrt my issues.


Get this bounty!!!

#StackBounty: #debian #dual-boot #uefi #refind How to boot by default to Debian Buster

Bounty: 50

I just upgrade Debian from Stretch to Buster. I have a Win 10 installation on another partition but before I was not able to get a Boot menu with both choices so I had to modify the BIOS settings to be able to boot from Windows.

With Buster, the situation is better, I have a rEFInd screen where I choose Windows or Debian. The remaining problem is that Windows is selected by default.

I have read few things but I cannot find how to set the default configuration for the boot manager.

Here is the output of parted:

GNU Parted 3.2
Using /dev/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print all                                                        
Model: ATA SAMSUNG HD204UI (scsi)
Disk /dev/sda: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  2000GB  2000GB  primary  ext4


Model: ATA Samsung SSD 850 (scsi)
Disk /dev/sdb: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system     Name                          Flags
 1      1049kB  473MB  472MB   ntfs            Basic data partition          hidden, diag
 2      473MB   578MB  105MB   fat32           EFI system partition          boot, esp
 3      578MB   595MB  16.8MB                  Microsoft reserved partition  msftres
 4      595MB   210GB  209GB   ntfs            Basic data partition          msftdata
 5      210GB   210GB  1049kB                                                bios_grub
 6      210GB   487GB  278GB   ext4
 7      487GB   500GB  12.8GB  linux-swap(v1)

I expected to find a refind.conf in /dev/sdb2 but I didn’t find anything.

$ tree -L 3 /boot/efi/
/boot/efi/
└── EFI
    ├── Boot
    │   └── bootx64.efi
    ├── Microsoft
    │   ├── Boot
    │   ├── bootmgfw.efi
    │   └── Recovery
    └── tools

Another thing to mention is that the output of efibootmgr is unexpected :

$ efibootmgr
BootCurrent: 0000
No BootOrder is set; firmware will attempt recovery

What do I have to do to boot by default to Debian ?


Get this bounty!!!

#StackBounty: #linux #debian #gnome #scaling Unable to change text-scaling-factor on gnome 3.30.2

Bounty: 100

On debian (testing) with gnome 3.30.2 I am unable to change the text-scaling-factor to 1.25. Neither the tweak-tool nor using the gsettings command works:
Option grayed out
As you can see on the screenshot the plus option is grayed out.

Using this command:

gsettings set org.gnome.desktop.interface text-scaling-factor 1.25

I get this error:

The provided value is outside of the valid range

Using the command line I can set the scaling factor to something equal to or below 1, but every value greater than 1 gives me the above error.

I am absolutely certain I was able to do this a few days ago. I do not remember installing any updates since then. Several reboots and logouts did not fix the problem. I would like to avoid uninstalling/reinstalling software since this is a relatively new debian install and I doubt it would help.

uname -a:

Linux T470s 4.19.0-5-amd64 #1 SMP Debian 4.19.37-3 (2019-05-15) x86_64 GNU/Linux

Are there any logs I can look at to see what’s wrong? How can I make that option available again?

I have tried turning the “Large Text” accessibility option on but that didn’t help either.


Get this bounty!!!

#StackBounty: #debian #systemd #services #systemctl systemd: Can't unmask root mount (-.mount)

Bounty: 50

(Dist: Debian 10)

I have a reoccurring error message that mainly pops up when using systemctl (also when installing a package, and occasionally in a few other places that escape me),

Unit -.mount is masked.

Sometimes (depending on what command called the error message) it is more verbose, such as

Error: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit -.mount is masked.

This error doesn’t impede installing packages or any systemd services which are enabled already (and as such are loaded at boot), but using systemctl or service to restart, start or stop a service fails. This means I have to reboot the whole server to restart a service, which can be a little annoying.

Trying to unmask the root mount with systemctl unmask -- -.mount appears to work (nothing is returned), but systemctl status -- -.mount still outputs the following after:

● -.mount - Root Mount
   Loaded: masked (Reason: Unit -.mount is masked.)
   Active: active (mounted) since Mon 2019-08-05 15:03:38 AEST; 4h 8min ago
    Where: /
     What: /dev/sde1
    Tasks: 0 (limit: 4915)
   Memory: 0B
   CGroup: /system.slice/-.mount

Any ideas? I’m don’t want to start from a fresh install for this server, so either I find a fix or just deal with having to restart if I need to reload a service.


Get this bounty!!!

#StackBounty: #debian #systemd #services #systemctl systemd: Can't unmask root mount (-.mount)

Bounty: 50

(Dist: Debian 10)

I have a reoccurring error message that mainly pops up when using systemctl (also when installing a package, and occasionally in a few other places that escape me),

Unit -.mount is masked.

Sometimes (depending on what command called the error message) it is more verbose, such as

Error: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit -.mount is masked.

This error doesn’t impede installing packages or any systemd services which are enabled already (and as such are loaded at boot), but using systemctl or service to restart, start or stop a service fails. This means I have to reboot the whole server to restart a service, which can be a little annoying.

Trying to unmask the root mount with systemctl unmask -- -.mount appears to work (nothing is returned), but systemctl status -- -.mount still outputs the following after:

● -.mount - Root Mount
   Loaded: masked (Reason: Unit -.mount is masked.)
   Active: active (mounted) since Mon 2019-08-05 15:03:38 AEST; 4h 8min ago
    Where: /
     What: /dev/sde1
    Tasks: 0 (limit: 4915)
   Memory: 0B
   CGroup: /system.slice/-.mount

Any ideas? I’m don’t want to start from a fresh install for this server, so either I find a fix or just deal with having to restart if I need to reload a service.


Get this bounty!!!

#StackBounty: #debian #systemd #services #systemctl systemd: Can't unmask root mount (-.mount)

Bounty: 50

(Dist: Debian 10)

I have a reoccurring error message that mainly pops up when using systemctl (also when installing a package, and occasionally in a few other places that escape me),

Unit -.mount is masked.

Sometimes (depending on what command called the error message) it is more verbose, such as

Error: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit -.mount is masked.

This error doesn’t impede installing packages or any systemd services which are enabled already (and as such are loaded at boot), but using systemctl or service to restart, start or stop a service fails. This means I have to reboot the whole server to restart a service, which can be a little annoying.

Trying to unmask the root mount with systemctl unmask -- -.mount appears to work (nothing is returned), but systemctl status -- -.mount still outputs the following after:

● -.mount - Root Mount
   Loaded: masked (Reason: Unit -.mount is masked.)
   Active: active (mounted) since Mon 2019-08-05 15:03:38 AEST; 4h 8min ago
    Where: /
     What: /dev/sde1
    Tasks: 0 (limit: 4915)
   Memory: 0B
   CGroup: /system.slice/-.mount

Any ideas? I’m don’t want to start from a fresh install for this server, so either I find a fix or just deal with having to restart if I need to reload a service.


Get this bounty!!!

#StackBounty: #debian #systemd #services #systemctl systemd: Can't unmask root mount (-.mount)

Bounty: 50

(Dist: Debian 10)

I have a reoccurring error message that mainly pops up when using systemctl (also when installing a package, and occasionally in a few other places that escape me),

Unit -.mount is masked.

Sometimes (depending on what command called the error message) it is more verbose, such as

Error: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit -.mount is masked.

This error doesn’t impede installing packages or any systemd services which are enabled already (and as such are loaded at boot), but using systemctl or service to restart, start or stop a service fails. This means I have to reboot the whole server to restart a service, which can be a little annoying.

Trying to unmask the root mount with systemctl unmask -- -.mount appears to work (nothing is returned), but systemctl status -- -.mount still outputs the following after:

● -.mount - Root Mount
   Loaded: masked (Reason: Unit -.mount is masked.)
   Active: active (mounted) since Mon 2019-08-05 15:03:38 AEST; 4h 8min ago
    Where: /
     What: /dev/sde1
    Tasks: 0 (limit: 4915)
   Memory: 0B
   CGroup: /system.slice/-.mount

Any ideas? I’m don’t want to start from a fresh install for this server, so either I find a fix or just deal with having to restart if I need to reload a service.


Get this bounty!!!