# Creating new topics by email does not work for me

**URL:** https://discuss.elastic.co/t/creating-new-topics-by-email-does-not-work-for-me/2351
**Category:** Meta Elastic
**Created:** [June 10, 2015, 4:14pm UTC](https://discuss.elastic.co/t/creating-new-topics-by-email-does-not-work-for-me/2351 "2015-06-10T16:14:57Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [June 10, 2015, 4:14pm UTC](https://discuss.elastic.co/t/creating-new-topics-by-email-does-not-work-for-me/2351/1 "2015-06-10T16:14:57Z")

</div>

I'm trying to announce new plugins using STMP and my messages don't appear. So I add them manually.

Is there anything wrong?

Here is what I'm sending:

```auto
Content-Type: multipart/alternative; boundary="===============2737587092076129416=="
MIME-Version: 1.0
Subject: [ANN] Elasticsearch Google Compute Engine cloud plugin 2.6.0 released
From: Elasticsearch Team <david@pilato.fr>
To: Elasticsearch Announcement List <discuss+announcements@elastic.co>

--===============2737587092076129416==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit

Heya,

We are pleased to announce the release of the Elasticsearch Google Compute Engine cloud plugin, version 2.6.0.

The Google Compute Engine (GCE) Cloud plugin allows to use GCE API for the unicast discovery mechanism..

https://github.com/elastic/elasticsearch-cloud-gce/

Release Notes - elasticsearch-cloud-gce - Version 2.6.0

Fix:
 * [47] - Fix non working update dynamic settings (https://github.com/elastic/elasticsearch-cloud-gce/issues/47)

Update:
 * [52] - Update to elasticsearch 1.6.0 (https://github.com/elastic/elasticsearch-cloud-gce/issues/52)
 * [50] - Remove component settings from AbstractComponent (https://github.com/elastic/elasticsearch-cloud-gce/issues/50)
 * [49] - Update to GCE API v1-rev59-1.20.0 (https://github.com/elastic/elasticsearch-cloud-gce/issues/49)

For questions or comments around this plugin, feel free to use elasticsearch mailing list: https://discuss.elastic.co/c/elasticsearch

Enjoy,

-The Elasticsearch team

--===============2737587092076129416==
Content-Type: text/html; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit

<html>
<body>
<p>Heya,</p>

<p>We are pleased to announce the release of the <b>Elasticsearch Google Compute Engine cloud plugin</b>, <b>version 2.6.0</b></p>

<blockquote>The Google Compute Engine (GCE) Cloud plugin allows to use GCE API for the unicast discovery mechanism..</blockquote>

<h1>Release Notes - Version 2.6.0</h1>

<h2>Fix</h2>
<ul>
<li>[<a href="https://github.com/elastic/elasticsearch-cloud-gce/issues/47">47</a>] - Fix non working update dynamic settings
</ul>

<h2>Update</h2>
<ul>
<li>[<a href="https://github.com/elastic/elasticsearch-cloud-gce/issues/52">52</a>] - Update to elasticsearch 1.6.0
<li>[<a href="https://github.com/elastic/elasticsearch-cloud-gce/issues/50">50</a>] - Remove component settings from AbstractComponent
<li>[<a href="https://github.com/elastic/elasticsearch-cloud-gce/issues/49">49</a>] - Update to GCE API v1-rev59-1.20.0
</ul>

<p>For questions or comments around this plugin, feel free to use elasticsearch
    <a href='https://discuss.elastic.co/c/elasticsearch'>mailing list</a>!</p>

<p>Enjoy,</p>
<p>- The <a href="http://www.elastic.co/">Elastic team</a></p>
</body>
</html>

--===============2737587092076129416==--

```

Sending to `discuss+announcements@elastic.co` from `david@pilato.fr` using `smtp.free.fr`.

---

<div class="post-metadata">

### Author: ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [June 15, 2015, 5:33am UTC](https://discuss.elastic.co/t/creating-new-topics-by-email-does-not-work-for-me/2351/3 "2015-06-15T05:33:26Z")

</div>

Sometimes it was working. Not every time.  
No I never got a failure message back.

---

<div class="post-metadata">

### Author: ![Sam\_Saffron](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sam_saffron/32/44937_2.png) [@Sam\_Saffron](https://discuss.elastic.co/u/Sam_Saffron)
#### Post date: [July 31, 2015, 7:23am UTC](https://discuss.elastic.co/t/creating-new-topics-by-email-does-not-work-for-me/2351/4 "2015-07-31T07:23:05Z")

</div>

This should be working now consistently. see:

> [@Errors when answering by email](https://discuss.elastic.co/t/errors-when-answering-by-email/1242/19):
>
> Today I spent a fair amount of time debugging this, first I added an option to very aggressively log any email failure Once that was done I deployed and turned it on here, I have been trying to reply to this very topic by email and kept on getting that message. When I looked at the log I saw nothing ... So ... the process running this site were not even getting the messages, where were they going ?? Well, elastic is an enterprise customer, they have a staging instance with all data and set…

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 1:47pm UTC](https://discuss.elastic.co/t/creating-new-topics-by-email-does-not-work-for-me/2351/5 "2017-07-06T13:47:21Z")

</div>


