How can I customise the welcome message when people subscribe to the list, for each individual list I have on my server, i.e. having a different welcome message for each list. The subscribe.txt file is common to all lists, and when I change it, it sends the same message whatever the list is.
>I've wondered, if the addresses are properly formatted with RFC822
>comments, will they be handled correctly at distribution time?
>Seems like a reasonable assumption, and it would be very nice
>indeed to have those real names handy. But it's never gotten to
>the top of my priorities to poke through the code, or try a
>test case on my list.
>
>Maybe one of the experts can say for sure one way or the other.
Using my own web-based front end to manage the subscriptions to my lists,
I keep real names in my dist files, using the format
user(a)domain.com (real name)
It doesn't cause any problems at all. I don't remember if I ever tried
real name <user(a)domain.com>
but, knowing how choplist works, I think this format would work fine as
well.
The changes needed to the subscribe script and the multigram source
didn't look trivial, so I've never tried to get SmartList itself to put
real names in the dist file.
-cary
At 11:10 PM -0400 7/30/02, Gyan Penrose-Kafka is rumored to have typed:
> I looked at the log and I kept seeing: "formail: Duplicate key found: ..."
That implies your message is returning to the mailing list for a second
go-round. Sounds (on a guess, based on insufficient information) that the
address you subscribed is somehow externally being redirected back to the
list address. This would imply a problem outside SmartList, maybe in your
.procmailrc file.
Simple way to see if the message was "delivered" my SmartList is to check
for its existance in the listdir/archive/latest directory (assuming it isn't
a digested list, of course, although it'll be there in the digest.body file
if it is).
You're on a hosting service; is it fair to assume you are using a
.procmailrc file to direct mail to the list on a virtual account? Or are you
using some "control panel" supplied by your provider to direct the mail?
(This is a seperate thing from a control panel that _controls_
SmartList...I'm trying to get a handle on how you're getting the mail
delivered to the list, since your previous posts imply you aren't rooting the
box and so need to use some other method than the alias file.)
Ah...crap.
I'm almost certain I know _exactly_ why you're getting this problem, and
it's partially my fault. Nothing like spending a minute or two to go back
over the last month's postings and catch up on the thread, which I should
have done before I started typing.
A while back, I explained that you could use a .procmailrc file to direct
mail to your list on a virtual domain, like:
:0
* ^TOlistname(a)yourdomain.tld
|/full/path/to/SmartList/.bin/flist testing
...and that's absolutely correct. But let's use the hypothetical domain
mydomain.tld and the hypothetical list mylist and examine what's happening.
You have:
:0
* ^TO mylist(a)mydomain.tld
|/full/path/to/SmartList/.bin/flist mylist
...in your .procmnailrc file. Ok, so far, so good. Now I subscribe as
charlie(a)lofcom.com. I post, SmartLIst accepts the mail, and sends it off to
subscribers, including me. Cool.
Now you subscribe the address gyan(a)mydomain.tld to the list, and send a
message (or _I_ send a message, doesn't matter). The message comes in, is
seen to be to the list address, and is piped to flist. SmartList distributes
it to the subscribers, including gyan(a)mydomain.tld; that copy of the
distribution comes into your .procmailrc file, is seen to be to the LIST
ADDRESS, and is piped to flist...which recognizes that it's a duplicate.
Blame the fact that it's been a whole lot of years since I had to run
SmartList as a virtual user on a shared machine, and not anticipating that
you'd not realize subscribing an address on the same account was a Bad Idea.
If you're going to subscribe an email address on the same virtual domain (or
a parked domain that uses the same real unix account, for that matter),
you'll need to trap out for that condition using something like:
:0:
* ^X-Loop:.*mylist@mydomain.tld
* ^TO mylist(a)mydomain.tld
/full/path/to/system/mailbox
:0
* ^TO mylist(a)mydomain.tld
|/full/path/to/SmartList/.bin/flist mylist
What you _should_ do is subscribe an external address to the mailing list;
if you have an account somewhere else, like maybe your access provider
(cox.net?), use it instead of an address on the same virtual server - that
will eliminate the problem entirely without having to trap out the mail
coming to you (different server, no harm no foul). You could also use other
header fields in the trap recipe (X-Envelope-To: if your provider adds it, or
maybe a Received:.*unixusername, or something else), anything that will ONLY
occur in mail to you, not to the list. Finally, instead of subscribing
yourself, you could add as the last recipe in the rc.local.s20 file:
:0 c
/full/path/to/system/mailbox
Note this problem will happen on _any_ address delivered to the same unix
account, and so running the same .procmailrc file. This also likely accounts
for the repeting subscribe.txt file loop...I'd almost bet there were
X-Diagnostic: headers in those things (ALWAYS check messages from the
-request side for X-Diagnostic: header fields...they are your friends).
You're also going to have to anticipate -request mails as well, especially if
you use an account on mydomain.tld as the admin account for X-Commands and
the like. I wouldn't; I'd use an address on an external machine to avoid all
the possible pitfalls.
If you don't understand what I'm saying here, let me know and I'll try to
explain it better; it's a simple problem, with a simple solution, regardless
of my verbosity.
Charlie (who should have figured this out long before now)
Hello,
I customised my rc.custom file and my rc.local.s10 fiel so that in the subject line, the name of mys list appears in all messages. Unfortunately, the subject line is duplicated every time the person who first originated a thread gets an answer. To explain more clearly, when someone answers to a message, all members of the list get the message with the correct subjetc line (like thise [List name] Subject), but the orginator of the message, gets the subject quoted twice like this : [List name] Re: [List name]: subject.
How can I stop the pre-customised subject to be duplicated in the subject line ?
Thanks
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
In configuring Smartlist, I delinked the accept list so that anyone could subscribe, but only actual club members could post. In testing, I subscribed via one of
my accounts and set that acct. as the only user in the accept list. I then subscribed as a seperate user from a different account. I then sent an e:mail from the
subscribed but non-accept list address and the accept.txt message got sent to me 25 times. Anyone know how to fix this?
Peace,
Gyan
Life is a mystery to be lived, not a problem to be solved. -- Osho.
���`�����`���o,,,,o���`���o���`���o,,,,o���`���o���`���
Gyan Penrose-Kafka * gyan(a)zenmonkey.net * ICQ # 37394131
P.O. Box 232092, Encinitas, CA 92023 USA -- tel: +760.613-4926
���`�����`���o,,,,o���`���o���`���o,,,,o���`���o���`���
For my PGP key send a message to pgpkey(a)zenmonkey.net
-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.7.1 (C) 1997-1999 Network Associates, Inc. and its affiliated companies.
iQA/AwUBPT9wKqpfFVI4NVzFEQKWkACgvQ74BUY0l2DQe9if6mE49ZhD2zoAnRxb
ITJCF+qhL02w2CXzA0HUEfvh
=fc+j
-----END PGP SIGNATURE-----
Hi,
This is not necessarily a SmartList question but with all the list
admins here I was hoping someone might be able to help.
Does anyone generate statistics of their list(s) like number of
messages per subscriber, subscribers with largest messages, largest
threads etc.? If so, what do you use for this?
Thanks,
Harshal
=====
http://www.mumbai-central.com : Where Mumbaikars meet
__________________________________________________
Do You Yahoo!?
Yahoo! Health - Feel better, live better
http://health.yahoo.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have an account with a web hosting service. I would like to set up SmartList to work on this, and I've been able to do everything except for setting up the
alias file because I don't have write access to the directory. How do I work around this?
Peace,
Gyan
Life is a mystery to be lived, not a problem to be solved. -- Osho.
���`�����`���o,,,,o���`���o���`���o,,,,o���`���o���`���
Gyan Penrose-Kafka * gyan(a)zenmonkey.net * ICQ # 37394131
P.O. Box 232092, Encinitas, CA 92023 USA -- tel: +760.613-4926
���`�����`���o,,,,o���`���o���`���o,,,,o���`���o���`���
For my PGP key send a message to pgpkey(a)zenmonkey.net
-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.7.1 (C) 1997-1999 Network Associates, Inc. and its affiliated companies.
iQA/AwUBPTzZu6pfFVI4NVzFEQKeSACgqDQNFWSSfdI5HhfY9lUDlqMquLQAoIfV
0U9sTp101Jn3MtjXj8oexB6T
=bD6a
-----END PGP SIGNATURE-----
I have a very basic question:
Is it possible to create a list remotely say, by a perl script or something...
The SmartList manual talks about maintaining lists remotely but I was wondering if it could be created as well.
Thanks
Nishi
Peter, the only criticism I have of this method is that it requires the
person sending the X-Command to know in advance that it's going to be
wrapped, and to put the magic "_END" at the end of this. This was not my
situation; the X-Commands just suddenly stopped working (for only long
email addresses, we discovered later) and no one knew why.
I prefer a solution which says:
"X-Commands, if they appear in the body of a message, must be the first
line, and must be followed by a blank line before the rest of the body
of the message, or be the only thing in the message. If there's more
than one X-Command in the body, they must not be separated by a blank
line."
I think that this would work more intuitively and naturally. It should
also work for automatic word wrapping which occurs without the author's
knowledge or consent.
Unfortunately, I don't know how to write the perl code for this.
Sorry.
Thank you for your efforts to update the FAQ. I've found it very
valuable.
-Kevin Zembower
>>> Peter Hartzler <pete(a)hartzler.net> 07/18/02 07:59PM >>>
Hmm...
I'm interested in updating the FAQ, but the code seems to be a bit
crazy
yet. (Ironically, the word-wrapping doesn't help. ;-)
Now, I could be way off on this one, so don't go jumping up to place
this
into production; there are some dark corners to this stuff that I'm
sure I
don't know about!
If the goal here is to pick out and unwrap text from a message and
inject
that text as a header using perl, then I'm thinking this might be
saner:
--- cut here ---
# Allow embedding a single X-Command on multiple lines
# within the body of an email. (Lines will be joined.)
# Look for FIRST magic X_CMD: token. If found,
# take from there to __END and add to message header.
# Like this: X_CMD: X-Command: blah blah blah __END
# (X-Command: blah blah blah..) can be across multiple lines...
# Note that this is kind of expensive, but X-Commands should
# be somewhat rare.
:0 Bw
* X_CMD:
* __END
{
XCMD=`perl -p -0077 -e \
's/[\n\r\s]+/ /sg; \
s/^.*?X_CMD:\s*(.*?)\s*__END.*/$1/;'`
:0 f
|formail -i "$XCMD"
}
# End of recipe
--- cut here ---
Please let me know if I'm out to lunch on this one.
Check out the SmartList FAQ at http://www.hartzler.net/smartlist/
Regards,
Pete.
_______________________________________________
Smartlist mailing list
Smartlist(a)lists.RWTH-Aachen.DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/smartlist
Richard's solution, below, seems to work like a champ. No problems in
testing with it so far.
For others who may implement this, make sure that, if you used the
original X-Commands-in-the-body recipe, from the FAQ, that you remove
the older recipe before you install and run this one. Forgetting to do
that cost me about an hour's work.
Richard, and all others who contributed to this discussion, thank you
very much.
-Kevin Zembower
>>> "Richard G. Ball" <Richard_Ball(a)merck.com> 07/16/02 04:25PM >>>
On [2002-Jul-16] Tim Pierce <twp(a)rootsweb.com> wrote:
> In article <sd342c82.076(a)ccp2.jhuccp.org>, KEVIN ZEMBOWER
<KZEMBOWER(a)jhuccp.org> wrote:
> >
> > We're using GroupWise here. As far as I can tell, there's no
option to
[snip]
> So, are there any alternative solutions?
>
> It's supposed to be legal to break headers into multiple lines
> by adding whitespace at the front of each "continuation line."
[snip]
>
> So you could try forcing the issue by breaking the X-Command into
> these continuation lines yourself well before the 72-character
limit.
> I don't know if SmartList/procmail will actually handle the
> continuation line correctly, but it seems like it ought to.
If Kevin can't turn off line-wrap he probably can't enforce headers
either :-(
Since x-commands are not common there isn't much of a performance
penalty for using the Perl sledge-hammer to make things fit. So: put the
x-command in the body on as many lines as needed and then in
rc.local.r00 do:
:0 B
* $ ^[ ]*\/$\X_COMMAND:.*[^ ]
{
# Remove the X_Command from the body, and insert it in the header
# allow it to extend over multiple lines. the perl script concatenates
the
# whole body together and removes irrelevant whitespace. this is then
fed back
# to procmail to extract the command and put it in the header.
:0 fw
|perl -ne 'if(/^$/ .. eof())
{chomp;push(@l,$_);}else{print;}if(eof()){forea
ch (@l){$i++;last if /__END/}$l=join(" ",@l[0..$i-1]);$l.="\n";$l=~tr/
/ /s;$l=
~s/^\s+//;$l.=join("\n",@l[$i..$#l]);print "\n$l\n";}'
:0 B
* $ ^\/$\X_COMMAND:.*[^ ]
{
:0 fw
| grep -v "^$X_COMMAND:" | formail -I"$MATCH"
}
}
Note: this assumes there are no x-commands in the headers (if there are
you need to account for that case separately. I think the above comes
out of code Alan Stebbens put out for handling this "problem".
Rich
--
richard_ball(a)merck.com
(I regret the presence of the legal disclaimer but I have no control
over it)
------------------------------------------------------------------------------
Notice: This e-mail message, together with any attachments, contains
information of Merck & Co., Inc. (Whitehouse Station, New Jersey, USA)
that may be confidential, proprietary copyrighted and/or legally
privileged, and is intended solely for the use of the individual or
entity named on this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by e-mail and then delete it.
==============================================================================
_______________________________________________
Smartlist mailing list
Smartlist(a)lists.RWTH-Aachen.DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/smartlist
