From majordomo-users-owner@greatcircle.com Sun Jan 1 14:12:59 2006 X-Original-To: majordomo-users@greatcircle.com Received: from smarthost4.mail.uk.easynet.net (smarthost4.mail.uk.easynet.net [212.135.6.14]) by mycroft.greatcircle.com (Postfix) with ESMTP id CFCBE32C19F for ; Sun, 1 Jan 2006 14:12:57 -0800 (PST) Received: from ip-217-204-130-250.easynet.co.uk ([217.204.130.250] helo=[10.24.7.1]) by smarthost4.mail.uk.easynet.net with esmtp (Exim 4.10) id 1EtBRg-0006nR-00 for majordomo-users@greatcircle.com; Sun, 01 Jan 2006 22:12:56 +0000 Mime-Version: 1.0 (Apple Message framework v746.2) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: majordomo-users@greatcircle.com From: Charles Teton Subject: How do I disabling majordomo temporarily? Date: Sun, 1 Jan 2006 22:12:55 +0000 X-Mailer: Apple Mail (2.746.2) X-Archive-Number: 200601/1 X-Sequence-Number: 5257 Hi All, How do I disabling majordomo? I do not want to uninstall it as it will probably break the RAQ interface. Just stop it working with sendmail so there is no way it can be used to spam. I'm running a RAQ 3 with majordomo installed for a few years. I've never used majordomo or even turned it on through the RAQ interface. About 2 months ago I've started to get a lot of chatter in my logs: ---------------start of log--------------- Dec 13 07:49:44 www sendmail[9385]: HAA09385: ... No such user here Dec 13 07:49:45 www sendmail[9385]: HAA09385: ... No such user here Dec 13 07:49:46 www sendmail[9385]: HAA09385: ... No such user here Dec 13 07:49:51 www sendmail[9385]: HAA09385: ... No such user here Dec 13 07:49:52 www sendmail[9385]: HAA09385: ... No such user here Dec 13 07:49:53 www sendmail[9385]: HAA09385: ... No such user here Dec 13 07:49:54 www sendmail[9385]: HAA09385: ... No such user here Dec 13 07:49:57 www sendmail[9385]: HAA09385: ... No such user here Dec 13 07:50:00 www sendmail[9385]: HAA09385: ... No such user here Dec 13 07:50:03 www sendmail[9385]: HAA09385: ... No such user here Dec 13 07:50:13 www sendmail[9385]: HAA09385: ... No such user here Dec 13 07:50:43 www sendmail[9429]: HAA09429: clone HAA09385, owner=admin Dec 13 07:50:48 www sendmail[9433]: HAA09433: Authentication-Warning: www.mydomain.com: mail set sender to Majordomo-Owner@www.mydomain.com using -f Dec 13 07:50:49 www sendmail[9435]: HAA09433: HAA09435: DSN: User unknown ---------------end of log--------------- New file being created: /tmp/majordomo.debug and emails similar to below: ---------------start of email--------------- To: Majordomo-Owner@www.mydomain.com MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary="KAA28086.1134125138/www.mydomain.com" Subject: Returned mail: User unknown Auto-Submitted: auto-generated (failure) This is a MIME-encapsulated message --KAA28086.1134125138/www.mydomain.com The original message was received at Fri, 9 Dec 2005 10:43:48 GMT from mail@localhost ----- The following addresses had permanent fatal errors ----- fredsanders@mail.com ----- Transcript of session follows ----- ... while talking to mail-com.mr.outblaze.com.: >>> RCPT To: <<< 550 : No thank you rejected: Account Unavailable: Possible Forgery 550 fredsanders@mail.com... User unknown --KAA28086.1134125138/www.mydomain.com Content-Type: message/delivery-status Reporting-MTA: dns; www.mydomain.com Arrival-Date: Fri, 9 Dec 2005 10:43:48 GMT Final-Recipient: RFC822; fredsanders@mail.com Action: failed Status: 5.1.1 Remote-MTA: DNS; mail-com.mr.outblaze.com Diagnostic-Code: SMTP; 550 : No thank you rejected: Account Unavailable: Possible Forgery Last-Attempt-Date: Fri, 9 Dec 2005 10:45:38 GMT --KAA28086.1134125138/www.mydomain.com Content-Type: message/rfc822 Return-Path: Received: (from mail@localhost) by www.mydomain.com (8.9.3/8.9.3) id KAA28084; Fri, 9 Dec 2005 10:43:48 GMT Date: Fri, 9 Dec 2005 10:43:48 GMT Message-Id: <200512091043.KAA28084@www.mydomain.com> X-Authentication-Warning: www.mydomain.com: mail set sender to Majordomo-Owner@www.mydomain.com using -f To: fredsanders@mail.com From: Majordomo@www.mydomain.com Subject: Majordomo results: Re: look at your web site stats... Reply-To: Majordomo@www.mydomain.com Followed by SPAM email and the followed by: **** No valid commands found. **** Commands must be in message BODY, not in HEADER. **** Help for Majordomo@www.mydomain.com: ETC. ---------------end of email--------------- I'm pretty sure I'm not spamming anyone? I just want to disabling majordomo without uninstall it, as I said before, it will probably break the RAQ interface if I do. Many thanks. Regards, C.Teton From majordomo-users-owner@greatcircle.com Sun Jan 1 14:52:15 2006 X-Original-To: majordomo-users@greatcircle.com Received: from web30212.mail.mud.yahoo.com (web30212.mail.mud.yahoo.com [68.142.201.225]) by mycroft.greatcircle.com (Postfix) with SMTP id 5F12D32C1EB for ; Sun, 1 Jan 2006 14:52:14 -0800 (PST) Received: (qmail 91904 invoked by uid 60001); 1 Jan 2006 22:52:13 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding; b=JbkErhxT89zCiM5uvR4b5njCl0AV1RoFyWRPAZtCBrdwClsXM8m9NRtfGFNa48XwPMpjohlP7ImbEKdZWViSQI/szZlH3k6dHe5qZxzGjqYjd9DlDOgH04Sz6JyOBvJXns8pZvD0nHmEADzanxs2Eo/gUGYk4yfEri7z1S6sBR0= ; Message-ID: <20060101225213.91902.qmail@web30212.mail.mud.yahoo.com> Received: from [85.74.51.179] by web30212.mail.mud.yahoo.com via HTTP; Sun, 01 Jan 2006 22:52:13 GMT Date: Sun, 1 Jan 2006 22:52:13 +0000 (GMT) From: Tom Sahrendt Subject: Re: How do I disabling majordomo temporarily? To: majordomo-users@greatcircle.com Cc: Charles Teton MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Archive-Number: 200601/2 X-Sequence-Number: 5258 hi there > How do I disabling majordomo? put some #s in front of the list alias entries in /etc/aliases or whatever file your configuration uses. one thing: if there is a server up and running, there will be spammers and hackers and scriptkiddies trying to break it. as long as there is one single html page or one single google news archive posting out there bearing your e-mail adress, some spammer is likely to use your adress for spamming. there is no way around this. sadly, this is how internet has grown to be. there are around 200 spamming attacks on my majordomo lists daily. they are not successful, however, cause my configuration refuses to accept e-mails containing HTML and/or attachements. since HTML is utterly useless on the kind of mailing lists I run, the users do not have a problem with it. now, even if some spammer is cunning enough to fake a member e-mail adress and is using it to try flodding the list, he can only do this if he does not use HTML or attachements - this makes trying often pretty useless. anyway, the main problem is sober. sober on the computers of infected users takes their outlook adress books and sends itself to all of them. often enough, one of my mailing lists is also in the adress book and thus the sober virus tries to send itself to this list as well. but since he has to attach himself to the e-mail, the e-mail is rejected by my majordomo due to having non-text parts. cu, Tom ___________________________________________________________ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com From majordomo-users-owner@greatcircle.com Sun Jan 1 15:27:34 2006 X-Original-To: majordomo-users@greatcircle.com Received: from smarthost1.mail.uk.easynet.net (smarthost1.mail.uk.easynet.net [212.135.6.11]) by mycroft.greatcircle.com (Postfix) with ESMTP id 2487832C2CB for ; Sun, 1 Jan 2006 15:27:33 -0800 (PST) Received: from ip-217-204-130-250.easynet.co.uk ([217.204.130.250] helo=[10.24.7.1]) by smarthost1.mail.uk.easynet.net with esmtp (Exim 4.10) id 1EtCbr-000DcW-00; Sun, 01 Jan 2006 23:27:31 +0000 In-Reply-To: <20060101225213.91902.qmail@web30212.mail.mud.yahoo.com> References: <20060101225213.91902.qmail@web30212.mail.mud.yahoo.com> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Cc: majordomo-users@greatcircle.com Content-Transfer-Encoding: 7bit From: Charles Teton Subject: Re: How do I disabling majordomo temporarily? Date: Sun, 1 Jan 2006 23:27:31 +0000 To: Tom Sahrendt X-Mailer: Apple Mail (2.746.2) X-Archive-Number: 200601/3 X-Sequence-Number: 5259 Thanks for getting back to me Tom... > On Jan 01, 2006, at 22:52, Tom Sahrendt wrote: > hi there > >> How do I disabling majordomo? > > put some #s in front of the list alias entries in > /etc/aliases or whatever file your configuration uses. I believe my file is /etc/aliases.majordomo Do I # out all the lines or just where there is the command: "|/usr/local/majordomo/wrapper -v" Also will this file not get rebuilt when the server restarts? --------------start /etc/aliases.majordomo-------------- # >>>>>>>>>> The program "newaliases" must be run after # >> NOTE >> this file is updated for any changes to # >>>>>>>>>> show through to sendmail. # majordomo: "|/usr/local/majordomo/wrapper majordomo" owner-majordomo: admin majordomo-owner: owner-majordomo site-adm: "|/usr/local/majordomo/wrapper resend -l site-adm site-adm- list" site-adm-list: :include:/usr/local/majordomo/lists/site-adm site-adm-request: "|/usr/local/majordomo/wrapper request-answer site- adm" site-adm-approval: admin owner-site-adm: admin site-adm-owner: owner-site-adm majordomo_home: "|/usr/local/majordomo/wrapper -v home -f www.sitehome.com majordomo" owner-majordomo_home: admin majordomo_home-owner: owner-majordomo_home majordomo_site1: "|/usr/local/majordomo/wrapper -v site1 -f www.site1.co.uk majordomo" owner-majordomo_site1: admin majordomo_site1-owner: owner-majordomo_site1 majordomo_site2: "|/usr/local/majordomo/wrapper -v site2 -f www.site2.com majordomo" owner-majordomo_site2: admin majordomo_site2-owner: owner-majordomo_site2 majordomo_site3: "|/usr/local/majordomo/wrapper -v site3 -f www.site3.com majordomo" --------------end /etc/aliases.majordomo-------------- Many many thanks. C.Teton > anyway, the main problem is sober. sober on the computers of > infected users > takes their outlook address books and sends itself to all of them. I thought it was something like that. I had a crash coarse in Linux, self taught a few years back, to enable me to tighten up the server. Its crazy how many attempts there are to break in... From majordomo-users-owner@greatcircle.com Sun Jan 1 23:38:34 2006 X-Original-To: majordomo-users@greatcircle.com Received: from web30213.mail.mud.yahoo.com (web30213.mail.mud.yahoo.com [68.142.201.226]) by mycroft.greatcircle.com (Postfix) with SMTP id AA65F32C16C for ; Sun, 1 Jan 2006 23:38:31 -0800 (PST) Received: (qmail 26294 invoked by uid 60001); 2 Jan 2006 07:38:30 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=hdOkD9uc0qYj5jjBskuBRBFLAii7U+O3C40Y41yV6HzWYbrfSAjma9ArK3HC0jV01FfYWZdRIdQC7GIS7EJIOwdZJYgR2XnMaYMzLhFy8KuYg3UYn6BSaGPldusr87AkRdFn6/cmPLg7O+VMhqJ7sFWP/GoNL+V5x/i/MeyRWCM= ; Message-ID: <20060102073830.26292.qmail@web30213.mail.mud.yahoo.com> Received: from [85.74.35.211] by web30213.mail.mud.yahoo.com via HTTP; Mon, 02 Jan 2006 07:38:30 GMT Date: Mon, 2 Jan 2006 07:38:30 +0000 (GMT) From: Tom Sahrendt Subject: Re: How do I disabling majordomo temporarily? To: majordomo-users@greatcircle.com MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Archive-Number: 200601/4 X-Sequence-Number: 5260 hi there at any rate you have to disable the LISTNAME and the LISTNAME-outgoing entries. > Also will this file not get rebuilt when the > server restarts? depends. If your sendmail is run with the -bi option it should rebuild the database automatically when restarted. To be honest, I don't know that because I work with postfix. If your "/etc/aliases.majordomo" doesn't get rebuilt automatically, you'll have a command to do so. It's called "postalias" for postfix, I'd look at the man pages of "makemap" and "newalias" for sendmail. cu, Tom ___________________________________________________________ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com From majordomo-users-owner@greatcircle.com Thu Jan 5 00:45:47 2006 X-Original-To: majordomo-users@greatcircle.com Received: from mail.oriflame-sw.com (mail.oriflame-sw.com [194.149.124.180]) by mycroft.greatcircle.com (Postfix) with ESMTP id 73C0432C1E1 for ; Thu, 5 Jan 2006 00:45:44 -0800 (PST) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Problem with cyrillic X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Date: Thu, 5 Jan 2006 09:45:42 +0100 Message-ID: <6639BA20B265594590E97DD72A8EE035421C68@exosw.osw.ori.local> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Problem with cyrillic Thread-Index: AcYR1GIdxVh4ptd5RoOaGCvMdFpuoQ== From: "Jevos, Peter" To: X-Archive-Number: 200601/5 X-Sequence-Number: 5261 Hi all, I have prroblem with cyrillic in the footer of the message. I need to place some text to the footer,but after message sending footer turns into strange characters. I'm using majordomo with postfix 2.2 Thanks a lot=20 Pet From majordomo-users-owner@greatcircle.com Fri Jan 6 08:28:10 2006 X-Original-To: majordomo-users@greatcircle.com Received: from moroni.ourldsfamily.com (ourldsfamily.com [198.60.114.90]) by mycroft.greatcircle.com (Postfix) with ESMTP id 1368E32C203 for ; Fri, 6 Jan 2006 08:28:08 -0800 (PST) Received: from ourldsfamily.com (eth1 [172.20.20.2]) by moroni.ourldsfamily.com (8.12.5/8.12.5) with ESMTP id k06GTuRV027546 for ; Fri, 6 Jan 2006 09:29:56 -0700 Received: from ats ([207.173.117.242]) (SquirrelMail authenticated user karlp) by ourldsfamily.com with HTTP; Fri, 6 Jan 2006 09:29:56 -0700 (MST) Message-ID: <36499.207.173.117.242.1136564996.squirrel@ourldsfamily.com> Date: Fri, 6 Jan 2006 09:29:56 -0700 (MST) Subject: Digests Are Broken From: karlp@ourldsfamily.com To: majordomo-users@greatcircle.com User-Agent: SquirrelMail/1.4.4-rc1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Archive-Number: 200601/6 X-Sequence-Number: 5262 Majordomo 1.94.5 I've noticed, because of a complaint, that the digest groups on my server are inconsistent in their delivery of digest emails. I've instituted a cron that does mkdigest on the offending lists. I've compared the config files for both the regular list and the digest list and can't seem to see anything. Is there a known issue with digests? I've been on the digest version of majordomo-users for a while and just switched back. I noticed that the delivery of my email for this list was apparently missing emails, too. Thanks for any help, hints, etc. you can give. -- karl _/ _/ _/ _/_/_/ ____________ __o _/ _/ _/ _/ _/ ____________ _-\<._ _/_/ _/ _/_/_/ (_)/ (_) _/ _/ _/ _/ ...................... _/ _/ arl _/_/_/ _/ earson KarlP@ourldsfamily.com --- Senior Consulting Sys/DB Analyst http://consulting.ourldsfamily.com --- My Thoughts on Terrorism In America: http://www.ourldsfamily.com/wtc.shtml --- A right is not what someone gives you; it's what no one can take from you. -Ramsey Clark --- From majordomo-users-owner@greatcircle.com Fri Jan 6 10:56:59 2006 X-Original-To: majordomo-users@greatcircle.com Received: from atlantis.emacolet.com (atlantis.emacolet.com [66.166.78.85]) by mycroft.greatcircle.com (Postfix) with ESMTP id AC10432C1C3 for ; Fri, 6 Jan 2006 10:56:57 -0800 (PST) Received: from webmail.emacolet.com (atlantis.emacolet.com [192.168.0.253]) by atlantis.emacolet.com (8.13.5/8.13.5) with SMTP id k06Iur0g026887; Fri, 6 Jan 2006 10:56:55 -0800 Received: from 66.52.88.35 (proxying for unknown) (SquirrelMail authenticated user ppbenac@emacolet.com); by webmail.emacolet.com with HTTP; Fri, 6 Jan 2006 10:56:56 -0800 (PST) Message-ID: <60504.66.52.88.35.1136573816.squirrel@66.52.88.35> In-Reply-To: References: Date: Fri, 6 Jan 2006 10:56:56 -0800 (PST) Subject: Re: How do I disabling majordomo temporarily? From: "Peter P. Benac" To: "Charles Teton" Cc: majordomo-users@greatcircle.com User-Agent: SquirrelMail/1.4.3 [CVS] X-Mailer: SquirrelMail/1.4.3 [CVS] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal X-Scanned-By: MIMEDefang 2.53 on 192.168.0.253 X-Archive-Number: 200601/7 X-Sequence-Number: 5263 If you have never used or configured MD why do you think this "Chatter" is being caused by MD. What I see below is normal in almost everyone's mail logs. It is a typical spammers tactic to try and send mail to every known name used in an email address. You might want to consider installing a better spam defense then to try and disable what you have already said you have never used. Regards, Pete > Hi All, > > How do I disabling majordomo? I do not want to uninstall it as it > will probably break the RAQ interface. Just stop it working with > sendmail so there is no way it can be used to spam. > > I'm running a RAQ 3 with majordomo installed for a few years. I've > never used majordomo or even turned it on through the RAQ interface. > > About 2 months ago I've started to get a lot of chatter in my logs: > > ---------------start of log--------------- > > Dec 13 07:49:44 www sendmail[9385]: HAA09385: > ... No such user here > Dec 13 07:49:45 www sendmail[9385]: HAA09385: > ... No such user here > Dec 13 07:49:46 www sendmail[9385]: HAA09385: > ... No such user here > Dec 13 07:49:51 www sendmail[9385]: HAA09385: > ... No such user here > Dec 13 07:49:52 www sendmail[9385]: HAA09385: > ... No such user here > Dec 13 07:49:53 www sendmail[9385]: HAA09385: ... > No such user here > Dec 13 07:49:54 www sendmail[9385]: HAA09385: ... > No such user here > Dec 13 07:49:57 www sendmail[9385]: HAA09385: ... > No such user here > Dec 13 07:50:00 www sendmail[9385]: HAA09385: ... > No such user here > Dec 13 07:50:03 www sendmail[9385]: HAA09385: > ... No such user here > Dec 13 07:50:13 www sendmail[9385]: HAA09385: > ... No such user here > Dec 13 07:50:43 www sendmail[9429]: HAA09429: clone HAA09385, > owner=admin > Dec 13 07:50:48 www sendmail[9433]: HAA09433: Authentication-Warning: > www.mydomain.com: mail set sender to Majordomo-Owner@www.mydomain.com > using -f > Dec 13 07:50:49 www sendmail[9435]: HAA09433: HAA09435: DSN: User > unknown > > ---------------end of log--------------- > > New file being created: > > /tmp/majordomo.debug > > and emails similar to below: > > ---------------start of email--------------- > > To: Majordomo-Owner@www.mydomain.com > MIME-Version: 1.0 > Content-Type: multipart/report; report-type=delivery-status; > boundary="KAA28086.1134125138/www.mydomain.com" > Subject: Returned mail: User unknown > Auto-Submitted: auto-generated (failure) > > This is a MIME-encapsulated message > > --KAA28086.1134125138/www.mydomain.com > > The original message was received at Fri, 9 Dec 2005 10:43:48 GMT > from mail@localhost > > ----- The following addresses had permanent fatal errors ----- > fredsanders@mail.com > > ----- Transcript of session follows ----- > ... while talking to mail-com.mr.outblaze.com.: > >>> RCPT To: > <<< 550 : No thank you rejected: Account > Unavailable: Possible Forgery > 550 fredsanders@mail.com... User unknown > > --KAA28086.1134125138/www.mydomain.com > Content-Type: message/delivery-status > > Reporting-MTA: dns; www.mydomain.com > Arrival-Date: Fri, 9 Dec 2005 10:43:48 GMT > > Final-Recipient: RFC822; fredsanders@mail.com > Action: failed > Status: 5.1.1 > Remote-MTA: DNS; mail-com.mr.outblaze.com > Diagnostic-Code: SMTP; 550 : No thank you > rejected: Account Unavailable: Possible Forgery > Last-Attempt-Date: Fri, 9 Dec 2005 10:45:38 GMT > > --KAA28086.1134125138/www.mydomain.com > Content-Type: message/rfc822 > > Return-Path: > Received: (from mail@localhost) > by www.mydomain.com (8.9.3/8.9.3) id KAA28084; > Fri, 9 Dec 2005 10:43:48 GMT > Date: Fri, 9 Dec 2005 10:43:48 GMT > Message-Id: <200512091043.KAA28084@www.mydomain.com> > X-Authentication-Warning: www.mydomain.com: mail set sender to > Majordomo-Owner@www.mydomain.com using -f > To: fredsanders@mail.com > From: Majordomo@www.mydomain.com > Subject: Majordomo results: Re: look at your web site stats... > Reply-To: Majordomo@www.mydomain.com > > > Followed by SPAM email and the followed by: > > **** No valid commands found. > **** Commands must be in message BODY, not in HEADER. > > **** Help for Majordomo@www.mydomain.com: > > ETC. > > ---------------end of email--------------- > > I'm pretty sure I'm not spamming anyone? > > I just want to disabling majordomo without uninstall it, as I said > before, it will probably break the RAQ interface if I do. > > Many thanks. > > Regards, > > C.Teton > ---- Peter P. Benac, CCNA Emacolet Networking Services, Inc Providing Network and Systems Project Management and Installation and Web Hosting. Phone: 919-618-2557 Web: http://www.emacolet.com Need quick reliable Systems or Network Management advice visit http://www.nmsusers.org To have principles... First have courage.. With principles comes integrity!!! From majordomo-users-owner@greatcircle.com Sat Jan 7 14:43:50 2006 X-Original-To: majordomo-users@greatcircle.com Received: from mail.sonny.com (unknown [70.58.223.141]) by mycroft.greatcircle.com (Postfix) with ESMTP id 1466932C204 for ; Sat, 7 Jan 2006 14:43:49 -0800 (PST) Received: from sonny.org (father.sonny.com [192.168.1.78]) by magnia.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0ISQ0084BUX3YG@magnia.sonny.com> for majordomo-users@greatcircle.com; Sat, 07 Jan 2006 16:39:04 -0600 (CST) Date: Sat, 07 Jan 2006 16:43:50 -0600 From: Daniel Liston Subject: Re: Digests Are Broken In-reply-to: <36499.207.173.117.242.1136564996.squirrel@ourldsfamily.com> To: karlp@ourldsfamily.com Cc: majordomo-users@greatcircle.com Message-id: <43C04426.1070004@sonny.org> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) References: <36499.207.173.117.242.1136564996.squirrel@ourldsfamily.com> X-Archive-Number: 200601/8 X-Sequence-Number: 5264 Under certain conditions, all the files in the digest_work_dir may not be used/removed from the directory. Adding sort to the @files arg on line 176 of digest solves the problem. foreach (sort @files) { Dan Liston karlp@ourldsfamily.com wrote: > Majordomo 1.94.5 > > I've noticed, because of a complaint, that the digest groups on my server > are inconsistent in their delivery of digest emails. > > I've instituted a cron that does mkdigest on the offending lists. I've > compared the config files for both the regular list and the digest list > and can't seem to see anything. > > Is there a known issue with digests? I've been on the digest version of > majordomo-users for a while and just switched back. I noticed that the > delivery of my email for this list was apparently missing emails, too. > > Thanks for any help, hints, etc. you can give. > From majordomo-users-owner@greatcircle.com Sat Jan 7 17:14:21 2006 X-Original-To: majordomo-users@greatcircle.com Received: from moroni.ourldsfamily.com (ourldsfamily.com [198.60.114.90]) by mycroft.greatcircle.com (Postfix) with ESMTP id 554B532C1C2 for ; Sat, 7 Jan 2006 17:14:19 -0800 (PST) Received: from webmail.ourldsfamily.com (eth1 [172.20.20.2]) by moroni.ourldsfamily.com (8.12.5/8.12.5) with ESMTP id k081EIxb001191; Sat, 7 Jan 2006 18:14:18 -0700 Received: from ourldsfamily.com ([198.60.114.90]) (SquirrelMail authenticated user karlp) by webmail.ourldsfamily.com with HTTP; Sat, 7 Jan 2006 18:14:19 -0700 (MST) Message-ID: <13844.198.60.114.90.1136682859.squirrel@webmail.ourldsfamily.com> In-Reply-To: <43C04426.1070004@sonny.org> References: <36499.207.173.117.242.1136564996.squirrel@ourldsfamily.com> <43C04426.1070004@sonny.org> Date: Sat, 7 Jan 2006 18:14:19 -0700 (MST) Subject: Re: Digests Are Broken From: karlp@ourldsfamily.com To: "Daniel Liston" Cc: majordomo-users@greatcircle.com User-Agent: SquirrelMail/1.4.4-rc1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Archive-Number: 200601/9 X-Sequence-Number: 5265 Thanks Dan. I've added it and will watch. Karl On Sat, January 7, 2006 3:43 pm, Daniel Liston said: > > Under certain conditions, all the files in the digest_work_dir may not > be used/removed from the directory. Adding sort to the @files arg on > line 176 of digest solves the problem. > > foreach (sort @files) { > > Dan Liston > > > karlp@ourldsfamily.com wrote: >> Majordomo 1.94.5 >> >> I've noticed, because of a complaint, that the digest groups on my >> server >> are inconsistent in their delivery of digest emails. >> >> I've instituted a cron that does mkdigest on the offending lists. I've >> compared the config files for both the regular list and the digest list >> and can't seem to see anything. >> >> Is there a known issue with digests? I've been on the digest version of >> majordomo-users for a while and just switched back. I noticed that the >> delivery of my email for this list was apparently missing emails, too. >> >> Thanks for any help, hints, etc. you can give. >> > -- karl _/ _/ _/ _/_/_/ ____________ __o _/ _/ _/ _/ _/ ____________ _-\<._ _/_/ _/ _/_/_/ (_)/ (_) _/ _/ _/ _/ ...................... _/ _/ arl _/_/_/ _/ earson KarlP@ourldsfamily.com --- Senior Consulting Sys/DB Analyst http://consulting.ourldsfamily.com --- My Thoughts on Terrorism In America: http://www.ourldsfamily.com/wtc.shtml --- A right is not what someone gives you; it's what no one can take from you. -Ramsey Clark --- From majordomo-users-owner@greatcircle.com Tue Jan 10 05:38:46 2006 X-Original-To: majordomo-users@greatcircle.com Received: from mail.oriflame-sw.com (mail.oriflame-sw.com [194.149.124.180]) by mycroft.greatcircle.com (Postfix) with ESMTP id AFF4932C314 for ; Tue, 10 Jan 2006 05:38:33 -0800 (PST) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Footer appears only from one sender X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Date: Tue, 10 Jan 2006 14:53:02 +0100 Message-ID: <6639BA20B265594590E97DD72A8EE035421CFE@exosw.osw.ori.local> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Footer appears only from one sender Thread-Index: AcYV7SgX1opMr88MQEOyeTKUJ8I90w== From: "Jevos, Peter" To: X-Archive-Number: 200601/10 X-Sequence-Number: 5266 Hello , I'd like to ask for advice. I put simple footer into my test.config list However, footer works and display only from one particular sender, it doesn't work with the other senders, which sends email messages into this test list. Why ? Pet From majordomo-users-owner@greatcircle.com Tue Jan 10 08:06:15 2006 X-Original-To: majordomo-users@greatcircle.com Received: from wbmler2.mail.xerox.com (wbmler2.mail.xerox.com [13.13.138.217]) by mycroft.greatcircle.com (Postfix) with ESMTP id 37AD432C1F6 for ; Tue, 10 Jan 2006 08:06:13 -0800 (PST) Received: from wbmlir3.mail.xerox.com (wbmlir3.mail.xerox.com [13.131.8.223]) by wbmler2.mail.xerox.com (8.13.4/8.13.1) with ESMTP id k0AG64kL026974; Tue, 10 Jan 2006 11:06:13 -0500 Received: from wbmlir3.mail.xerox.com (localhost [127.0.0.1]) by wbmlir3.mail.xerox.com (8.13.4/8.13.1) with ESMTP id k0AG58G0009247; Tue, 10 Jan 2006 11:05:08 -0500 Received: from usa0300gw02.na.xerox.net (usa0300gw02.na.xerox.net [13.129.0.42]) by wbmlir3.mail.xerox.com (8.13.4/8.13.1) with ESMTP id k0AG4ocA008796; Tue, 10 Jan 2006 11:05:00 -0500 Received: from usa0300ms02.na.xerox.net ([13.135.34.11]) by usa0300gw02.na.xerox.net with Microsoft SMTPSVC(6.0.3790.211); Tue, 10 Jan 2006 11:04:30 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Re: Footer appears only from one sender Date: Tue, 10 Jan 2006 11:04:34 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Footer appears only from one sender Thread-Index: AcYV7SgX1opMr88MQEOyeTKUJ8I90wAEjWRQ From: "Doty, Robert" To: "Jevos, Peter" , X-OriginalArrivalTime: 10 Jan 2006 16:04:30.0579 (UTC) FILETIME=[8A2E9430:01C615FF] X-Archive-Number: 200601/11 X-Sequence-Number: 5267 Using traditional majordomo, footers will only show up in Plain Text messages. You might want to verify the format that each user is using when sending to the system.=20=20 I have made modifications to majordomo and resend such that this limitation is removed. I can provide this information if you want it. Thanks, Rob =20 G. Robert Doty MCD Integration Manager XOG / SEBU / MCD Xerox Corporation Phone: 585-427-3681 Robert.Doty@xerox.com "This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient(s) please contact the sender by reply e-mail and destroy all copies of the original message. Finally, the recipient should check that this email is authentic and examine it for the presence of viruses. Xerox does perform virus checks but cannot accept liability for any damage caused by any virus transmitted by this email. Thank you." =20=20=20=20=20=20=20 -----Original Message----- From: majordomo-users-owner@greatcircle.com [mailto:majordomo-users-owner@greatcircle.com] On Behalf Of Jevos, Peter Sent: Tuesday, January 10, 2006 8:53 AM To: majordomo-users@greatcircle.com Subject: Footer appears only from one sender Hello , I'd like to ask for advice. I put simple footer into my test.config list However, footer works and display only from one particular sender, it doesn't work with the other senders, which sends email messages into this test list. Why ? Pet From majordomo-users-owner@greatcircle.com Tue Jan 10 13:54:05 2006 X-Original-To: majordomo-users@greatcircle.com Received: from mail.sonny.com (unknown [70.58.223.141]) by mycroft.greatcircle.com (Postfix) with ESMTP id E82BB32C1D7 for ; Tue, 10 Jan 2006 13:54:03 -0800 (PST) Received: from sonny.org (father.sonny.com [192.168.1.78]) by magnia.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0ISW00I22CKJDV@magnia.sonny.com> for majordomo-users@greatcircle.com; Tue, 10 Jan 2006 15:48:19 -0600 (CST) Date: Tue, 10 Jan 2006 15:54:10 -0600 From: Daniel Liston Subject: Re: Footer appears only from one sender In-reply-to: To: "Doty, Robert" Cc: "Jevos, Peter" , majordomo-users@greatcircle.com Message-id: <43C42D02.2000502@sonny.org> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) References: X-Archive-Number: 200601/12 X-Sequence-Number: 5268 I would be interested in these patches. Can you post them to the majordomo-users list? Dan Liston Doty, Robert wrote: > Using traditional majordomo, footers will only show up in Plain Text > messages. You might want to verify the format that each user is using > when sending to the system. > > I have made modifications to majordomo and resend such that this > limitation is removed. I can provide this information if you want it. > > Thanks, > > Rob > > > > > > G. Robert Doty > MCD Integration Manager > XOG / SEBU / MCD > Xerox Corporation > Phone: 585-427-3681 > Robert.Doty@xerox.com > > "This e-mail message, including any attachments, is for the sole > use of the intended recipient(s) and may contain confidential > information. Any unauthorized review, use, disclosure or distribution is > prohibited. If you are not the intended recipient(s) please contact the > sender by reply e-mail and destroy all copies of the original message. > Finally, the recipient should check that this email is authentic and > examine it for the presence of viruses. Xerox does perform virus checks > but cannot accept liability for any damage caused by any virus > transmitted by this email. Thank you." > > > > > > > > -----Original Message----- > From: majordomo-users-owner@greatcircle.com > [mailto:majordomo-users-owner@greatcircle.com] On Behalf Of Jevos, Peter > Sent: Tuesday, January 10, 2006 8:53 AM > To: majordomo-users@greatcircle.com > Subject: Footer appears only from one sender > > > Hello , > I'd like to ask for advice. I put simple footer into my test.config list > However, footer works and display only from one particular sender, it > doesn't work with the other senders, which sends email messages into > this test list. > Why ? > Pet From majordomo-users-owner@greatcircle.com Wed Jan 11 12:23:33 2006 X-Original-To: majordomo-users@greatcircle.com Received: from exch01ny.nyc.amlaw.corp (exchange1.ljx.com [208.3.165.72]) by mycroft.greatcircle.com (Postfix) with ESMTP id 0C74732C17F for ; Wed, 11 Jan 2006 12:23:32 -0800 (PST) Received: from 10.1.11.22 ([10.1.11.22]) by exch01ny.nyc.amlaw.corp ([10.1.50.5]) with Microsoft Exchange Server HTTP-DAV ; Wed, 11 Jan 2006 20:23:32 +0000 User-Agent: Microsoft-Entourage/11.2.1.051004 Date: Wed, 11 Jan 2006 15:23:30 -0500 Subject: start and finish of the list From: Tahir Chaudry To: Message-ID: Thread-Topic: start and finish of the list Thread-Index: AcYW7OLPIZQFOILgEdqfZQAKlefRWg== In-Reply-To: <43C42D02.2000502@sonny.org> Mime-version: 1.0 Content-type: multipart/alternative; boundary="B_3219837811_37337658" X-Archive-Number: 200601/13 X-Sequence-Number: 5269 > This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --B_3219837811_37337658 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit is there any way of knowing or time stamping start of a list and when the list was completed. I am using majordomo with postfix. thank you. -- tahir --B_3219837811_37337658 Content-type: text/html; charset="US-ASCII" Content-transfer-encoding: quoted-printable start and finish of the list i= s there any way of knowing or time stamping start of a list and when the li= st was completed.

