similar to: Majordomo results: RE: Message Notify

-- >>>> ----------geinwhjqlzkmqlsdwpel **** Command '----------geinwhjqlzkmqlsdwpel' not recognized. >>>> Content-Type: text/html; charset="us-ascii" **** Command 'content-type:' not recognized. >>>> Content-Transfer-Encoding: 7bit **** Command 'content-transfer-encoding:' not recognized. >>>> >>>>

-- >>>> 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

-- >>>> 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.

-- >>>> ----------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 =) ****

-- >>>> ----------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. >>>> >>>>

-- >>>> 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. >>>>

-- >>>> 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. >>>>

-- >>>> This is a multi-part message in MIME format. **** Command 'this' not recognized. >>>> >>>> ------=_NextPart_000_0006_7916E83F.C56F8A13 **** Command '------=_nextpart_000_0006_7916e83f.c56f8a13' not recognized. >>>> Content-Type: text/plain; **** Command 'content-type:' not recognized. >>>>

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),

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),

"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

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

Hi, i was running the latest ;-) Version of Majordomo (1.94.5) successful on CentOS 6.5 for years. Since i installed CentOS 7, majordomo isn't working any more (sendmail error). Is there anyone, who is running majordomo on CentOS 7 or has any hint? I know that Majordomo ist very old and greatcircle isn't supporting ist since years and the majordomo-Mailing-list ended 2003. I know about

--------------------------------------------------------------------- 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

I've got a CentOS 5 server joined to a Windows 2003 Domain. The Linux machine joined the Windows domain successfully and imported users, created their home directories and migrated their passwords. When looking at the current home directory It lists permissions and ownership properly for a few minutes drwxr-xr-x 2 jdoe domain users 4.0K Jun 14 2007 jdoe drwxr-xr-x 2 jqpublic domain

-- Someone (possibly you) has requested that your email address be added to or deleted from the mailing list "vorbis@xiph.org". If you really want this action to be taken, please send the following commands (exactly as shown) back to "majordomo@xiph.org": auth 4d3444ab subscribe vorbis vorbis@xiph.org If you do not want this action to be taken, simply ignore this message

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

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

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

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