Home >> Support Board

Support Board

Date/Time: Wed, 15 May 2024 21:00:52 +0000

How to Post a Message for Support

[Locked] - Email Alerts

View Count: 3321

[2019-01-07 07:24:20] #1 [Go To First Post]
User78442 - Posts: 260
My email alerts have stopped working. I've tested the address and it works. please advise

[2019-01-07 08:20:15] #2 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
These are always external email delivery problems which are not within our control. Refer to: General Settings Window: E-mail Notifications for Alerts Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2019-01-07 08:20:26

[2019-01-07 12:40:33] #3 [Go To First Post]
User78442 - Posts: 260
Alert log said message sent. Please check SC end that you are delivering to trade.alert@interx.co

[2019-01-07 15:31:10] #4 [Go To First Post]
Sierra Chart - Max - Posts: 5614
From the email logs: relay=interx.co[188.65.115.132]:25, delay=7.7, delays=0.01/0.02/0.24/7.5, dsn=2.0.0, status=sent This indicates that the email server "interx.co" accepted the email. Sierra Chart Support

[2019-01-08 05:45:20] #5 [Go To First Post]
User78442 - Posts: 260
can you please tell me the SC address from which you are sending emails. I want to ensure that mails from this address are not treated as spam.

[2019-01-08 20:20:38] #6 [Go To First Post]
Sierra Chart - Max - Posts: 5614
The email address is alerts@sierrachart.com Sierra Chart Support

[2019-01-14 06:27:09] #7 [Go To First Post]
User78442 - Posts: 260
I've tested this to death my end. I've changed the email on SC to my main james.pape@interx.co address - no cigar. Can you please check one last time as it still says you are sending the alert. thanks, I'm really frustrated as it was working great a few weeks ago...

[2019-01-14 06:47:15] #8 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
You are going to be frustrated because email delivery is simply just not reliable especially due to other users sending lots of alert messages and causing domains to block the emails. Use another email address. Set up your own domain. And set up your own mail server. We are not going to check. Maybe we should set up another domain for alerts, and sell email addresses. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2019-01-14 06:48:47

[2019-01-14 08:00:23] #9 [Go To First Post]
User78442 - Posts: 260
This is my domain. Please see the recent response from the hosting provider - They see NO mails from Sierra Chart. Please confirm that mails are being sent your end... ###~~~--- Please reply ABOVE this line ---~~~### Hi James, Thank you for contacting us on this matter. I have tested your mail account and managed to send/receive a message with no issues. Also, checking the server logs, there are no records of any delivery failed emails from alerts@sierrachart.com. Would you please, test again from your end and let us know in case you are not able to receive ? Kind regards, Martin G. -------------------------------- Ticket history -------------------------------- From: James Bernard Pape <james.pape@jbpconsult.com> At: 14/Jan/2019 07:13 Opened from client area by 178.196.22.220 Historically this mail address worked. It accepted alerts (emails) from alerts@sierrachart.com. A few weeks ago this stopped working. Can you please investigate where/what is happening at the domain end to these emails from alerts@sierrachart.com as they (SierraChart) have checked and they are sending and not seeing any return bounces...

[2019-01-15 07:00:35] #10 [Go To First Post]
User78442 - Posts: 260
Can you please check your alert server. My domain techs (not a stupid trader) are telling me that no alerts are coming to the interx.co domain from SC. This domain is not used by anyone but me for minimal daily traffic.

[2019-01-15 07:35:23] #11 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Okay we will check. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing

[2019-01-15 15:11:27] #12 [Go To First Post]
Sierra Chart - Max - Posts: 5614
Your email server is now blocking our alerts server: Jan 15 15:07:19 58e53c9ca92a postfix/smtp[15574]: connect to interx.co[188.65.115.132]:25: Connection timed out Jan 15 15:07:19 58e53c9ca92a postfix/smtp[15605]: connect to interx.co[188.65.115.132]:25: Connection timed out Jan 15 15:07:19 58e53c9ca92a postfix/smtp[15604]: AB2A3760261: to=<trade.alert@interx.co>, relay=none, delay=353146, delays=353116/0/30/0, dsn=4.4.1, status=deferred (connect to interx.co[188.65.115.132]:25: Connection timed out) Jan 15 15:07:19 58e53c9ca92a postfix/smtp[15605]: D2821760265: to=<trade.alert@interx.co>, relay=none, delay=353142, delays=353112/0/30/0, dsn=4.4.1, status=deferred (connect to interx.co[188.65.115.132]:25: Connection timed out) Jan 15 15:07:19 58e53c9ca92a postfix/smtp[15575]: AAA2C760263: to=<trade.alert@interx.co>, relay=none, delay=353145, delays=353115/0/30/0, dsn=4.4.1, status=deferred (connect to interx.co[188.65.115.132]:25: Connection timed out) Jan 15 15:07:19 58e53c9ca92a postfix/smtp[15574]: BF68076025C: to=<trade.alert@interx.co>, relay=none, delay=353148, delays=353118/0/30/0, dsn=4.4.1, status=deferred (connect to interx.co[188.65.115.132]:25: Connection timed out) Sierra Chart Support Date Time Of Last Edit: 2019-01-15 15:17:00

