[opensuse] OT: email etiquette 201: stripping address from reposted content
Wow... I wonder if I should read my messages... (referring to the invitation in the original message below...) Usually such things are filtered out for me, but for some reason, the wording and language in this email did not, statistically, look like spam. Friendly reminder? (Yes, this is X-posted, as were the originals below, so just so people on both lists are reminded..)... Some people's email SW strips out email addresses and only puts the name in the content section so when mail-archive services pick up the list, email addressses don't end up as feed for phishing and spamming stuff... Then there are people who don't use such email SW. Using the below phish/spam I got, I'd say, at least these people ought to think about how their email SW is configured to include someone's name on reply: Patrick, Andrey, Greg, and Cristian among others that aren't as clearly attributed (guess they got lucky!). But a friendly reminder about internet email hygiene practices, I thought, might be useful. FWIW, I've been guilty in the past as well and had to make sure my settings didn't violate such courtesies (usually told to me as being rules or common sense, but I'm not quite as militant about it...). p.s. note, I did obfuscate, (I hope enough! -- used utf8-display versions of at and dot -- just watch some email SW be "smart" and convert it back into the ansi equivs...there, mangled the dom's too. No comments/replies to this email are needed by me... -------- Original Message -------- Received by 'my_email_infrastructure...' Received from lexmailer4.data.lt (lexmailer4.data.lt [31.193.193.40]) Received from from qmail-test.data.lt (qmail-test.data.lt [31.193.193.201]) Subject: 36 unread messages wait for you in Qmail Date: Tue, 12 Feb 2013 22:02:58 -0000 From: no-reply@qwekee.com Reply-To: no-reply@qwekee.com To: suse＠tlnx．org Hello suse＠tlnx．org, We've noticed that it's been a week since you read your Qmail messages. Your colleagues might be confused and wait for your answers Colleagues whose messages wait unread: Oddball wrote:> Op 30-10-12 08:48, Freek de Kruijf schreef:>> Op maandag 29 oktober 2012 01:44:09 schreef Oddball:>>>>>> so still unable to login to root desktop..---- There's a /etc/securetty that specifies what terms r... ------------------------------------------------------------------------ Michael Schroeder wrote:> On Thu, Nov 08, 2012 at 06:41:03PM +0100, Stefan Dirsch wrote:>> This is *not* a bug, but an intentional change. ;-) The GLUE layer is now>> built on the target system.> > Uh, doesn't that conflict wi... ------------------------------------------------------------------------ On Mon, 2012-11-12 at 04:00 -0800, Linda W wrote: > Michael Schroeder wrote:> > On Thu, Nov 08, 2012 at 06:41:03PM +0100, Stefan Dirsch wrote:> >> This is *not* a bug, but an intentional change. ;-) The GLUE layer is now> ... ------------------------------------------------------------------------ Patrick Shanahan wrote:> * Linda W <suse＠tlnx．org> [11-13-12 18:21]:>> I stared upgrading to 12.2 -- and all was going fine until I>> rebooted. Then complete failure -- had to use rescue disk.> & gt; You have asked an ... ------------------------------------------------------------------------ Carlos E. R. wrote:> -----BEGIN PGP SIGNED MESSAGE-----> Hash: SHA256> > On 2012-11-14 00:52, Greg Freemyer wrote:>> So the question / bugzilla is why /usr is not mounted in your>> case. > Indeed.> The change was do... ------------------------------------------------------------------------ Felix Miata wrote:> On 2012-11-13 19:54 (GMT-0500) Patrick Shanahan composed:> Of course, it did get discussed here, so if Linda didn't already she > should comb through the archives (and Bugzilla) to see whether there's > any hope to ... ------------------------------------------------------------------------ Carlos E. R. wrote:> Because that's the solution the devs here implemented, that's why. If> you want a different solution you will have to make a very sound case> to convince them (and a year after!) or implement it yourself.> Otherwis... ------------------------------------------------------------------------ Felix Miata wrote:> On 2012-11-14 08:37 (GMT-0800) Linda W composed:> >> I was told at the time that systemd no longer had this requirement>> and that it could mount /usr a s an initial step.> > If systemd is your pr... ------------------------------------------------------------------------ Carlos E. R. wrote:> -----BEGIN PGP SIGNED MESSAGE-----> Hash: SHA256> > On 2012-11-14 02:39, David Haller wrote:> >>> You need initrd- If you do not want to use it, then you will need>>> to hack your own solution.... ------------------------------------------------------------------------ Andreas Jaeger wrote:> Linda, stop accusing people. We always said that an initrd is needed, if > you didn't understand that, then it's your problem but stop calling > users liars.---- It was clear that initrd was needed to load *drivers*... ------------------------------------------------------------------------ Andrey Borzenkov wrote:> On Thu, Nov 15, 2012 at 12:17 PM, Linda W <suse＠tlnx．org> wrote:>> Give me ANY reason.> Personal experience.> > - mount by LABEL/UUID/whatever, but not by /dev/sdX. Uncountable times> I got ... ------------------------------------------------------------------------ On 11/15/2012 09:17 AM, Linda W wrote: > Moreover, what is there on initrd that you can't put in root? Find out yourself: $ mkdir /tmp/initrd $ cd /tmp/ini trd $ gzip -dc - < /boot/initrd | cpio -i $ find . -ls [...] It's a ... ------------------------------------------------------------------------ Claudio Freire wrote: > In any case, in that discussion, IIRC the decision to leave symlinks> in /bin was made to be backwards-compatible. With those symlinks, a> script would only break if run from an initrd script, before /usr is> ... ------------------------------------------------------------------------ Stefan Seyfried wrote:> Am 15.11.2012 22:10, schrieb Linda W:> >> of loading a 20-40MB initrd (cf. my kernel=~5MB), which duplicates>> /usr/bin.> > susi:~ # ls -l /boot/initrd* -h> lrwxrwxrwx 1 root root 22 Nov 12 ... ------------------------------------------------------------------------ Greg Freemyer wrote:> On Thu, Nov 15, 2012 at 1:14 PM, Claudio Freire <klaussfreire＠gemail．com> wrote:>> With those symlinks, a>> script would only break if run from an initrd script, before /usr is>> mounted. Is that you... ------------------------------------------------------------------------ Per Jessen wrote:> Rajko wrote:> >> On Fri, 16 Nov 2012 19:23:54 -0800>> Linda W <suse＠tlnx．org> wrote:>>> >> Ahh.. resorting to childish name calling now.>> Linda, it is childish they way you act.&... ------------------------------------------------------------------------ Linda W wrote:> Greg KH wrote:>> On Thu, Nov 15, 2012 at 12:17:47AM -0800, Linda W wrote:>>> So far no one is able to explain why it is needed other than>>> It's a fad or it's cool..>>>> Because the o... ------------------------------------------------------------------------ On Sun, Nov 18, 2012 at 7:02 AM, Dirk Gently <dirk.gently00＠gemail．com> wrote:> It's just like KDE 4.0 all over AGAIN.>> If it weren't for YaST, I would of ditched this distribution controlled> by the biggest bunch of arrogant ass... ------------------------------------------------------------------------ Carlos E. R. wrote:> -----BEGIN PGP SIGNED MESSAGE-----> Hash: SHA256> > On 2012-11-18 19:27, Linda W wrote:> >> Nep. /usr = short for /user... as separate from system.> > Wrong.--- Sorry, but have a quote of Dennis... ------------------------------------------------------------------------ On Mon, Nov 19, 2012 at 10:58 AM, Linda W <suse＠tlnx．org> wrote:>> On 2012-11-18 19:27, Linda W wrote:>>>>> Nep. /usr = short for /user... as separate from system.>>>>>> Wrong.>> --->... ------------------------------------------------------------------------ Carlos E. R. wrote:> Seconds against hours.--- Seconds? to Hours? for a user to regenerate theirkernel in the field? Factory could stick w/initrd, butmy suggestion was to allow users to optimize that to directboot by installing & runnin... ------------------------------------------------------------------------ Philipp Thomas wrote:> The question is, how do I support a maximum> of different devices *without* requiring the user to compile his own> kernel.> >> For those, you *offer* them the option to rebuild the kernel with>> thei... ------------------------------------------------------------------------ -----Original Message-----From: "Linda W" <suse＠tlnx．org>Sent: Wednesday, November 21, 2012 8:12pmTo: "oS-fctry" <opensuse-factory＠opensuse．org>Subject: [opensuse-factory] Re: Why is initrd needed - to support moving bin files fro... ------------------------------------------------------------------------ Andrey Borzenkov wrote:>> I couldn't understand why boot processes no longer worked -- "boot.local">> was reserved for calling site-local boot needed processes after boot and before>> single-user. It is no longer called,> &g... ------------------------------------------------------------------------ Cristian Rodríguez wrote:> El 28/11/12 21:07, Linda W escribió:>> Perhaps someone can explain to me why Windows doesn't>> need a pre-boot ramdisk in order to boot, while Linux does?> > Linux does not need an initrd to boot... ------------------------------------------------------------------------ On 11/29/2012 09:26 AM, Hans Witvliet wrote:> from original MS-cd/dvd but lack support for all sorts of things.> Some even don't recognise network hardware, so you need a different> machine connected to the Net, and an USB-stick to downlo... ------------------------------------------------------------------------ Felix Miata wrote:> Likely the registry, if you can call that doing anything right.> > Ever tried moving a Windows HD to another motherboard and booting it. I > don't think it ever works.---- It almost always works. What doesn't work ... ------------------------------------------------------------------------ Jim Henderson wrote:> If you want to understand why Linux uses initrd, I suggest you take some > time and talk with the Linux kernel developers, after reading up on the > history of the Linux kernel.---- Linux kernel developers will say i... ------------------------------------------------------------------------ Ken Schneider - openSUSE wrote:> On 11/28/2012 07:07 PM, Linda W pecked at the keyboard and wrote:> > Linda,> > You have been ask several times to stop cross posting, so once again > please stop.---- Um which list does one po... ------------------------------------------------------------------------ Anders Johansson wrote:> No, but it is something distributions do - the idea is to have one solution > that fits all users. I dare you to build one kernel that will work for all > openSUSE users, or even just you and me--- As others have ... ------------------------------------------------------------------------ Peter Hanisch wrote:>> Functionally intermediate binary that is loaded during boot and>> includes filesystem and possibly volume manager drivers and logic to>> load additional drivers on demand is initrd. With the primary differe... ------------------------------------------------------------------------ Carlos E. R. wrote:>> ----&g t;> You tell me where it belongs. It's about Suse>> 12.2 and suse 12.3 and beyond. Last person I asked which>> list I should shut out of the discussion, I got no answer,>> so what's your... Join and try it out, it‘s free and your colleagues will only be grateful. Click on this link and you'll only have to create a password. Activate <http://www.qwekee.com/profile/sign-up/step1/9841229a5d5c9f4273a1/?next=http://qmail.qwekee.com/>. Qmail Be in charge Qmail team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 12/02/13 20:48, Linda Walsh escribió:
Wow... I wonder if I should read my messages... (referring to the invitation in the original message below...)
Usually such things are filtered out for me, but for some reason, the wording and language in this email did not, statistically, look like spam.
Friendly reminder? (Yes, this is X-posted, as were the originals below, so just so people on both lists are reminded..)...
It is a spam generated by some very shady marketing stuff and it is not related to openSUSE in any way. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Linda Walsh <suse@tlinx.org> [02-12-13 18:52]: [...]
Some people's email SW strips out email addresses and only puts the name in the content section so when mail-archive services pick up the list, email addressses don't end up as feed for phishing and spamming stuff...
Then there are people who don't use such email SW. Using the below phish/spam I got, I'd say, at least these people ought to think about how their email SW is configured to include someone's name on reply:
Patrick, Andrey, Greg, and Cristian among others that aren't as clearly attributed (guess they got lucky!). But a friendly reminder about internet email hygiene practices, I thought, might be useful.
jfyi, it is no harder to strip email addresses from the body of msgs as from the header.... mox nix [...]
-------- Original Message -------- Received by 'my_email_infrastructure...' Received from lexmailer4.data.lt (lexmailer4.data.lt [31.193.193.40]) Received from from qmail-test.data.lt (qmail-test.data.lt [31.193.193.201]) Subject: 36 unread messages wait for you in Qmail Date: Tue, 12 Feb 2013 22:02:58 -0000 From: no-reply@qwekee.com Reply-To: no-reply@qwekee.com To: suse＠tlnx．org
Hello suse＠tlnx．org,
We've noticed that it's been a week since you read your Qmail messages. Your colleagues might be confused and wait for your answers
Colleagues whose messages wait unread: [...]
This is a different/clever attempt to data mine via social engineering. I have seen seven of these/similar posts in the last few weeks. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2013-02-12 at 15:48 -0800, Linda Walsh wrote:
Some people's email SW strips out email addresses and only puts the name in the content section so when mail-archive services pick up the list, email addressses don't end up as feed for phishing and spamming stuff...
Then there are people who don't use such email SW. Using the below phish/spam I got, I'd say, at least these people ought to think about how their email SW is configured to include someone's name on reply:
While that is true, it is not the case for the sample spam you post below. HAD you read this mail list emails, you would have noticed that we commented on it days ago. The spammer is related to some kind of ISP and is subscribed to the list. The spam was probably sent to everybody here. - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlEa6I8ACgkQtTMYHG2NR9VcJQCcC9QRsOloJR+L7AdwA0LL8pLB BHoAn0aWHAavao8oknR+x6HflGT5yMcM =GqR3 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
Then there are people who don't use such email SW. Using the below phish/spam I got, I'd say, at least these people ought to think about how their email SW is configured to include someone's name on reply:
While that is true, it is not the case for the sample spam you post below.
You may have gotten a different email. The one I got had 2 other email addresses included in the text in addition to my own. They were not in the headers of what was included. It may be the case they are on list, but it appeared, from the messages I saw, that only content was examined. Example (1 of several): Patrick Shanahan wrote:> * Linda W <suse＠tlnx．org> [11-13-12 18:21]:>> I stared upgrading to 12.2 -- and all was going fine until I>> rebooted. Then complete failure -- had to use rescue disk.> & gt; You have asked an ... Patrick's "wrote response" included my email address -- not just my name. As I stated in the original posting. 1) I substituted UTF-8 chars and munged the domain names in the posting I included. Had you read the email I just posted before replying to it, youl would have seen it included examples where people quoted with replies using email@addr's.
HAD you read this mail list emails, you would have noticed that we commented on it days ago.
I DON'T read every email from every list I am on. I tend to average 300-400/day unless i'm subb'ed to lkml and related lists, at the time, in which case it's easily over 1000 on weekdays and around 500-600 on weekends. However, I DO read emails I am responding ;-/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, 12 Feb 2013 18:50:36 -0800 Linda Walsh <suse@tlinx.org> wrote: And this is from header that I can see in my client:
From: Linda Walsh <suse@tlinx.org>
What is the difference that tells you that they examined only message body and not whole message. To me both strings starting with "Linda" are the same. Fact that they used part of the message with email address in it doesn't meant that they could not find address in a header. Of course, you don't have to be subscribed to get email addresses, and obscuring "Linda Walsh <suse@xxxxxxxxxx> wrote:" as it is done in official archive web page does not help. Also, I was curios about that < and > . It appears as html harvester, so there it is: http://lists.opensuse.org/opensuse/2013-02/msg00214.html ------------------------------------------------------------------ From: Linda Walsh <suse@xxxxxxxxx> Date: Tue, 12 Feb 2013 18:50:36 -0800 Message-id: <511AFF7C.1080101@tlinx.org> ------------------------------------------------------------------ There is no need to dive too far if you know that <suse@xxxxx> and <511AFF7C.1080101@tlinx.org> have all you need. As harvester is working on source of the page it will see < and >, and as it is not very sophisticated it will not try to replace those lt's and gt's with < and >, nor find messages that are not from last year (that is what I got from them). And they harvest just about anything: http://permalink.gmane.org/gmane.science.linguistics.corpora/17274 BTW, isn't easier to set filter and send spam into trash, then invent new rules how to behave online without actually checking can they work? -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Rajko wrote:
BTW, isn't easier to set filter and send spam into trash, then invent new rules how to behave online without actually checking can they work?
I have rules for spam, but rely on Bayseian as it's the most success for the least work. As for new rules? Haven't been on the internet long? a google search turn up a few other lists prompting such etiquette: http://www.daycomsolutions.com/Support/EmailEtiquette.html (1) When you forward an email, DELETE all of the other addresses that appear in the body of the message (at the top). That's right, DELETE them. Highlight them and delete them, backspace them, cut them, whatever it is you know how to do. It only takes a second. (You MUST of course click the "Forward" button first and then you will have full editing capabilities against the body and headers of the message. If you don't click on "Forward" first, you won't be able to edit the message at all.) http://www.tpcug-ct.org/email-etiquette.html (1) Before you send out a forwarded email, delete all of the other addresses that appear in the body of the message (at the top). That's right, delete them. Highlight them and delete them, backspace them, cut them, whatever it is you know how to do. It only takes a second. Once you click the Forward button you can edit the body and headers of the message. (text looks similar) http://cygwin.com/lists.html ***Please do not feed the spammers by including raw email addresses in the body of your message***. (in bold type... you will get called on it if you do it.)... ---- Other lists (gvim?) have similar policies... It's not a new rule... just one better known by those who've been around for a while...as I mentioned -- I get quite a few emails because I'm on multiple lists of things that interest me.... I have 'diverse' interests... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2013-02-13 at 04:09 -0800, Linda Walsh wrote:
a google search turn up a few other lists prompting such etiquette:
http://www.daycomsolutions.com/Support/EmailEtiquette.html
(1) When you forward an email, DELETE all of the other addresses that appear in the body of the message (at the top). That's right, DELETE them.
You do not listen. Even with that rule applied, you would have gotten that particular spam post. They are not harvesting from archives, they subscribed. They have full information, the same as you have or I have. - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlEbq/gACgkQtTMYHG2NR9V8bwCcDQN6LTdK7q0uEBNAutHM13nq n88AniULIW22idf5u9C7HEv7bWV6QgU1 =tRv4 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 13 Feb 2013 04:09:39 -0800 Linda Walsh <suse@tlinx.org> wrote:
As for new rules? Haven't been on the internet long?
:) Length of the Internet presence is advantage only before senior moments start to interfere with adaptability. Rules that you posted may have sense when applied on a different infrastructure, but they make no sense with openSUSE mail lists. Spammers have multiple ways to acquire emails, and cleaning up one, does not help with other few. Closing all holes will make every step of our life harder and the only benefit is that we will not see sporadic spam that escaped cascade of spam filters, from all servers it has to pass to our own mail clients. Interesting is that while our discussion still lives, particular spammer is filtered out few days ago, proving that spam filters work, not random rules from the net given with a clout of experienced user advice. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Rajko said the following on 02/14/2013 12:47 AM:
Closing all holes will make every step of our life harder and the only benefit is that we will not see sporadic spam that escaped cascade of spam filters, from all servers it has to pass to our own mail clients.
Indeed. Just recently someone suggested that instead of using ne of the many domains available to me personally for a variety of reasons that I use gmail "as it has excellent spam filtering". Well fine, but I have excellent spam filtering and so do my ISP services. Yes, occasionally I see a new one, and like the Borg, my spam filtering system adapts. To be honest I'm more upset by the runny nose I get from breathing cold air when I go for walks in the winter than I am by spam. However I don't consider this an excuse for "Global Warming". As it happens I never saw the original of the piece of spam that Linda is complaining about. As far as I can see this thread has been more intrusive than the spam. Can we please drop it. -- "How well we communicate is determined not by how well we say things but by how well we are understood." -- Andrew S. Grove. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-ID: <alpine.LNX.2.00.1302131148230.6785@Telcontar.valinor>
On Tuesday, 2013-02-12 at 18:50 -0800, Linda Walsh wrote:
> Carlos E. R. wrote:
>>> Then there are people who don't use such email SW. Using the
>>> below phish/spam I got, I'd say, at least these people ought
>>> to think about how their email SW is configured to include
>>> someone's name on reply:
>>
>> While that is true, it is not the case for the sample spam you post below.
>
>
> You may have gotten a different email.
> The one I got had 2 other email addresses included in the text
> in addition to my own.
So what? Mine had got your emails:
+++··········
- -----BEGIN PGP SIGNED MESSAGE-----Hash: SHA256 On 2012-10-31 08:57,
Oddball wrote:> Op 30-10-12 22:02, Linda Walsh schreef: >> There's a
/etc/securetty that specifies what terms root can login on. Are you sure
the>> "terminal" ...
__________________________________________________________________________________________________________________________________________
Carlos E. R. wrote:> -----BEGIN PGP SIGNED MESSAGE-----&g t; Hash: SHA256>
> On 2012-11-14 01:31, Linda Walsh wrote:> >> I have no initrd
- -- and I never saw this solution proposed on this>> (as someone else calls
it, "develo...
__________________________________________________________________________________________________________________________________________
- -----BEGIN PGP SIGNED MESSAGE-----Hash: SHA256 On 2012-11-14 01:31, Linda
Walsh wrote: > I have no initrd -- and I never saw this solution
proposed on this> (as someone else calls it, "development discussion" list
- -- and > they though...
··········++-
It is simply spam made of email collected by the spammer after subscribing
to the list. He has our complete emails.
>> HAD you read this mail list emails, you would have noticed that we
>> commented on it days ago.
> -----------
> I DON'T read every email from every list I am on.
And you expect we read your very long and profuse emails, if you don't
read ours? >:-)
If you want to comment on etiquette, do not use that email you got
labelled : “Subject: 36 unread messages wait for you in Qmail”. We all
got it, and it is not related at all to how we write emails here. I
carefully strip the email addresses from all emails I write, and I got
that spam, too.
- --
Cheers,
Carlos E. R.
(from 12.1 x86_64 "Asparagus" at Telcontar)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
iEYEARECAAYFAlEbcKEACgkQtTMYHG2NR9VEOACdGkoUfuKwmZskWvBitNBMmfAk
jPwAn2e3sBuYh+JVXzasdb84H/yVQyH1
=u3EV
-----END PGP SIGNATURE-----
Carlos E. R. wrote: on.
And you expect we read your very long and profuse emails, if you don't read ours? >:-)
--- If you are personally replying to me, I pay attention. If you are having a discussion with others about many other topics, I don't. I tend to be long in emails to try to be *clear*, as I find it VERY difficult to get across my thoughts and opinions effectively -- so I try extra hard... I also try to pay attention to different list rules on different lists... (not that I always abide by them if they are impeding communication -- but usually). On thing that people are more militant on this list about is having email sent to both them AND the list, whereas I often have preferred it that way -- since both copies end up in different folders. If you have addressed it to me (my email address is in the headers), it goes into a folder that gets < 20/day (<5-10 that are useful). Whereas the OTHER copy that you send to the list -- gets sorted into the list folder. So I have copies in both folders -- if someone wants to be sure I get their email in a timely fashion, they'll CC me, at least. My emails gets sorted by various means including list headers -- so the copy that comes to me doesn't come through a reflector and my SW can tell them apart. In the past 7 days, 51 different folders (besides my inbox) have received email. So I do alot of sorting. (perl)... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Anton Aylward -
Carlos E. R. -
Cristian Rodríguez -
Linda Walsh -
Patrick Shanahan -
Rajko