Attached is a patch which corrects an error with the example given in
the tinbuild readme in regards to working with gmail.
I also added that the smtp port needs to be changed in the tinbuild
script itself to 587 if using gmail.
Thanks
Jonathan
From 570e0dbcbb692727a821dc0b8d71fc4ef8f69029 Mon Sep 17 00:00:00 2001
From: Jonathan Aquilina <eagles051387@gmail.com>
Date: Wed, 11 May 2011 15:33:55 +0200
Subject: [PATCH] update the example execution script in regards to gmail smtp server and port
---
README | 3 +++
bin/tinbuild | 4 ++--
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/README b/README
index a259834..d953556 100644
--- a/README
+++ b/README
@@ -44,6 +44,9 @@ like this:
tinbuild -m joe_hacker@gmail.com -s smtp.gmail.com -u joe_hacker -p SeCrEt -c tls -t "Linux
gcc-4.4.1 (x86_64)"
+Please note that you will need to change the default smtp port to port
+587 if you would like to use gmail.
+
If you don't want the user or password to show up in the process list,
simply edit the tinbuild script - rather at the top of it, there are
SMTPUSER and SMTPPW variables, to be set.
diff --git a/bin/tinbuild b/bin/tinbuild
index 731f796..c6e3571 100755
--- a/bin/tinbuild
+++ b/bin/tinbuild
@@ -1,4 +1,4 @@
-#!/bin/sh
+#!/bin/bash
export LC_ALL="C"
@@ -15,7 +15,7 @@ TINDERNAME=
BANDWIDTH=
LOCK=
-SMTPPORT=25
+SMTPPORT=587
SMTPCRYPT=none
SMTPHOST=
SMTPUSER=
--
1.7.4.1
Context
- [Libreoffice] [PATCH] tinbuild Readme · Jonathan Aquilina
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.