similar to: top-posting and netiquette

I would prefer simple text in tech and security related news but you are right - they are HTML formatted. I think it is pure marketing thing. people dump other stuff to remind you who they are and for a sort of entertaining us. The same story is in OS desktop GUI including Linux. I use CentOS 6 and 7 and still do not like 7. Not to mention in the morning Win 10 with all its crap included.

Your right with this part But as I also have some knowldge on other parts but ms , *nix etc I know it is nowadays possible for almost every email client to correctly display html email. And be honest does it not read more easy if you have a nice font and some markup available? I know mailman is an old package and should be more flexible in handling and distributing html email. For standards:

What is the proper netiquette of monitoring a router? How often is often enough verses too often? How large should the monitoring probes be? Is there an aggregate speed (bps) or amount (pps) or both (bps and pps) that should not be exceeded? Grant. . . .

Look into mutipart and offer both html and plain text in the same email. This allows the client to view it as they see fit. If you do send html it has a much more restrictive implementation than html and css for a webpage so study up on what you can and can't do. Mailchimp has some great info about this. Cameron On Fri, Feb 2, 2018 at 1:36 AM, Nicolas Kovacs <info at microlinux.fr>

Hi, This question is not exactly CentOS-related strictly speaking, but here goes. I'm running a few newsletter servers for myself and a handful of clients on public CentOS servers with PHPList. For the last twenty years or so I've followed the basic rule that mails should have no formatting whatsoever, only simple text. And now I wonder if that basic rule of netiquette also applies to

On 12/01/2018 05:00 PM, Hendrik Boom wrote: > > There's an extensive email etiquette post somewhere on the net > explaining why setting 'reply-to' to the list is a bad idea. > > Reply-to is intended for the sender to explain that replies shouldn't > be sent to the obvious sending address, but to another address. > This is essential if, say, the sender is

What follows is a sample of the output of svn2cl for the trunk. I added the username-to-email mapping file, enabled revision numbers, and told it to group commits on a single day by the same author: $ svn2cl --group-by-day --include-rev --authors=../../svn2cl.authors Arjen: I used your main email address that you typically list in the ChangeLog entries. Arnaud: I wasn't sure which address

Hi guys, I wrote for Arnaud that I tested the liebertgxt2 driver in 2.4.3. I compare output of Richard's code, Spiros code and nut 2.4.3. Output of Richard and Spiros codes was same and right. Output of Liebertgxt2 driver isn't. Examples: Our UPS : Liebert GXT2-1000RT230 Model Name,Firmware version,SN,date of manufactured values was right. Fields

Hi folks, I''ve noticed in recent times on the list that we seem to be getting a low signal-to-noise ratio with a lot of posts (particularly those where people include their configuration). Once you have posted the appropriate information once, there is no need to keep quoting it unless it is central to the discussion. Trimming irrelevant material makes it easy for people who have been

If you must use an out-of-office feature in your email, please exclude any mailing lists you're subscribed to. I deleted the message that I was forwarding in this, but I'm sure we all know what I'm talking about. Tim Conway Unix System Administration Contractor - IBM Global Services desk:3032734776 conway@us.ibm.com

Gentle susbscribers, This is a reminder to all samba mailing list subscribers that this list is moderated. Most of you know what that means, so for the benefit of those who are new to the list or who are not familiar with the mechanics of a mailing list please note the following: 1) Incoming messages are scanned and filtered by mailman to remove messages that may have objectionable content, are

Great, thanks! Two questions: * what is a domain literal? Is this something like 192.168.0.1? In this case, the '[]' are probably unnecessary. * are you sure you want to use fprintf(stderr, ...) in a library? This doesn't seem like a good idea to me. Wouldn't it be more consistent to extend upscli_errlist[] ? -- Peter Arjen de Korte wrote: > > Author:

-----Original message----- > From:Turritopsis Dohrnii Teo En Ming <teo.en.ming.smartphone at gmail.com> > Sent: Friday 18th October 2019 4:28 > To: J Martin Rushton via CentOS <centos at centos.org> > Subject: [CentOS] Top 7 Programming Languages That Employers Really Want [snip] Your posting fails to follow the CentOS mailinglist policy [1], specifically: Do not Cross

On 15-04-16 13:14, g wrote: > > > On 04/15/16 04:29, Patrick Laimbock wrote: >> On 15-04-16 00:39, Andrew Daviel wrote: > <<>> > > Patrick, > > 'threading breaking' is against centos etiquette and netiquette. > > replying thread breakers does nothing but encourage them to do so again. > > many subscribers frown on thread breakers and

2009/10/19 Jobbagy Robert > |Hi Arnaud! Hi Robert, > I'm a hungarian developer and I need make a linux driver for this ups: > "Liebert" ? ? ? "ups" ? "5" ? ? "UPStation GXT2" ? ? ? ?"contact-closure > cable" "liebert" (I copied it from your previous mail) > So please help me,where should I start it ? > > |Thank

On 12/25/23 00:30, Vegard Nossum wrote: > > On 25/12/2023 08:40, Randy Dunlap wrote: >> I do see one thing that I don't like in the generated html output. >> It's not a problem with this patch. >> The #defines for DRM_NOUVEAU_VM_BIND_OP_MAP etc. have a ';' at the >> end of each line: >> >> struct drm_nouveau_vm_bind_op { >> ????

Hi! I have a samba file server (192.168.1.2) and wins server (192.168.1.2) with ~70 clients. The server's netbios names are ALMA and KORTE. The Workgroup's name is ALMA. Issue 1: -------- nmblookup -U 192.168.1.2 -R korte querying korte on 192.168.1.2 192.168.1.2 korte<00> nmblookup -U 192.168.1.2 -R alma querying alma on 192.168.1.2 255.255.255.255 alma<00> strange.... I

On 12/01/2018 05:49 PM, Ralph Seichter wrote: > * Michael A. Peters: > >> Netiquette posts are just someone's opinion, and they often don't take >> into account the vastly different way different types of minds work. > > Mailing list netiquette has been around for decades, for good reasons. > If Joe User's mind "works differently", Joe needs to

On 12/24/23 22:51, Vegard Nossum wrote: > As of commit b77fdd6a48e6 ("scripts/kernel-doc: restore warning for > Excess struct/union"), we see the following warnings when running 'make > htmldocs': > > ./include/uapi/drm/nouveau_drm.h:292: warning: Excess struct member 'DRM_NOUVEAU_VM_BIND_OP_MAP' description in 'drm_nouveau_vm_bind_op' >

On 02/12/2018 03:05, Michael A. Peters wrote: [...] > But - I would wager that over 95% of the time when someone hits the > reply button on a list post, their intent is to reply to the list. Even if it's 99%: What is the lesser risk if someone get's it wrong? Apart from the situation that people send mails over the mailing list with "for X.Y." in the subject and no one