The token is unique to each poster, and will differ from server to server. There is no way to know what the token for [log in to unmask] is going to be on this or that LISTSERV installation. It would have been much easier to implement something like ‘joe%yahoo.com’ but that would have opened the door to abuse. As implemented, you can only contact a Yahoo user via the [log in to unmask] address if the Yahoo user in question has submitted a posting and that posting has been accepted for distribution. Typically one would have an incoming rule directing *-request to LISTSERV (and it is automatic on Windows). Eric From: LISTSERV List Owners' Forum [mailto:[log in to unmask]] On Behalf Of Wayne T Smith Sent: Wednesday, April 23, 2014 13:18 To: [log in to unmask] Subject: Re: Problem now with From: *@aol.com On Tue, Apr 22, 2014 at 9:12 PM, Ben Parker <[log in to unmask]<mailto:[log in to unmask]>> wrote , in part : -If From: address re-write is necessary, you can see the format: [token][log in to unmask]<mailto:[log in to unmask]>. The numerical [token] is unique to each LISTSERV instance. I'm wondering a couple of things, which no doubt will become obvious soon ... * Is the token fixed for a server or fixed for a server-poster combination? * If the latter, how does the Listserv postmaster/installer have his/her mail facility direct incoming mail to such a generic address (to Listserv)? Cheers, Wayne ________________________________ To unsubscribe from the LSTOWN-L list, click the following link: http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTOWN-L&A=1 ############################ To unsubscribe from the LSTOWN-L list: write to: mailto:[log in to unmask] or click the following link: http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTOWN-L&A=1