Pat, It may not be a Rootsweb problem. My cousin switched from AT & T to gmail and set up a pop forward so her AT & T mail was to go to her mew gmail account. The other day she looked at her old A T & T account and there were a bunch of messages in there that had never forwarded. Janet On Mon, Nov 5, 2018 at 10:43 PM Pat Asher <pasher@ee.net> wrote: > AGAIN, I am no longer receiving list mail at my att.net addresses. > The posts from me at my att.net address are in the archives, but I am > not receiving them as list posts, I have checked my webmail for posts > held as spam and they are not there. > > Anyone else noticed a problem again with ATT and the baby bells? > > > Pat Asher > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe > https://lists.rootsweb.com/postorius/lists/listowners@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb > community >

Hi Keith I had to google INAL ;-) Can you expand on what you mean by not relaying via gmail? I use gmail and as far as I can see its working as it should (unlike it seems like many others) I agree that there are certain "features" imposed upon us like gmail not accepting copies of your own posts (or is that what you mean in your post?) In their words "to stop clutter in my inbox" I think I should be the judge of that not they ;-) Nivard Ovington in Cornwall (UK) On 06/11/2018 07:35, Keith Meintjes wrote: > I don't know about ATT, but I use gmail. It is too clever by half. > > If I send a message to the list I manage (South-Africa), gmail blocks the > relay of that message from Rootsweb. > It's not a Rootsweb problem. If others send messages to the list, the > relays come through fine. > > INAL (I am not a Luddite), but it seems we are being inundated by useless > "features" that are infuriatingly > complex to figure out. > > Keith

I don't know about ATT, but I use gmail. It is too clever by half. If I send a message to the list I manage (South-Africa), gmail blocks the relay of that message from Rootsweb. It's not a Rootsweb problem. If others send messages to the list, the relays come through fine. INAL (I am not a Luddite), but it seems we are being inundated by useless "features" that are infuriatingly complex to figure out. Keith On Mon, Nov 5, 2018 at 6:33 PM Bony, Jan <jbony@ochoco.com> wrote: > Pat, did you receive the post to LO that you made, or the replies? I'm > doing a reply to list and as a CC directly to you... It might help Anne > when she digs back into the problem... > > Jan B > > On Mon, Nov 5, 2018 at 2:42 PM, Pat Asher <pasher@ee.net> wrote: > > > AGAIN, I am no longer receiving list mail at my att.net addresses. The > > posts from me at my att.net address are in the archives, but I am not > > receiving them as list posts, I have checked my webmail for posts held as > > spam and they are not there. > > > > Anyone else noticed a problem again with ATT and the baby bells? > > > > > > Pat Asher > > > > _______________________________________________ > > Email preferences: http://bit.ly/rootswebpref > > Unsubscribe https://lists.rootsweb.com/postorius/lists/listowners@rootsw > > eb.com > > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > > https://ancstry.me/2HDBym9 > > Rootsweb Blog: http://rootsweb.blog > > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb > > community > > > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe > https://lists.rootsweb.com/postorius/lists/listowners@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb > community > -- +1.248.891.6434 Michigan, USA (Eastern Time)

At 06:08 PM 11/5/2018, John Taylor wrote: >I managed 6 lists. I sent an announcement to all 6 the other day. >One message showed up in about 30 mins, the second message took over >3 hours. The other 4 lists have not come through although all of >them show up in the archives. I am not on ATT. Administrative mail (notices of subs, unsubs, held posts, etc.) are being delivered to my ATT address. Posts are not. Today is when I discovered I had not received several posts starting yesterday afternoon. Something changed then. Guessing it is a header problem i.e. a disparity between the poster's email vs.the sender, rootsweb.com Pat Asher

Pat, did you receive the post to LO that you made, or the replies? I'm doing a reply to list and as a CC directly to you... It might help Anne when she digs back into the problem... Jan B On Mon, Nov 5, 2018 at 2:42 PM, Pat Asher <pasher@ee.net> wrote: > AGAIN, I am no longer receiving list mail at my att.net addresses. The > posts from me at my att.net address are in the archives, but I am not > receiving them as list posts, I have checked my webmail for posts held as > spam and they are not there. > > Anyone else noticed a problem again with ATT and the baby bells? > > > Pat Asher > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe https://lists.rootsweb.com/postorius/lists/listowners@rootsw > eb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb > community >

