Hi there!
I am looking for translated (German) smartlist help-files. Any
pointers?
TIA&Cheers,
Gerhard
P.S.: Please cc me, I am not on the list.
--
Dipl.-Phys. Gerhard Killesreiter <killesreiter(a)physik.uni-freiburg.de>
Es sind nicht nur die Möllemanesken und Kanzlerkasperaden, die die
politische Spaßgesellschaft und ihre Showeffekte entlarven.
Wolfram Weimer, in »Die Welt«, 23.5.2001
Hello,
Our non-profit organization is using Smartlist to manage its mailing
lists for press contacts, donors, etc.. We have a web interface that
lets the individual managers add/remove people from their mailing lists,
but I was wondering if there was a way to turn the "you have been
subscribed to so&so list" off.
Instead of using outlook to manage sending emails out, I set up
smartlist mailing lists for obvious reasons. They are complaining to me
now that they do not want the recipient receiving an email if they are
added to the list.
Any help would be much appreciated
-Hitesh Aidasani
Asian Americans for Equality
hitesh(a)aafe.org
We have been having trouble with one particular subscriber. This person can
use their e-mail address fine anywhere else, but not with our mailing list.
In this particular case, the welcome message sent from the list to this
person bounced. Here are the header lines:
=====
X-Diagnostic: Mail to xxx(a)skyenet.net bounced 8 times
X-Diagnostic: Bounces exceed threshold of 4
X-Diagnostic: Removed: xxx(a)skyenet.net 32746
X-Diagnostic: Mail coming from a daemon, ignored
X-Diagnostic: Possible loopback problem
=====
Here is a portion of the body of the message:
=====
The original message was received at Tue, 14 May 2002 20:49:25 -0400
from brucev@localhost
----- The following addresses had permanent fatal errors -----
xxx(a)skyenet.net
(reason: 550 5.7.1 Mail from 209.239.35.21 refused by blackhole site
bl.spamcop.net)
----- Transcript of session follows -----
.... while talking to mf02.hypervine.net.:
>>> MAIL From:<tlcc-list-request(a)trilakes.org>
<<< 550 5.7.1 Mail from 209.239.35.21 refused by blackhole site
bl.spamcop.net
554 5.0.0 xxx(a)skyenet.net... Service unavailable--
=====
What is going on here?
--Bruce
What does the following header line mean?
X-Diagnostic: Mail coming from a daemon, ignored
I'm having trouble subscribing a particular person to the list from a web
interface provided by my web provider, and this is appearing in the header
of the message sent back to the list administrator.
Also, is there a particular reason why I need to look in the mail header for
specifics of why something has gone awry? Couldn't this information be
reported in a more user-friendly manner in the message body?
--
Bruce Vander Werf
brucev(a)cyberlink.com
Hi, new user here...and I just want to know if someone can tell me what "uncomment means. I'm reading this:
<<In your rc.custom file, uncomment the line that reads "RC_LOCAL_SUBMIT_10 =
rc.local.s10", and make a file called "rc.local.s10" in your list directory, in that file put
this:
---- Cut Here ----
SUBJ=`formail -zx Subject:` # extract the subject
:0fw
* ! ^Subject:.*\[listname\]
* ! ^Subject:.Re: *
| formmail -I "Subject: [listname] $SUBJ"
---- End Here ----
Be sure to replace "[listname]" with what you would like to be at the beginning of the
subject line.>>
And I am just not totally sure what the word "uncomment" means in this situation.Do I remove the lower case text rc.local.s10 from the custom file or what? I'm just so confused. HELP PLEASE!
K.Torres
Many list admins probably have the problem of spam sent to the request and
the mailling list address and forwarded later to the maintainer address.
To make things worse the standard SmartList installation will send a help
message or a "You are not a member of this list" message to the nonexistent
spam address which leads to bounces - again forwarded to the maintainer.
To silently delete most of the spam sent to my mailing list addresses I extended
the rc.local.s00 recipe hook which I am using now to sort out certain mail
e.g. with attachments or sent as html. The recipe sorted out the mail very
well but sent a message to the maintainer and the sender even if it was pure
spam. I modified it to check before if the sender is on the accept list(s).
If not, the message is silently dumped to /dev/null.
Since most of the spam is sent as html and/or with attachments the spams sent
to the maintainer have stopped almost completely. The drawback of this
solution is, that if a non member wanting to contribute to the list with
a mail attachment he won't get any hint that he has to subscribe before
posting.
You can find the modified rc.local.s00 recipes attached.
To block the forwarding of spam sent to the request address I am going to
use the following recipe in rc.local.r30:
:0
* !^X-Diagnostic: Already on the subscriber list
* > 4096
/dev/null
I haven't tested it in production but I am confident that it will sort
out all remaining spam. It could create problems if peoples are trying to
(un)subscribe with messages larger than 4k which I haven't experienced yet
as far as I remember.
Werner