I am using majordomo with postfix.

thank you.

-- tahir
--B_3219837811_37337658-- From majordomo-users-owner@greatcircle.com Wed Jan 11 13:48:22 2006 X-Original-To: majordomo-users@greatcircle.com Received: from mail.sonny.com (unknown [70.58.223.141]) by mycroft.greatcircle.com (Postfix) with ESMTP id 5EB1F32C2C6 for ; Wed, 11 Jan 2006 13:48:21 -0800 (PST) Received: from sonny.org (father.sonny.com [192.168.1.78]) by magnia.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0ISY00K0D6YH6H@magnia.sonny.com> for majordomo-users@greatcircle.com; Wed, 11 Jan 2006 15:42:18 -0600 (CST) Date: Wed, 11 Jan 2006 15:48:33 -0600 From: Daniel Liston Subject: Re: start and finish of the list In-reply-to: To: Tahir Chaudry Cc: majordomo-users@greatcircle.com Message-id: <43C57D31.4070905@sonny.org> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) References: X-Archive-Number: 200601/14 X-Sequence-Number: 5270 Are you referring to a list creation and termination date? Or do you mean when delivery of a distribution begins and completes? The former can be accomplished with comments in your aliases file, and the latter with log parsing or a dedicated queue to each list. Just throwing ideas around. Dan Liston Tahir Chaudry wrote: > is there any way of knowing or time stamping start of a list and when > the list was completed. > > I am using majordomo with postfix. > > thank you. > > -- tahir From majordomo-users-owner@greatcircle.com Thu Jan 12 04:30:22 2006 X-Original-To: majordomo-users@greatcircle.com Received: from ns.jp-achieve.co.jp (ns.jp-achieve.co.jp [210.239.50.83]) by mycroft.greatcircle.com (Postfix) with ESMTP id 12F3E32C352 for ; Thu, 12 Jan 2006 04:29:42 -0800 (PST) Received: from Y4 (s184154.ppp.asahi-net.or.jp [220.157.184.154]) by ns.jp-achieve.co.jp (8.12.11/8.12.10) with ESMTP id k0CCixAQ029033 for ; Thu, 12 Jan 2006 21:44:59 +0900 From: "Hiroyasu Ishida (Achieve)" To: Subject: Does anyone know "message from someone except 'resend' "? Date: Thu, 12 Jan 2006 21:36:14 +0900 Message-ID: <004001c61774$c68ccfc0$3d0ba8c0@Y4> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0041_01C617C0.367477C0" X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcYXdMYjq4ivZSRWTuiyc74IEqpSOA== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 X-Archive-Number: 200601/15 X-Sequence-Number: 5271 This is a multi-part message in MIME format. ------=_NextPart_000_0041_01C617C0.367477C0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I created a mailing-list using Majordomo, which is provided by an ISP. I sent a test message to the mailing-list, but the message has not been sent to any subscribed users, but an error message is sent to the administrator (It's me!). The message title is "message from someone except 'resend' " and the e-mail sent by subscribed user is attached on the e-mail. And, nothing is wrote in the message body. Has anyone experienced the same problem? Or does anyone know how I should fix the problem? Please advice me. Thanks, -- Hiroyasu Ishida from Japan ------=_NextPart_000_0041_01C617C0.367477C0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
I created a=20 mailing-list using Majordomo, which is provided by an ISP.
I sent a test=20 message to the mailing-list, but the message has not been sent to any subsc= ribed=20 users, but an error message is sent to the administrator (It's=20 me!).
 
The message=20 title is "message from someone except 'resend' " and the e-mail sent by=20 subscribed user is attached on the e-mail.
And, nothing is=20 wrote in the message body.
 
Has anyone=20 experienced the same problem?
Or does anyone=20 know how I should fix the problem?
 
Please advice=20 me.
 
Thanks,
 
--
Hiroyasu Ishida=20 from Japan
------=_NextPart_000_0041_01C617C0.367477C0-- From majordomo-users-owner@greatcircle.com Fri Jan 13 11:42:10 2006 X-Original-To: majordomo-users@greatcircle.com Received: from moroni.ourldsfamily.com (ourldsfamily.com [198.60.114.90]) by mycroft.greatcircle.com (Postfix) with ESMTP id 1DF6E32C1EF for ; Fri, 13 Jan 2006 11:42:08 -0800 (PST) Received: from webmail.ourldsfamily.com (eth1 [172.20.20.2]) by moroni.ourldsfamily.com (8.12.5/8.12.5) with ESMTP id k0DJg6C5028797 for ; Fri, 13 Jan 2006 12:42:07 -0700 Received: from ourldsfamily.com ([198.60.114.90]) (SquirrelMail authenticated user karlp) by webmail.ourldsfamily.com with HTTP; Fri, 13 Jan 2006 12:42:07 -0700 (MST) Message-ID: <29652.198.60.114.90.1137181327.squirrel@webmail.ourldsfamily.com> Date: Fri, 13 Jan 2006 12:42:07 -0700 (MST) Subject: MD 1.94.5 Aliases VIA Spamassassin From: karlp@ourldsfamily.com To: majordomo-users@greatcircle.com User-Agent: SquirrelMail/1.4.4-rc1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Archive-Number: 200601/16 X-Sequence-Number: 5272 Is there a safe method for parsing incoming emails through SpamAssassin before they are delivered to the email groups? I had one come through that didn't get checked before being sent out. (I've fixed the problem that caused it to come through in the first place, so hopefully there won't be a repeat). TIA -- karl _/ _/ _/ _/_/_/ ____________ __o _/ _/ _/ _/ _/ ____________ _-\<._ _/_/ _/ _/_/_/ (_)/ (_) _/ _/ _/ _/ ...................... _/ _/ arl _/_/_/ _/ earson KarlP@ourldsfamily.com --- Senior Consulting Sys/DB Analyst http://consulting.ourldsfamily.com --- From majordomo-users-owner@greatcircle.com Thu Jan 19 09:07:53 2006 X-Original-To: Majordomo-Users@GreatCircle.COM Received: from fc.sd91.bc.ca (www.e-bus.com.sd91.bc.ca [142.27.75.20]) by mycroft.greatcircle.com (Postfix) with ESMTP id AB26232C150 for ; Thu, 19 Jan 2006 09:06:02 -0800 (PST) Message-id: Date: Thu, 19 Jan 2006 09:07:59 -0800 Subject: Stripping HTML from messages X-FC-SERVER-TZ: 6554336 To: Majordomo-Users@GreatCircle.COM From: "Kevin Scott" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Archive-Number: 200601/17 X-Sequence-Number: 5273 Is there a way to strip html and unwanted characters from incoming messages ? Kevin Scott From majordomo-users-owner@greatcircle.com Thu Jan 19 09:10:43 2006 X-Original-To: Majordomo-Users@GreatCircle.COM Received: from mail.oriflame-sw.com (mail.oriflame-sw.com [194.149.124.180]) by mycroft.greatcircle.com (Postfix) with ESMTP id A4EB632C2DC for ; Thu, 19 Jan 2006 09:10:41 -0800 (PST) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Re: Stripping HTML from messages X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Date: Thu, 19 Jan 2006 18:10:29 +0100 Message-ID: <6639BA20B265594590E97DD72A8EE035421D42@exosw.osw.ori.local> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Stripping HTML from messages Thread-Index: AcYdGv7Z2tWHkumPQMeLPjXpPvS9OwAACznw From: "Jevos, Peter" To: "Kevin Scott" , X-Archive-Number: 200601/18 X-Sequence-Number: 5274 Try to use demime br=20=20 Peter Jevos peter.jevos@oriflame-sw.com Oriflame Software , s.r.o - Oriflame IT services Na Pankraci 30, Praha 4, Czech rep. Tel. +420 225 994 456, Fax +420225994412 -----Original Message----- From: majordomo-users-owner@greatcircle.com [mailto:majordomo-users-owner@greatcircle.com] On Behalf Of Kevin Scott Sent: Thursday, January 19, 2006 6:08 PM To: Majordomo-Users@GreatCircle.COM Subject: Stripping HTML from messages Is there a way to strip html and unwanted characters from incoming messages ? Kevin Scott From majordomo-users-owner@greatcircle.com Thu Jan 19 13:32:45 2006 X-Original-To: Majordomo-Users@GreatCircle.COM Received: from fc.sd91.bc.ca (www.e-bus.com.sd91.bc.ca [142.27.75.20]) by mycroft.greatcircle.com (Postfix) with ESMTP id 3EA3332C32B for ; Thu, 19 Jan 2006 13:32:42 -0800 (PST) Message-id: Date: Thu, 19 Jan 2006 13:34:29 -0800 Subject: Re: Stripping HTML from messages X-FC-SERVER-TZ: 6554336 To: "Jevos, Peter" Cc: Majordomo-Users@GreatCircle.COM From: "Kevin Scott" References: <6639BA20B265594590E97DD72A8EE035421D42@exosw.osw.ori.local> In-Reply-To: <6639BA20B265594590E97DD72A8EE035421D42@exosw.osw.ori.local> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Archive-Number: 200601/19 X-Sequence-Number: 5275 "Jevos, Peter" on Thursday, January 19, 2006 at 9:10 AM -0800 wrote: >Try to use demime > >br > > >Peter Jevos peter.jevos@oriflame-sw.com >Oriflame Software , s.r.o - Oriflame IT services >Na Pankraci 30, Praha 4, Czech rep. >Tel. +420 225 994 456, Fax +420225994412 >-----Original Message----- >From: majordomo-users-owner@greatcircle.com >[mailto:majordomo-users-owner@greatcircle.com] On Behalf Of Kevin Scott >Sent: Thursday, January 19, 2006 6:08 PM >To: Majordomo-Users@GreatCircle.COM >Subject: Stripping HTML from messages > >Is there a way to strip html and unwanted characters from incoming >messages ? >Kevin Scott > Thanks I will give that a try. Kevin > From majordomo-users-owner@greatcircle.com Fri Jan 20 01:38:52 2006 X-Original-To: majordomo-users@greatcircle.com Received: from bandsman.co.uk (nigelhorne.force9.co.uk [212.159.106.41]) by mycroft.greatcircle.com (Postfix) with ESMTP id DD6EA32C330 for ; Fri, 20 Jan 2006 01:37:59 -0800 (PST) Received: from [192.168.1.2] (njh [192.168.1.2]) (authenticated bits=0) by bandsman.co.uk (8.13.4/8.13.4) with ESMTP id k0K9dEkX015405 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 20 Jan 2006 09:39:16 GMT Message-ID: <43D0AFC3.2030209@bandsman.co.uk> Date: Fri, 20 Jan 2006 09:39:15 +0000 From: Nigel Horne Organization: NJH Music User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929) X-Accept-Language: en-us, en MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Digest trouble Content-Type: multipart/mixed; boundary="------------070401000509080003090501" Received-SPF: pass (bandsman.co.uk: 192.168.1.2 is authenticated by a trusted mechanism) X-DCC-sonic.net-Metrics: bandsman.co.uk 1156; Body=1 Fuz1=2 Fuz2=2 X-Archive-Number: 200601/20 X-Sequence-Number: 5276 This is a multi-part message in MIME format. --------------070401000509080003090501 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I've set up a digest according to the instructions in 3.11 and using the file .../majordomo-1.94.5/Doc/digest.aliases as a template but: 1) Subscribers who elected to receive in digest form can't post to the list 2) mkdigest does nothing: no error, no nothing. Here's my majordomo.aliases file. brass-band: "|/usr/majordomo/wrapper resend -l brass-band -h bandsman.co.uk brass-band-outgoing" brass-band-outgoing: :include:/usr/majordomo/lists/brass-band, brass-band-archive, brass-band-digestify brass-band-request: "|/usr/majordomo/wrapper majordomo -l brass-band" brass-band-approval: njh owner-brass-band: njh owner-brass-band-outgoing: owner-brass-band brass-band-archive: /usr/majordomo/archive/brass-band brass-band-digestify: "|/usr/majordomo/wrapper digest -r -C -l brass-band-digest brass-band-digest-outgoing" brass-band-digest: brass-band brass-band-digest-outgoing: :include:/usr/majordomo/lists/brass-band-digest brass-band-digest-request: "|/usr/majordomo/wrapper majordomo -l brass-band-digest" brass-band-digest-approval: njh owner-brass-band-digest-outgoing: owner-brass-band majordomo: "|/usr/majordomo/wrapper majordomo" owner-majordomo: njh, majordomo-owner: njh -Nigel -- Nigel Horne. Arranger, Adjudicator, Band Trainer, Composer, Tutor, Typesetter. NJH Music, Barnsley, UK. ICQ#20252325 njh@bandsman.co.uk http://www.bandsman.co.uk --------------070401000509080003090501 Content-Type: text/x-vcard; charset=utf-8; name="njh.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="njh.vcf" begin:vcard fn:Nigel Horne n:Horne;Nigel org:NJH Music email;internet:njh@bandsman.co.uk tel;fax:+44 870 705 9334 note:Skype: nigelhorne x-mozilla-html:FALSE version:2.1 end:vcard --------------070401000509080003090501-- From majordomo-users-owner@greatcircle.com Fri Jan 20 06:08:44 2006 X-Original-To: majordomo-users@greatcircle.com Received: from wrenkasky.com (esson.net [216.102.129.43]) by mycroft.greatcircle.com (Postfix) with ESMTP id 4CA6C32C377 for ; Fri, 20 Jan 2006 06:00:49 -0800 (PST) Received: from EDS.esson.net (eds.wrenkasky.com [10.10.10.11]) (authenticated bits=0) by wrenkasky.com (8.13.5/8.13.5) with ESMTP id k0KEECcK003350 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT); Fri, 20 Jan 2006 06:14:17 -0800 Message-Id: <6.0.0.22.2.20060120061119.01bda4a0@mail.esson.net> X-Sender: ed@mail.esson.net X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Fri, 20 Jan 2006 06:14:14 -0800 To: Nigel Horne , majordomo-users@greatcircle.com From: Ed Kasky Subject: Re: Digest trouble In-Reply-To: <43D0AFC3.2030209@bandsman.co.uk> References: <43D0AFC3.2030209@bandsman.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Received-SPF: pass (wrenkasky.com: 10.10.10.11 is authenticated by a trusted mechanism) X-Virus-Scanned: ClamAV 0.88/1246/Thu Jan 19 13:44:42 2006 on yoda2.wrenkasky.com X-Virus-Status: Clean X-Archive-Number: 200601/21 X-Sequence-Number: 5277 At 01:39 AM Friday, 1/20/2006, Nigel Horne wrote -=> >I've set up a digest according to the instructions in 3.11 >and using the file .../majordomo-1.94.5/Doc/digest.aliases >as a template but: > >1) Subscribers who elected to receive in digest form can't >post to the list Is the file of the recipients of the digest listed under restrict_post of the config file? How are you calling mkdigest? Ed . . . . . . . . . . . . . . . . . . Randomly Generated Quote (374 of 1030): All's well that ends. From majordomo-users-owner@greatcircle.com Fri Jan 20 06:52:56 2006 X-Original-To: majordomo-users@greatcircle.com Received: from bandsman.co.uk (nigelhorne.force9.co.uk [212.159.106.41]) by mycroft.greatcircle.com (Postfix) with ESMTP id F40A332C153 for ; Fri, 20 Jan 2006 06:52:47 -0800 (PST) Received: from [192.168.1.2] (njh [192.168.1.2]) (authenticated bits=0) by bandsman.co.uk (8.13.4/8.13.4) with ESMTP id k0KEqis5022235 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 20 Jan 2006 14:52:46 GMT Message-ID: <43D0F93D.6080706@bandsman.co.uk> Date: Fri, 20 Jan 2006 14:52:45 +0000 From: Nigel Horne Organization: NJH Music User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929) X-Accept-Language: en-us, en MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Re: Digest trouble References: <43D0AFC3.2030209@bandsman.co.uk> <6.0.0.22.2.20060120061119.01bda4a0@mail.esson.net> In-Reply-To: <6.0.0.22.2.20060120061119.01bda4a0@mail.esson.net> Content-Type: multipart/mixed; boundary="------------080200010204030707020106" Received-SPF: pass (bandsman.co.uk: 192.168.1.2 is authenticated by a trusted mechanism) X-DCC-Misty-Metrics: bandsman.co.uk 1170; Body=1 Fuz1=1 Fuz2=1 X-Archive-Number: 200601/22 X-Sequence-Number: 5278 This is a multi-part message in MIME format. --------------080200010204030707020106 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Ed Kasky wrote: > At 01:39 AM Friday, 1/20/2006, Nigel Horne wrote -=> > >> I've set up a digest according to the instructions in 3.11 >> and using the file .../majordomo-1.94.5/Doc/digest.aliases >> as a template but: >> >> 1) Subscribers who elected to receive in digest form can't >> post to the list > > > Is the file of the recipients of the digest listed under restrict_post > of the config file? I've added that, thanks. I couldn't see that mentioned in the FAQ. > How are you calling mkdigest? echo mkdigest brass-band xxx | mail majordomo > > Ed -Nigel -- Nigel Horne. Arranger, Adjudicator, Band Trainer, Composer, Tutor, Typesetter. NJH Music, Barnsley, UK. ICQ#20252325 njh@bandsman.co.uk http://www.bandsman.co.uk --------------080200010204030707020106 Content-Type: text/x-vcard; charset=utf-8; name="njh.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="njh.vcf" begin:vcard fn:Nigel Horne n:Horne;Nigel org:NJH Music email;internet:njh@bandsman.co.uk tel;fax:+44 870 705 9334 note:Skype: nigelhorne x-mozilla-html:FALSE version:2.1 end:vcard --------------080200010204030707020106-- From majordomo-users-owner@greatcircle.com Fri Jan 20 09:32:27 2006 X-Original-To: majordomo-users@greatcircle.com Received: from ns.nrns.ca (ns.nrns.ca [216.191.212.230]) by mycroft.greatcircle.com (Postfix) with ESMTP id B68C632C152 for ; Fri, 20 Jan 2006 09:32:26 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by ns.nrns.ca (_) with ESMTP id A4B2125744 for ; Fri, 20 Jan 2006 12:32:24 -0500 (EST) Received: from feline.nrns.ca (feline.nrns.ca [10.111.111.68]) by ns.nrns.ca (_) with ESMTP id D30F025722 for ; Fri, 20 Jan 2006 12:32:21 -0500 (EST) Received: from nrns.ca (host76.nrns.ca [10.111.111.76]) by feline.nrns.ca (Postfix) with ESMTP id 0BC7A3F41C6 for ; Fri, 20 Jan 2006 12:32:22 -0500 (EST) Message-ID: <43D11F77.3060708@nrns.ca> Date: Fri, 20 Jan 2006 12:35:51 -0500 From: "Allan P. Magmanlac" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: MAJORDOMO-USERS Subject: dealing with bounced messages Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at nrns.ca X-Archive-Number: 200601/23 X-Sequence-Number: 5279 Hello, Scenario: User A sends a rich text message uing outlook to testlist owned by User B. User A is not a member of testlist and so the bounce message goes to User B. User B receives the bounce message notification the but the original message is returned as text, original format is gone and so cannot view the contents of the original message. (i.e ) ------=_NextPart_000_0001_01C61DB9.925495D0 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="winmail.dat" eJ8+IjARAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEGgAMADgAAANYHAQAUAAwAAwAAAAUABgEB A5AGAMQOAAApAAAACwACAAEAAAALACMAAAAAAAMAJgAAAAAACwApAAAAAAADADYAAAAAAB4AcAAB AAAAFwAAAHRlc3RpbmcgYm91bmNlIG1lc3NhZ2UAAAIBcQABAAAAFgAAAAHGHeN49Z1s5LMZWkDo Questions: 1) Is there a way to configure majordomo to forward the bounced message to the owner with the original message format intact so that he can view the message? how? 2) OR is it sendmail that needs to be configured, how? From majordomo-users-owner@greatcircle.com Fri Jan 20 09:38:58 2006 X-Original-To: majordomo-users@greatcircle.com Received: from wrenkasky.com (esson.net [216.102.129.43]) by mycroft.greatcircle.com (Postfix) with ESMTP id 0908632C189 for ; Fri, 20 Jan 2006 09:38:57 -0800 (PST) Received: from KASKY.esson.net (kasky.priority.usc.edu [128.125.63.85]) (authenticated bits=0) by wrenkasky.com (8.13.5/8.13.5) with ESMTP id k0KHcbJR010086 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT); Fri, 20 Jan 2006 09:38:42 -0800 Message-Id: <6.0.0.22.2.20060120092602.01cbd3c0@mail.esson.net> X-Sender: ed@mail.esson.net X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Fri, 20 Jan 2006 09:38:30 -0800 To: Nigel Horne From: Ed Kasky Subject: Re: Digest trouble Cc: majordomo-users@greatcircle.com In-Reply-To: <43D0F93D.6080706@bandsman.co.uk> References: <43D0AFC3.2030209@bandsman.co.uk> <6.0.0.22.2.20060120061119.01bda4a0@mail.esson.net> <43D0F93D.6080706@bandsman.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Received-SPF: pass (wrenkasky.com: 128.125.63.85 is authenticated by a trusted mechanism) X-Virus-Scanned: ClamAV 0.88/1246/Thu Jan 19 13:44:42 2006 on yoda2.wrenkasky.com X-Virus-Status: Clean X-Archive-Number: 200601/24 X-Sequence-Number: 5280 At 06:52 AM Friday, 1/20/2006, you wrote -=> >Ed Kasky wrote: >>At 01:39 AM Friday, 1/20/2006, Nigel Horne wrote -=> >> >>>I've set up a digest according to the instructions in 3.11 >>>and using the file .../majordomo-1.94.5/Doc/digest.aliases >>>as a template but: >>> >>>1) Subscribers who elected to receive in digest form can't >>>post to the list >> >>Is the file of the recipients of the digest listed under restrict_post of >>the config file? > >I've added that, thanks. I couldn't see that mentioned in the FAQ. It's in the config file: # restrict_post [restrict_post] (undef) # If defined, only addresses listed in these files (colon or space # separated) can post to the mailing list. By default, these files # are relative to the lists directory. These files are also checked # when get_access, index_access, info_access, intro_access, # which_access, or who_access is set to 'list'. This is less useful # than it seems it should be since there is no way to create these # files if you do not have access to the machine running resend. # This mechanism will be replaced in a future version of # majordomo/resend. restrict_post = therox therox-digest >>How are you calling mkdigest? > >echo mkdigest brass-band xxx | mail majordomo You've told it which digest to make but seem to be missing the recipient. Were the digests created and put in the proper folder under lists/digest or however you configured it? This is one of my digest cron jobs: echo mkdigest therox-digest therox-digest-outgoing therox.passwd | mail majordomo@esson.net The passwd is stored in the file "therox.passwd" which is in the same location as the config file. A copy is left in "/usr/local/majordomo/lists/digest/the-rox" Pertinent digest recipient alias: therox-digest-outgoing: :include:/usr/local/majordomo/lists/therox-digest,nobody Ed Kasky ~~~~~~~~~ Randomly Generated Quote (363 of 498): Knowing ignorance is strength; ignoring knowledge is sickness. -Lao-Tzu, philosopher (6th century BCE) From majordomo-users-owner@greatcircle.com Fri Jan 20 09:42:44 2006 X-Original-To: majordomo-users@greatcircle.com Received: from bandsman.co.uk (nigelhorne.force9.co.uk [212.159.106.41]) by mycroft.greatcircle.com (Postfix) with ESMTP id C33CE32C36F for ; Fri, 20 Jan 2006 09:42:43 -0800 (PST) Received: from [192.168.1.2] (njh [192.168.1.2]) (authenticated bits=0) by bandsman.co.uk (8.13.4/8.13.4) with ESMTP id k0KHgcgw025355 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 20 Jan 2006 17:42:40 GMT Message-ID: <43D1210E.20306@bandsman.co.uk> Date: Fri, 20 Jan 2006 17:42:38 +0000 From: Nigel Horne Organization: NJH Music User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929) X-Accept-Language: en-us, en MIME-Version: 1.0 Cc: majordomo-users@greatcircle.com Subject: Re: Digest trouble References: <43D0AFC3.2030209@bandsman.co.uk> <6.0.0.22.2.20060120061119.01bda4a0@mail.esson.net> <43D0F93D.6080706@bandsman.co.uk> <6.0.0.22.2.20060120092602.01cbd3c0@mail.esson.net> In-Reply-To: <6.0.0.22.2.20060120092602.01cbd3c0@mail.esson.net> Content-Type: multipart/mixed; boundary="------------020302050209030307080700" Received-SPF: pass (bandsman.co.uk: 192.168.1.2 is authenticated by a trusted mechanism) X-DCC-EATSERVER-Metrics: bandsman.co.uk 1166; Body=1 Fuz1=1 Fuz2=1 X-Archive-Number: 200601/25 X-Sequence-Number: 5281 This is a multi-part message in MIME format. --------------020302050209030307080700 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Ed Kasky wrote: >>> How are you calling mkdigest? >> >> >> echo mkdigest brass-band xxx | mail majordomo > > > You've told it which digest to make but seem to be missing the > recipient. Were the digests created and put in the proper folder under > lists/digest or however you configured it? > > This is one of my digest cron jobs: > > echo mkdigest therox-digest therox-digest-outgoing therox.passwd | mail > majordomo@esson.net That doesn't tally with FAQ item 4.2 which has no outgoing argument. > Ed Kasky > ~~~~~~~~~ > Randomly Generated Quote (363 of 498): > Knowing ignorance is strength; ignoring knowledge is sickness. > -Lao-Tzu, philosopher (6th century BCE) -- Nigel Horne. Arranger, Adjudicator, Band Trainer, Composer, Tutor, Typesetter. NJH Music, Barnsley, UK. ICQ#20252325 njh@bandsman.co.uk http://www.bandsman.co.uk --------------020302050209030307080700 Content-Type: text/x-vcard; charset=utf-8; name="njh.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="njh.vcf" begin:vcard fn:Nigel Horne n:Horne;Nigel org:NJH Music email;internet:njh@bandsman.co.uk tel;fax:+44 870 705 9334 note:Skype: nigelhorne x-mozilla-html:FALSE version:2.1 end:vcard --------------020302050209030307080700-- From majordomo-users-owner@greatcircle.com Fri Jan 20 09:49:04 2006 X-Original-To: majordomo-users@greatcircle.com Received: from bandsman.co.uk (nigelhorne.force9.co.uk [212.159.106.41]) by mycroft.greatcircle.com (Postfix) with ESMTP id D149B32C38F for ; Fri, 20 Jan 2006 09:49:03 -0800 (PST) Received: from [192.168.1.2] (njh [192.168.1.2]) (authenticated bits=0) by bandsman.co.uk (8.13.4/8.13.4) with ESMTP id k0KHmrJw025531 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 20 Jan 2006 17:48:54 GMT Message-ID: <43D12285.1000909@bandsman.co.uk> Date: Fri, 20 Jan 2006 17:48:53 +0000 From: Nigel Horne Organization: NJH Music User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929) X-Accept-Language: en-us, en MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Re: Digest trouble References: <43D0AFC3.2030209@bandsman.co.uk> <6.0.0.22.2.20060120061119.01bda4a0@mail.esson.net> <43D0F93D.6080706@bandsman.co.uk> <6.0.0.22.2.20060120092602.01cbd3c0@mail.esson.net> <43D1210E.20306@bandsman.co.uk> In-Reply-To: <43D1210E.20306@bandsman.co.uk> Content-Type: multipart/mixed; boundary="------------020506010908020403060902" Received-SPF: pass (bandsman.co.uk: 192.168.1.2 is authenticated by a trusted mechanism) X-DCC-EATSERVER-Metrics: bandsman.co.uk 1166; Body=1 Fuz1=1 Fuz2=1 X-Archive-Number: 200601/26 X-Sequence-Number: 5282 This is a multi-part message in MIME format. --------------020506010908020403060902 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Go it. The name of the outgoing isn't needed, but the [digest-name] referred to in the FAQ is in fact the [list-name] with -digest at the end, which I failed to appreciate. The issue of digest members posting may have been fixed by Ed's comments, seems to be that FAQ 3.11 should reflect that point. -Nigel -- Nigel Horne. Arranger, Adjudicator, Band Trainer, Composer, Tutor, Typesetter. NJH Music, Barnsley, UK. ICQ#20252325 njh@bandsman.co.uk http://www.bandsman.co.uk --------------020506010908020403060902 Content-Type: text/x-vcard; charset=utf-8; name="njh.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="njh.vcf" begin:vcard fn:Nigel Horne n:Horne;Nigel org:NJH Music email;internet:njh@bandsman.co.uk tel;fax:+44 870 705 9334 note:Skype: nigelhorne x-mozilla-html:FALSE version:2.1 end:vcard --------------020506010908020403060902-- From majordomo-users-owner@greatcircle.com Sat Jan 21 22:57:49 2006 X-Original-To: majordomo-users@greatcircle.com Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.205]) by mycroft.greatcircle.com (Postfix) with ESMTP id 7050132C3D8 for ; Sat, 21 Jan 2006 22:57:48 -0800 (PST) Received: by uproxy.gmail.com with SMTP id k40so753584ugc for ; Sat, 21 Jan 2006 22:57:46 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=cftxNH5i7htRE7Gs8mfNVWMBi9O+g55pUjvh7NeZhjI38F5OCOZO6UZRybBkVekELjZnsCvTY0kZS0o0iGlU575o3Nvt8uP8QdSnfUZIOjFs8BJkYpJHOEGDUUR6oaULLN4kTYAYXRpzpdCmDPyWQMW1m1YDFgWT6FmjrLxziLc= Received: by 10.49.87.12 with SMTP id p12mr252624nfl; Sat, 21 Jan 2006 22:57:46 -0800 (PST) Received: by 10.49.78.8 with HTTP; Sat, 21 Jan 2006 22:57:46 -0800 (PST) Message-ID: Date: Sat, 21 Jan 2006 21:57:46 -0900 From: Jim Dory To: majordomo-users@greatcircle.com Subject: undeliverable message handling - over quota MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_5897_22366992.1137913066633" X-Archive-Number: 200601/27 X-Sequence-Number: 5283 ------=_Part_5897_22366992.1137913066633 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I get several undeliverable messages a day from users on our list (I'm the admin) that are overquota. It doesn't really do me any good to see these messages.. how to you , if you can, send them to null or whatever? Occasionally when someone moves away, I get "undeliverable: unknown user" error messages and I would like to keep getting those error msgs. So basically I just want to filter out the over quota ones. Possible? many thanks, Jim ------=_Part_5897_22366992.1137913066633 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I get several undeliverable messages a day from users on our list (I'm the = admin) that are overquota. It doesn't really do me any good to see these me= ssages.. how to you , if you can, send them to null or whatever?