I managed 6 lists. I sent an announcement to all 6 the other day. One message showed up in about 30 mins, the second message took over 3 hours. The other 4 lists have not come through although all of them show up in the archives. I am not on ATT. John Taylor On 11/5/2018 5:02 PM, Mike Flannigan wrote: > > I am definitely receiving some of them. > Just last night I was corresponding with MOPerry. > Plus I am receiving from at least 3 other lists - > all in the past 3 days. > > I'm thinking it is working fine for me. > I am testing a few other lists with this e-mail. > > > > Mike > > > > On 11/5/2018 4:42 PM, Pat Asher wrote: >> AGAIN, I am no longer receiving list mail at my att.net addresses. >> The posts from me at my att.net address are in the archives, but I am >> not receiving them as list posts, I have checked my webmail for posts >> held as spam and they are not there. >> >> Anyone else noticed a problem again with ATT and the baby bells? >> >> >> Pat Asher > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe > https://lists.rootsweb.com/postorius/lists/listowners@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY  Terms and Conditions: > https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal > RootsWeb community

I am definitely receiving some of them. Just last night I was corresponding with MOPerry. Plus I am receiving from at least 3 other lists - all in the past 3 days. I'm thinking it is working fine for me. I am testing a few other lists with this e-mail. Mike On 11/5/2018 4:42 PM, Pat Asher wrote: > AGAIN, I am no longer receiving list mail at my att.net addresses. The > posts from me at my att.net address are in the archives, but I am not > receiving them as list posts, I have checked my webmail for posts held > as spam and they are not there. > > Anyone else noticed a problem again with ATT and the baby bells? > > > Pat Asher

AGAIN, I am no longer receiving list mail at my att.net addresses. The posts from me at my att.net address are in the archives, but I am not receiving them as list posts, I have checked my webmail for posts held as spam and they are not there. Anyone else noticed a problem again with ATT and the baby bells? Pat Asher

Seems I read they had the settings set to approve automatically and were getting request to approve anyways. I will re read that. Could have got the point of that post possibly miss read. If so. My bad. On Sat, Nov 3, 2018, 1:47 PM Nivard Ovington <ovington.one@gmail.com wrote: > Not sure if you do it just to wind people up Dan > > The question posed was "I am getting requests to confirm subscriptions > though they are supposed to be set to be approved automatically." > > I gave a reason why, when the subscription policy was set to "Confirm" > > ie there should be no need for admin intervention but sub requests are > still held because the would be subscriber hasn't confirmed their request > > So there is no problem (if you understand whats happening) and the > system is working correctly, in so far as, if the would be subscriber > confirms the email (if they get it) they get subscribed > > Nivard Ovington in Cornwall (UK) > > On 03/11/2018 16:16, Dan M wrote: > > Looked like he completely missed the requested topic. > > "Set to post automatically but asking for confirm" looks like its still a > > core issue. Program not working. > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe > https://lists.rootsweb.com/postorius/lists/listowners@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb > community >

Yes, but I moderate an unrelated list where the spammers will subscribe and immediately then post a message. If they have to wait and then confirm a subscription, they never do. Keith On Sat, Nov 3, 2018 at 7:48 PM Mike Flannigan <mikeflan@att.net> wrote: > > Sounds like everybody may be right here, but I want > to point out that most people who subscribe do so > to immediately post a message. Those who don't > successfully subscribe, but then try to post a > message, are probably very confused when they receive > a rejection notice of some kind. > There is probably nothing we can do about that. > > > Mike > > > On 11/3/2018 6:37 PM, Keith Meintjes wrote: > > I understand. > > > > If I see subscription requests I will simply approve them. > > > > That seems much simpler than coaching wannabe subscribers on how to > confirm > > their subscription requests. > > > > Keith > > > > > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe > https://lists.rootsweb.com/postorius/lists/listowners@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb > community > -- +1.248.891.6434 Michigan, USA (Eastern Time)

Sounds like everybody may be right here, but I want to point out that most people who subscribe do so to immediately post a message.  Those who don't successfully subscribe, but then try to post a message, are probably very confused when they receive a rejection notice of some kind. There is probably nothing we can do about that. Mike On 11/3/2018 6:37 PM, Keith Meintjes wrote: > I understand. > > If I see subscription requests I will simply approve them. > > That seems much simpler than coaching wannabe subscribers on how to confirm > their subscription requests. > > Keith > >