[2019-01-15 16:19:53] #13 [Go To First Post]
User78442 - Posts: 260
Thanks, I'll forward to the Domain techs...

[2019-01-16 05:27:35] #14 [Go To First Post]
User78442 - Posts: 260
OK, the Domain Techs have responded (see below) and 'white-listed' alerts@sierrachart.com, lets see if this works.... Hi James, Thank you for getting back to us with this information. I checked the oldest email logs available for a mention of alerts@sierrachart.com and found the last entry to be from the 21st of December. It mentioned the IP 204.15.192.107, so I searched our firewall settings. However, this IP was not blocked. To further try and ensure their emails are getting through, I have whitelisted the IP address and added alerts@sierrachart.com to the whitelisted addresses in your SpamAssassin configuration. If the delivery issues persist, please ask the Sierra Chart support to confirm which IP they are connecting, so I can check that against our firewall settings. We remain available if further assistance is required. Kind regards, Svetozar -------------------------------- Ticket history -------------------------------- From: James Bernard Pape <james.pape@jbpconsult.com> At: 15/Jan/2019 16:25 Attached: 1 file Hi Martin & al… I contacted Sierra Chart - Apparently you are blocking their emails... see below; <cid:image001.png@01D4ACF7.39E7D020> Please can you fix this. Thanks

[2019-01-16 10:50:42] #15 [Go To First Post]
User78442 - Posts: 260
The last alert that went through from SC was on 21st December, sent from IP 204.15.192.107. This IP has been whitelisted. I instigated an alert at 08:33 CET today the alert mail from SC was NOT seen by my domain people. Can you please confirm from which IP address your alerts are coming from, is it a static IP address?

[2019-01-16 15:35:26] #16 [Go To First Post]
Sierra Chart - Max - Posts: 5614
They need to white list the ip for sierrachart.com (46.4.97.203) Sierra Chart Support

[2019-01-17 05:20:15] #17 [Go To First Post]
User78442 - Posts: 260
I had some connection lost alerts last night at 20:20:58 CET. No SC email alerts arrived. Can SC please send me (james.pape@interx.co) a full copy of the email, including the headers so TSO Host (Domain) can investigate.

[2019-01-17 05:20:49] #18 [Go To First Post]
User78442 - Posts: 260
BTW 46.4.97.203 was whitelisted.

