| 1 |
On Sunday, 26 January 2020 23:45:14 GMT james wrote: |
| 2 |
> On 1/26/20 3:58 AM, Mick wrote: |
| 3 |
> > On Sunday, 26 January 2020 08:36:15 GMT Peter Humphrey wrote: |
| 4 |
> >> On Sunday, 26 January 2020 05:35:04 GMT Dale wrote: |
| 5 |
> >>> james wrote: |
| 6 |
> >>>> just a test via another mail-route. curious if it works |
| 7 |
> >>> |
| 8 |
> >>> FYI, it came through but the threading was broken. It appeared here as |
| 9 |
> >>> a new thread. |
| 10 |
> >> |
| 11 |
> >> Not so here. KMail threaded it right. |
| 12 |
> > |
| 13 |
> > +1 on Kmail |
| 14 |
> |
| 15 |
> Hmmmmm. |
| 16 |
> |
| 17 |
> Well I've contact several ISPs about a /29 set of static IPs (routed) as |
| 18 |
> part of an upgrade. We'll see how that pans out. Sure, I hate SendMail, |
| 19 |
> but it's an old system that can be configured, with fine-grain |
| 20 |
> semantics, and we have much history together. |
| 21 |
> |
| 22 |
> |
| 23 |
> KMail is an interesting alternative, should I decide against static IPs. |
| 24 |
> I need those statics to showcase |
| 25 |
> some embedded devices I'm been working; so why not fix these VERIZON |
| 26 |
> ahole mail issues, once and for all. |
| 27 |
|
| 28 |
Kmail is a desktop GUIfied email client, not a mail delivery mechanism. |
| 29 |
|
| 30 |
I seem to always receive your messages to the list and Kmail threads them |
| 31 |
correctly from what I have noticed. |
| 32 |
|
| 33 |
|
| 34 |
> ls /usr/portage/mail-mta yeilds 12 packages. |
| 35 |
> (suggestions/discussions on running a mail server are all welcome. |
| 36 |
> |
| 37 |
> I'm tire of waisting all this time, only to discover that other folks |
| 38 |
> running mail services, are basically a bunch of ahole, anti-linux |
| 39 |
> bigots. So why not just run my own mail server? Besides, I've got to go |
| 40 |
> back to work, and mail_administration is always a good thing for a |
| 41 |
> resume, ymmv. |
| 42 |
|
| 43 |
I'll leave others to comment on the workload which running your own mail |
| 44 |
server could produce. Besides using a suitable application to configure a |
| 45 |
dynamically updated blacklist and virus checker to keep spammers and malware |
| 46 |
out, you'll also need to configure SPF, DKIM & DMARK to make sure your emails |
| 47 |
are delivered reliably to the mass market ISPs like hotmail, yahoo.com!, etc. |
| 48 |
Otherwise such ISPs may just drop them unseen and without warning. |
| 49 |
|
| 50 |
Random google result: |
| 51 |
|
| 52 |
https://www.csoonline.com/article/3254234/mastering-email-security-with-dmarc-spf-and-dkim.html |
| 53 |
|
| 54 |
|
| 55 |
> > Regarding the original post, do not forget the incantations: |
| 56 |
> > eselect python list |
| 57 |
> > eselect python update |
| 58 |
> > eselect python cleanup |
| 59 |
> > to update your python symlinks and cleanup any stragglers. |
| 60 |
> |
| 61 |
> It switched me from python-3.6 to python-3.7 as the default; I'll see |
| 62 |
> how that goes.... |
| 63 |
> They all ran nice and clean, except for this package:: |
| 64 |
> that fails to build regardless of what I do/try. |
| 65 |
> |
| 66 |
> dev-perl/Authen-SASL |
| 67 |
|
| 68 |
The moment I come across a perl package emerge problem and before I try to |
| 69 |
troubleshoot it further, I run: |
| 70 |
|
| 71 |
perl-cleaner --reallyall |
| 72 |
|
| 73 |
-- |
| 74 |
Regards, |
| 75 |
|
| 76 |
Mick |
Archives