There is a member of our list who has his mail client set to include a read
receipt on every message. He refuses to remove the read receipt when posting
to our list. Since this hasn't previously been a rule on the list, I'm
reluctant to take action against him. I'd like to know if it's possible to
simply remove the receipt request before the post goes out to the list.
Thanks!
-Judy
The SmartList FAQ says about using the Postfix MTA:
"For large lists it may be advantageous to replace choplist with the
direct sendmail wrapper call because postfix doesn't need a helper
program for the load balancing."
So how do I do that exactly?
rc.init simply says:
#alt_sendmail # uncomment if you'd prefer sendmail
# to handle the $listdist expansion
But when I uncomment this delivery to the list fails with an error
message from Postfix:
<test-dist(a)lab.applinet.nl>: unknown user: "test-dist"
What's the right way to let Postfix do the load balancing itself?
Regards,
René Pijlman
PLEASE HELP
My messages are not going trough to any of my mailing list, Mailman 2.05 was
set up by my hosting company on their server, following is a copy of the
error message:
This message was created automatically by mail delivery software (Exim).
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:
pipe to |/usr/local/cpanel/3rdparty/mailman/mail/wrapper post all_chesed.ws
generated by all(a)chesed.ws
Child process of virtual_address_pipe transport returned 2 from command:
/usr/local/cpanel/3rdparty/mailman/mail/wrapper
The following text was generated during the delivery attempt:
------ pipe to |/usr/local/cpanel/3rdparty/mailman/mail/wrapper post
all_chesed.ws
generated by all(a)chesed.ws ------
Failure to exec script. WANTED gid 12, GOT gid 99. (Reconfigure to take 99?)
------ This is a copy of the message, including all the headers. ------
The SmartList FAQ says about using the Postfix MTA:
"For large lists it may be advantageous to replace choplist with the
direct sendmail wrapper call because postfix doesn't need a helper
program for the load balancing."
So how do I do that exactly?
rc.init simply says:
#alt_sendmail # uncomment if you'd prefer sendmail
# to handle the $listdist expansion
But when I uncomment this delivery to the list fails with an error
message from Postfix:
<test-dist(a)lab.applinet.nl>: unknown user: "test-dist"
What's the right way to let Postfix do the load balancing itself?
Regards,
René Pijlman
In article <v03130303b770f0719e21(a)[24.104.7.214]>,
Charlie Summers <charlie(a)lofcom.com> writes:
> At 11:22 AM -0400 7/10/01, KEVIN ZEMBOWER is rumored to have typed:
>
>> Is this an appropriate use of SmartList, or should I consider some other
>>solution?
>
> This is not, IMHO, an appropriate use of SmartList. SmartList is designed
> to use uncluded externals to send the same message to "batches" of addressees
> at a time; what you want to do is send seperate messages to each addressee
> (as a seperate entry in the mail queue), changing the content of the message
> (the header is part of the message) for each mail. Therefore you would have
> to rework so much of SmartList that it would make more sense to write
> something yourself.
Not really true. I think it would be sufficient to write a "choplist"
replacement: something that travels through the dist file, inserting
each address it finds into the "To" header and handing it off to the
mail server.
It's not clear whether that would be a particularly good solution.
It would increase by quite a lot the amount of bandwidth and RAM you
use. If you're not hosting a lot of really large lists, that may not
turn out to be an issue. Other mailing list managers also use a
single message per recipient, but they get really precise bounce
processing as a result. (I don't know if it would be easy to munge
the "To" headers in the same fashion with other MTAs.)
One of my users wants mail from his list to contacts at various news organizations to look like
personal correspondence from him to the news contact. In other words, he wants the destination's
name to appear in the "To:" header, and not the name of the list in "To:" and the destination's
name in "BCC:". I still am encouraging SmartList use so that it can handle the bounces, although
we'll have to subscribe and unsubscribe new changes through X-Commands. The appearance
as personal correspondence doesn't have to hold up to close scrutiny of the mail headers, just
to casual appearance in mail readers that just show "To:", "From:", "CC:" and "BCC:" headers.
Is this an appropriate use of SmartList, or should I consider some other solution?
If I use SmartList, where and how should I make these changes? I'm not real familiar with
procmail commands, but I have all the documentation and could figure them out.
Will making these changes break any other aspect of email operation or SmartList's ability to
handle bounces?
Thank you for all your help and advise on my problem.
-Kevin Zembower
My primary interest in SmartList is due to a high-volume list I admin that runs
in both digest and individual mail modes... it was running fine and
well-configured on majordomo when a suddent catastrophe struck and necesitated
the transition to a new hosting provider -- who doesn't support majordomo, but
rather SmartList.
Now, my problem is that I cannot get subscribers to the digest to be able to
post to the regular list, without being subscribed as members to the list. I
don't want to open the full list up to anyone posting, as that could become a
very bad thing, but I need my digest-members to be able to post to the full list.
Any suggestions?
Graves
--
MCH/VO S* W- N+++++ PEC+++ D(s++/r) A a+>+++ C* G++(++++) Q+ 666 Y
Thank you for the assistance, Charlie!
SmartList sent me 2 separate emails....
#1 was an error message. Text follows:
Unknown command This.
This archive server knows the following commands:
get filename ...
ls directory ...
egrep case_insensitive_regular_expression filename ...
maxfiles nnn
version
quit
Aliases for 'get': send, sendme, getme, gimme, retrieve, mail
Aliases for 'ls': dir, directory, list, show
Aliases for 'egrep': search, grep, fgrep, find
Aliases for 'quit': exit
Lines starting with a '#' are ignored.
Multiple commands per mail are allowed.
Setting maxfiles to zero will remove the limit (to protect you against
yourself no more than maxfiles files will be returned per request).
Egrep supports most common flags.
If you append a non-standard signature, you should use the quit command
to prevent the archive server from interpreting the signature.
Examples:
ls latest
get latest/12
egrep some.word latest/*
#2 message arrived four minutes later. It executed the command and attached the most current newsletter from the archive.
So, this has half worked!
Any suggestions as to eliminate the first message indicating there was an error?
Thank you again!
Scott
I've just set up Newsletter SmartList which functions normally with one exception.
No matter what message I enter in the body, I can not get archive messages sent form the server. Each request gets either no reply or a "command error" reply.
I've read threads dating back to 97 with this issue and what I have tried does not work. Ultimately, I'd like to get the Archive onto a web page at my site, but I don't know how to do that, either.
Any help is most welcome and appreciated.
tia
Scott Lancey
WREL Radio, Lexington, VA
I think I've seen this answered before somewhere, but can't find it for the
life of me now that I need it.
One list I administer has gotten quite heavy in email traffic. Some members
only want certain emails from it, but the digest mode doesn't quite meet
their needs. Since my subscription base is quite varied, it's hard to just tell
them like it or not, particularly when the email programs they use vary as
widely as possible.
Is there a way to filter the email to a secondary list based on a keyword
either in the email itself or the subject line? That way the list members only
wanting certain emails could subscribe to the secondary list and not the
primary one.
Thanks...I'm learning it all slowly, and decided it would be faster to seek
more experienced help that to keep going at it trial and error. Other than
this one issue, my subscribers are delighted with the list compared to what we
used to utilize.
Angie
--
Sent through GMX FreeMail - http://www.gmx.net