[2019-01-17 16:49:22] #19 [Go To First Post]
Sierra Chart - Max - Posts: 5614
We do not store copies of alert emails. Here is the content of a sample sent to gmail: Delivered-To: ****@gmail.com Received: by 2002:aed:3726:0:0:0:0:0 with SMTP id i35csp1965133qtb; Thu, 17 Jan 2019 08:47:29 -0800 (PST) X-Google-Smtp-Source: ALg8bN4gA4UgpwnzVj8fkXrlT7+g0mi2pu3ohA8kjRC/Nbq/nqvd9Dn8Xn0EJXPtdy6H0ivOsRu1 X-Received: by 2002:adf:9ec8:: with SMTP id b8mr13358806wrf.164.1547743649216; Thu, 17 Jan 2019 08:47:29 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547743649; cv=none; d=google.com; s=arc-20160816; b=pDAb09DLfpiu9/2P4rN8NmwQSo6EHAX3oPsYMPjL3eNq8s8+Gcl7hNgNlkYF1B9XHZ CTE8HeEsAtu7luwTsGuL9MiNbdft+aC8BVdxwqIfPR4GGe8iDE8GiqHSW83jV0MNoAAq DxsORH39vztnFFkqrxViaB5FYyTYl0kik8e6XhMcU6I/AE5L5sKy2pdg+Fs+erNQEFOE F3+sbAIBLid+5qjE8c3EL0TA5tv3vBZRG19TKgi9FL00QHv1aSiprGk/GKiw0dy9GdQS qhC//+npVSZ4liV01MD20jJrN6aoB4wd8hGj2W3e8rxFcDztf9s3zJfCOIySB+iHMPd3 ZmIA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=mime-version:message-id:subject:reply-to:from:to:date; bh=WLBdZWpu/kfjW9ushlSDjpqIw+y3DMD7Bb+yBQUSAYk=; b=0QvxFcijo7G+Rbfuk/OVyPKfaH31CgaUibgggHNO6LVmEebzmg/K+LnOQZPQ+txV2d AXQTfoxZQqqQb7DHiJVoq6QYreaZG5xO9GR+YGXWpoQt+dD5f3CFAd59eA6+CYNHc09L fQ1J52Q/pZCUgBqwleUQBDd5teVEPKiPNBkYHWbgWLh7D3cgiu8yK1rtrZs8YqE6dbYk zcxccvsMUREHbDWjffO/stoZpFICSFVrN3ZknMsia6y4idOn6o6QP1sQOf2EEVUdM3H5 W2Q0cZ2pK6z9KC/gNRdjUhZs3lAgdsOwF+xhoCkciWwsmY7W5++6vdiainx/7NcqNvog IwAw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of alerts@sierrachart.com designates 46.4.97.203 as permitted sender) smtp.mailfrom=alerts@sierrachart.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=sierrachart.com Return-Path: <alerts@sierrachart.com> Received: from sierrachart.com (sierrachart.com. [46.4.97.203]) by mx.google.com with ESMTP id s18si49214246wro.429.2019.01.17.08.47.29 for <**@gmail.com>; Thu, 17 Jan 2019 08:47:29 -0800 (PST) Received-SPF: pass (google.com: domain of alerts@sierrachart.com designates 46.4.97.203 as permitted sender) client-ip=46.4.97.203; Authentication-Results: mx.google.com; spf=pass (google.com: domain of alerts@sierrachart.com designates 46.4.97.203 as permitted sender) smtp.mailfrom=alerts@sierrachart.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=sierrachart.com Received: from www.sierrachart.com by sierrachart.com (Postfix) with ESMTPA id E3A327607F2 for <**@gmail.com>; Thu, 17 Jan 2019 16:47:28 +0000 (UTC) Date: Thu, 17 Jan 2019 16:47:28 +0000 To: ** <**@gmail.com> From: Sierra Chart Email Alerts <alerts@sierrachart.com> Reply-To: Sierra Chart Support <support@sierrachart.com> Subject: Study Alert Message-ID: <9141cb77b790474821ce230ae06c3dd1@www.sierrachart.com> X-Mailer: PHPMailer 5.2.26 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Alert - Chart: EURUSD [M] 1 Min #1 \| Formula: =1 is TRUE. \| Last Price: 1.16735 \| Bar start date-time: 2018-09-19 21:37:00 \| Alert: AlertSound (1) Our logs still show that the IP is being blocked: Jan 17 16:47:22 58e53c9ca92a postfix/smtp[21487]: 8C753760801: to=<trade.alert@interx.co>, relay=none, delay=56989, delays=56959/0/30/0, dsn=4.4.1, status=deferred (connect to interx.co[188.65.115.132]:25: Connection timed out) Jan 17 16:47:22 58e53c9ca92a postfix/smtp[21488]: 03B94760691: to=<trade.alert@interx.co>, relay=none, delay=201948, delays=201918/0/30/0, dsn=4.4.1, status=deferred (connect to interx.co[188.65.115.132]:25: Connection timed out) Jan 17 16:47:22 58e53c9ca92a postfix/smtp[21477]: A0C107607F1: to=<trade.alert@interx.co>, relay=none, delay=59363, delays=59333/0/30/0, dsn=4.4.1, status=deferred (connect to interx.co[188.65.115.132]:25: Connection timed out) Sierra Chart Support Date Time Of Last Edit: 2019-01-17 18:51:51**

[2019-01-18 09:40:32] #20 [Go To First Post]
User78442 - Posts: 260
Seems like we are heading for an impasse. Is it possible the two technical departments can communicate directly on my behalf, I am a longstanding customer of both... Here's their latest request... Hi James, Can you ask them (Sierra Chart) to whitelist 188.65.115.132, the IP they are trying to connect to. Kind regards, Virginia K. -------------------------------- Ticket history --------------------------------

[2019-01-18 15:33:49] #21 [Go To First Post]
Sierra Chart - Max - Posts: 5614
Yes, they can contact us directly by email. But we will tell what we are telling you now. We are not blocking connections to "188.65.115.132". There is no whitelist to add the IP to. Our log shows that we are connecting to the email server, but the email server is not responding to our requests, or delaying the acceptance of the emails. Our assessment of the situation at the moment is that the receiving email server is blocking the alerts. It might be accepting the connection from the email server, but not accepting the alert email. What do their logs show? Sierra Chart Support

