On 1/26/20 7:06 PM, Mick wrote:
On Sunday, 26 January 2020 23:45:14 GMT james wrote:
On 1/26/20 3:58 AM, Mick wrote:
On Sunday, 26 January 2020 08:36:15 GMT Peter Humphrey wrote:
On Sunday, 26 January 2020 05:35:04 GMT Dale wrote:
james wrote:
just a test via another mail-route. curious if it works
FYI, it came through but the threading was broken. It appeared here as
a new thread.
Not so here. KMail threaded it right.
+1 on Kmail
Hmmmmm.
Well I've contact several ISPs about a /29 set of static IPs (routed) as
part of an upgrade. We'll see how that pans out. Sure, I hate SendMail,
but it's an old system that can be configured, with fine-grain
semantics, and we have much history together.
KMail is an interesting alternative, should I decide against static IPs.
I need those statics to showcase
some embedded devices I'm been working; so why not fix these VERIZON
ahole mail issues, once and for all.
Kmail is a desktop GUIfied email client, not a mail delivery mechanism.
I seem to always receive your messages to the list and Kmail threads them
correctly from what I have noticed.
ls /usr/portage/mail-mta yeilds 12 packages.
(suggestions/discussions on running a mail server are all welcome.
I'm tire of waisting all this time, only to discover that other folks
running mail services, are basically a bunch of ahole, anti-linux
bigots. So why not just run my own mail server? Besides, I've got to go
back to work, and mail_administration is always a good thing for a
resume, ymmv.
I'll leave others to comment on the workload which running your own mail
server could produce. Besides using a suitable application to configure a
dynamically updated blacklist and virus checker to keep spammers and malware
out, you'll also need to configure SPF, DKIM & DMARK to make sure your emails
are delivered reliably to the mass market ISPs like hotmail, yahoo.com!, etc.
Otherwise such ISPs may just drop them unseen and without warning.
Random google result:
https://www.csoonline.com/article/3254234/mastering-email-security-with-dmarc-spf-and-dkim.html
Regarding the original post, do not forget the incantations:
eselect python list
eselect python update
eselect python cleanup
to update your python symlinks and cleanup any stragglers.
It switched me from python-3.6 to python-3.7 as the default; I'll see
how that goes....
They all ran nice and clean, except for this package::
that fails to build regardless of what I do/try.
dev-perl/Authen-SASL
The moment I come across a perl package emerge problem and before I try to
troubleshoot it further, I run:
perl-cleaner --reallyall
So::
perl-cleaner --reallyall
It runs on 64/145 packages just fine, then, as always, fails on
"Emerging (65 of 145)dev-perl/Authen-SASL-2.160.0-r1::argent-main"
Any other ideas? Maybe I need to download that package again, as it
somehow got corrupted?
Here's the first part of the error message::
Failed to emerge dev-perl/Authen-SASL-2.160.0-r1, Log file:
>>> '/var/log/portage/dev-perl:Authen-SASL-2.160.0-r1:20200127-044809.log'
>>> Jobs: 64 of 145 complete, 1 failed Load avg: 1.45,
1.62, 1.07
* Package: dev-perl/Authen-SASL-2.160.0-r1
* Repository: argent-main
* Maintainer: p...@gentoo.org
* USE: abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU
* FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox
>>> Unpacking source...
>>> Unpacking Authen-SASL-2.16.tar.gz to
/var/tmp/portage/dev-perl/Authen-SASL-2.160.0-r1/work
>>> Source unpacked in
/var/tmp/portage/dev-perl/Authen-SASL-2.160.0-r1/work
>>> Preparing source in
/var/tmp/portage/dev-perl/Authen-SASL-2.160.0-r1/work/Authen-SASL-2.16 ...
>>> Source prepared.
>>> Configuring source in
/var/tmp/portage/dev-perl/Authen-SASL-2.160.0-r1/work/Authen-SASL-2.16 ...
* Using ExtUtils::MakeMaker
* perl Makefile.PL PREFIX=/usr INSTALLDIRS=vendor INSTALLMAN3DIR=none
DESTDIR=/var/tmp/portage/dev-perl/Authen-SASL-2.160.0-r1/image/
Can't locate inc/Module/Install.pm in @INC (you may need to install the
inc::Module::Install module) (@INC contains: /etc/perl
/usr/local/lib64/perl5/5.30.1/x86_64-linux-thread-multi
/usr/local/lib64/perl5/5.30.1
/usr/lib64/perl5/vendor_perl/5.30.1/x86_64-linux-thread-multi
/usr/lib64/perl5/vendor_perl/5.30.1 /usr/local/lib64/perl5
/usr/lib64/perl5/vendor_perl/5.28.2 /usr/lib64/perl5/vendor_perl/5.26.2
/usr/lib64/perl5/vendor_perl/5.24.3 /usr/lib64/perl5/vendor_perl
/usr/lib64/perl5/5.30.1/x86_64-linux-thread-multi
/usr/lib64/perl5/5.30.1) at Makefile.PL line 6.
BEGIN failed--compilation aborted at Makefile.PL line 6.
* ERROR: dev-perl/Authen-SASL-2.160.0-r1::argent-main failed
(configure phase):
* Unable to build!
*
* Call stack:
* ebuild.sh, line 125: Called src_configure
* environment, line 2482: Called perl-module_src_configure
* environment, line 2104: Called die
* The specific snippet of code:
* perl Makefile.PL "$@" <<< "${pm_echovar}" || die
"Unable to build!";
*
Any guidance or suggestion are welcome.
A specific list of files to purge and download again?
James
