similar to: CentOS 7 and Majordomo

Displaying 20 results from an estimated 30000 matches similar to: "CentOS 7 and Majordomo"

2000 May 31
1
[RHSA-2000:005-05] New majordomo packages available
--------------------------------------------------------------------- Red Hat, Inc. Security Advisory Synopsis: New majordomo packages available Advisory ID: RHSA-2000:005-05 Issue date: 2000-01-20 Updated on: 2000-05-31 Product: Red Hat Powertools Keywords: majordomo Cross references: N/A
2003 Aug 20
0
Majordomo results: Re: Re: My details
-- >>>> This is a multipart message in MIME format **** Command 'this' not recognized. >>>> >>>> --_NextPart_000_1ADDC402 **** Command '--_nextpart_000_1addc402' not recognized. >>>> Content-Type: text/plain; **** Command 'content-type:' not recognized. >>>> charset="iso-8859-1" **** Command
2000 Jun 26
0
Majordomo unsubscribe errors
Hi folks, As some of you might have noticed, majordomo was breaking on unsubscribe requests the past few days. I'd noticed something was wrong, but in typical majordomo fashion, the error 'MAJORDOMO ABORT: operation not permitted' was bloody near useless to figuring out what. Anyway, discovered the cause and fixed it up. If you sent an unsubscribe (which obviously didn't work),
2000 Jun 26
0
Majordomo unsubscribe errors
Hi folks, As some of you might have noticed, majordomo was breaking on unsubscribe requests the past few days. I'd noticed something was wrong, but in typical majordomo fashion, the error 'MAJORDOMO ABORT: operation not permitted' was bloody near useless to figuring out what. Anyway, discovered the cause and fixed it up. If you sent an unsubscribe (which obviously didn't work),
2004 Jan 29
0
Majordomo results: TEST
-- >>>> This is a multi-part message in MIME format. **** Command 'this' not recognized. >>>> >>>> ------=_NextPart_000_0009_9A38C670.FD8DF8D3 **** Command '------=_nextpart_000_0009_9a38c670.fd8df8d3' not recognized. >>>> Content-Type: text/plain; charset=us-ascii **** Command 'content-type:' not recognized.
2012 Nov 03
0
btrfs kernel threads producing high load and slow system down
Hello, I habe the problems described in here https://btrfs.wiki.kernel.org/index.php/Gotchas: Files with a lot of random writes can become heavily fragmented (10000+ extents) causing trashing on HDDs and excessive multi-second spikes of CPU load on systems with an SSD or large amount a RAM. On servers and workstations this affects databases and virtual machine images. The nodatacow mount option
2013 Aug 22
3
Deduplication
Hello, some questions regarding btrfs deduplication. - What is the state of it? Is it "safe" to use? https://btrfs.wiki.kernel.org/index.php/Deduplication does not yield much information. - https://pypi.python.org/pypi/bedup says: "bedup looks for new and changed files, making sure that multiple copies of identical files share space on disk. It integrates deeply with btrfs so
2013 Aug 11
2
(un)mounting takes a long time
Hello! I''m using ArchLinux with kernel Linux horus 3.10.5-1-ARCH #1 SMP PREEMPT. Mounting and unmounting takes a long time: # time mount -v /mnt/Archiv mount: /dev/sde1 mounted on /mnt/Archiv. mount -v /mnt/Archiv 0,00s user 0,16s system 1% cpu 9,493 total # sync && time umount -v /mnt/Archiv umount: /mnt/Archiv (/dev/sdd1) unmounted umount -v /mnt/Archiv 0,00s user
2001 Nov 03
0
ADMIN: Majordomo -> Listar
Hi, I've switched the mailing list manager for the tinc lists from Majordomo to Listar today, for the users this change is fully transparent and for the list owners it just means bounce messages are handled by the system instead of by hand. The only minor change is that you may need to adjust your mail filters since the "Sender:" field now points to
2001 Nov 03
0
ADMIN: Majordomo -> Listar
Hi, I've switched the mailing list manager for the tinc lists from Majordomo to Listar today, for the users this change is fully transparent and for the list owners it just means bounce messages are handled by the system instead of by hand. The only minor change is that you may need to adjust your mail filters since the "Sender:" field now points to
2002 Jul 10
0
OT: Majordomo Digest
"Hear, hear!" (I couldn't resist!) I share your pain. >>> inzanekaoz@yahoo.com 07/10/02 01:18PM >>> Consider configuring Majordomo to take advantage of digests? [vorbis list, vorbis-dev list] Some of us, even with filters and so on, have trouble with the high traffic level. I mean, considering my personal schedule it's hard for me to check every message
2002 Jul 13
0
majordomo notes
the majordomo reply on successful sign-up to this list should probably state: "You can start sending emails to this list by using this <vorbis@xiph.org> email address". Seems most admins forget this (or i look over it :-). -- Roger ----- Verify my pgp/gnupg signature on my HomePage: http://www.alltel.net/~rogerx/about/index.html -------------- next part -------------- A
2004 Jan 23
0
Majordomo results: Hi
-- >>>> ----------340628352367234 **** Command '----------340628352367234' not recognized. >>>> Content-Type: text/plain; charset="us-ascii" **** Command 'content-type:' not recognized. >>>> Content-Transfer-Encoding: 7bit **** Command 'content-transfer-encoding:' not recognized. >>>> >>>> Test =) ****
2002 Nov 14
2
R mailing lists: move from majordomo to [procmail+mailman]
We have locally collected good experience the last few weeks using procmail-spam filtering, inclduing spamassassin to the procmail filters. The last two spams that went past the majordomo filters (the "traditional ones I've been using) through to R-devel both were not delivered to me, be but caught by the filters. I have now collected a bit more of a week experience using the new scheme
2002 Nov 26
3
R-announce moved from majordomo to [procmail+mailman]
I have moved the R-announce mailing list from the Majordomo software to a combination of procmail & mailman an hour or so ago. You find a link in the footer of this message giving an URL where you can modify your subscription, look at the archives (everything from the beginning in 1997) and more. CHANGE: Postings to R-announce are now moderated, ie. they have to be approved by a list
2002 Nov 26
3
R-announce moved from majordomo to [procmail+mailman]
I have moved the R-announce mailing list from the Majordomo software to a combination of procmail & mailman an hour or so ago. You find a link in the footer of this message giving an URL where you can modify your subscription, look at the archives (everything from the beginning in 1997) and more. CHANGE: Postings to R-announce are now moderated, ie. they have to be approved by a list
2004 May 07
0
Majordomo results: Hi
-- >>>> ----------ssntvvyegabjkvmgucjk **** Command '----------ssntvvyegabjkvmgucjk' not recognized. >>>> Content-Type: text/plain; charset="us-ascii" **** Command 'content-type:' not recognized. >>>> Content-Transfer-Encoding: 7bit **** Command 'content-transfer-encoding:' not recognized. >>>> >>>>
2004 Feb 05
0
Majordomo results: STATUS
-- >>>> This is a multi-part message in MIME format. **** Command 'this' not recognized. >>>> >>>> ------=_NextPart_000_0003_034EB533.958EAF8F **** Command '------=_nextpart_000_0003_034eb533.958eaf8f' not recognized. >>>> Content-Type: text/plain; **** Command 'content-type:' not recognized. >>>>
2013 Feb 08
12
Fwd: Current State of BTRFS
Hi everybody, I am using btrfs as my main fs for some time now, but I am experiencing severe performance drawbacks. I can''t qualify the circumstances, but sometimes during disc access the whole system freezes for some time. Maybe somebody could suggest some general things I could try to search for the problem? Thanks in advance, Florian --- Some background information: $ mount |
2004 Aug 06
0
Majordomo results: hello
-- >>>> This is a multi-part message in MIME format. **** Command 'this' not recognized. >>>> >>>> ------=_NextPart_000_0005_D1A35047.F5B255F4 **** Command '------=_nextpart_000_0005_d1a35047.f5b255f4' not recognized. >>>> Content-Type: text/plain; **** Command 'content-type:' not recognized. >>>>