[Date Prev][Date Next][Thread Prev][Thread Next]   [Date Index] [Thread Index] [Author Index

Re: Free-will vs. listserver



On Tue, 11 Nov 2003 22:07:02 -0500, Tim Gwinn <***> wrote:

>>
>> First, ... help!   Am not receiving postings thru email (my
>> preferred way to
>> post/read) so some advice from the knowledgable would be appreciated. :-)
>
>
>Hmmm, I'm not sure why you are not receiving posts by email. Usually if
>there an error sending a message or a message "bounces" back from an ISP, I
>will receive an error report. I have not received any error reports tonite.

Does everyone have to check the "to the list" box when they write
a post or reply?  I looked at my "subscriber's corner" settings
and 'regular' email was selected.  But I don't get emails of anyones posts
except my own.

As far as other lists, Listserv also carries Complex-M which I'm
on and the settings are identical with the Rosen settings, and I
do get emails from it.

>I reviewed your subscription setup and it looks perfectly normal. After
>subscribing, did you receive the automated "Welcome" email?
>
>Assuming you are receiving email from other sites, one possibility that
>comes to mind is that your ISP might possibly be blocking all email from
>lsoft.com. This has been an intermittent yet recurring problem with some
>ISPs who erroneously confuse lsoft email with spam email, and then block the
>sending domain or IP address.In those cases, the email is not necessarily
>always bounced back; instead, the ISP may just flush it and I would never
>see an error.

I use SBC/Prodigy.

>Try emailing *** with INFO REFCARD as the only text
>in the body of the message.

Will do.

> That command does not even require you to be a
>subscriber. It should email you back with a FAQ of list commands. If that
>works, it may mean your subscription has something odd going on with it, so
>we might have to delete it and re-add it. If that doesn't work, then there
>is a more pervasive problem between the listserver, your ISP, and/or your
>email system.
>
>Regards,
>Tim

Thanks Tim,   Jamie