Occasionally when someone moves away, I get "undeliverable: unknown us= er" error messages and I would like to keep getting those error msgs. = So basically I just want to filter out the over quota ones. Possible?

many thanks, Jim
------=_Part_5897_22366992.1137913066633-- From majordomo-users-owner@greatcircle.com Sun Jan 22 20:30:51 2006 X-Original-To: majordomo-users@GreatCircle.com Received: from host-technology.com (210-210-79-232.lan.sify.net [210.210.79.232]) by mycroft.greatcircle.com (Postfix) with ESMTP id A3A8C32C17B for ; Sun, 22 Jan 2006 20:30:49 -0800 (PST) X-MDSPF-Result: none (host-technology.com) Received-SPF: none (host-technology.com: sailaja.mulakaluri@host-technology.com does not designate permitted sender hosts) x-spf-client=MDaemon.PRO.v8.1.3.R receiver=host-technology.com client-ip=221.134.7.132 envelope-from= helo=192.168.24.16 Received: from 192.168.24.16 ([221.134.7.132]) by host-technology.com (host-technology.com) (MDaemon.PRO.v8.1.3.R) with ESMTP id md50000355275.msg for ; Mon, 23 Jan 2006 10:02:51 +0530 Subject: majordomo From: "Sailaja.Mulakaluri" To: majordomo-users@GreatCircle.com Content-Type: text/plain Date: Mon, 23 Jan 2006 04:31:03 +0000 Message-Id: <1137990663.3030.24.camel@HOST16> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-HOST1.0) Content-Transfer-Encoding: 7bit X-Spam-Processed: host-technology.com, Mon, 23 Jan 2006 10:02:51 +0530 (not processed: spam filter disabled) X-MDRemoteIP: 221.134.7.132 X-Return-Path: sailaja.mulakaluri@host-technology.com X-MDaemon-Deliver-To: majordomo-users@GreatCircle.com X-MDAV-Processed: host-technology.com, Mon, 23 Jan 2006 10:02:53 +0530 X-Archive-Number: 200601/28 X-Sequence-Number: 5284 I am a newbie trying to set majordomo-mail list manager for my sendmail server. After the entire configuration, what needs to be done? I mean how to test majordomo -- Regards, Sailaja.Mulakaluri From majordomo-users-owner@greatcircle.com Mon Jan 23 12:04:01 2006 X-Original-To: majordomo-users@greatcircle.com Received: from providence.edu (emailgw.providence.edu [198.7.241.33]) by mycroft.greatcircle.com (Postfix) with ESMTP id A9B8932C19E for ; Mon, 23 Jan 2006 12:02:24 -0800 (PST) Received: from ([10.1.50.2]) by emailgw.providence.edu with ESMTP id KP-KZ166.47377499; Mon, 23 Jan 2006 15:01:58 -0500 From: "Edward Chase" To: Subject: line / paragraph length limit Date: Mon, 23 Jan 2006 15:01:57 -0500 Message-ID: <009601c62057$dd8d8200$0232010a@providence.col> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal X-ESP: ESP<0>=RBL:<0> RDNS:<0> SHA:<0> UHA:<0> SLS:<0> BAYES:<0> SenderID:<0> X-Archive-Number: 200601/29 X-Sequence-Number: 5285 Howdy! A rather lengthy message got sent through a mailing list I'm in charge of. There were unexpected paragraph/line breaks just after the 990th character in the pargraph(s). Can you help me expliain to my supervisor why this happened? Thanks. -- Edward Chase Providence College Information Technology From majordomo-users-owner@greatcircle.com Mon Jan 23 12:11:33 2006 X-Original-To: majordomo-users@greatcircle.com Received: from providence.edu (emailgw.providence.edu [198.7.241.33]) by mycroft.greatcircle.com (Postfix) with ESMTP id 4E6D232C194 for ; Mon, 23 Jan 2006 12:11:32 -0800 (PST) Received: from ([10.1.50.2]) by emailgw.providence.edu with ESMTP id KP-KZ166.47378219; Mon, 23 Jan 2006 15:11:08 -0500 From: "Edward Chase" To: Subject: Re: line / paragraph length limit Date: Mon, 23 Jan 2006 15:11:07 -0500 Message-ID: <009a01c62059$2581a770$0232010a@providence.col> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: <009601c62057$dd8d8200$0232010a@providence.col> Importance: Normal X-ESP: ESP<0>=RBL:<0> RDNS:<0> SHA:<0> UHA:<0> SLS:<0> BAYES:<0> SenderID:<0> X-Archive-Number: 200601/30 X-Sequence-Number: 5286 Just to add... majordomo is v1.94.5 (not an RPM install) redhat 9 postfix is v1.1.12 I found something that might point to postfix causing the break. Maybe... > -----Original Message----- > From: majordomo-users-owner@greatcircle.com > [mailto:majordomo-users-owner@greatcircle.com] On Behalf Of > Edward Chase > Sent: Monday, January 23, 2006 3:02 PM > To: majordomo-users@greatcircle.com > Subject: line / paragraph length limit > > > Howdy! > > A rather lengthy message got sent through a mailing list I'm > in charge of. > > There were unexpected paragraph/line breaks just after the > 990th character > in the pargraph(s). > > Can you help me expliain to my supervisor why this happened? > > Thanks. > > -- > Edward Chase > Providence College > Information Technology > From majordomo-users-owner@greatcircle.com Mon Jan 23 12:13:16 2006 X-Original-To: majordomo-users@greatcircle.com Received: from bigbrother.aphasianet.com (mailbox.onlinepolicy.net [64.62.161.194]) by mycroft.greatcircle.com (Postfix) with ESMTP id 51FFB32C2A0 for ; Mon, 23 Jan 2006 12:13:16 -0800 (PST) Received: by bigbrother.aphasianet.com (Postfix, from userid 1002) id 596602843C; Mon, 23 Jan 2006 12:29:05 -0800 (PST) Received: from [127.0.0.1] (c-67-168-99-147.hsd1.wa.comcast.net [67.168.99.147]) by bigbrother.aphasianet.com (Postfix) with ESMTP id AC5A228427; Mon, 23 Jan 2006 12:29:02 -0800 (PST) Message-ID: <43D538D0.8070900@queernet.org> Date: Mon, 23 Jan 2006 12:13:04 -0800 From: "Roger B.A. Klorese" User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Edward Chase Cc: majordomo-users@greatcircle.com Subject: Re: line / paragraph length limit References: <009601c62057$dd8d8200$0232010a@providence.col> In-Reply-To: <009601c62057$dd8d8200$0232010a@providence.col> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on bigbrother.aphasianet.com X-Spam-Level: X-Spam-Status: No, score=-0.5 required=4.0 tests=BAYES_00,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 X-Archive-Number: 200601/31 X-Sequence-Number: 5287 Edward Chase wrote: > Howdy! > > A rather lengthy message got sent through a mailing list I'm in charge of. > > There were unexpected paragraph/line breaks just after the 990th character > in the pargraph(s). > > Can you help me expliain to my supervisor why this happened? > The SMTP protocol requires it. text line The maximum total length of a text line including the is 1000 characters (not counting the leading dot duplicated for transparency). This number may be increased by the use of SMTP Service Extensions. The extra ten characters are pad for delimiters. From majordomo-users-owner@greatcircle.com Mon Jan 23 12:18:02 2006 X-Original-To: majordomo-users@greatcircle.com Received: from providence.edu (emailgw.providence.edu [198.7.241.33]) by mycroft.greatcircle.com (Postfix) with ESMTP id 79E0632C28B for ; Mon, 23 Jan 2006 12:18:01 -0800 (PST) Received: from ([10.1.50.2]) by emailgw.providence.edu with ESMTP id KP-KZ166.47378687; Mon, 23 Jan 2006 15:17:42 -0500 From: "Edward Chase" To: "'Roger B.A. Klorese'" Cc: Subject: Re: line / paragraph length limit Date: Mon, 23 Jan 2006 15:17:41 -0500 Message-ID: <009c01c6205a$105db540$0232010a@providence.col> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: <43D538D0.8070900@queernet.org> Importance: Normal X-ESP: ESP<0>=RBL:<0> RDNS:<0> SHA:<0> UHA:<0> SLS:<0> BAYES:<0> SenderID:<0> X-Archive-Number: 200601/32 X-Sequence-Number: 5288 > Edward Chase wrote: > > Howdy! > > > > A rather lengthy message got sent through a mailing list > I'm in charge of. > > > > There were unexpected paragraph/line breaks just after the > 990th character > > in the pargraph(s). > > > > Can you help me expliain to my supervisor why this happened? > > > > From: Roger B.A. Klorese [mailto:rogerk@queernet.org] > The SMTP protocol requires it. > > text line > The maximum total length of a text line including the is > 1000 characters (not counting the leading dot duplicated for > transparency). This number may be increased by the use of SMTP > Service Extensions. > > The extra ten characters are pad for delimiters. Thank you for that. One followup on this. The same message sent from one Outlook user to another Outlook user did not show the same forced breaks. Can you explain that? From majordomo-users-owner@greatcircle.com Mon Jan 23 12:20:53 2006 X-Original-To: majordomo-users@greatcircle.com Received: from bigbrother.aphasianet.com (mailbox.onlinepolicy.net [64.62.161.194]) by mycroft.greatcircle.com (Postfix) with ESMTP id D88AC32C226 for ; Mon, 23 Jan 2006 12:20:52 -0800 (PST) Received: by bigbrother.aphasianet.com (Postfix, from userid 1002) id 735AC28421; Mon, 23 Jan 2006 12:36:47 -0800 (PST) Received: from [127.0.0.1] (c-67-168-99-147.hsd1.wa.comcast.net [67.168.99.147]) by bigbrother.aphasianet.com (Postfix) with ESMTP id 491462847A; Mon, 23 Jan 2006 12:36:45 -0800 (PST) Message-ID: <43D53AA0.9060300@queernet.org> Date: Mon, 23 Jan 2006 12:20:48 -0800 From: "Roger B.A. Klorese" User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Edward Chase Cc: majordomo-users@greatcircle.com Subject: Re: line / paragraph length limit References: <009c01c6205a$105db540$0232010a@providence.col> In-Reply-To: <009c01c6205a$105db540$0232010a@providence.col> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on bigbrother.aphasianet.com X-Spam-Level: X-Spam-Status: No, score=-0.5 required=4.0 tests=BAYES_00,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 X-Archive-Number: 200601/33 X-Sequence-Number: 5289 Edward Chase wrote > Thank you for that. One followup on this. The same message sent from one > Outlook user to another Outlook user did not show the same forced breaks. > > Can you explain that? > > If mail never leaves the server, but it just sent from one Outlook user to another, SMTP restrictions do not apply. Even if the mail leaves the server, the sending and receiving servers may negotiate a line-length extension, as the definition I gave supports. You can't just assume that any mail server does, however. From majordomo-users-owner@greatcircle.com Mon Jan 23 12:53:47 2006 X-Original-To: majordomo-users@greatcircle.com Received: from providence.edu (emailgw.providence.edu [198.7.241.33]) by mycroft.greatcircle.com (Postfix) with ESMTP id 81D3B32C2E4 for ; Mon, 23 Jan 2006 12:53:46 -0800 (PST) Received: from ([10.1.50.2]) by emailgw.providence.edu with ESMTP id KP-KZ166.47381364; Mon, 23 Jan 2006 15:53:26 -0500 From: "Edward Chase" To: "'Roger B.A. Klorese'" Cc: Subject: Re: line / paragraph length limit Date: Mon, 23 Jan 2006 15:53:25 -0500 Message-ID: <00a701c6205f$0dce6590$0232010a@providence.col> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: <43D53AA0.9060300@queernet.org> Importance: Normal X-ESP: ESP<0>=RBL:<0> RDNS:<0> SHA:<0> UHA:<0> SLS:<0> BAYES:<0> SenderID:<0> X-Archive-Number: 200601/34 X-Sequence-Number: 5290 > Edward Chase wrote > > Thank you for that. One followup on this. The same > message sent from one > > Outlook user to another Outlook user did not show the same > forced breaks. > > > > Can you explain that? > From: Roger B.A. Klorese [mailto:rogerk@queernet.org] > If mail never leaves the server, but it just sent from one > Outlook user > to another, SMTP restrictions do not apply. > > Even if the mail leaves the server, the sending and receiving servers > may negotiate a line-length extension, as the definition I > gave supports. > > You can't just assume that any mail server does, however. Thanks again. The long message in that prompted this was sent out via a crontab job. ie. 23 01 00 12 * mail list@server < message.txt I'm limited to the SMTP protocol's rules since there isn't much else there to negoiate line lengths? There actually was a jump between servers. Hmmm... However, I'll try to cron the job up on the majordomo server and see what happens... From majordomo-users-owner@greatcircle.com Mon Jan 23 13:10:32 2006 X-Original-To: majordomo-users@greatcircle.com Received: from bigbrother.aphasianet.com (mailbox.onlinepolicy.net [64.62.161.194]) by mycroft.greatcircle.com (Postfix) with ESMTP id 2BFB832C17E for ; Mon, 23 Jan 2006 13:10:32 -0800 (PST) Received: by bigbrother.aphasianet.com (Postfix, from userid 1002) id B58B7284EE; Mon, 23 Jan 2006 13:26:26 -0800 (PST) Received: from [127.0.0.1] (c-67-168-99-147.hsd1.wa.comcast.net [67.168.99.147]) by bigbrother.aphasianet.com (Postfix) with ESMTP id C24B3284FC; Mon, 23 Jan 2006 13:26:25 -0800 (PST) Message-ID: <43D5464A.3030409@queernet.org> Date: Mon, 23 Jan 2006 13:10:34 -0800 From: "Roger B.A. Klorese" User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Edward Chase Cc: majordomo-users@greatcircle.com Subject: Re: line / paragraph length limit References: <00a701c6205f$0dce6590$0232010a@providence.col> In-Reply-To: <00a701c6205f$0dce6590$0232010a@providence.col> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on bigbrother.aphasianet.com X-Spam-Level: X-Spam-Status: No, score=-0.5 required=4.0 tests=BAYES_00,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 X-Archive-Number: 200601/35 X-Sequence-Number: 5291 Edward Chase wrote: > Thanks again. The long message in that prompted this was sent out via a > crontab job. > > ie. 23 01 00 12 * mail list@server < message.txt > > If you want a text file of arbitrary line length to be sent via email, you need to build a MIME message with a proper encoding. From majordomo-users-owner@greatcircle.com Mon Jan 23 13:41:55 2006 X-Original-To: majordomo-users@greatcircle.com Received: from providence.edu (emailgw.providence.edu [198.7.241.33]) by mycroft.greatcircle.com (Postfix) with ESMTP id 96DAD32C2FD for ; Mon, 23 Jan 2006 13:41:54 -0800 (PST) Received: from ([10.1.50.2]) by emailgw.providence.edu with ESMTP id KP-KZ166.47385763; Mon, 23 Jan 2006 16:41:23 -0500 From: "Edward Chase" To: "'Roger B.A. Klorese'" Cc: Subject: Re: line / paragraph length limit Date: Mon, 23 Jan 2006 16:41:22 -0500 Message-ID: <00b201c62065$c09a4800$0232010a@providence.col> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: <43D5464A.3030409@queernet.org> Importance: Normal X-ESP: ESP<0>=RBL:<0> RDNS:<0> SHA:<0> UHA:<0> SLS:<0> BAYES:<0> SenderID:<0> X-Archive-Number: 200601/36 X-Sequence-Number: 5292 > Edward Chase wrote: > > Thanks again. The long message in that prompted this was sent out via a crontab job. > > > > ie. 23 01 00 12 * mail list@server < message.txt > From: Roger B.A. Klorese [mailto:rogerk@queernet.org]=20 > If you want a text file of arbitrary line length to be sent=20 > via email, you need to build a MIME message with a proper encoding. You wouldn't happen to have a handy link to online documentation on how to accmomplish that, would you? From majordomo-users-owner@greatcircle.com Thu Jan 26 00:27:11 2006 X-Original-To: majordomo-users@greatcircle.com Received: from rzjgate.joanneum.ac.at (rzjgate.joanneum.ac.at [143.224.185.1]) by mycroft.greatcircle.com (Postfix) with ESMTP id 960E232C20F for ; Thu, 26 Jan 2006 00:27:07 -0800 (PST) Received: from RZJC2EX.jr1.local (rzjs028.joanneum.ac.at [143.224.71.152]) by rzjgate.joanneum.ac.at (8.13.1/8.13.1) with ESMTP id k0Q8R5O8381156 for ; Thu, 26 Jan 2006 09:27:05 +0100 (MET) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: Setting REPLY-To to the REPLY-TO: field of the original e-mail Date: Thu, 26 Jan 2006 09:27:04 +0100 Message-ID: <768DACDC356ED04EA1F1130F97D29852A9C149@RZJC2EX.jr1.local> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Setting REPLY-To to the REPLY-TO: field of the original e-mail Thread-Index: AcYEpFscOu8TEOFuQlSsQ3Ofvh09lQ== From: "Thallinger, Georg" To: X-Archive-Number: 200601/37 X-Sequence-Number: 5293 Hi, it would be helpful if there was an option to set the reply-to field of th= e resend e-mail to the REPLY-To: contents of the original e-mail. Naively I tried setting reply-to to "$REPLY-TO" (hoping that this token is = defined in the same manner as $SENDER) but had to discover that this does n= ot work. Any hints? Best regards, Georg -------------------------------------------------------------------- Georg Thallinger Institute of Information Systems & Information Management JOANNEUM RESEARCH Forschungsgesellschaft mbH Steyrergasse 17, A-8010 Graz, AUSTRIA =20 e-mail: mailto:georg.thallinger@joanneum.at=20 phone: +43-316-876-1240 fax: +43-316-876-1191 web: http://www.joanneum.at/iis=20 geo: N47=B003.843' E15=B027.181' (WGS84) -------------------------------------------------------------------- From majordomo-users-owner@greatcircle.com Sat Jan 28 07:39:28 2006 X-Original-To: majordomo-users@greatcircle.com Received: from smtp7.libero.it (smtp7.libero.it [193.70.192.90]) by mycroft.greatcircle.com (Postfix) with ESMTP id 5C58B32C159 for ; Sat, 28 Jan 2006 07:39:27 -0800 (PST) Received: from localhost (172.16.1.48) by smtp7.libero.it (7.0.027-DD01) id 439D91A3039628F8 for majordomo-users@greatcircle.com; Sat, 28 Jan 2006 16:39:28 +0100 Received: from smtp20.libero.it ([172.16.1.77]) by localhost (asav8.libero.it [193.70.193.94]) (amavisd-new, port 10024) with ESMTP id 14105-01 for ; Sat, 28 Jan 2006 16:39:28 +0100 (CET) Received: from luciopc (adsl-ull-115-189.44-151.net24.it [151.44.189.115]) by smtp20.libero.it (Postfix) with SMTP id 2F21F50765 for ; Sat, 28 Jan 2006 16:39:28 +0100 (MET) Date: Sat, 28 Jan 2006 16:39:26 +0100 From: "Luciano" To: majordomo-users@greatcircle.com Subject: Majordomo configuration X-mailer: Foxmail 4.1 [it] Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <20060128153928.2F21F50765@smtp20.libero.it> X-Scanned: with antispam and antivirus automated system at libero.it X-Archive-Number: 200601/38 X-Sequence-Number: 5294 I have opened a newsletter through our provider which exploits Majordomo. I have to modify the welcome message that arrives to a new member, by replacing the message of default. I have just sent the message of "intro" using "newintro newsletter" and the other message of "info" making use of "newinfo newsletter", and then with the appropriate controls i have ckecked (controllare) that my messages had been changed. Although this, a new member receive a welcome message with the messagge of default in addition to my message "intro". How can I avoid the message of default? thank you for the attention Luciano From majordomo-users-owner@greatcircle.com Sat Jan 28 08:46:23 2006 X-Original-To: majordomo-users@greatcircle.com Received: from cloud.ccsf.cc.ca.us (cloud.ccsf.cc.ca.us [147.144.1.212]) by mycroft.greatcircle.com (Postfix) with ESMTP id E7F3D32C225 for ; Sat, 28 Jan 2006 08:46:22 -0800 (PST) Received: from localhost (jjah@localhost) by cloud.ccsf.cc.ca.us (8.11.6/8.11.2) with ESMTP id k0SGkIQ17482; Sat, 28 Jan 2006 08:46:19 -0800 (PST) Date: Sat, 28 Jan 2006 08:46:18 -0800 (PST) From: "Joe R. Jah" To: Luciano Cc: "majordomo-users@greatcircle.com" Subject: Re: Majordomo configuration In-Reply-To: <20060128153928.2F21F50765@smtp20.libero.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200601/39 X-Sequence-Number: 5295 On Sat, 28 Jan 2006, Luciano wrote: > Date: Sat, 28 Jan 2006 16:39:26 +0100 > From: Luciano > To: "majordomo-users@greatcircle.com" > Subject: Majordomo configuration > > I have opened a newsletter through our provider which exploits Majordomo. > I have to modify the welcome message that arrives to a new member, by replacing the message of default. > I have just sent the message of "intro" using "newintro newsletter" and the other message of "info" making use of "newinfo newsletter", and then with the appropriate controls i have ckecked (controllare) that my messages had been changed. > Although this, a new member receive a welcome message with the messagge of default in addition to my message "intro". > > How can I avoid the message of default? See ftp://ftp.ccsf.org/majordomo-patches/1.94.5/majordomo.7 # This patch will fix a bug in majordomo dealing with .intro file. # The patched majordomo will send only the contents of .intro file # if one exists, without prepending the standard majordomo greeting. # # To apply the patch: # # - Save the patch to a file on your Majordomo server. # - Login as Majordomo user, (e.g. majordom.) # - In Majordomo home run the following command: # # patch < /path/to/majordomo.7 > thank you for the attention > Luciano Regards, Joe -- _/ _/_/_/ _/ ____________ __o _/ _/ _/ _/ ______________ _-\<,_ _/ _/ _/_/_/ _/ _/ ......(_)/ (_) _/_/ oe _/ _/. _/_/ ah jjah@cloud.ccsf.cc.ca.us From majordomo-users-owner@greatcircle.com Sun Jan 29 15:02:25 2006 X-Original-To: majordomo-users@greatcircle.com Received: from smtp20.libero.it (smtp20.libero.it [193.70.192.147]) by mycroft.greatcircle.com (Postfix) with ESMTP id 3A4E932C15A for ; Sun, 29 Jan 2006 15:02:24 -0800 (PST) Received: from localhost (172.16.1.8) by smtp20.libero.it (7.0.027-DD01) id 439D916F03A62996; Mon, 30 Jan 2006 00:02:15 +0100 Received: from smtp0.libero.it ([172.16.1.76]) by localhost (asav9.libero.it [193.70.192.87]) (amavisd-new, port 10024) with ESMTP id 14064-07; Mon, 30 Jan 2006 00:02:14 +0100 (CET) Received: from luciopc (adsl-ull-7-149.41-151.net24.it [151.41.149.7]) by smtp0.libero.it (Postfix) with SMTP id 6E33E333866; Mon, 30 Jan 2006 00:02:14 +0100 (MET) Date: Mon, 30 Jan 2006 0:2:12 +0100 From: "Luciano" To: Joe R.Jah Cc: majordomo-users@greatcircle.com Subject: Re: Majordomo configuration X-mailer: Foxmail 4.1 [it] Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <20060129230214.6E33E333866@smtp0.libero.it> X-Scanned: with antispam and antivirus automated system at libero.it X-Archive-Number: 200601/40 X-Sequence-Number: 5296 >See ftp://ftp.ccsf.org/majordomo-patches/1.94.5/majordomo.7 > ># This patch will fix a bug in majordomo dealing with .intro file. ># The patched majordomo will send only the contents of .intro file ># if one exists, without prepending the standard majordomo greeting. ># ># To apply the patch: ># ># - Save the patch to a file on your Majordomo server. ># - Login as Majordomo user, (e.g. majordom.) ># - In Majordomo home run the following command: ># ># patch < /path/to/majordomo.7 > >> thank you for the attention >> Luciano > >Regards, > >Joe >-- > _/ _/_/_/ _/ ____________ __o > _/ _/ _/ _/ ______________ _-\<,_ > _/ _/ _/_/_/ _/ _/ ......(_)/ (_) > _/_/ oe _/ _/. _/_/ ah jjah@cloud.ccsf.cc.ca.us Thank you for the precious suggestion! Unfortunately, i'm not indipendent in doing this patch but i must contact my provider, where is installed Majordomo. However at least i know that it isn't a problem of configuration. Regards, Luciano From majordomo-users-owner@greatcircle.com Sun Jan 29 16:50:04 2006 X-Original-To: majordomo-users@greatcircle.com Received: from moroni.ourldsfamily.com (ourldsfamily.com [198.60.114.90]) by mycroft.greatcircle.com (Postfix) with ESMTP id B778232C177 for ; Sun, 29 Jan 2006 16:50:01 -0800 (PST) Received: from webmail.ourldsfamily.com (eth1 [172.20.20.2]) by moroni.ourldsfamily.com (8.12.5/8.12.5) with ESMTP id k0U0o0kk006407 for ; Sun, 29 Jan 2006 17:50:01 -0700 Received: from ourldsfamily.com ([198.60.114.90]) (SquirrelMail authenticated user karlp) by webmail.ourldsfamily.com with HTTP; Sun, 29 Jan 2006 17:50:01 -0700 (MST) Message-ID: <17403.198.60.114.90.1138582201.squirrel@webmail.ourldsfamily.com> In-Reply-To: <13844.198.60.114.90.1136682859.squirrel@webmail.ourldsfamily.com> References: <36499.207.173.117.242.1136564996.squirrel@ourldsfamily.com> <43C04426.1070004@sonny.org> <13844.198.60.114.90.1136682859.squirrel@webmail.ourldsfamily.com> Date: Sun, 29 Jan 2006 17:50:01 -0700 (MST) Subject: Re: Digests Are Broken From: karlp@ourldsfamily.com To: majordomo-users@greatcircle.com User-Agent: SquirrelMail/1.4.4-rc1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Archive-Number: 200601/41 X-Sequence-Number: 5297 I've monitoored my digest lists (about 50 of them) since applying the fix you recommended. It worked!!! Thanks Dan. Karl On Sat, January 7, 2006 6:14 pm, karlp@ourldsfamily.com said: > Thanks Dan. I've added it and will watch. > > Karl > > On Sat, January 7, 2006 3:43 pm, Daniel Liston said: >> >> Under certain conditions, all the files in the digest_work_dir may not >> be used/removed from the directory. Adding sort to the @files arg on >> line 176 of digest solves the problem. >> >> foreach (sort @files) { >> >> Dan Liston >> >> >> karlp@ourldsfamily.com wrote: >>> Majordomo 1.94.5 >>> >>> I've noticed, because of a complaint, that the digest groups on my >>> server >>> are inconsistent in their delivery of digest emails. >>> >>> I've instituted a cron that does mkdigest on the offending lists. I've >>> compared the config files for both the regular list and the digest list >>> and can't seem to see anything. >>> >>> Is there a known issue with digests? I've been on the digest version of >>> majordomo-users for a while and just switched back. I noticed that the >>> delivery of my email for this list was apparently missing emails, too. >>> >>> Thanks for any help, hints, etc. you can give. >>> >> > > > -- > karl > _/ _/ _/ _/_/_/ ____________ __o > _/ _/ _/ _/ _/ ____________ _-\<._ > _/_/ _/ _/_/_/ (_)/ (_) > _/ _/ _/ _/ ...................... > _/ _/ arl _/_/_/ _/ earson KarlP@ourldsfamily.com > --- > Senior Consulting Sys/DB Analyst > http://consulting.ourldsfamily.com > --- > My Thoughts on Terrorism In America: > http://www.ourldsfamily.com/wtc.shtml > --- > A right is not what someone gives you; it's what no one can take from > you. > -Ramsey Clark > --- > > -- karl _/ _/ _/ _/_/_/ ____________ __o _/ _/ _/ _/ _/ ____________ _-\<._ _/_/ _/ _/_/_/ (_)/ (_) _/ _/ _/ _/ ...................... _/ _/ arl _/_/_/ _/ earson KarlP@ourldsfamily.com --- Senior Consulting Sys/DB Analyst http://consulting.ourldsfamily.com --- My Thoughts on Terrorism In America: http://www.ourldsfamily.com/wtc.shtml --- A right is not what someone gives you; it's what no one can take from you. -Ramsey Clark --- From majordomo-users-owner@greatcircle.com Mon Jan 30 15:38:03 2006 X-Original-To: majordomo-users@greatcircle.com Received: from maja.humerca.com (mail.humerca.com [86.61.74.181]) by mycroft.greatcircle.com (Postfix) with ESMTP id F30BA32C155 for ; Mon, 30 Jan 2006 15:37:59 -0800 (PST) Received: from localhost (localhost.localdomain [127.0.0.1]) by maja.humerca.com (Postfix) with ESMTP id 50596100E7 for ; Tue, 31 Jan 2006 00:37:58 +0100 (CET) Received: from maja.humerca.com ([127.0.0.1]) by localhost (maja.humerca.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19638-04 for ; Tue, 31 Jan 2006 00:37:55 +0100 (CET) Received: from [192.168.0.3] (bigk.humerca [192.168.0.3]) by maja.humerca.com (Postfix) with ESMTP id ACD2F100B5 for ; Tue, 31 Jan 2006 00:37:55 +0100 (CET) Message-ID: <43DEA354.3060208@humerca.com> Date: Tue, 31 Jan 2006 00:37:56 +0100 From: Klemen Humerca Reply-To: klemen@humerca.com Organization: Klemen Humerca User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: member list file Content-Type: text/plain; charset=windows-1250; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at humerca.com X-Archive-Number: 200601/42 X-Sequence-Number: 5298 Hello. I'm trying to make a "member list" for a (some) list to have different ownership than majordomo:majordomo. I've made a sym link to a file with addresses. File is created with php, that means owner is apache:apache. When I try to send email to the list, i get tis error: : cannot open include file /var/lib/majordomo/lists/posta: Permission denied My MTU is Postfix. If I chnage group to majordomo I still get this error, but if I change ownershipt to majordomo:majordom everything is ok. So how can I make majordomo/postfix to send mails if majordomo is not the owner of "member list" file? -- Klemen Humerca -----e-mail&web--------- klemen@humerca.com forum.humerca.com ------------------------ From majordomo-users-owner@greatcircle.com Tue Jan 31 07:43:17 2006 X-Original-To: Majordomo-Users@GreatCircle.COM Received: from hermes.jjbedmonton.com (unknown [209.148.223.55]) by mycroft.greatcircle.com (Postfix) with ESMTP id D33BE32C1A8 for ; Tue, 31 Jan 2006 07:43:09 -0800 (PST) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6267D.0A84A94D" Subject: One Sticky Point X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Tue, 31 Jan 2006 08:43:22 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: One Sticky Point Thread-index: AcYmfREXS3bvqud/QvqGac6UZiHIgA== From: "Daniel Kaliel" To: X-Archive-Number: 200601/43 X-Sequence-Number: 5299 This is a multi-part message in MIME format. ------_=_NextPart_001_01C6267D.0A84A94D Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable We have an exchange server running but it does not do lists nearly as well as Majordomo. So I installed linux / majordomo / postfix on a box and got them working. Here is what I do not know. Is it possible to have the linux server running in the same domain as the exchange? I can't figure out how emails would ever arrive at the linux box with exchange as the primary mx. So if I am right on that, I believe I may need to setup another domain like and make the majordomo server the primary mx for that domain then send emails to mylist@lists.mydomain.com. =20 Is my thought process correct here? ------_=_NextPart_001_01C6267D.0A84A94D Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
We have a= n exchange=20 server running but it does not do lists nearly as well as Majordomo.  = So I=20 installed linux / majordomo / postfix on a box and got them working.&n= bsp;=20 Here is what I do not know.  Is it possible to have the linux server= =20 running in the same domain as the exchange?  I can't figure out how em= ails=20 would ever arrive at the linux box with exchange as the primary mx.  S= o if=20 I am right on that, I believe I may need to setup another domain like=20 <lists.mydomain.com> and make the majordomo server the primary mx for= that=20 domain then send emails to mylist@lists.mydomain.com.
 
