I'd like to get a sanity check/confirmation on how I think removals
get processed by SmartList v3.15. From looking at the procbounce
script in the distro, it seems that when a DSN, or other error message
is received:
1: the offending address is extracted as "addr"
2: $addr is added to a file in bounces/, named per today's date
3: all but the most recent $maxhist files are removed from bounces/
4: a count is made of all files in bounces/ that contain $addr
5: if $count >= $minbounce then $addr is removed
Do I have that right? If so, the only mechanism for blessing a
no-longer-bouncing address is when other bouncing addresses cause
enough daily bounces/ files to be generated so that the old address
passes out of the system. I had always thought there was some
mechanism whereby successful delivery to an address would reset the
counter for that address, so a bounce limit of, say, 4 meant that a
subscriber needed 4 bounces without a successful delivery to be
removed. But now I think I was very wrong, and the situation is much
more complex and depends on a lot more than just the offending bouncer.
As an extreme example, if one subscriber happened to be the only
bouncer and he bounced, say, once a month, he'd still get removed
after 4 months, no matter how many times he took delivery of the list
traffic during all that time.
Am I missing something?
TIA,
Jim
Hello,
I have been using the following recipe to generate an auto-reply message
to customers who send e-mail to our support department. Well it just
stopped working. Nothing has been changed. Any ideas why it would just
stop working.
Thanks
Jerry Sloan
REPLY_TEMP=/home/smart/fpsupport/autoreply.tpl
REPLY_TEXT=/home/smart/fpsupport/autoreply.txt
REPLY_SUBJECT="Your message has been received DO NOT REPLY to this
e-mail"
ORIG_SUB=`formail -zx Subject:`
:0 whc
| formail -rtzc -xTo: >tmp.from ; \
sed 's/\$SUBJECT/'"$ORIG_SUB"/g $REPLY_TEMP > $REPLY_TEXT
:0 ch :autoreply.lock
| (formail -rtzc -I "Subject: $REPLY_SUBJECT" \
-A"Precedence: reply" ; cat $REPLY_TEXT) | \
$SENDMAIL -t -f sysadm(a)fptech.net `cat tmp.from`
I have a few smartlist questions:
1. How can I save messages to an mbox file, where I can search it
quicker and easier than opening thousands of individual message files?
Ideally, I'd like to group the messages into mbox files by month.
2. I have an existing database of users, and I will be creating a web
page where they can log in, see which lists they are subscribed to, and
change their subscriptions. What is the best way to synchronize a
database of user enrollments with the dist list? Should I rewrite the
dist file from the database each time? The alternative method of
sending an email with an XCommand seems like so much overhead,
particularly since I don't want any email response to the command, and
because I may need to subscribe a large number of users at once. Why
isn't there a simple script, ala Mailman, for handling admin functions?
3. How can users select their own digest mode, rather than setting it
globally for the list?
Thanks in advance.
--
Gary
Chenge the line in "rc.submit" from "archive/archive/."
to "archive/YOUR_MBOX_NAME" will do.
Zhiliang
On Thu, 8 Jul 2004, Roger Burton West wrote:
> On Wed, Jul 07, 2004 at 03:17:36PM -0400, Gary Weinfurther wrote:
>
> >1. How can I save messages to an mbox file, where I can search it
> >quicker and easier than opening thousands of individual message files?
> >Ideally, I'd like to group the messages into mbox files by month.
>
> All you need to do is cat the individual message files together.
I'm looking for a new web hosting service that has procmail available and
suppports email lists via smartlist. My current service is becoming less and
less reliable (over a 10% lost mail rate for mail going out from my email
lists) and since they appear to be incapable of solving the problem, and since
I've been a long-term subscriber to these lists, I thought I'd ask here for
recommendations for a new service. The email lists are small (<150
subscribers) and the traffic is not high so a mid-range plan is plenty of
capacity (200MB, 100 email addresses, 5 email lists). I've poked about in
Nancy's compilation and at a couple of the on-line rating groups but a
personal recommendation would help as well. Any suggestions?
Rich
I'm looking for a new web hosting service that has procmail available and
suppports email lists via smartlist. My current service is becoming less and
less reliable (over a 10% lost mail rate for mail going out from my email
lists) and since they appear to be incapable of solving the problem, and since
I've been a long-term subscriber to these lists, I thought I'd ask here for
recommendations for a new service. The email lists are small (<150
subscribers) and the traffic is not high so a mid-range plan is plenty of
capacity (200MB, 100 email addresses, 5 email lists). I've poked about in
Nancy's compilation and at a couple of the on-line rating groups but a
personal recommendation would help as well. Any suggestions?
Rich
Thanks to those of you that replied to my earlier posting. The problem is
still ongoing with other members of my list. When they attempt to post,
they get messages that tell them that they are not authorized to post. The
same message will go through if they try again.
I have the dist and accept lists set up identically, e.g. everyone who is
authorized to receive messages posted to the list can also post to the list.
Further, some of the "Mail delivery subsystem" error messages I am receiving
are showing that my own address (the one from which I am posting this
message and to which I receive more than 100 messages a day) is invalid. I
freely admit to being a dope in this area, so if anyone has any suggestions
that will make administration of this list a bit more smooth, I would
appreciate hearing about them.
Tim Dees
tim(a)timdees.com
On Thu, Jun 17, 2004 at 09:03:52PM -0700, Tim Dees wrote:
> I am a new Smartlist user, so please forgive any really obvious ignorance.
> The messages on my list are mostly getting delivered to the list members,
> but all of the messages delivered to my mailbox have the subject line "Mail
> delivery failed: returning message to sender" or something similar. The
> very bottom of this message will usually have the body of the message posted
> to the list by another user. Does anyone have any suggestions for making
> this delivery system resemble something a little more normal-looking?
>
> Tim Dees
> tim(a)timdees.com
I guess you'd have to tell what would be "more normal-looking" to
you. It sounds pretty normal to me.
Your list is sending mail to mailservers which for one reason or
another are unable to complete the delivery. It might be
temporary, like say the user is overquota, or permanent like the
address is no longer valid. So the server for these members return
the mail to you, the list owner and therefore the sender.
Somewhere in the message it may tell you why it was unable to
complete the delivery.
Or are you saying that you get a delivery failed message on
messages that actually didn't fail? If I've missed your point,
maybe you could make it clearer.
Don MacDougall
dmacdoug(a)usc.edu
Greetings I know my question has been answered here before but I am not
smart enough to implement the solution successfully. We are on a shared
commercial server webhost which allows me direct access to SmartList code
but not direct access to sendmail etc.
My subscribers complain they aren't getting our (opt-in) newsletter. I have
told them to put our domain on their ISP whitelists which some claim to have
done. I know we get filtered by Yahoo Mail to the bulk mail filters. AOL
seems to trash us directly. We are not on blacklists so presumably most is
due to headers.
The recipient sees in his/her Outlook Express:
From: "Larc Webmaster" <webmaster(a)OURDOMAIN.org>
To: newsletter(a)OURDOMAIN.org
Reply-To: webmaster(a)OURDOMAIN.org
I guess I am stuck with that "to" line using SmartList (that is, no
individual recipient addressing), which certainly results in some deletions
as spam.
In the hidden headers (the shared server is globalnameservers.com, where we
are user-id larc):
X-Authentication-Warning: host10.globalnameservers.com: larc set sender
to newsletter-request(a)OURDOMAIN.org using -f
I have added the recommended code to remove X headers to my rc.local.s20 but
this still appears (presumably added by sendmail which I cannot access).
The other additions to rc.local.s20 work fine (referencing my custom
footer.txt). Could this be leading to spam deletions?
Similarly:
Return-Path: <newsletter-request(a)OURDOMAIN.org>
Can I or should I be concerned about this? I do not want to screw up my
Smartlist.
Thanks for any assistance. Smartlist is very handy but if our susbcribers
don't get the messages it is futile.
Chas
powercat(a)verizon.net
