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
Ben Parker <[log in to unmask]>
Thu, 7 Jun 2012 19:10:27 -0600
text/plain (128 lines)
On Fri, 8 Jun 2012 09:29:55 +1000, Jeff Allison
<[log in to unmask]> wrote:

>So I take it that's a no 

No, it's just that what you ask is normally A Really Bad Idea™.

After all, your website is www.domain.com and I would bet the name of the
server itself is probably mail.domain.com and maybe you have an ftp server
that is ftp.domain.com, etc.  All of these different names identify a
particular or expected function of traffic to/from that kind of server.  So
when you go against the grain, things will be (much) harder.

-------------------
Changing the domain name that LISTSERV uses for its ougoing mails is quite
simple.  Just change the value for NODE= in your site.cfg/go.user file.  Note
that MYDOMAIN= may also need changing.  (The first-listed value in MYDOMAIN=
must be the same as whatever is in NODE=.  Additional domain names the server
should also recognize may follow in any order.)

The normal ways to do this are  (note different OS syntax)

(Windows site.cfg)
...
NODE=domain.com
MYDOMAIN=%NODE% host.domain.com
...

(unix go.user)
...
NODE="domain.com"
MYDOMAIN="$NODE host.domain.com"
...

Stop and restart LISTSERV (and SMTPL if on Windows).

---------------

The problem however is not the domain.com used when sending out the email but
anciallary addresses needed for other LISTSERV functions responding to
incoming mail like handling bounces, List Owner generic address,
special-action (sub/unsub) addresses, etc.  LISTSERV must be correctly
configured so ALL of these functions work properly or you will have
never-ending headaches.

These are the 9 email address variants necessary FOR EACH LISTNAME:

necessary email aliases

 [log in to unmask]            list address for posting 
 [log in to unmask]    fwd to list owner
 [log in to unmask]      for non-delivery bounces
 owner-listname*user**example*[log in to unmask]  PROBE format bounces

special action aliases

 [log in to unmask]  special action (subscribe)
 [log in to unmask]  special action (unsubscribe)
 [log in to unmask]  special action (unsubscribe)
 [log in to unmask]  special action (email archives search)
 [log in to unmask]  special action (email archives search results)

You also need 3 addresses for LISTSERV itself:

 [log in to unmask]            listserv address for commands
 [log in to unmask]    fwd to server admin
 [log in to unmask]      for non-delivery bounces of non-list mail

And as Paul pointed out, you have the special case of PROBE-style bounce
addresses:

 owner-listname*user**example*[log in to unmask]  PROBE format bounces

which could mean a potentially infinite number of address aliases you have to
create and maintain along with all the subscribers to all of your lists.  
(I did say that this is A Really Bad Idea™ and a LOT of work.)
You are already doing this with your 'jiggery pokey' work, which you want to
replace with other 'jiggery pokey' work.

All of the above problems go away if you simply route mail to LISTSERV on the
domain part of the address (right of @):  *@host.domain.com
Then LISTSERV will manage all of that shenannigans, which you are paying for
it to do anyway.

------------------
You haven't said what OS your server is and that makes a difference in how to
do this Bad Idea.

If on unix/linux, then this is somewhat easier to do.  
On this OS, you can use the command line command (as root) in ~/home/listserv

 make list name=listname

This uses the Makefile to create all of the above email aliases, runs
'newaliases' (to hash them) and stops/restarts sendmail (assuming you are
runing sendmail).  You have to repeat this process every time you create a new
list.

See
http://www.lsoft.com/manuals/16.0/install/LISTSERV16.0_InstallManual_UNIX.htm#_Toc290567953
for how to configure you server for sendmail, postfix, or qmail in order to
handle the PROBE format email bounces.  There is also a procmail+sendmail
script method posted to LSTSRV-L some years ago.

-------------------
On Windows, prayer is about the only recourse.  You can create the standard
email aliases easily enough, but I know of no script that will do this easily
for you like the above L-Soft script on Unix/Linux.  So you will have to
create 9 x (number_of_lists) + 3 = X aliases manually.  Make some coffee and
get started.  

Unfortunately I know of no easy way to handle the PROBE format email bounces.
Simply ignoring them is not a responsible way to run a server, so sending them
to a 'dead-letter' mailbox followed by some manual processing is the only
method that comes to mind.  But others may have more helpful suggestions.  (I
think I did say that this is A Really Bad Idea™ and a LOT of work.)

Hopefully that gives you some clues how to proceed, or some ammunition to use
to convince the 'powers-that-be' that this isn't really such a good idea after
all.

############################

To unsubscribe from the LSTSRV-L list:
write to: mailto:[log in to unmask]
or click the following link:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=LSTSRV-L&A=1

ATOM RSS1 RSS2