The Email server is now back online and functioning normally. Please let me know if you encounter any difficulties. Thanks! Tim

On 07/11/14 11:55, Baron wrote: That would be a useful feature.

On Saturday 08 November 2014, Andrew Young wrote: I might missunderstand but - I always see / saw my own mail on the list (working with Kmail). Gerhard

Same here as well, with various clients. I am aware of some providers having interoperability issues with the pearsoncomputing.net Email server; hopefully the upgrade has resolved most of them but I need feedback to know one way or the other.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224 Thank you for the update. I now have some useful information in my server logs from your last attempt; let me see what I can do to fix this (Earthlink is explicitly blocking my mail server with error 550). Tim

Next up, please improve the mailing list archive usability. What I see: http://fm.no-ip.com/SS/trinitylistarchive1411.png Proposed fix: [bunch of css stuff snipped]

On Sun, Nov 09, 2014 at 05:17:43AM -0800, Dan Youngquist wrote: When you say "easily usable by everyone", do you mean "everyone with perfect 20/20 vision"? Websites should honour the user's choice of typeface and typesize, if nothing else, and that doesn't add much in the way of complexity. (If anything, websites that force their own choice of font are more complex, not less.)

Lisi Reisz composed on 2014-11-12 17:03 (UTC-0500): What you see, and provided in your attached binary, tells us little, in contrast to the screenshot URL I provided. In mine, the viewer can see what the browser's default size is, and what the whole array of DE sizes are, so that the fonts in the web page can be see in the context of both the defaults, and the whole rest of the desktop. It could be reproduced by anyone who wished to, because context is adequate. The only thing it lacks is actual zoom level applied, which Firefox doesn't offer. The zoom level in fact is none (100% of the size dictated by page CSS), so the archive page is in fact displaying the 10px size dictated by the page's CSS. Your page provides only one context: the UI text in your browser. That frame of reference indicates you've applied several zoom levels to the page. Firefox by default remembers zoom levels by domain, so once you've been there and applied zoom, you shouldn't need to do it again until the site is restyled to use different sizes. The way the shot cuts off the top of the page, if negects to show the vast difference in font size between the "beautifully clear and highly legible" body fonts and the zoomed to gigantic page title fonts. If you revisit the page in a new browser with a new profile, or the same browser with a new profile, or reset the zoom level to none (Ctrl-0), you'll find the resulting fonts not so "beautifully clear and highly legible", probably to a size smaller than your tiny Firefox UI menu fonts. Browser zoom is a *defense* mechanism. Defenses are only needed in the context of offensive behavior. In the instant case, the offensive behavior is web page font sizing that *completely* disregards the optimum size pre-defined via the visitors' browser default size settings. It may be acceptable to people who only use one computer and one DE to have to ever apply zoom on any given page or domain, but they shouldn't have to. Those who use a lot of DEs and a lot of browsers won't have the luxury of having been to any every frequented page before and having zoom level remembered. There's no good reason for anyone to have had to apply zoom ever in the first place. Web pages don't need to be rude, as their creators do have tools that enable them to embrace user defaults to get the results they want. The instant case if it remains as it is will remain particularly perplexing, as the TDE main site CSS is one of the very unfortunately few places on web where rude styling is not in place, in stark contrast its mailing list archive.

@Lisi, I think Felix is trying to say that the only reason it is, as you say "Beautifully clear and highly legible" is because you use zoom. If you didn't use zoom then it would not be "Beautifully clear and highly legible". The real point in this is, not the css etc or the pixel setting but rather, the fact you use zoom in this but not in others.

Any further suggestions?

