<p><strong>Stick with Google and use STunnel to avoid TLS</strong></p>
<p>There is a useful article describing how to get this to work here: <a href="https://groups.google.com/a/googleproductforums.com/forum/#!category-topic/apps/mail-settings/oCwPE2o_oCM" rel="nofollow noreferrer">https://groups.google.com/a/googleproductforums.com/forum/#!category-topic/apps/mail-settings/oCwPE2o_oCM</a></p>
<p>The relevant excerpts are:</p>
<blockquote>
<p>You can use STunnel to allow non-SSL devices to connect.  STunnel
should be run on a computer on your network that is up 24/7.  The
network printers will connect to STunnel using non-SSL SMTP then
STunnel will bridge the connection to Google Apps using an SSL
connection.  STunnel can be downloaded at:</p>
<p><a href="http://www.stunnel.org/" rel="nofollow noreferrer">http://www.stunnel.org/</a></p>
<p>Your stunnel.conf file should look like:</p>
<p>-- begin stunnel.conf --</p>
<p>cert = stunnel.pem</p>
<p>socket = l:TCP_NODELAY=1</p>
<p>socket = r:TCP_NODELAY=1</p>
<p>client = yes</p>
<p>[pop3s]</p>
<p>accept  = 110</p>
<p>connect = pop.gmail.com:995</p>
<p>[imaps]</p>
<p>accept  = 143</p>
<p>connect = imap.gmail.com:993</p>
<p>[ssmtp]</p>
<p>accept  = 25</p>
<p>connect = smtp.gmail.com:465</p>
<p>-- end stunnel.conf --</p>
</blockquote>
<p>It's worth reading around the rest of the information on the site</p>
<p><strong>I tried STunnel and failed! What now?</strong></p>
<p>Try using the sneaky printer backdoor to Google's SMTP servers that avoids SSL. Instructions are here: <a href="http://support.google.com/a/bin/answer.py?hl=en&amp;hlrm=en&amp;answer=176600" rel="nofollow noreferrer">http://support.google.com/a/bin/answer.py?hl=en&amp;hlrm=en&amp;answer=176600</a></p>
<p>Relevant info is:</p>
<blockquote>
<p>If your device does not support SSL, connect to aspmx.l.google.com on port 25.</p>
<p>You must configure an SPF record for your domain with the IP address
of the device to ensure that recipients do not reject mail sent from
it. You must also add this IP address to the Email Whitelist box in
your Google Apps control panel.</p>
<p>For example. if your sending device
sends from 123.45.67.89, add that address to your SPF record without
removing the Google Apps mail servers from the record: v=spf1
ip4:123.45.67.89 include:_spf.google.com ~all</p>
</blockquote>

CC BY-SA 3.0
2012-01-24T11:07:36.770Z
Thanks. I'm assuming I can run STunnel on the same BAMT rig?
Sean Chapman
CC BY-SA 3.0
2012-01-24T11:21:15.153Z
Give it a go and see how it works out. If it works well then provide some feedback so that others can take advantage too. You might find the printer backdoor method works better for your situation.
Gary
CC BY-SA 3.0
2012-01-24T11:00:36.390Z
2012-01-24T11:00:36.390Z
2020-06-16T11:10:03.350Z
Gary
<p>I have BAMT running on my rig but I don't think the email alerts are working, possibly due to a bad config.</p>

<p>I would like to use Google's SMTP server if possible (or any other free SMTP provider) but Google's uses TLS, which isn't supported in the BAMT configs I believe, so if this isn't possible (and no other free SMTP servers are available), how would I go about setting up my own SMTP server on the rig?</p>

<p>Thanks</p>

<miner-configuration><bamt>
BAMT Email Alerts Setup
Sean Chapman
# BAMT Email Alerts Setup

(Asked by: username_0 on 2011-12-13)

I have BAMT running on my rig but I don't think the email alerts are working, possibly due to a bad config.

I would like to use Google's SMTP server if possible (or any other free SMTP provider) but Google's uses TLS, which isn't supported in the BAMT configs I believe, so if this isn't possible (and no other free SMTP servers are available), how would I go about setting up my own SMTP server on the rig?

Thanks

**Tags:** miner-configuration, bamt


---

## 1 answers

### Answer by username_1 on 2012-01-24. Score: 1 | Accepted answer

**Stick with Google and use STunnel to avoid TLS**

There is a useful article describing how to get this to work here: <https://groups.google.com/a/googleproductforums.com/forum/#!category-topic/apps/mail-settings/oCwPE2o_oCM>

The relevant excerpts are:

> You can use STunnel to allow non-SSL devices to connect. STunnel
> should be run on a computer on your network that is up 24/7. The
> network printers will connect to STunnel using non-SSL SMTP then
> STunnel will bridge the connection to Google Apps using an SSL
> connection. STunnel can be downloaded at:
>
> <http://www.stunnel.org/>
>
> Your stunnel.conf file should look like:
>
> -- begin stunnel.conf --
>
> cert = stunnel.pem
>
> socket = l:TCP\_NODELAY=1
>
> socket = r:TCP\_NODELAY=1
>
> client = yes
>
> [pop3s]
>
> accept = 110
>
> connect = pop.gmail.com:995
>
> [imaps]
>
> accept = 143
>
> connect = imap.gmail.com:993
>
> [ssmtp]
>
> accept = 25
>
> connect = smtp.gmail.com:465
>
> -- end stunnel.conf --

It's worth reading around the rest of the information on the site

**I tried STunnel and failed! What now?**

Try using the sneaky printer backdoor to Google's SMTP servers that avoids SSL. Instructions are here: <http://support.google.com/a/bin/answer.py?hl=en&hlrm=en&answer=176600>

Relevant info is:

> If your device does not support SSL, connect to aspmx.l.google.com on port 25.
>
> You must configure an SPF record for your domain with the IP address
> of the device to ensure that recipients do not reject mail sent from
> it. You must also add this IP address to the Email Whitelist box in
> your Google Apps control panel.
>
> For example. if your sending device
> sends from 123.45.67.89, add that address to your SPF record without
> removing the Google Apps mail servers from the record: v=spf1
> ip4:123.45.67.89 include:\_spf.google.com ~all

> **Comments:**
> **username_0**: Thanks. I'm assuming I can run STunnel on the same BAMT rig?  
> **username_1**: Give it a go and see how it works out. If it works well then provide some feedback so that others can take advantage too. You might find the printer backdoor method works better for your situation.  

---

