similar to: Majordomo results: Hi

-- >>>> 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_0009_9A38C670.FD8DF8D3 **** Command '------=_nextpart_000_0009_9a38c670.fd8df8d3' not recognized. >>>> Content-Type: text/plain; charset=us-ascii **** Command 'content-type:' 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

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

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

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

----=_NextPart_ST_21_29_48_Monday_February_23_2004_11097 Content-Type: text/plain; Your message could not be sent. A transcript of the attempts to send the message follows. The number of attempts made: 1 Addressed To: john@spaar.com Mon, 23 Feb 2004 21:29:47 -0600 (2) Failed to send to identified host, [10.0.0.2], 550 5.1.1 User unknown [SMTP server error] --- Message non-deliverable.

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

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

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

Hi. This is the qmail-send program at provida.org.br. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. <musical@provida.org.br>: vdeliver: ERRO: Usu?rio n?o existe: 'musical'. --- Below this line is a copy of the message. Return-Path: <r-bugs@r-project.org>

Michael Stone wrote: > It seems that touch -a does update ctime on btrfs, invalidating one of > the assumptions behind this test and causing it to fail. s/does/does not/ Thanks for the report. I''ve just confirmed this test failure by building and running coreutils'' "make check" on a btrfs file system I''d just created using mkfs.btrfs v0.19 on Fedora

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

"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