Timothy Pearson composed on 2014-11-12 20:14 (UTC-0600): Little new. :-( Better, but: 1-Spindly, worst looking "common" monospace font I've ever seen, Courier, is still what it's using, since Monaco is only found on Macs. On Linux installations that do not have M$ web fonts installed, and even on plenty of those that don't, Courier is extra bad, since it's usually an ancient bitmap font (available in limited sizes) instead of a vector font.

2-font size is still disrespecting users. What purpose is served setting small on PRE here?

Not previously mentioned: previous/next and month are set to .7em (physical size 49% of default). Why? http://fm.no-ip.com/Auth/area70.html

(I prefer Courier New as a monospace font, since it's effectively invisible to me and lets me concentrate on the content.

The best suggestion I can offer is the same as always, defer to the defaults selected by the user.

Fine. But I can see it. Most archives are virtually inaccessible to me. I like being able to see it, and regard it as a strength of the archives that they make it possible.

What other lists' archives are a problem for you? Maybe we can help you change something on your system to make it easier for you.

Based on the font sizes in your browser UI, one would not expect you to need such big web page fonts for you to be able to consider them "beautifully clear and highly legible".

Felix Miata wrote:

> http://fm.no-ip.com/SS/trinitylistarchive1411.png

> Proposed fix:

...or not. Your screen image looks perfectly readable to me.

Am Samstag, 8. November 2014 schrieb Felmon Davis: Anything that consumes power when you do not use it is a waste of some kind, at least of money. Nik

folks, hoping to drink from the font of your wisdom. I have a NAS through which I can pipe printing via cups. it works fine but I wonder if it wouldn't save electricity to get a dedicated print server and only use the NAS when I am doing serious backups. btw my problem with kpowersave not showing configuration options was solved (sort of) by restarting /usr/sbin/hald. long for a cleaner solution. that's a different topic. what about NAS vs print servers? F. -- Felmon Davis Many hands make light work. -- John Heywood --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@ lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists. pearsoncomputing.net Read list messages on the web archive: http://trinity-users. pearsoncomputing.net/ Please remember not to top-post: http://trinity. pearsoncomputing.net/mailing_lists/#top-posting

On Saturday 08 November 2014, Andrew Young wrote: I might missunderstand but - I always see / saw my own mail on the list (working with Kmail). Gerhard

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224 But you do see all other posts to the list, correct? I wonder if gmail is trying to be "helpful" and blocking your posts from coming back in...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224 But you do see all other posts to the list, correct?

I wonder if gmail is trying to be "helpful" and blocking your posts from coming back in...

Hi Guys, Apologies for top post ! I get these messages quite regularly ! Now I just ignore them since most of the posts refered to I seem to get anyway. Best Regards: Baron

On Friday 21 November 2014 09:12:41 Ilya Dogolazky wrote: &lt;kb9vqf(a)pearsoncomputing.net&gt;et>: > > During this window I will (in addition to many other changes) be > > addressing the sporadic list delivery issues to specific > > addresses relating to DKIM implementation on certain service > > providers. It is hoped that these upgrades will stabilize the > > lists somewhat and make them easier to use. > > Was your maintenance work in the beginning of November related to > sporadic "bouncing message" issue? > > Sometimes messages from the list can't be delivered to my gmail > account, and I think it doesn't have to do with my account > specifically. Anyway, see the "bouncing warning" as an example > below. I receiving such warnings quite often. If it's a problem on > the mailing list side, then I could provide more information, not > hesitate to ask. > > -- Ilya > > Here is the "warning" I received today: > > ---------- Forwarded message ---------- > From: &lt;trinity-users-help(a)lists.pearsoncomputing.net&gt; > Date: 2014-11-21 2:34 GMT+02:00 > Subject: warning from trinity-users(a)lists.pearsoncomputing.net > To: ilya.dogolazky(a)gmail.com > > > Hi! This is the ezmlm program. I'm managing the > trinity-users(a)lists.pearsoncomputing.net mailing list. > > I'm working for my owner, who can be reached > at trinity-users-owner(a)lists.pearsoncomputing.net. > > > Messages to you from the trinity-users mailing list seem to > have been bouncing. I've attached a copy of the first bounce > message I received. > > If this message bounces too, I will send you a probe. If the probe > bounces, I will remove your address from the trinity-users mailing > list, without further notice. > > Copies of these messages may be in the archive. > > To retrieve a set of messages 123-145 (a maximum of 100 per > request), send an empty message to: > &lt;trinity-users-get.123_145(a)lists.pearsoncomputing.net&gt; > > To receive a subject and author list for the last 100 or so > messages, send an empty message to: > &lt;trinity-users-index(a)lists.pearsoncomputing.net&gt; > > Here are the message numbers: > > 6970 > 6999 > > --- Enclosed is a copy of the bounce message I received. > > Return-Path: &lt;MAILER-DAEMON(a)vali.starlink.edu&gt; > Received: (qmail 8614 invoked by uid 64014); 8 Nov 2014 15:27:27 > -0600 Received: by mail.pearsoncomputing.net (Postfix) > id 4A46664059F; Sat, 8 Nov 2014 15:27:27 -0600 (CST) > Date: Sat, 8 Nov 2014 15:27:27 -0600 (CST) > From: MAILER-DAEMON(a)mail.pearsoncomputing.net (Mail Delivery > System) Subject: Undelivered Mail Returned to Sender > To: > trinity-users-return-6970-ilya.dogolazky=gmail.com(a)lists.pearsoncom >puting.net Auto-Submitted: auto-replied > MIME-Version: 1.0 > Content-Type: multipart/report; report-type=delivery-status; > boundary="184B2640507.1415482047/mail.pearsoncomputing.net" > Content-Transfer-Encoding: 7bit > Message-Id: &lt;20141108212727.4A46664059F(a)mail.pearsoncomputing.net&gt; > > This is a MIME-encapsulated message. > > --184B2640507.1415482047/mail.pearsoncomputing.net > Content-Description: Notification > Content-Type: text/plain; charset=us-ascii > > This is the mail system at host mail.pearsoncomputing.net. > > I'm sorry to have to inform you that your message could not > be delivered to one or more recipients. It's attached below. > > For further assistance, please send mail to postmaster. > > If you do so, please include this problem report. You can > delete your own text from the attached returned message. > > The mail system > > &lt;ilya.dogolazky(a)gmail.com&gt;om>: host > gmail-smtp-in.l.google.com[74.125.201.26] said: 550-5.7.1 > Unauthenticated email from yahoo.com is not accepted due to > domain's 550-5.7.1 DMARC policy. Please contact administrator of > yahoo.com domain if 550-5.7.1 this was a legitimate mail. Please > visit 550-5.7.1 http://support.google.com/mail/answer/2451690 to > learn about DMARC 550 5.7.1 initiative. hz7si14466145icc.64 - gsmtp > (in reply to end of DATA command) > > --184B2640507.1415482047/mail.pearsoncomputing.net > Content-Description: Delivery report > Content-Type: message/delivery-status > > Reporting-MTA: dns; mail.pearsoncomputing.net > X-Postfix-Queue-ID: 184B2640507 > X-Postfix-Sender: rfc822; > trinity-users-return-6970-ilya.dogolazky=gmail.com(a)lists.pearsoncom >puting.net Arrival-Date: Sat, 8 Nov 2014 15:27:26 -0600 (CST) > > Final-Recipient: rfc822; ilya.dogolazky(a)gmail.com > Original-Recipient: rfc822;ilya.dogolazky(a)gmail.com > Action: failed > Status: 5.7.1 > Remote-MTA: dns; gmail-smtp-in.l.google.com > Diagnostic-Code: smtp; 550-5.7.1 Unauthenticated email from > yahoo.com is not accepted due to domain's 550-5.7.1 DMARC policy. > Please contact administrator of yahoo.com domain if 550-5.7.1 this > was a legitimate mail. Please visit 550-5.7.1 > http://support.google.com/mail/answer/2451690 to learn about DMARC > 550 5.7.1 initiative. hz7si14466145icc.64 - gsmtp > > --184B2640507.1415482047/mail.pearsoncomputing.net > Content-Description: Undelivered Message > Content-Type: message/rfc822 > Content-Transfer-Encoding: 7bit > > Return-Path: > &lt;trinity-users-return-6970-ilya.dogolazky=gmail.com(a)lists.pearsonco >mputing.net> Received: from localhost (localhost [127.0.0.1]) > by mail.pearsoncomputing.net (Postfix) with ESMTP id > 184B2640507 for &lt;ilya.dogolazky(a)gmail.com&gt;om>; Sat, 8 Nov 2014 > 15:27:26 -0600 (CST) Received: from mail.pearsoncomputing.net > ([127.0.0.1]) > by localhost (vali.starlink.edu [127.0.0.1]) (amavisd-new, > port 10032) with ESMTP id 4Z0AwczzKYz2 for > &lt;ilya.dogolazky(a)gmail.com&gt;om>; Sat, 8 Nov 2014 15:27:25 -0600 (CST) > Received: from localhost (localhost [127.0.0.1]) > by mail.pearsoncomputing.net (Postfix) with ESMTP id > 4CC3E6405B8 for &lt;ilya.dogolazky(a)gmail.com&gt;om>; Sat, 8 Nov 2014 > 15:27:11 -0600 (CST) X-Virus-Scanned: amavisd-new at > pearsoncomputing.net > Received: from mail.pearsoncomputing.net ([127.0.0.1]) > by localhost (vali.starlink.edu [127.0.0.1]) (amavisd-new, > port 10026) with ESMTP id AOFsSTpgHHzp for > &lt;ilya.dogolazky(a)gmail.com&gt;om>; Sat, 8 Nov 2014 15:27:11 -0600 (CST) > Received: from vali.starlink.edu (vali.starlink.edu [192.168.1.21]) > by mail.pearsoncomputing.net (Postfix) with SMTP id > 5EC6E6405BE for &lt;ilya.dogolazky(a)gmail.com&gt;om>; Sat, 8 Nov 2014 > 15:27:05 -0600 (CST) Received: (qmail 7106 invoked by uid 1002); 8 > Nov 2014 15:27:03 -0600 Mailing-List: contact > trinity-users-help(a)lists.pearsoncomputing.net; run by ezmlm > Precedence: bulk > X-No-Archive: yes > List-Post: <mailto:trinity-users@lists.pearsoncomputing.net> > List-Help: <mailto:trinity-users-help@lists.pearsoncomputing.net> > List-Unsubscribe: > <mailto:trinity-users-unsubscribe@lists.pearsoncomputing.net> > List-Subscribe: > <mailto:trinity-users-subscribe@lists.pearsoncomputing.net> > Reply-To: trinity-users(a)lists.pearsoncomputing.net > Delivered-To: mailing list trinity-users(a)lists.pearsoncomputing.net > Received: (qmail 7098 invoked by uid 64014); 8 Nov 2014 15:27:03 > -0600 X-Virus-Scanned: amavisd-new at pearsoncomputing.net > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; > s=s2048; t=1415482021; > bh=UzH5/VHrwmb9JvkCfI8ufuvq+VkIKY2AeDPg1SiCdYo=; > h=From:Reply-To:To:Subject:Date:References:In-Reply-To:From:Subject >; > b=Po7MpSsKOjADl05QLz3Edy933/1M+IQ9b4Pyj/t36LRcTEcsOLav83eVi2UAwDZ8B >7hO9fAFupC2OGM04Y5c+yZM/iyv+T5qwJEs0GBWMcyqWF/C2GCujIi8YjpGuX4F1zzqk >Aytx0OKyVC2Ppwv6co/KNuD58jJMs65ymkburf5BFfedSArH+EgG0sY2rPdP8j5V5j++ >kJGiA1IWqWnkcaw/mHbU3F8TlV90cFRSIwUDxVRvAZyuj/159IGv7VXBNnV1loyJdbnF >AuPs2vLdgaf3J1Pa69huM0HTHtE7zaMWUrVYIEt0D3av2nulfmZWACQCfjQ3CTC+inGk >VsglA== DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s2048; > d=yahoo.com; > b=UCx6qklfZYp+a8IiOkKP9n07+euU/XV5/HABRcNqWg1ngM8fxFJIoE9rVDWSgH8A/ >uXN/mw0zaXoQrrfGC3qXwKbxqMixmxajFYNq4kCJcfDuaaaeTdZmUgQIDWTtpHZf79/H >aV8PSL0VZ+o+Cg3a2DZPBvECIXQvtuuoZNpbJS7M5KwOO6Stv3r724SjHXzlFeU93FUy >r0KwnjA9mzRs+QXs70v3MmKT670vs8c8TIniCq0eh5shwHqhd2Nt+27upxoVYt+YLK0+ >xvWGzSbNhBUBXVJK8UmOGVOYjcEhzBwzN9BMNxpI2+WGd8eBEeA3mJXs01gmg8nGpkLO >+7Gew==; X-Yahoo-Newman-Id: > 819014.71042.bm(a)smtp110.mail.ne1.yahoo.com X-Yahoo-Newman-Property: > ymail-3 > X-YMail-OSG: nK7eEHMVM1kn.1lcBElgG120QiF4YnIPZiEja12srvi.zJF > qyadEvWorrnd5hc6cw9TzPvEhQ0vQZFUv.PyLrI3q4.FUNKroyazgy857m4I > 0X4DvT4HyesYvOkORA.e_Ox_tyoq4bna7Kcd3crmO2VKeMT5m1qbzMU5UA5a > 7aAxR.Y1_LgVF4VUoiy4ipQd.IGfxpDZMi.JDewyXlGXw7RQuZd5hIJtKWv6 > AVzzTXmyooqoIES7RGE2Ex0oexpa4K4dRAXxpBVqmnjTsdDC_huVRrqPSZrF > JcI_kC8aGTe99qCirt_Q8_VYDE3DXJNMxlWCdeE8Nszb_.2JziKI0Gng_ZRP > SHzTNL7zCaf6BEtIteoAEihui8yucV7ALCgkstyO6vqneiJhgTW2rcSgi84B > UmkwfB3ZNDqOamCSD.J9tiLb3cdWfFKzKPJmDRiNOrX0k.0KrpVzes00AWQs > 4qn.VnnWQppsrPdbm0uNOYri3IexjVfqyqzNjd96I.LXJA7KPYZ1VNH0JuZR > vhHvxEl6a90GXplGZkwrYoR1eg3gai39YecBJoReyGVur9_lDp7X8yd9s05Y > Zfdsn_i20Z_3LL3o27c2DGMzBv547aIbj53W7a_MGP2KLp0YcsxMvKKInF3p > n0X25pEhjS2ZVw0a1yWLsy_TUBqav3dH51XQ- > X-Yahoo-SMTP: oof8RZSswBD6lyWf5CrTMZF.f7.PtyA- > From: Andy &lt;Andy4stuff(a)yahoo.com&gt; > To: trinity-users(a)lists.pearsoncomputing.net > Date: Sat, 8 Nov 2014 16:27:01 -0500 > User-Agent: KMail/1.9.10 (enterprise35 0.20100827.1168748) > References: > &lt;7e2577d182b15c9f809141d3b3d77203.squirrel(a)vali.starlink.edu&gt; > &lt;201411082157.04471.gerhard.zintel(a)mrs-thomas.de&gt; > &lt;020c0156d6b7ef517c3bb28cd2f845be.squirrel(a)vali.starlink.edu&gt; > In-Reply-To: > &lt;020c0156d6b7ef517c3bb28cd2f845be.squirrel(a)vali.starlink.edu&gt; > X-KMail-QuotePrefix: > > MIME-Version: 1.0 > Content-Type: Text/Plain; > charset="utf-8" > Content-Transfer-Encoding: 7bit > Content-Disposition: inline > Message-Id: &lt;201411081627.01647.Andy4stuff(a)yahoo.com&gt; > Subject: Re: [trinity-users] Email server maintenance > > On Saturday 08 November 2014 04:00:46 pm Timothy Pearson wrote: > > > On Saturday 08 November 2014, Andrew Young wrote: > > >> On 07/11/14 11:55, Baron wrote: > > >> > On Friday 07 November 2014 03:08:29 Timothy Pearson wrote: > > >> >> The Email server is now back online and functioning > > >> >> normally. Please let me know if you encounter any > > >> >> difficulties. > > >> >> > > >> >> Thanks! > > >> >> > > >> >> Tim > > >> > > > >> > I wonder, does this mean that I might be able to see my own > > >> > posts. :-) > > >> > > >> That would be a useful feature. > > > > > > I might missunderstand but - I always see / saw my own mail on > > > the list (working with Kmail). > > > Gerhard > > > > Same here as well, with various clients. I am aware of some > > providers having interoperability issues with the > > pearsoncomputing.net Email server; hopefully the upgrade has > > resolved most of them but I need feedback to know one way or the > > other. > > > > Tim > > I'm using Yahoo email through Kmail. I *used* to see my own posts, > but haven't in a long time. > > Andy

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224 Probably not--that has been ongoing for some time. The maintinance laid the groundwork for me to attempt to deal with the problem via DKIM, but that has not been activated at this time. The critical portion of the message is this header: "Unauthenticated email from yahoo.com is not accepted" As to why Google thinks "pearsoncomputing.net" == "yahoo.com" I have no idea, but it seems that we are not alone in dealing with this issue: http://www.openwall.com/lists/oss-security/2014/08/31/1 http://onyx-pc.com/content/ezmlm-warning http://osdir.com/ml/opensource-software-security/2014-08/msg00198.html http://squid-web-proxy-cache.1019090.n4.nabble.com/problem-with-squid-users -maillist-td4667315.html etc. That last message at least outlines the problem. Trouble is we are one of the sites struggling with inertia; we couldn't implement DKIM until the recent upgrades, and after the upgrades I have been too busy with R14 release to roll out DKIM, etc. Boils down to the typical human condition I suppose: too much to do, too little time and money. :-)