for some of my smartlists, i have been using the following to
put the listname in the Subject. however, strange things happen
from time to time and i believe it is due to people inserting
manually 'Re: ' and 'Re: [listname]'.
:0wfh
* $!^Subject: *(re:[ ]*)?\[$list\]
* ^Subject: \/.*
| formail -I"Subject: [$list] $MATCH"
is:
* $!^Subject: *(re:[ ]*)?\[$list\]
really a better way to go than something like:
* $!^Subject: *Re:.[$list\]
to be honest, i lost track of just exactly what
* $!^Subject: *(re:[ ]*)?\[$list\] is doing.
any comments would be appreciated.
thanks,
--paul
--
pegmgr(a)cgfs.com writes:
>Hmmm. I've been running into the same problem with Redhat 7.2 .
>
>My /etc/smrsh is definitely pointing to the correct flist.
...
Are we 100% sure that smrsh is looking in /etc/smrsh for the programs
it runs? What does
strings /path/to/smrsh/binary | grep /sm
On the only redhat system I have handy, I find:
callisto% cat /etc/redhat-release
Red Hat Linux release 6.1 (Cartman)
callisto% strings /usr/sbin/smrsh | grep /sm
/usr/adm/sm.bin
callisto%
Philip Guenther
I had a mailing list up and running but ran into some difficulties because I didn't handle the foreign_submit line correctly. I deleted all the mailing lists from the control panel and tried to start over.
My mail directory showed no files however when I reconstructed the list using the same list name and did a test subscription I had the last seven issues of my newsletter returned to me. There must be some files lurking somewhere that I can't find.
My host does not offer tech support for listserve and I can't find anything about this in the manuals.
Can anyone help?
I am testing the bounce/remove function and have a problem I can't figure
out. I have got a combination of test addresses in the dist file. Some are
valid, some are not. When I send a message to the list, only one bad address
is removed from dist. The others generate a "returned mail" error in
log/request, but the bad address stays in the dist file.
In rc.custom, I have minbounce = 1, auto_off_threshold = $loose I also have
no value for maintainer because I prefer that these messages be delivered to
the request file instead of to me. (I get the same results with maintainer =
[a value] and different combinations of minbounce and threshold. If
maintainer = my email, I have the same problem with the dist file, but I do
get the returned email, error=550 "user unknown.")
All these bounced messages come from MAILER-DAEMON(a)domain.com The first
remove is always accepted, all subsequent removes have daemon complaints ...
possibly a response from the attempt to deliver a "you have been removed"
message to a non-existent address? Frankly, I have no clue what is happening
here.
The first entry in the log is always this, and it removes the bad address
from dist:
procmail: Executing "procbounce"
procbounce: Removed: bademail(a)domain.com
A message is sent to this bad email address, advising that the bad email has
been removed from the list. Then ...
All successive entries after this first successful "remove" look like this:
procmail: Executing "formail,-A,X-Diagnostic: Mail coming from a daemon,
ignored"
procmail: Match on "^X-Loop: ()mylist(a)mydomain\.com"
procmail: Executing "formail,-A,X-Diagnostic: Possible loopback problem"
procmail: No match on ! "^X-(Diagnostic|Processed):"
procmail: Assigning "INCLUDERC="
procmail: No match on ! "^X-(Diagnostic|Processed):"
procmail: Executing "formail,-AX-Envelope-To: mylist-request"
procmail: No match on ! "."
procmail: Assigning "fOPT=-fslist(a)mydomain.com"
procmail: Executing " formail -R"From
X-From_:" -iDate: -iReturn-Receipt-To: -iRead-Receipt-To: \
-iAcknowledge-To: | \
$SENDMAIL $fOPT $sendmailOPTnorm $sendmailOPTp $maintainer"
I'm using procmail v 3.21 SmartList 3.15 Something is augwiedered here, and
I don't know how to fix it. I appreciate whatever guidance you can provide.
Thanks,
Kim
Greetings,
Is it possible to block the reply of certain individuals from being
distributed to a mailing list? Their accounts have been removed and it is
only possible for certain people to post to the list. However, neither one
of these options eliminates the possibility of these unwanted individuals
from responding.
Thanks in advance.
Tom O'Rourke
I've installed SmartList on RedHat Linux 7.1
Procmail v 3.21
I've put an flist symlink into /etc/smrsh, I've adjusted
/etc/aliases to read:
testing: "|flist testing"
testing-request: "|flist testing-request"
When any mail gets sent to testing or testing-request the following message
is sent:
flist: no sequence specified or Unseen-Sequence profile entry found
554 5.3.0 unknown mailer error 1
Can anyone help me resolve this?
Thanks!
Kim
Good Morning,
I run a list for our tech support department that sends an auto-reply to
the original sender. My problem is this e-mail address gets a boatload
of spam. But when the messages come through smartlist has stripped the
original message headers. Is there any way to keep the original message
headers so that I can use them to block spam?
Thanks in advance for any help
Jerry Sloan
Network/System Admin
fP Technologies, Inc
--
"Let us take care that age does not make more wrinkles on our spirit
than on our face."
Michel de Montaigne
Ha ha, speak of misconfigured autoresponders, look what I just got in my
email box after posting to the list:
On Fri, 18 Jan 2002, Mailer-Daemon wrote:
> Sorry. Your message could not be delivered to:
>
> paonia,Mass College Art (The name was not found at the remote site. Check
> that the name has been entered correctly.)
Be careful out there!
--paul
CueMan
--
http://www.cuenet.com Info(a)cuenet.com
-= At the speed of the Internet =-
Howdy,
I know this subject has been visited before but....
Has anyone come up with any heuristics that procmail can
use to determine that a message to a mailing list from a
poorly configured autoresponder (the message appears to come
from an individual and does not include headers from
daemons, proper Precendence: , etc) and prevent it from
creating an infinite loop with the mailing list?
I realize people who can't properly setup an autoresponder
have no business using one and should be publicly humiliated
at their local soccer stadium, however this is not an option
available to me.
Cheers,
--Paul T.
Cueman
--
http://www.cuenet.com Info(a)cuenet.com
-= At the speed of the Internet =-
Good Morning,
I run a list for our tech support department that sends an auto-reply to
the original sender. My problem is this e-mail address gets a boatload
of spam. But when the messages come through smartlist has stripped the
original message headers. Is there any way to keep the original message
headers so that I can use them to block spam?
Thanks in advance for any help
Jerry Sloan
Network/System Admin
fP Technologies, Inc
--
"Let us take care that age does not make more wrinkles on our spirit
than on our face."
Michel de Montaigne
