Date: Sat, 07 Jul 2001 19:11:17 -0500 From: Jon Loeliger <jdl@jdl.com> To: questions@freebsd.org Subject: Majordomo Hacking? Message-ID: <200107080011.TAA04036@chrome.jdl.com>
next in thread | raw e-mail | index | archive | help
Hi Folks,
So, I turn to the collected knowledge of the FreeBSD team again.
I've Googled around the net and Majordomo sites looking for
any insight into what I suspect is an attempted Majordomo-based
mail-redelivery, spamming or hacking effort. I've not been able
to find anything that describes what I am seeing, or discusses
a Majordomo exploit.
I run both jdl.com and UncommonCon.com.
UncommonCon.com looks like:
FreeBSD www.uncommoncon.com 4.2-RELEASE FreeBSD 4.2-RELEASE #0:
Mon Nov 20 13:02:55 GMT 2000
jkh@bento.FreeBSD.org:/usr/src/sys/compile/GENERIC i386
and
www 550 # exim -bV
Exim version 3.16 #1 built 26-Mar-2001 19:54:13
Copyright (c) University of Cambridge 2000
and
# $Header: /sources/cvsrepos/majordomo/majordomo_version.pl,v
1.28 2000/01/18 13:28:07 cwilson Exp $
$majordomo_version = "1.94.5";
Here's what I think is happening:
Someone sends a message that looks sort of like base64 encoding
to majordomo@uncommoncon.com. Majordomo tries to interpret
all that junk as commands, and fails a lot. Somehow, some
m636614464@hotmail.com address ends up being the recipient
and fails to get delivered. It bounces back to Majordomo,
where I get it as the sorry sysadmin. It then gets forwarded
to me at jdl.com where I'm reading things.
Mystery questions:
How does m636614464@hotmail.com end up a recipient?
Who's doing this, and how can I knee-cap them?
So I'm trying desperately not to be an open relay, of course.
Here's what exim says around 08:00 this morning:
2001-07-07 08:02:46 15IrjO-000AmG-00 <= m636614464@hotmail.com H=(server.hwanan) [210.61.154.243] P=esmtp S=3933
2001-07-07 08:02:47 15IrjT-000AmN-00 <= Majordomo-Owner@www.uncommoncon.com U=majordom P=local S=17304
2001-07-07 08:02:47 15IrjO-000AmG-00 => |/usr/local/majordomo/wrapper majordomo <majordomo@uncommoncon.com> D=majordomo_aliases T=address_pipe
2001-07-07 08:02:47 15IrjO-000AmG-00 Completed
2001-07-07 08:02:48 15IrjT-000AmN-00 ** m636614464@hotmail.com R=lookuphost T=remote_smtp: SMTP error from remote mailer after RCPT TO:<m636614464@hotmail.com>: host mc2.law5.hotmail.com [64.4.55.135]: 550 Requested action not taken: mailbox unavailable
2001-07-07 08:02:48 15IrjU-000AmP-00 <= <> R=15IrjT-000AmN-00 U=root P=local S=18301
2001-07-07 08:02:48 15IrjT-000AmN-00 Error message sent to Majordomo-Owner@www.uncommoncon.com
2001-07-07 08:02:48 15IrjT-000AmN-00 Completed
2001-07-07 08:02:48 15IrjU-000AmP-00 => jdl@jdl.com <Majordomo-Owner@www.uncommoncon.com> R=lookuphost T=remote_smtp H=chrome.jdl.com [209.39.144.2]
2001-07-07 08:02:48 15IrjU-000AmP-00 Completed
So, is 210.61.154.243 the real perpetrator here?
Should I just add them to my host_reject_recipients and never hear
from them again?!
Any insight greatly appreciated!
jdl
------- Forwarded Message
Return-Path: MAILER-DAEMON
Received: from www.uncommoncon.com (www.uncommoncon.com [209.39.144.8])
by chrome.jdl.com (8.9.1/8.9.1) with ESMTP id IAA03367
for <jdl@jdl.com>; Sat, 7 Jul 2001 08:11:46 -0500 (CDT)
(envelope-from )
Received: from root by www.uncommoncon.com with local (Exim 3.16 #1)
id 15IrjU-000AmP-00
for Majordomo-Owner@www.uncommoncon.com; Sat, 07 Jul 2001 08:02:48 -0500
X-Failed-Recipients: m636614464@hotmail.com
From: Mail Delivery System <Mailer-Daemon@uncommoncon.com>
To: Majordomo-Owner@uncommoncon.com
Subject: Mail delivery failed: returning message to sender
Message-Id: <E15IrjU-000AmP-00@www.uncommoncon.com>
Date: Sat, 07 Jul 2001 08:02:48 -0500
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
m636614464@hotmail.com:
SMTP error from remote mailer after RCPT TO:<m636614464@hotmail.com>:
host mc2.law5.hotmail.com [64.4.55.135]:
550 Requested action not taken:
mailbox unavailable
- ------ This is a copy of the message, including all the headers. ------
Return-path: <Majordomo-Owner@www.uncommoncon.com>
Received: from majordom by www.uncommoncon.com with local (Exim 3.16 #1)
id 15IrjT-000AmN-00
for m636614464@hotmail.com; Sat, 07 Jul 2001 08:02:47 -0500
To: m636614464@hotmail.com
From: majordomo@www.uncommoncon.com
Subject: Majordomo results: 亞迪DVD讓您血脈噴張！．．．．．亞迪DVD讓
Reply-To: majordomo@www.uncommoncon.com
Message-Id: <E15IrjT-000AmN-00@www.uncommoncon.com>
Date: Sat, 07 Jul 2001 08:02:47 -0500
- --
>>>> PGh0bWw+DQoNCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250
**** Command 'pgh0bww+dqoncjxozwfkpg0kpg1ldgegahr0cc1lcxvpdj0iq29udgvudc1uexbli
ibjb250' not recognized.
>>>> ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9YmlnNSI+DQo8dGl0bGU+qMitfWR2ZLBUrqc8L3Rp
**** Command 'zw50psj0zxh0l2h0bww7ignoyxjzzxq9ymlnnsi+dqo8dgl0bgu+qmitfwr2zlbur
qc8l3rp' not recognized.
>>>> dGxlPg0KPG1ldGEgbmFtZT0iR0VORVJBVE9SIiBjb250ZW50PSJNaWNyb3NvZnQgRnJvbnRQ
**** Command 'dgxlpg0kpg1ldgegbmftzt0ir0vorvjbve9siibjb250zw50psjnawnyb3nvznqgr
njvbnrq' not recognized.
>>>> YWdlIDMuMCI+DQo8L2hlYWQ+DQoNCjxib2R5IGJnY29sb3I9IiMwMDVBODciPg0KPGRpdiBh
**** Command 'ywdlidmumci+dqo8l2hlywq+dqoncjxib2r5igjny29sb3i9iimwmdvbodcipg0kp
grpdibh' not recognized.
>>>> bGlnbj0iY2VudGVyIj48Y2VudGVyPg0KDQo8dGFibGUgYm9yZGVyPSIwIiB3aWR0aD0iNDkl
**** Command 'bglnbj0iy2vudgvyij48y2vudgvypg0kdqo8dgfibgugym9yzgvypsiwiib3awr0a
d0indkl' not recognized.
>>>> IiBjZWxsc3BhY2luZz0iMCIgY2VsbHBhZGRpbmc9IjAiPg0KICA8dHI+DQogICAgPHRkIHdp
**** Command 'iibjzwxsc3bhy2luzz0imcigy2vsbhbhzgrpbmc9ijaipg0kica8dhi+dqogicagp
hrkihdp' not recognized.
>>>> ZHRoPSIxMDAlIj48IS0td2ViYm90IGJvdD0iSW1hZ2VNYXAiIHN0YXJ0c3Bhbg0KICAgIHJl
**** Command 'zhropsixmdalij48is0td2viym90igjvdd0isw1hz2vnyxaiihn0yxj0c3bhbg0ki
cagihjl' not recognized.
>>>> Y3RhbmdsZT0iICgzLDUpICg0NzEsIDE5NikgIGh0dHA6Ly93d3cuZ2VvY2l0aWVzLmNvbS9s
**** Command 'y3rhbmdszt0iicgzldupicg0nzeside5nikgigh0dha6ly93d3cuz2vvy2l0awvzl
mnvbs9s' not recognized.
>>>> dWZsdWluMzQyIiBzcmM9Imh0dHA6Ly9ob21lLnBjaG9tZS5jb20udHcvY2xpY2svbW9kbHVz
**** Command 'dwzsdwlumzqyiibzcmm9imh0dha6ly9ob21llnbjag9tzs5jb20udhcvy2xpy2svb
w9kbhvz' not recognized.
>>>> c2FhL21haWx0b3AuZ2lmIiB3aWR0aD0iNDcyIg0KICAgIGhlaWdodD0iMTk3IiBhbHQ9IqjI
**** Command 'c2fhl21hawx0b3auz2lmiib3awr0ad0indcyig0kicagighlawdodd0imtk3iibhb
hq9iqji' not recognized.
>>>> rX1kdmS69K+4IiBib3JkZXI9IjAiIC0tPjxNQVAgTkFNRT0iRnJvbnRQYWdlTWFwMCI+PEFS
**** Command 'rx1kdms69k+4iibib3jkzxi9ijaiic0tpjxnqvagtkfnrt0irnjvbnrqywdltwfwm
ci+pefs' not recognized.
>>>> RUEgU0hBUEU9IlJFQ1QiIENPT1JEUz0iMywgNSwgNDcxLCAxOTYiIEhSRUY9Imh0dHA6Ly93
**** Command 'ruegu0hbueu9iljfq1qiienpt1jeuz0imywgnswgndcxlcaxotyiiehsruy9imh0d
ha6ly93' not recognized.
>>>> d3cuZ2VvY2l0aWVzLmNvbS9sdWZsdWluMzQyIj48L01BUD48aW1nIHNyYz0iaHR0cDovL2hv
**** Command 'd3cuz2vvy2l0awvzlmnvbs9sdwzsdwlumzqyij48l01bud48aw1nihnyyz0iahr0c
dovl2hv' not recognized.
>>>> bWUucGNob21lLmNvbS50dy9jbGljay9tb2RsdXNzYWEvbWFpbHRvcC5naWYiIHdpZHRoPSI0
**** Command 'bwuucgnob21llmnvbs50dy9jbgljay9tb2rsdxnzywevbwfpbhrvcc5nawyiihdpz
hropsi0' not recognized.
>>>> NzIiIGhlaWdodD0iMTk3IiBhbHQ9IqjIrX1kdmS69K+4IiBib3JkZXI9IjAiIHVzZW1hcD0i
**** Command 'nziiighlawdodd0imtk3iibhbhq9iqjirx1kdms69k+4iibib3jkzxi9ijaiihvzz
w1hcd0i' not recognized.
>>>> I0Zyb250UGFnZU1hcDAiPjwhLS13ZWJib3QgYm90PSJJbWFnZU1hcCINCiAgICBpLWNoZWNr
**** Command 'i0zyb250ugfnzu1hcdaipjwhls13zwjib3qgym90psjjbwfnzu1hccinciagicbpl
wnozwnr' not recognized.
>>>> c3VtPSIyOTg4NiIgZW5kc3BhbiAtLT48L3RkPg0KICA8L3RyPg0KICA8dHI+DQogICAgPHRk
**** Command 'c3vtpsiyotg4niigzw5kc3bhbiatlt48l3rkpg0kica8l3rypg0kica8dhi+dqogi
cagphrk' not recognized.
>>>> IHdpZHRoPSIxMDAlIj48IS0td2ViYm90IGJvdD0iSW1hZ2VNYXAiIHN0YXJ0c3Bhbg0KICAg
**** Command 'ihdpzhropsixmdalij48is0td2viym90igjvdd0isw1hz2vnyxaiihn0yxj0c3bhb
g0kicag' not recognized.
>>>> IHJlY3RhbmdsZT0iICgyODIsMikgKDQ3MSwgNjkpICBodHRwOi8vd3d3Lmdlb2NpdGllcy5j
**** Command 'ihjly3rhbmdszt0iicgyodismikgkdq3mswgnjkpicbodhrwoi8vd3d3lmdlb2npd
gllcy5j' not recognized.
>>>> b20vbHVmbHVpbjM0MiIgc3JjPSJodHRwOi8vaG9tZS5wY2hvbWUuY29tLnR3L2NsaWNrL21v
**** Command 'b20vbhvmbhvpbjm0miigc3jjpsjodhrwoi8vag9tzs5wy2hvbwuuy29tlnr3l2nsa
wnrl21v' not recognized.
>>>> ZGx1c3NhYS9tYWlsZG93bi5naWYiIHdpZHRoPSI0NzIiDQogICAgaGVpZ2h0PSI3MCIgYWx0
**** Command 'zgx1c3nhys9tywlszg93bi5nawyiihdpzhropsi0nziidqogicagagvpz2h0psi3m
cigywx0' not recognized.
>>>> PSJtYWlsZG93bi5naWYgKDY4MDIgYnl0ZXMpIiBib3JkZXI9IjAiIC0tPjxNQVAgTkFNRT0i
**** Command 'psjtywlszg93bi5nawygkdy4mdigynl0zxmpiibib3jkzxi9ijaiic0tpjxnqvagt
kfnrt0i' not recognized.
>>>> RnJvbnRQYWdlTWFwMSI+PEFSRUEgU0hBUEU9IlJFQ1QiIENPT1JEUz0iMjgyLCAyLCA0NzEs
**** Command 'rnjvbnrqywdltwfwmsi+pefsruegu0hbueu9iljfq1qiienpt1jeuz0imjgylcayl
ca0nzes' not recognized.
>>>> IDY5IiBIUkVGPSJodHRwOi8vd3d3Lmdlb2NpdGllcy5jb20vbHVmbHVpbjM0MiI+PC9NQVA+
**** Command 'idy5iibiukvgpsjodhrwoi8vd3d3lmdlb2npdgllcy5jb20vbhvmbhvpbjm0mii+p
c9nqva+' not recognized.
>>>> PGltZyBzcmM9Imh0dHA6Ly9ob21lLnBjaG9tZS5jb20udHcvY2xpY2svbW9kbHVzc2FhL21h
**** Command 'pgltzybzcmm9imh0dha6ly9ob21llnbjag9tzs5jb20udhcvy2xpy2svbw9kbhvzc
2fhl21h' not recognized.
>>>> aWxkb3duLmdpZiIgd2lkdGg9IjQ3MiIgaGVpZ2h0PSI3MCIgYWx0PSJtYWlsZG93bi5naWYg
**** Command 'awxkb3dulmdpziigd2lkdgg9ijq3miigagvpz2h0psi3mcigywx0psjtywlszg93b
i5nawyg' not recognized.
>>>> KDY4MDIgYnl0ZXMpIiBib3JkZXI9IjAiIHVzZW1hcD0iI0Zyb250UGFnZU1hcDEiPjwhLS13
**** Command 'kdy4mdigynl0zxmpiibib3jkzxi9ijaiihvzzw1hcd0ii0zyb250ugfnzu1hcdeip
jwhls13' not recognized.
>>>> ZWJib3QgYm90PSJJbWFnZU1hcCINCiAgICBpLWNoZWNrc3VtPSIzMzc4NyIgZW5kc3BhbiAt
**** Command 'zwjib3qgym90psjjbwfnzu1hccinciagicbplwnozwnrc3vtpsizmzc4nyigzw5kc
3bhbiat' not recognized.
>>>> LT48L3RkPg0KICA8L3RyPg0KICA8dHI+DQogICAgIDx0ZCB3aWR0aD0iMTAwJSIgYWxpZ249
**** Command 'lt48l3rkpg0kica8l3rypg0kica8dhi+dqogicagidx0zcb3awr0ad0imtawjsigy
wxpz249' not recognized.
>>>> ImNlbnRlciI+PHAgYWxpZ249ImNlbnRlciI+PGZvbnQgY29sb3I9IiNmZmZmZmYiPqW7r7il
**** Command 'imnlbnrlcii+phagywxpz249imnlbnrlcii+pgzvbnqgy29sb3i9iinmzmzmzmyip
qw7r7il' not recognized.
>>>> w6RbuvSnfaFHPHN0cm9uZz5odHRwOi8vZHZkOTkudHcuc3Q8L3N0cm9uZz48L2ZvbnQ+PC90
**** Command 'w6rbuvsnfafhphn0cm9uzz5odhrwoi8vzhzkotkudhcuc3q8l3n0cm9uzz48l2zvb
nq+pc90' not recognized.
>>>> ZD4NCiAgPC90cj4NCiAgPHRyPg0KICAgIDx0ZCB3aWR0aD0iMTAwJSIgYWxpZ249ImNlbnRl
**** Command 'zd4nciagpc90cj4nciagphrypg0kicagidx0zcb3awr0ad0imtawjsigywxpz249i
mnlbnrl' not recognized.
>>>> ciI+PHAgYWxpZ249ImNlbnRlciI+PGZvbnQgY29sb3I9IiM3NUQyRkYiPjxicj4NCiAgICCt
**** Command 'cii+phagywxpz249imnlbnrlcii+pgzvbnqgy29sb3i9iim3nuqyrkyipjxicj4nc
iagicct' not recognized.
>>>> sLv5sNWhbafzt3OuybahoUcyMDAxpn4wN6TrMDak6aFurbC7+bDVPC9mb250PjwvdGQ+DQog
**** Command 'slv5snwhbafzt3ouybahoucymdaxpn4wn6trmdak6afurbc7+bdvpc9mb250pjwvd
gq+dqog' not recognized.
>>>> IDwvdHI+DQo8L3RhYmxlPg0KPC9jZW50ZXI+PC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DTxI
**** Command 'idwvdhi+dqo8l3rhymxlpg0kpc9jzw50zxi+pc9kaxy+dqo8l2jvzhk+dqo8l2h0b
ww+dtxi' not recognized.
>>>> VE1MPg0KPEEgbmFtZT0iDQqoyK19RFZEDQpQTSAwMTo1NDo0NQ0KMjAwMS83LzcNCjEwMDAw
**** Command 've1mpg0kpeegbmftzt0idqqoyk19rfzedqpqtsawmto1ndo0nq0kmjawms83lzcnc
jewmdaw' not recognized.
>>>> Mw0KIj48L2E+DQo8L0hUTUw+DTxIVE1MPg0KPEEgbmFtZT0iDQqoyK19RFZEDQpQTSAwMjow
**** Command 'mw0kij48l2e+dqo8l0hutuw+dtxive1mpg0kpeegbmftzt0idqqoyk19rfzedqpqt
sawmjow' not recognized.
>>>> NjoyOQ0KMjAwMS83LzcNCjEwMDAwMw0KIj48L2E+DQo8L0hUTUw+DTxIVE1MPg0KPEEgbmFt
**** Command 'njoyoq0kmjawms83lzcncjewmdawmw0kij48l2e+dqo8l0hutuw+dtxive1mpg0kp
eegbmft' not recognized.
>>>> ZT0iDQqoyK19RFZExf2xeqblr9+8UbFpoUmhRKFEoUShRKFEqMitfQ0KUE0gMDI6MTU6MDMN
**** Command 'zt0idqqoyk19rfzexf2xeqblr9+8ubfpoumhrkfeoushrkfeqmitfq0kue0gmdi6m
tu6mdmn' not recognized.
>>>> CjIwMDEvNy83DQoxMDAwMDMNCiI+PC9hPg0KPC9IVE1MPg08SFRNTD4NCjxBIG5hbWU9Ig0K
**** Command 'cjiwmdevny83dqoxmdawmdmncii+pc9hpg0kpc9ive1mpg08sfrntd4ncjxbig5hb
wu9ig0k' not recognized.
>>>> qMitfURWRMX9sXqm5a/fvFGxaaFJoUShRKFEoUShRKFEoUShRKFEqMitfQ0KUE0gMDI6MjI6
**** Command 'qmitfurwrmx9sxqm5a/fvfgxaafjoushrkfeoushrkfeoushrkfeqmitfq0kue0gm
di6mji6' not recognized.
>>>> NTcNCjIwMDEvNy83DQoxMDAwMDMNCiI+PC9hPg0KPC9IVE1MPg08SFRNTD4NCjxBIG5hbWU9
**** Command 'ntcncjiwmdevny83dqoxmdawmdmncii+pc9hpg0kpc9ive1mpg08sfrntd4ncjxbi
g5hbwu9' not recognized.
>>>> Ig0KqMitfURWRMX9sXqm5a/fvFGxaaFJoUShRKFEoUSoyK19RFZEDQpQTSAwOToxNTozMg0K
**** Command 'ig0kqmitfurwrmx9sxqm5a/fvfgxaafjoushrkfeousoyk19rfzedqpqtsawotoxn
tozmg0k' not recognized.
>>>> MjAwMS83LzcNCjEwMDAwMw0KIj48L2E+DQo8L0hUTUw+DQo=
**** Command 'mjawms83lzcncjewmdawmw0kij48l2e+dqo8l0hutuw+dqo=' not recognized.
>>>>
>>>>
**** No valid commands found.
**** Commands must be in message BODY, not in HEADER.
**** Help for majordomo@www.uncommoncon.com:
This help message is being sent to you from the Majordomo mailing list
management system at majordomo@www.uncommoncon.com.
This is version 1.94.5 of Majordomo.
If you're familiar with mail servers, an advanced user's summary of
Majordomo's commands appears at the end of this message.
Majordomo is an automated system which allows users to subscribe
and unsubscribe to mailing lists, and to retrieve files from list
archives.
You can interact with the Majordomo software by sending it commands
in the body of mail messages addressed to "majordomo@www.uncommoncon.com".
Please do not put your commands on the subject line; Majordomo does
not process commands in the subject line.
You may put multiple Majordomo commands in the same mail message.
Put each command on a line by itself.
If you use a "signature block" at the end of your mail, Majordomo may
mistakenly believe each line of your message is a command; you will
then receive spurious error messages. To keep this from happening,
either put a line starting with a hyphen ("-") before your signature,
or put a line with just the word
end
on it in the same place. This will stop the Majordomo software from
processing your signature as bad commands.
Here are some of the things you can do using Majordomo:
I. FINDING OUT WHICH LISTS ARE ON THIS SYSTEM
To get a list of publicly-available mailing lists on this system, put the
following line in the body of your mail message to majordomo@www.uncommoncon.co
m:
lists
Each line will contain the name of a mailing list and a brief description
of the list.
To get more information about a particular list, use the "info" command,
supplying the name of the list. For example, if the name of the list
about which you wish information is "demo-list", you would put the line
info demo-list
in the body of the mail message.
II. SUBSCRIBING TO A LIST
Once you've determined that you wish to subscribe to one or more lists on
this system, you can send commands to Majordomo to have it add you to the
list, so you can begin receiving mailings.
To receive list mail at the address from which you're sending your mail,
simply say "subscribe" followed by the list's name:
subscribe demo-list
If for some reason you wish to have the mailings go to a different address
(a friend's address, a specific other system on which you have an account,
or an address which is more correct than the one that automatically appears
in the "From:" header on the mail you send), you would add that address to
the command. For instance, if you're sending a request from your work
account, but wish to receive "demo-list" mail at your personal account
(for which we will use "jqpublic@my-isp.com" as an example), you'd put
the line
subscribe demo-list jqpublic@my-isp.com
in the mail message body.
Based on configuration decisions made by the list owners, you may be added
to the mailing list automatically. You may also receive notification
that an authorization key is required for subscription. Another message
will be sent to the address to be subscribed (which may or may not be the
same as yours) containing the key, and directing the user to send a
command found in that message back to majordomo@www.uncommoncon.com. (This can
be
a bit of extra hassle, but it helps keep you from being swamped in extra
email by someone who forged requests from your address.) You may also
get a message that your subscription is being forwarded to the list owner
for approval; some lists have waiting lists, or policies about who may
subscribe. If your request is forwarded for approval, the list owner
should contact you soon after your request.
Upon subscribing, you should receive an introductory message, containing
list policies and features. Save this message for future reference; it
will also contain exact directions for unsubscribing. If you lose the
intro mail and would like another copy of the policies, send this message
to majordomo@www.uncommoncon.com:
intro demo-list
(substituting, of course, the real name of your list for "demo-list").
III. UNSUBSCRIBING FROM MAILING LISTS
Your original intro message contains the exact command which should be
used to remove your address from the list. However, in most cases, you
may simply send the command "unsubscribe" followed by the list name:
unsubscribe demo-list
(This command may fail if your provider has changed the way your
address is shown in your mail.)
To remove an address other than the one from which you're sending
the request, give that address in the command:
unsubscribe demo-list jqpublic@my-isp.com
In either of these cases, you can tell majordomo@www.uncommoncon.com to remove
the address in question from all lists on this server by using "*"
in place of the list name:
unsubscribe *
unsubscribe * jqpublic@my-isp.com
IV. FINDING THE LISTS TO WHICH AN ADDRESS IS SUBSCRIBED
To find the lists to which your address is subscribed, send this command
in the body of a mail message to majordomo@www.uncommoncon.com:
which
You can look for other addresses, or parts of an address, by specifying
the text for which Majordomo should search. For instance, to find which
users at my-isp.com are subscribed to which lists, you might send the
command
which my-isp.com
Note that many list owners completely or fully disable the "which"
command, considering it a privacy violation.
V. FINDING OUT WHO'S SUBSCRIBED TO A LIST
To get a list of the addresses on a particular list, you may use the
"who" command, followed by the name of the list:
who demo-list
Note that many list owners allow only a list's subscribers to use the
"who" command, or disable it completely, believing it to be a privacy
violation.
VI. RETRIEVING FILES FROM A LIST'S ARCHIVES
Many list owners keep archives of files associated with a list. These
may include:
- - back issues of the list
- - help files, user profiles, and other documents associated with the list
- - daily, monthly, or yearly archives for the list
To find out if a list has any files associated with it, use the "index"
command:
index demo-list
If you see files in which you're interested, you may retrieve them by
using the "get" command and specifying the list name and archive filename.
For instance, to retrieve the files called "profile.form" (presumably a
form to fill out with your profile) and "demo-list.9611" (presumably the
messages posted to the list in November 1996), you would put the lines
get demo-list profile.form
get demo-list demo-list.9611
in your mail to majordomo@www.uncommoncon.com.
VII. GETTING MORE HELP
To contact a human site manager, send mail to Majordomo-Owner@www.uncommoncon.c
om.
To contact the owner of a specific list, send mail to that list's
approval address, which is formed by adding "-approval" to the user-name
portion of the list's address. For instance, to contact the list owner
for demo-list@www.uncommoncon.com, you would send mail to demo-list-approval@ww
w.uncommoncon.com.
To get another copy of this help message, send mail to majordomo@www.uncommonco
n.com
with a line saying
help
in the message body.
VIII. COMMAND SUMMARY FOR ADVANCED USERS
In the description below items contained in []'s are optional. When
providing the item, do not include the []'s around it. Items in angle
brackets, such as <address>, are meta-symbols that should be replaced
by appropriate text without the angle brackets.
It understands the following commands:
subscribe <list> [<address>]
Subscribe yourself (or <address> if specified) to the named <list>.
unsubscribe <list> [<address>]
Unsubscribe yourself (or <address> if specified) from the named <list>.
"unsubscribe *" will remove you (or <address>) from all lists. This
_may not_ work if you have subscribed using multiple addresses.
get <list> <filename>
Get a file related to <list>.
index <list>
Return an index of files you can "get" for <list>.
which [<address>]
Find out which lists you (or <address> if specified) are on.
who <list>
Find out who is on the named <list>.
info <list>
Retrieve the general introductory information for the named <list>.
intro <list>
Retrieve the introductory message sent to new users. Non-subscribers
may not be able to retrieve this.
lists
Show the lists served by this Majordomo server.
help
Retrieve this message.
end
Stop processing commands (useful if your mailer adds a signature).
Commands should be sent in the body of an email message to
"majordomo@www.uncommoncon.com". Multiple commands can be processed provided
each occurs on a separate line.
Commands in the "Subject:" line are NOT processed.
If you have any questions or problems, please contact
"Majordomo-Owner@www.uncommoncon.com".
------- End of Forwarded Message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200107080011.TAA04036>