Re: [PLUG] Understanding where e-mails can get lost

2017-06-15 Thread Rich Shepard
On Thu, 15 Jun 2017, Michael wrote: > They tell you the messages bounce. Ask one of them to forward you a copy > of the bounce message. That will tell you why your system bounced it. You > can then examine log files with a reference point. Michael, I've asked for a copy of the bounce message,

Re: [PLUG] Understanding where e-mails can get lost

2017-06-15 Thread Michael
On 2017-06-14 10:27, Rich Shepard wrote: > I'm a member of an organization that sends a weekly newsletter to > members > via e-mail every Tuesday at 8:00pm PDT (although their mail server's > clock > is set to UTC). They undoubtably run Windows on all their machines and > I'm > assuming they use

Re: [PLUG] Understanding where e-mails can get lost

2017-06-14 Thread Michael Barnes
I have often seen this with "home-brew" mass mailings, especially from Windows systems. I have had very good results with MailChimp for this kind of thing. They have all kinds of tools and features. For smaller quantities, the service is free. I especially like the user management. People can subsc

Re: [PLUG] Understanding where e-mails can get lost

2017-06-14 Thread wes
> > >Is there anything I can run from here to try to find why these > newsletters > never arrive while other messages have no problems? > > Rich > newsletters and other automated mailings are often sent through a third party provider, which introduces the complexity of validating that provider

[PLUG] Understanding where e-mails can get lost

2017-06-14 Thread Rich Shepard
I'm a member of an organization that sends a weekly newsletter to members via e-mail every Tuesday at 8:00pm PDT (although their mail server's clock is set to UTC). They undoubtably run Windows on all their machines and I'm assuming they use the MS equivalent of 'at' to send the messages while n