Hello,
I just upgraded sendmail to 8.12.9 and now some of my lists are not
working. I can send to their e-mail addresses but nobody is getting the
e-mail. It isn´t bouncing either...it is like it is just going into the
unknown..
Jerry Sloan
PS
One list is working..
Are there plans (or existing hacks) to allow SmartList to be multi-lingual
in its messages (e.g. the feedback sent by rc.submit with "subscribe",
"unsubscribe", "help", etc.)?
I currently have lists in German, Spanish, Danish, and English, so it
would be convenient to have, for example, a "locale" parameter in
rc.custom.
Cheers,
Seth Chaiklin
Hi,
When does Smartlist check if the message is from a subscriber? I have a
bunch of checks in rc.local.s00 (for attachments, too much quoted text
etc.) and these are being checked for every incoming email even if it
is not from a subscriber. And I get a lot of junk on the list address.
So all these checks and actions are being taken for messages that end
up getting shunted to the list-admin mailbox.
Can I move these checks to rc.local.s20 or even later if possible?
Thanks,
Harshal
__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
Hello,
I have been using SmartList for years without any problems. Recently i have
a list that works fine for most users but one cause problems. The
messages is not sent to members of the list but to the maintainer of
the list.
I get the following line in the message and the equivalent in syslog.
X-Authentication-Warning: host.mydomain.ca: slist set sender to <username> using -f
This would be OK if <username> was the name of the list as usual but instead it is the
name of the user that maintain the list.
Anyone have a hint for me.
Sylvain
While my first message on this issue waits for approval from the mailing list
admin (don't know why) I send a second solution for the bug with addresses
like foo(a)is.not.so.com or alex(a)wait.change.ti. Such addresses cannot be
subscribed because the following line in rc.request matches if the subject
line contains "subscribe alex(a)wait.change.ti".
* -100^0 ^Subject:(.*[^a-z])?(Re:|erro|change|problem|((can)?not|.*n't)\>)
I would suggest to modify the third condition line of the recipe
* 100^0 ^Subject:[ ]*archive
to
* 100^0 ^Subject:[ ]*(archive|(un)?subscribe)
My first solution (which could be come late if the list admin is on holidays)
suggested to modify the first regex in brackets of the first condition line,
removing the .* greedy regex, but this would weaken the filtering capabilities
for non administrative messages.
Werner
I've got some recipes that I'd like to know if we're dealing
with a list subscriber, so using multigram comes to mind.
The only multigram documentation I find is in the manual,
section 6. "Multigram and the thresholds in rc.init/rc.custom"
which gives one example of calling multigram, and a brief
description of its output. Is there any other "man multigram"
sort of documentation I should be looking for?
Looking in the source for multigram.c, I see some documentation
output from a case statement, which looks like clues as to the
options, so that's a possibility for understanding the invocation.
For understanding the output, it'd be nice to run multigram on my
home machine. I have the Smartlist sources, but I haven't done a
real install at home, because I run Smartlist on my ISP's server.
Typing cc multigram.c gives lots of errors regarding missing includes
and such, so my next question is, is it possible to play with
multigram without doing a full Smartlist install? I don't see a
makefile anywhere in the sources, but maybe one is generated by the
install.sh scripts.
I can probably use egrep to do what I need to do in my rc.locals. Am
I wasting my time trying to learn enough about multigram to use it?
Do I need to use egrep to use the output of multigram anyway? Or
does it produce a true/false exit status that I can use directly in a
procmail recipe?
Of course, there's the example in Smartlist's rc.submit; I can copy
it and hope for the best, but I'd prefer to understand a bit more of
what's really going on. I hate to do much testing on my real list
without some beta work offline at home.
FWIW, my ISP uses the ancient procmail 3.10 and its Smartlist.
The manual section 6 seems to be identical for procmail 3.13/SL.
TIA,
Jim
We got a strange attack from a nasty server that have set tons of
messages with different mesageid but the same body.
Someone have built a loop detection based of an (md5?!) hash of the
body, or some sort of quota based on site?!
Thanks.
--
Le parti si impegnano [...] ad astenersi nelle relazioni internazionali
dalla minaccia o dall'uso della forza in ogni modo in contrasto con
gli scopi delle Nazioni Unite. (art.1 Trattato NATO)
Hi:
Per FAQ 8.3, adding text to the Subject of list messages [which I've always used
succesfully in the past] via rc.local.s20 [see way below]:
On the most recent list I've set up, some messages contain this text and some DO
NOT. Both senders are on dist, I don't think I see any differences in the
headers, and I can't figure out what makes one different from the other. Has
anyone seen this before, or does anyone have any suggestions for what I might
look into to resolve?
Thanks, Mitch
------------------------------------------
SUBJ=`formail -zx Subject:` # extract the subject
:0fw
* ! Subject:.*\[Focusing, Contemplative Practices and Spiritual
Paths\]
* ! Subject:.Re: *
| formail -I "Subject: [Focusing, Contemplative Practices and
Spiritual Paths] $SUBJ"
#
# Appending a footer to every outgoing mail:
#
:0 fbw
| cat - footer.txt
----------------------------------------
Mitchell Darer, Systems Support / List Manager, mitch(a)focusing.org
The Focusing Institute, 34 East Lane, Spring Valley, NY 10977
http://www.focusing.org (845) 362-5222, fax(845) 678-2276
Multipart/alternative/html/encoded woes ...
I have my lists set up to block (reject) posts with HTML, but even this
isn't really solving a whole lot of my problems, because people (mostly
AOLers) continue to send messages in HTML and then wonder why they're not
going through. Even though my reject message clearly states what the
problem is and directs them to pages that have instructions for turning off
the HTML in just about every mail program, every frickin' time AOL
upgrades, it causes a whole new set of problems because the new program
isn't on any of the instruction lists yet.
So I'm wondering... is there any way [or can anyone here come up with a
way] to make Smartlist simply convert any and all HTML/encoded messages to
plain text? There has got to be *some* way to make that happen, doesn't
there? I have other friends running mailing lists using other software
programs and they've been able to do this, so it seems like Smartlist
should be able to as well.
The past few months a lot of my list members have taken to saying,
"Smartlist isn't very smart, is it?" every time the program has
difficulties handling particular types of messages. I just don't want to
believe that because I'm sort of attached to it, but I must admit I'm
starting to become more and more frustrated as times goes on. I swear I
have just about every script possible in my various local and submit files,
and I dunno..... It gets to a point where, when your whole program seems
to be held together and controlled more by the spit-and-glue of numerous
fixes than the basic program itself, you start wondering if the program
you're using is the most efficient choice.
If I had a wish list of things I'd change about Smartlist, the first thing
would be to have some way to set it to strip HTML from messages. I think
that should be a basic part of the program, because HTML encoding is one of
the biggest problems facing most list owners these days.
The second thing I'd change is the way the program cannot seem to interpret
short messages with no subject line (or short subject lines) as posts, but
flags them as "undecipherable" and sends out the help file. This is really
annoying, and it happens all the time. A person on my list had a birthday
today, and when someone attempted to send a message with the subject "30!"
and a short note in the body wishing them a happy birthday, Smartlist
bumped it and sent the help file.
Unfortunately, I don't have the skills to create a script to fix either
thing myself. But I know several of you do, or know others who do, so I'm
putting this out there in the hopes that someone here might be able to come
up with something that could help.
Violet
xoxox
For most normal traffic the logabstract gets a Subject: line and a Folder: line (with choplist info in it) but no From: line. Messages to the request address and most error messages seem to get a From line. Why don't all messages get a From line in the logabstract? Is there any way at the rc.custom level to change this behaviour?
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.
==============================================================================