I understand. If I see subscription requests I will simply approve them. That seems much simpler than coaching wannabe subscribers on how to confirm their subscription requests. Keith On Sat, Nov 3, 2018 at 4:47 PM Nivard Ovington <ovington.one@gmail.com> wrote: > Not sure if you do it just to wind people up Dan > > The question posed was "I am getting requests to confirm subscriptions > though they are supposed to be set to be approved automatically." > > I gave a reason why, when the subscription policy was set to "Confirm" > > ie there should be no need for admin intervention but sub requests are > still held because the would be subscriber hasn't confirmed their request > > So there is no problem (if you understand whats happening) and the > system is working correctly, in so far as, if the would be subscriber > confirms the email (if they get it) they get subscribed > > Nivard Ovington in Cornwall (UK) > > On 03/11/2018 16:16, Dan M wrote: > > Looked like he completely missed the requested topic. > > "Set to post automatically but asking for confirm" looks like its still a > > core issue. Program not working. > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe > https://lists.rootsweb.com/postorius/lists/listowners@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb > community > -- +1.248.891.6434 Michigan, USA (Eastern Time)

Not sure if you do it just to wind people up Dan The question posed was "I am getting requests to confirm subscriptions though they are supposed to be set to be approved automatically." I gave a reason why, when the subscription policy was set to "Confirm" ie there should be no need for admin intervention but sub requests are still held because the would be subscriber hasn't confirmed their request So there is no problem (if you understand whats happening) and the system is working correctly, in so far as, if the would be subscriber confirms the email (if they get it) they get subscribed Nivard Ovington in Cornwall (UK) On 03/11/2018 16:16, Dan M wrote: > Looked like he completely missed the requested topic. > "Set to post automatically but asking for confirm" looks like its still a > core issue. Program not working.

Subscription policy is a bit hard to find: Go to your list Go to subscription requests and see that you have nothing pending Go to Settings/ list settings [ See > List Identity; Automatic Responses; Custom messaging; Message size; message acceptance; *Subscription policy]* Go to Subscription policy and you will get a page with just a single item that indicates how to handle new subscriptions. Choose from 4 choices: Open: Subscriptions are added automatically Confirm: Subscribers need to confirm the subscription using an email sent to them Moderate: Moderators will have to authorize each subscription manually. Confirm then Moderate: First subscribers have to confirm, then a moderator needs to authorize. *Save any changes* Janet

One thing struck me in the process of subscribing & unsubscribing In the subscribing process using "Confirm" there is an email sent to the prospective subscriber To which they have to respond to confirm the subscribe request They receive an email from listname-confirm which they have to reply to However each time a second email is received, subject line "The results of your email commands" , the body of the message ends with the word "Done" You get two similar messages when you unsubscribe I wonder if some would be subscribers receive that second message and think it means its completed Nivard Ovington in Cornwall (UK)

You are quite correct Malcolm There is no visible difference when the subscription policy is set to Confirm then Moderate, before or after the would be subscriber replies to confirm So how would an admin know they had confirmed the subscription? At least with "Confirm" set, if the email address is still in "Subscription requests" it means the would be subscriber has not confirmed the request to subscribe Nivard Ovington in Cornwall (UK) > I fear you are right Nivard, I think I have seen this happen. > > I say 'fear' because it is potentially dangerous. If a list is set for > subscription requests to require both confirmation by the requestor > *and* approval by the moderator, then it appears to me that there is no > way for the moderator to tell whether the confirmation has been done. It > is *very* important that the moderator knows that so they don't approve > a malicious subscription request involving a faked address. > > Malcolm.

On Sat, 03 Nov 2018 14:09:22 -0000, Nivard Ovington <ovington.one@gmail.com> wrote: > If you have "Subscription Policy" set for "Confirm" > > The would be subscriber has to respond to the subscribe request email > that comes to them > > If they don't the subscription request will sit in "Subscription > requests" until they confirm the subscribe or the admin actions it I fear you are right Nivard, I think I have seen this happen. I say 'fear' because it is potentially dangerous. If a list is set for subscription requests to require both confirmation by the requestor *and* approval by the moderator, then it appears to me that there is no way for the moderator to tell whether the confirmation has been done. It is *very* important that the moderator knows that so they don't approve a malicious subscription request involving a faked address. Malcolm. > If the would be subscriber confirms the email the subscribe request > disappears > > Or the admin can manually Accept Reject or Discard the subscription > request > > Could it be that the confirmation email sent to the would be subscriber > has ended up in spam ? > > To my mind if the email address looks okay the admin can email the would > be subscriber to ask if they meant to subscribe (they may be blissfully > unaware they are not subscribed) > > If the email address looks unlike a potential researcher the admin can > discard it > > Nivard Ovington in Cornwall (UK) > > On 03/11/2018 02:30, Keith Meintjes wrote: >> Well, if you want an issue, I am getting requests to confirm >> subscriptions >> though they are >> supposed to be set to be approved automatically. >> Keith > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe > https://lists.rootsweb.com/postorius/lists/listowners@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb > community -- Malcolm Austen <malcolm.austen@weald.org.uk>