Is my tho= ught=20 process correct here?
------_=_NextPart_001_01C6267D.0A84A94D-- From majordomo-users-owner@greatcircle.com Tue Jan 31 16:00:07 2006 X-Original-To: majordomo-users@greatcircle.com Received: from hermes.jjbedmonton.com (unknown [209.148.223.55]) by mycroft.greatcircle.com (Postfix) with ESMTP id 4791032C1F4 for ; Tue, 31 Jan 2006 16:00:06 -0800 (PST) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C626C2.74798730" Subject: Around in Circles X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Tue, 31 Jan 2006 16:59:26 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Around in Circles Thread-index: AcYmwl35iZF6SqEnSjm/07Sda9Noew== From: "Daniel Kaliel" To: X-Archive-Number: 200601/44 X-Sequence-Number: 5300 This is a multi-part message in MIME format. ------_=_NextPart_001_01C626C2.74798730 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Here is the setup =20 the mx belongs to our exchange server =20 the mx belongs to our postfix / majordomo server =20 When I send an email to the test list, which contains one email address me@= mydomain.com =20 I get the following bounced message. =20 < myserver.lists.mydomain.com #5.0.0 X-Postfix; mail for lists.jjbedmonton.= com loops back to myself> =20 I find this odd since the emails on the list, do not contain the domain me@= lists.mydomain.com any ideas? ------_=_NextPart_001_01C626C2.74798730 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Here is the setup
 
<mydomain.com> the mx belongs to our= exchange=20 server
 
<lists.mydomain.com> the mx belongs = to our=20 postfix / majordomo server
 
When I send an email to the test list, whi= ch=20 contains one email address me@mydomain.com
 
I get the following bounced message.
 
< myserver.lists.mydomain.com #5.0.0 X-Postfix; mail for=20 lists.jjbedmonton.com loops back to myself>
 
I find this odd since the emails on the list, do not contain the domai= n me@lists.mydomain.com  any= =20 ideas?
------_=_NextPart_001_01C626C2.74798730--