LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Al Iverson <[log in to unmask]>
Sat, 15 Dec 2001 16:27:26 -0600
text/plain (58 lines)
Ballew Kinnaman wrote:
>
> Does your front end do a confirmation step,
> to be sure LISTSERV can communicate with
> the new account e-mail address? [probably not]

Yes, actually, it does include a successful and working closed-loop opt-in.

> So now we see that what you really want,
> maybe, is a little warning flag to come up and
> say,
>
> "Are you sure you want to
>
> ADD [log in to unmask] Idiot Admin?
>
> To prevent mail loops, the subscriber with this
> account will be unable to communicate with
> LISTSERV. You will be required to handle all
> account changes *for* this account. Are
> you sure you want to create this disabled
> account?"

Could you explain on how forwarding mail from administrator@anywhere to
the site owner mailbox prevents mail loops?

My concern is actually that if Listserv considers administrator@ to be a
reserved username, then it should implement restrictions upon use of
that email address equally.

There's an implicit understanding that any address imported into a
LISTSERV list, via any method, for any reason, is likely to receive mail
from that LISTSERV. There's also an implicit understanding that the
user, who received that mail, should be able to respond to the LISTSERV
to modify settings, unsubscribe, post to a list, whatever. What you're
saying is that's simply not the case, and not expected to be the case,
*unless* the user subscribes directly via LISTSERV.

I can't find any reference to Administrator being a reserved email
address in RFC, and it doesn't seem to be restricted or reserved in the
two mail server packages I'm most familiar with Sendmail and Postfix. I
could quite easily and successfully receive, read, reply to, and sign up
for lists with the email address [log in to unmask], and have
absolutely no issue or concern about a security risk for doing so, on
any number of platforms, using any number of mail clients.

Thanks for the lecture, however misplaced it may be, but I'm not a
spammer, and in fact, I'm a long time advocate of end user control over
what mail he or she receives, long standing member of the anti-spam
community, and creator of multiple successful mail blocking lists.

Best regards,
Al Iverson

--
Al Iverson -- http://www.radparker.com -- Minneapolis, Minnesota, USA
Support Minnesota Jazz -- Disclaimer: All of my opinions are mine alone.

ATOM RSS1 RSS2