Dirk, Thank you very much for the full explanation about the email recipient list. My errors with google were intermittent. Some messages went through and others did not. Under Setup, I have ticked the box for separating the messages by recipient. So it seems likely that now they will all go through. About the 302 issue, yes, the timeout was definitely longer than the time it took to get the 302 response, say 25ms versus probably 4ms. I am downloading the latest beta and will put that in place. Great support <g>.
Ann On 05/15/2013 5:16 AM, Dirk Bulinckx wrote: > By default a mail is send as ONE mail TO severl addresses. There is > however in the SETUP-ALERTS-SMTP-PRIMARY (and ALTERNATE) an option to send > multiple mails to multiple addresses, meaning the mails are send to each > person individualy. > You need to separate the addresses (might it be direct addresses or people > or teams) by comma's. > The way the alert is send is not different if you use a > team/person/direct-address. Using PEOPLE and TEAMS has other reasons. > > > About the 302 issue...the way the timeout works in an HTTP check (and that > would be a way to get out of that loop) is that IF there is more then > <timemout> time between the different results received from the server then > we get the timeout else we just follow the redirects and could indeed get > into a loop. > > > > > Dirk Bulinckx > Servers Alive - http://www.woodstone.nu > StellarDNS (DNS Hosting) - http://www.stellardns.com > > -----Original Message----- > From: Servers Alive Discussion List [mailto:[email protected]] On Behalf > Of Ann Lynnworth > Sent: Wednesday, May 15, 2013 2:16 AM > To: Servers Alive Discussion List > Subject: [SA-list] SMTP configuration for multiple recipients; 302 redirect > loop > > Hi, > > Main question: > Could you clarify the syntax for sending one email message to multiple > recipients? In particular, is the required separator a comma? Is semi-colon > allowed or only comma? Are plain-text recipients such as > [email protected],[email protected] allowed or is it necessary to combine "person" > or "team" references? Does the use of plain-text email addresses versus > "person" relate in any way to the way the To: and/or Cc: mail headers are > generated? > > The reason I ask is that I have been having trouble queuing emails to > multiple recipients whose domains are hosted with gmail. Here is an example > error as reported back to me from the ISP (Sonic.net) sitting between my > Servers Alive machine and google: > > May 14 15:09:18 b.mail.sonic.net sm-mta[6727]: r4EM9HlP006714: > to=<[email protected]>, delay=00:00:01, xdelay=00:00:01, mailer=esmtp, > pri=180533, relay=aspmx.l.google.com. [74.125.141.27], dsn=4.3.0, > stat=Deferred: 451-4.3.0 Multiple destination domains per transaction is > unsupported. > > My email message configuration includes 3 parties, of which 2 are on the > same domain, e.g. snip.com in the text above. I had to change the domain > name for privacy reasons but otherwise that error message is exact. > > This rule about multiple destination domains seems to be a new rule from > gmail since maybe May 2012. ( > https://productforums.google.com/forum/?fromgroups=#!topic/gmail/qQ3vDWouukk > ) I only ran into it now because of the need to alert two mailboxes at the > same domain. > > The reason I'm asking about the syntax is because I'm wondering whether > there is any way that I can control the number of separate To: or Cc: > headers generated, or whether I really have to create separate alerts when > there need to be multiple recipients at the same google-hosted domain. > > > Fyi: > Yesterday I ran into an unrelated problem which essentially hung Servers > Alive - rendered it unable to check every URL in its list. That was: > multiple checks running into repeat 302 bounce loops - bouncing back to the > same URL that it was trying to test. This was essentially a problem that > happened on multiple servers, multiple sites, all at once. However I wanted > to let you know the SA did not really recover. I tried stopping and > starting the service, and rebooting the whole machine, and none of that > helped. S.A. would get through a few requests but literally got stuck, > leaving the majority of the URLs "unchecked since..." 4 hours time. > Eventually I realized the root cause, fixed the 302 problem, and then of > course SA worked as per normal. > > Best, > > Ann > > To unsubscribe send a message with UNSUBSCRIBE in the subject line to > [email protected] If you use auto-responders (like out-of-the-office > messages), make sure that they are not sent to the list nor to individual > members. Doing so will cause you to be automatically removed from the list. > > To unsubscribe send a message with UNSUBSCRIBE in the subject line to > [email protected] > If you use auto-responders (like out-of-the-office messages), make sure that > they are not sent to the list nor to individual members. Doing so will cause > you to be automatically removed from the list. > > . > To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list.
