SSMTP on Ubuntu 18.10 server stopped sending email through GMail

I use SSMTP on many of our servers. As of June 6th 2019 I can no longer get SSMTP on any of my ubuntu servers to send email. I have some raspberry pies using the same scripts and they send just fine. On site and offsite using different Google domain names stopped sending, so its not tied to one specific Google apps domain. Nor is it tied to a specific network. All systems are running 18.10. Other things using this same account, send fine, through Ubuntu. PHP mailings for example.

It also does not matter what user I try to use within each Google domain. I can use SSMTP with a yahoo user and that sends from Ubuntu.

When I do ssmtp with -v on a linux box I see:

[<-] 220 smtp.gmail.com ESMTP b6sm3003334iok.71 – gsmtp [->] EHLO munki.xxxxx.com [<-] 250 SMTPUTF8 [->] STARTTLS [<-] 220 2.0.0 Ready to start TLS [->] EHLO munki.xxxxx.com [<-] ssmtp: (munki.xxxxx.com)

When I do the same on a pi I see:

[<-] 220 smtp.gmail.com ESMTP w23sm3846674iod.12 – gsmtp [->] EHLO upsd-c03.xxxxx.com [<-] 250 SMTPUTF8 [->] STARTTLS [<-] 220 2.0.0 Ready to start TLS [->] EHLO upsd-c03.xxxxx.com [<-] 250 SMTPUTF8 [->] AUTH LOGIN [<-] 334 Vjjl;hbWU6 [->] bmFnaW9zQG5XJzLm9yZw== [<-] 334 UGFzc3dvcmQ6 [<-] 235 2.7.0 Accepted [->] MAIL FROM: [<-] 250 2.1.0 OK w23sm38674iod.12 – gsmtp [->] RCPT TO: [<-] 250 2.1.5 OK w23sm38674iod.12 – gsmtp [->] DATA [<-] 354 Go ahead w23sm3874iod.12 – gsmtp [->] Received: by upsd-c03.xxxxx.com (sSMTP sendmail emulation); Fri, 14 Jun 2019 16:59:33 -0500 [->] From: “root” [->] Date: Fri, 14 Jun 2019 16:59:33 -0500 [->] test [->] [->] . [<-] 250 2.0.0 OK 1560549575 w23sm3846iod.12 – gsmtp [->] QUIT [<-] 221 2.0.0 closing connection w23sm3846iod.12 – gsmtp

Just wondering if anyone else using Google to send email with SSMTP has seen the same behavior? I haven’t tested an 18.04 or 19.04.

Thank you!!

Jim

RAM usage discrepancy? Memory leak? Ubuntu 18.10 with Cinnamon

So I’m fairly new to using Ubuntu, but what I’ve been finding is that I need to reboot regularly because eventually (over the course of a day or two) I seem to run out of usable RAM and stop being able to play the games I play because they lock up and start disk thrashing and if I’m lucky I’ll be able to wait it out and force-close the game, and if I’m not I’ll need to just hard-reboot. The weirdest thing about it, though is this: https://i.imgur.com/mD8wVRE.png

This shows that just about half my RAM is in use. But then I tab over to the processes page and: https://i.imgur.com/cZ4sZqm.png

As you can see, this is without even running things like a browser or anything. So where has the RAM gone?

What is the standard source list file for 18.10?

Okay I’ve badly damaged my package system. So I found another solution, sudo apt-get build-dep

I typed sudo apt-get build-dep update-manager Reading package lists… Done E: You must put some ‘source’ URIs in your sources.list

Then I accessed it using the sudo nano /etc/apt/sources.list. The list was blank. Now I’m unsure on how to add more source URIs. I cannot access the software updates to change it.

Problem with python in Ubuntu 18.10

I recently upgraded to 18.10 from 18.04, but I am facing a new problem.

When I type python, I am getting this

Python 3.7.3 (default, Apr 9 2019, 04:56:51)

[GCC 8.3.0] on linux

But when I type python3, I am getting an error

bash: /usr/lib/command-not-found: /usr/bin/python3: bad interpreter: No such file or directory

I couldnt opem ny terminal so I changed the very first line of /usr/bin/gnome-terminal to:

!#usr/bin/python from #!usr/bin/python3 since then I am able to open my terminal. Upon entering sudo apt-get update I am getting this error

sh: 1: /usr/lib/cnf-update-db: not found Reading package lists... Done E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/lib/command-not-found/ -a -e /usr/lib/cnf-update-db; then /usr/lib/cnf-update-db > /dev/null; fi' E: Sub-process returned an error code 

No matter whether I enter

pip

or

pip3

I am getting this error bash: /usr/local/bin/pip: /usr/bin/python3: bad interpreter: No such file or directory I tried sudo update-alternatives --config python3 I got There is only one alternative in link group python3 (providing /usr/bin/python3.6): /usr/bin/python3.7 Nothing to configure.

But when I type sudo update-alternatives --config python I am getting

There are 2 choices for the alternative python (providing /usr/bin/python). 

Selection Path Priority Status ------------------------------------------------------------

0 /usr/bin/python3.6 2 auto mode

* 1 /usr/bin/python3.6 2 manual mode

2 /usr/bin/python3.7 2 manual mode

The Software&Updates and Software Updater are also not loading when I click on their icon

Ubuntu 18.10 stuck at initialising ramdisk after fresh install and subsequent update

Specs

  • Asus Zenbook 14 UX433FN (NVMe PCIe SSD)
  • Ubuntu 18.10 and Windows 10 dual boot, Windows 10 working fine.

Background

Today my Ubuntu 18.10 suddenly gave me a “purple screen of death” after I closed my laptop lid (ie. it couldn’t wake up from suspend).

After which, I forced shutdown and tried to reboot (both normally and with recovery mode), and both times it got stuck at Loading initial ramdisk...

Quirky Behaviour

After this I successfully reinstalled Ubuntu 18.10 using CD. TWICE.

Each time, after successfully installing graphics drivers and everything, Ubuntu automatically prompts me to do security updates etc. Before installing updates, I can use and boot into Ubuntu normally.

BUT after installing these updates successfully, and rebooting, I get stuck at Loading initial ramdisk... again.

Resolution attempts

  1. Use LiveCD as per https://help.ubuntu.com/community/LiveCdRecovery#Update_Failure.
  2. Update kernels before installing.
  3. Replacing quiet splash with nomodeset.

Why is this so? Is there a bug in the update repositories somewhere?

I can use Ubuntu without updating of course, but this leaves my computer vulnerable to security issues. In the long-run, being afraid of updating the computer lest I get this same error is quite stupid.