It's not really a smartlist issue, but more of an
administrative issue.
I seem to get the occasional user that subscribes under one
address, but then forwards the list emails from that address
to another. Unfortunately the address that message gets
forwarded to gets full or disabled and the servers that
handle the bounce loose the original headers along the way.
This makes it hard to for the smartlist to unsub an address
that it does not have. Sometimes I can find some clue in
the header that lets me figure out the correct address to do
it manually, but I've seem to have gotten a bounce that has
little info.
Does anyone have suggestion for tracking down the `pop` box
that is forwarding the email?
On [2002-Jan-18] Charlie Summers <charlie(a)lofcom.com> wrote:
[snip]
>
> There are various scripts out there you can use to send your probe, or you
> can write a simple one yourself. Just make sure there's info in the Subject:
> header field _and_ the body to give yourself a better chance of figuring out
> what address went dead.
>
> Charlie (who nominates this for a FAQ...)
Charlie,
If it warrants FAQ status maybe it'd be better to include the names & contact info for a few of those scripts "out there" (a quicky google search for "email perl probe" doesn't seem to grab anything interesting).
Rich
Most common problem is the user placing security restrictions to not receive
internet e-mail. This is frustrating because they can send e-mail to you,
but you can not reply.
Dan
-----Original Message-----
From: Gary Funck [mailto:gary@intrepid.com]
Sent: Tuesday, January 01, 2002 11:51 AM
To: Smartlist(a)Lists.RWTH-Aachen.DE
Cc: CueMan
Subject: RE: AOL email troubles?
Paul T. wrote:
> -----Original Message-----
> Sent: Saturday, December 01, 2001 11:08 AM
> Subject: AOL email troubles?
>
> Hi,
>
> Anyone out there with AOL subscribers on your SmartList(s) not
> receiving all your deliveries or maybe not being able to post
> to your list from AOL?
>
> Thanks and happy holidays!
>
> --Paul T.
This may provide a possible explanation:
http://www.interesting-people.org/archives/interesting-people/200201/msg0006
6.html
[...]
>I work for a company that delivers large amounts of e-mail for Fortune-1000
>companies.
>
>We had a very similar problem with AOL: we started to see many of our
>messages fail to arrive in AOL mailboxes even though AOL reported they were
>successfully accepted for delivery.
>
>Sending one or two messages at a time would work flawlessly, but when
>sending anything larger, some might arrive while many would not.
>
>After a lot of testing, we discovered AOL has some very interesting
policies
>regarding email delivery.
>
>In a nutshell, if you deliver more than some number messages to AOL within
>an a certain timeframe, AOL will accept them for delivery but in actuality,
>delete them without notice. The metrics AOL uses to decide what should or
>should not be delivered are not published.
[...]
background:
http://www.interesting-people.org/archives/interesting-people/200201/msg0006
1.html
_______________________________________________
Smartlist mailing list
Smartlist(a)lists.RWTH-Aachen.DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/smartlist
I have a request from one of the lists that I support to provide a
"Welcome Letter" introducing new members to the list!
Rather than "just say no" I wondered if any of you have any ideas?
The letter would be sent to the list AFTER the new user is subscribed
and would read something like:
Please welcome <FIRSTNAME> <LASTNAME> to the List.
This would supposedly serve two purposes:
Let everyone know that there is a new list member
Let the new member receive an email from the list
(So where do I get <FIRSTNAME> <LASTNAME>?)
I've been thinking about adding a CGI form front end but thought some of
the SL gurus may have dealt with something like this previously.
TIA,
David W. Gulley
Destiny Designs
Hey!
I've been on the list a few months now hoping someone will bring this up, as
I've been unable to find it in the FAQ (although I have a geeky friend who
tells me it's a problem he's seen before.)
I run 4 comparatively small mailing lists (the biggest is about 150
subscribers.) I am hosted by nomonthlyfees.com, which seems decent most of
the time, but has been really terrible about this particular problem. It's
compounded by the fact that they have a web interface for
subscribe/unsubscribes and charge extra for SSH access, which is not
something I particularly want to purchase, since 1) it would necessitate
learning how to use it, and, for the most part I get along pretty well
without it and 2) I'm a poor college student.
I've customized each list to send custom subscribe/unsubscribe messages. Of
course, I upload these files to the directories of their respective lists.
The problem is that Smartlist sends whichever sub/unsub custom message I've
uploaded most recently to every subscriber who attempts to subscribe or
unsubscribe, (it sends them respectively, i.e., doesn't confuse subscribe
messages with unsubscribe messages) regardless of the list with which
they're trying to interact. Restated, a prospective subscriber for the XYZ
list gets whichever custom list subscribe message I uploaded most recently
rather than the message appropriate to the list of interest.
The only thing that makes sense to me is that the files are hard linked
someplace, and I think I could persuade the techs at nomonthlyfees to fix
the problem if I could pinpoint it more exactly. Of course, I could be
wrong.
Thanks in advance for any advice!
Matthew Poe
Hi,
Anyone out there with AOL subscribers on your SmartList(s) not
receiving all your deliveries or maybe not being able to post
to your list from AOL?
Thanks and happy holidays!
--Paul T.
--
In article <v0313030db836032b2a4e(a)[192.168.123.10]>,
Charlie Summers <charlie(a)lofcom.com> writes:
> At 12:11 AM -0500 12/7/01, Remco Rijnders is rumored to have typed:
>
>> This is counter intuitive though. I know what it says and all that,
>> but it easily leads you to assume that the "uncomment this line" part
>> refers to the line just before it.
>
> It says pretty clearly to uncomment THIS line, not the line before it.
C programs often use the same text, but it means exactly the opposite
thing:
/* HAVE_BLURFL: uncomment this line if your system has the
blurfl() system call. */
/* #define HAVE_BLURFL */
The idiosyncratic syntax of procmail scripts makes the "uncomment this
line" text more ambiguous than it might otherwise be. Sorry, Charlie.
It sucks.
Currently my lists forward emails to be from those not on the accept list.
How can I have the list send them a message explaining how to subscribe.
I DO NOT want to enable auto subscribe for various reasons.
Thank you.
Jeff
mailto:Jeff@intrepid-video.com www.9-11-2001tragedy.com
FAX 1-413-280-0677
Intrepid Video & Electronics
Harrisburg, PA 17111
717-909-8844
www.intrepid-video.comwww.tech-repair.netwww.thetoolcaddy.com
hi,
On Thu, 20 Dec 2001 20:55:09 Irwin Lazar wrote:
> Folks, I'm having trouble tracing down a problem subscriber and
> I wanted to see if any list member could offer some tips. [...]
> is there any way to trace this below message back to a specific
> mailbox that can be removed?
>
if you have access to a linux/unix box you can try the program
"vrfy"
URL ftp://ftp.nikhef.nl/pub/network/vrfy.tar.Z
URL http://www.nikhef.nl/user/e07
which will trace an e-mail address through mail servers, proxies
and the like. It also allows for checking all e-mail addresses in
a file (check its documentation). Nonetheless, note that broken
servers could impede vrfy to complete its job.
For instance, a suitable command line could be,
$ vrfy -R -vvv -dHn someone(a)att.com
rcpt 'someone(a)att.com' at 'kcmsi1.att.com'
smtp phase connect
connecting to kcmsi1.att.com (192.128.134.69) port 25
connected to kcmsi1.att.com
smtp phase greeting wait
<<< 220 kcmsi1.proxy.att.com ESMTP AT&T IPNS/MSI-3.0 ; Fri, 21 Dec 2001
03:09:57 -0500 (EST)
>>> EHLO sermn02.uab.es
smtp phase EHLO wait
<<< 250-kcmsi1.proxy.att.com Hello [158.109.8.53], pleased to meet you
<<< 250-ENHANCEDSTATUSCODES
<<< 250-8BITMIME
<<< 250-SIZE 500000000
<<< 250-ONEX
<<< 250-XUSR
<<< 250 HELP
>>> VERB on
smtp phase VERB wait
<<< 502 5.7.0 Verbose unavailable
>>> MAIL From:<>
smtp phase MAIL wait
<<< 250 2.1.0 <>... Sender ok
>>> RCPT To:<someone(a)att.com>
smtp phase RCPT wait
<<< 250 2.1.5 <someone(a)att.com>... Recipient ok
2.1.5 <someone(a)att.com>... Recipient ok
>>> RSET
smtp phase RSET wait
<<< 250 2.0.0 Reset state
>>> QUIT
smtp phase QUIT wait
<<< 221 2.0.0 kcmsi1.proxy.att.com closing connection
and a more verbose one would be `vrfy -R -vvv -dHn someone(a)att.com`
which will interact will all possible mail exchangers.
Miquel
--
Miquel E Cabanas ------------------------------------------------------
SeRMN, Universitat Autonoma de Barcelona (Miquel.Cabanas(a)uab.es)
------------------------------------------o-oo--ooo---ooo--oo-o--------
Folks, I'm having trouble tracing down a problem subscriber and I wanted to
see if any list member could offer some tips. For the last several months
every message sent to my list has generated the below. I've e-mailed
postmaster(a)att.com and have not received any response. Short of removing
all 30-40 list members in the att.com domain, is there any way to trace
this below message back to a specific mailbox that can be removed?
Thanks in advance,
Irwin
----------------------
>X-Persona: <mplsforum>
>X-POP3-Rcpt: mplsrc12(a)mplsrc.com
>Received: (from mplsrc12@localhost)
> by host.secure4-hosting.net (8.10.2/8.10.2) id fBKJJLj27991
> for mplsrc12(a)mplsrc.com; Thu, 20 Dec 2001 14:19:21 -0500
>Date: Thu, 20 Dec 2001 14:19:21 -0500
>X-Authentication-Warning: host.secure4-hosting.net: mplsrc12 set sender to
>mpls-ops-request(a)mplsrc.com using -f
>X-From_: Thu Dec 20 14:19:19 2001
>Received: from kcmso1.proxy.att.com (kcmso1.att.com [192.128.133.69])
> by host.secure4-hosting.net (8.10.2/8.10.2) with ESMTP id
> fBKJJJp27960
> for <mpls-ops-request(a)mplsrc.com>; Thu, 20 Dec 2001 14:19:19 -0500
>Received: from attrh3i.attrh.att.com ([135.71.62.12])
> by kcmso1.proxy.att.com (AT&T IPNS/MSO-3.0) with ESMTP id
> fBKJJDn15282
> for <mpls-ops-request(a)mplsrc.com>; Thu, 20 Dec 2001 14:19:13
> -0500 (EST)
>Received: by attrh3i.attrh.att.com (5.5.029) id 3C069505004DF0E2 for
>mpls-ops-request(a)mplsrc.com; Thu, 20 Dec 2001 14:18:44 -0500
>Message-Id: <200112201918.RBQ13665(a)attrh3i.attrh.att.com>
>Old-Date: Thu, Dec 20 2001 14:18:39 EST
>From: MAILER-DAEMON(a)attrh3i.attrh.att.com
>To: mpls-ops-request(a)mplsrc.com
>Subject: Message status notification
>X-Diagnostic: Mail coming from a daemon, ignored
>X-Diagnostic: Possible loopback problem
>X-Envelope-To: mpls-ops-request
>
>The mail routing agent encountered the following class of error:
>
>No entries found in directory for query
>
>----- Original Message Text Follows -----
>
>Received: from wsscan.att.com (135.71.63.10) by attrh3i.attrh.att.com
>(5.5.029)
> id 3C069505004DF0C9; Thu, 20 Dec 2001 14:18:37 -0500
>Received: by wsscan.att.com; id OAA06742; Thu, 20 Dec 2001 14:18:55 -0500
>(EST)
>Received: from almsi1.proxy.att.com(192.168.109.69) by
>cyrus0.wsscan.att.com via csmap (V4.1)
> id srcAAAisaOjn; Thu, 20 Dec 01 14:18:54 -0500
>Received: from host.secure4-hosting.net ([209.239.41.31])
> by almsi1.proxy.att.com (AT&T IPNS/MSI-3.0) with ESMTP id
> fBKJIwG10837;
> Thu, 20 Dec 2001 14:18:58 -0500 (EST)
>Received: (from mplsrc12@localhost)
> by host.secure4-hosting.net (8.10.2/8.10.2) id fBKJIva27924;
> Thu, 20 Dec 2001 14:18:57 -0500
>Resent-Date: Thu, 20 Dec 2001 14:18:57 -0500
>X-Authentication-Warning: host.secure4-hosting.net: mplsrc12 set sender to
>mpls-ops-request(a)mplsrc.com using -f