Looked like he completely missed the requested topic. "Set to post automatically but asking for confirm" looks like its still a core issue. Program not working. On Sat, Nov 3, 2018, 9:10 AM Keith Meintjes <kmeintjes@gmail.com wrote: > Nivard, > > Thank you for the explanation. > > Keith > > On Sat, Nov 3, 2018 at 10:09 AM Nivard Ovington <ovington.one@gmail.com> > wrote: > > > If you have "Subscription Policy" set for "Confirm" > > > > The would be subscriber has to respond to the subscribe request email > > that comes to them > > > > If they don't the subscription request will sit in "Subscription > > requests" until they confirm the subscribe or the admin actions it > > > > If the would be subscriber confirms the email the subscribe request > > disappears > > > > Or the admin can manually Accept Reject or Discard the subscription > request > > > > Could it be that the confirmation email sent to the would be subscriber > > has ended up in spam ? > > > > To my mind if the email address looks okay the admin can email the would > > be subscriber to ask if they meant to subscribe (they may be blissfully > > unaware they are not subscribed) > > > > If the email address looks unlike a potential researcher the admin can > > discard it > > > > Nivard Ovington in Cornwall (UK) > > > > On 03/11/2018 02:30, Keith Meintjes wrote: > > > Well, if you want an issue, I am getting requests to confirm > > subscriptions > > > though they are > > > supposed to be set to be approved automatically. > > > > > > Keith > > > > _______________________________________________ > > Email preferences: http://bit.ly/rootswebpref > > Unsubscribe > > https://lists.rootsweb.com/postorius/lists/listowners@rootsweb.com > > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > > https://ancstry.me/2HDBym9 > > Rootsweb Blog: http://rootsweb.blog > > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb > > community > > > > > -- > +1.248.891.6434 > Michigan, USA (Eastern Time) > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe > https://lists.rootsweb.com/postorius/lists/listowners@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb > community >

Nivard, Thank you for the explanation. Keith On Sat, Nov 3, 2018 at 10:09 AM Nivard Ovington <ovington.one@gmail.com> wrote: > If you have "Subscription Policy" set for "Confirm" > > The would be subscriber has to respond to the subscribe request email > that comes to them > > If they don't the subscription request will sit in "Subscription > requests" until they confirm the subscribe or the admin actions it > > If the would be subscriber confirms the email the subscribe request > disappears > > Or the admin can manually Accept Reject or Discard the subscription request > > Could it be that the confirmation email sent to the would be subscriber > has ended up in spam ? > > To my mind if the email address looks okay the admin can email the would > be subscriber to ask if they meant to subscribe (they may be blissfully > unaware they are not subscribed) > > If the email address looks unlike a potential researcher the admin can > discard it > > Nivard Ovington in Cornwall (UK) > > On 03/11/2018 02:30, Keith Meintjes wrote: > > Well, if you want an issue, I am getting requests to confirm > subscriptions > > though they are > > supposed to be set to be approved automatically. > > > > Keith > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe > https://lists.rootsweb.com/postorius/lists/listowners@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb > community > -- +1.248.891.6434 Michigan, USA (Eastern Time)

If you have "Subscription Policy" set for "Confirm" The would be subscriber has to respond to the subscribe request email that comes to them If they don't the subscription request will sit in "Subscription requests" until they confirm the subscribe or the admin actions it If the would be subscriber confirms the email the subscribe request disappears Or the admin can manually Accept Reject or Discard the subscription request Could it be that the confirmation email sent to the would be subscriber has ended up in spam ? To my mind if the email address looks okay the admin can email the would be subscriber to ask if they meant to subscribe (they may be blissfully unaware they are not subscribed) If the email address looks unlike a potential researcher the admin can discard it Nivard Ovington in Cornwall (UK) On 03/11/2018 02:30, Keith Meintjes wrote: > Well, if you want an issue, I am getting requests to confirm subscriptions > though they are > supposed to be set to be approved automatically. > > Keith