[2019-01-18 15:36:21] #22 [Go To First Post]
Sierra Chart - Max - Posts: 5614
Here are also the latest logs: Jan 18 15:27:29 58e53c9ca92a postfix/smtp[24547]: connect to interx.co[188.65.115.132]:25: Connection timed out Jan 18 15:27:29 58e53c9ca92a postfix/smtp[24544]: connect to interx.co[188.65.115.132]:25: Connection timed out Jan 18 15:27:29 58e53c9ca92a postfix/smtp[24548]: connect to interx.co[188.65.115.132]:25: Connection timed out Jan 18 15:27:29 58e53c9ca92a postfix/smtp[24512]: connect to interx.co[188.65.115.132]:25: Connection timed out Jan 18 15:27:29 58e53c9ca92a postfix/smtp[24544]: 94D897607CB: to=<trade.alert@interx.co>, relay=none, delay=160058, delays=160028/0/30/0, dsn=4.4.1, status=deferred (connect to interx.co[188.65.115.132]:25: Connection timed out) Jan 18 15:27:29 58e53c9ca92a postfix/smtp[24512]: 863E27607C7: to=<trade.alert@interx.co>, relay=none, delay=160075, delays=160045/0/30/0, dsn=4.4.1, status=deferred (connect to interx.co[188.65.115.132]:25: Connection timed out) Jan 18 15:27:29 58e53c9ca92a postfix/smtp[24547]: 474A8760836: to=<trade.alert@interx.co>, relay=none, delay=113744, delays=113714/0/30/0, dsn=4.4.1, status=deferred (connect to interx.co[188.65.115.132]:25: Connection timed out) Jan 18 15:27:29 58e53c9ca92a postfix/smtp[24548]: 880007607CD: to=<trade.alert@interx.co>, relay=none, delay=160021, delays=159991/0/30/0, dsn=4.4.1, status=deferred (connect to interx.co[188.65.115.132]:25: Connection timed out) Jan 18 15:31:59 58e53c9ca92a postfix/error[24595]: 9784E7601D2: to=<trade.alert@interx.co>, relay=none, delay=140999, delays=140999/0/0/0, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to interx.co[188.65.115.132]:25: Connection timed out) Jan 18 15:31:59 58e53c9ca92a postfix/error[24595]: 1D5D77607D0: to=<trade.alert@interx.co>, relay=none, delay=160206, delays=160206/0/0/0.01, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to interx.co[188.65.115.132]:25: Connection timed out) Jan 18 15:31:59 58e53c9ca92a postfix/error[24598]: CFB3F760838: to=<trade.alert@interx.co>, relay=none, delay=113739, delays=113739/0/0/0.01, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to interx.co[188.65.115.132]:25: Connection timed out) Jan 18 15:31:59 58e53c9ca92a postfix/error[24596]: F0CD97605D1: to=<james.pape@interx.co>, relay=none, delay=378524, delays=378524/0/0/0.01, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to interx.co[188.65.115.132]:25: Connection timed out) Jan 18 15:31:59 58e53c9ca92a postfix/error[24600]: 446D9760849: to=<trade.alert@interx.co>, relay=none, delay=105492, delays=105492/0.01/0/0.01, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to interx.co[188.65.115.132]:25: Connection timed out) The highlighted part show that the receiving email server is not accepting emails for interx.co. Sierra Chart Support Date Time Of Last Edit: 2019-01-18 16:31:18

[2019-01-18 16:25:01] #23 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
At this point, any further support you require from us in this regard, will be chargeable at 50 USD per hour. We will be deducting that from your account. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2019-01-18 16:26:27

[2019-01-28 05:56:11] #24 [Go To First Post]
User78442 - Posts: 260
I can't get interx.co to work.. swapped domain.. it now works. Thanks for your efforts. It was my domain chaps that couldn't fix it.

[2020-04-07 02:51:11] #25 [Go To First Post]
Luis Wuilfredo - Posts: 1
Buenas, equipo de Sierra Chart. los contacto para saber como puedo hacer para conectar mi cuenta DEMO en sierra chart ya que me da error al intentar conectarme. me dice que esta mal y estoy colocando bien los datos que me llegaron al correo. The problem is that if I don't put the CQG DEMO account, I can't place orders on the chart. Thank you very much and I await your prompt response.


2.jpg / V - Attached On 2020-04-07 02:47:42 UTC - Size: 181.58 KB - 332 views 3.jpg / V - Attached On 2020-04-07 02:47:50 UTC - Size: 153.04 KB - 330 views 4.jpg / V - Attached On 2020-04-07 02:48:31 UTC - Size: 121.2 KB - 314 views

To post a message in this thread, you need to log in with your Sierra Chart account: