What characters are illegal in password in ssmtp.conf?SSMTP with Gmail (Google Apps)
Frame failure sudden death?
Do any instruments not produce overtones?
Why was the Sega Genesis marketed as a 16-bit console?
Is it a problem if <h4>, <h5> and <h6> are smaller than regular text?
What's the name of this light airplane?
Why would future John risk sending back a T-800 to save his younger self?
What risks are there when you clear your cookies instead of logging off?
When 2-pentene reacts with HBr, what will be the major product?
Can the poison from Kingsmen be concocted?
Passing multiple files through stdin (over ssh)
How Can I Tell The Difference Between Unmarked Sugar and Stevia?
Was the output of the C64 SID chip 8 bit sound?
How is water heavier than petrol, even though its molecular weight is less than petrol?
Investing in a Roth IRA with a Personal Loan?
1980s live-action movie where individually-coloured nations on clouds fight
What is wrong with this proof that symmetric matrices commute?
How to tell your grandparent to not come to fetch you with their car?
Russian equivalents of "no love lost"
What does the term "railed" mean in signal processing?
Using a found spellbook as a Sorcerer-Wizard multiclass
Preventing Employees from either switching to Competitors or Opening Their Own Business
How do I write "Show, Don't Tell" as a person with Asperger Syndrome?
Smooth switching between 12 V batteries, with a toggle switch
When conversion from Integer to Single may lose precision
What characters are illegal in password in ssmtp.conf?
SSMTP with Gmail (Google Apps)
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I'm running Ubuntu Server 16.04 with the ssmtp package for sendmail. I've read from a variety of places that you cannot use "special" characters in the password, and I've discovered it's true that I cannot escape nor quote the password. I have only been able to verify alphanumeric passwords in ssmtp.conf to work, but I cannot find this documented anywhere. My question is, what are the allowed/forbidden characters for a password?
Alternatively, is there any other method of escaping? I've tried backslash, single, and double quotes to no avail.
Thanks
ssmtp
add a comment |
I'm running Ubuntu Server 16.04 with the ssmtp package for sendmail. I've read from a variety of places that you cannot use "special" characters in the password, and I've discovered it's true that I cannot escape nor quote the password. I have only been able to verify alphanumeric passwords in ssmtp.conf to work, but I cannot find this documented anywhere. My question is, what are the allowed/forbidden characters for a password?
Alternatively, is there any other method of escaping? I've tried backslash, single, and double quotes to no avail.
Thanks
ssmtp
add a comment |
I'm running Ubuntu Server 16.04 with the ssmtp package for sendmail. I've read from a variety of places that you cannot use "special" characters in the password, and I've discovered it's true that I cannot escape nor quote the password. I have only been able to verify alphanumeric passwords in ssmtp.conf to work, but I cannot find this documented anywhere. My question is, what are the allowed/forbidden characters for a password?
Alternatively, is there any other method of escaping? I've tried backslash, single, and double quotes to no avail.
Thanks
ssmtp
I'm running Ubuntu Server 16.04 with the ssmtp package for sendmail. I've read from a variety of places that you cannot use "special" characters in the password, and I've discovered it's true that I cannot escape nor quote the password. I have only been able to verify alphanumeric passwords in ssmtp.conf to work, but I cannot find this documented anywhere. My question is, what are the allowed/forbidden characters for a password?
Alternatively, is there any other method of escaping? I've tried backslash, single, and double quotes to no avail.
Thanks
ssmtp
ssmtp
edited Apr 13 '17 at 12:14
Community♦
1
1
asked Jan 17 '17 at 21:26
Jeff PuckettJeff Puckett
195114
195114
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
There seem to be a number of outstanding bugs listed here with regards to problematic characters in the AuthPass
directive:
- bug report 768129: the hash/pound character #
- bug report 463196: the equals = and the colon : characters
and I don't know if that would be the case for ssmtp specifically but generally bad characters to use in passwords are spaces, extended ASCII: è é ê ë etc. and UNICODE. Stick to a-z A-Z 0-9 .-
and make passwords longer rather than more complex.
add a comment |
Looking at the read_config()
method on line 883 of the current blob af4d1e58d28fa9450bfc6a80fbacc75ca28c2220 it appears as though an equals sign =
or a pound hash sign #
would cause it to silently continue and skip parsing that line of the config file.
/* Make comments invisible */
if((p = strchr(buf, '#')))
*p = (char)NULL;
/* Ignore malformed lines and comments */
if(strchr(buf, '=') == (char *)NULL) continue;
I would still like to see an authoritative answer on the subject or a definitive reference to documentation.
add a comment |
You can use the following workaround:
- feed the password directly in the command line argument
ssmtp -ap "Hash#Password" ...
- alternatively put the password in an environment variable.
ssmtp -ap $PASSWD ...
Hope it helped.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f826875%2fwhat-characters-are-illegal-in-password-in-ssmtp-conf%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
There seem to be a number of outstanding bugs listed here with regards to problematic characters in the AuthPass
directive:
- bug report 768129: the hash/pound character #
- bug report 463196: the equals = and the colon : characters
and I don't know if that would be the case for ssmtp specifically but generally bad characters to use in passwords are spaces, extended ASCII: è é ê ë etc. and UNICODE. Stick to a-z A-Z 0-9 .-
and make passwords longer rather than more complex.
add a comment |
There seem to be a number of outstanding bugs listed here with regards to problematic characters in the AuthPass
directive:
- bug report 768129: the hash/pound character #
- bug report 463196: the equals = and the colon : characters
and I don't know if that would be the case for ssmtp specifically but generally bad characters to use in passwords are spaces, extended ASCII: è é ê ë etc. and UNICODE. Stick to a-z A-Z 0-9 .-
and make passwords longer rather than more complex.
add a comment |
There seem to be a number of outstanding bugs listed here with regards to problematic characters in the AuthPass
directive:
- bug report 768129: the hash/pound character #
- bug report 463196: the equals = and the colon : characters
and I don't know if that would be the case for ssmtp specifically but generally bad characters to use in passwords are spaces, extended ASCII: è é ê ë etc. and UNICODE. Stick to a-z A-Z 0-9 .-
and make passwords longer rather than more complex.
There seem to be a number of outstanding bugs listed here with regards to problematic characters in the AuthPass
directive:
- bug report 768129: the hash/pound character #
- bug report 463196: the equals = and the colon : characters
and I don't know if that would be the case for ssmtp specifically but generally bad characters to use in passwords are spaces, extended ASCII: è é ê ë etc. and UNICODE. Stick to a-z A-Z 0-9 .-
and make passwords longer rather than more complex.
edited Jan 17 '17 at 21:54
answered Jan 17 '17 at 21:53
HBruijnHBruijn
58.4k1191155
58.4k1191155
add a comment |
add a comment |
Looking at the read_config()
method on line 883 of the current blob af4d1e58d28fa9450bfc6a80fbacc75ca28c2220 it appears as though an equals sign =
or a pound hash sign #
would cause it to silently continue and skip parsing that line of the config file.
/* Make comments invisible */
if((p = strchr(buf, '#')))
*p = (char)NULL;
/* Ignore malformed lines and comments */
if(strchr(buf, '=') == (char *)NULL) continue;
I would still like to see an authoritative answer on the subject or a definitive reference to documentation.
add a comment |
Looking at the read_config()
method on line 883 of the current blob af4d1e58d28fa9450bfc6a80fbacc75ca28c2220 it appears as though an equals sign =
or a pound hash sign #
would cause it to silently continue and skip parsing that line of the config file.
/* Make comments invisible */
if((p = strchr(buf, '#')))
*p = (char)NULL;
/* Ignore malformed lines and comments */
if(strchr(buf, '=') == (char *)NULL) continue;
I would still like to see an authoritative answer on the subject or a definitive reference to documentation.
add a comment |
Looking at the read_config()
method on line 883 of the current blob af4d1e58d28fa9450bfc6a80fbacc75ca28c2220 it appears as though an equals sign =
or a pound hash sign #
would cause it to silently continue and skip parsing that line of the config file.
/* Make comments invisible */
if((p = strchr(buf, '#')))
*p = (char)NULL;
/* Ignore malformed lines and comments */
if(strchr(buf, '=') == (char *)NULL) continue;
I would still like to see an authoritative answer on the subject or a definitive reference to documentation.
Looking at the read_config()
method on line 883 of the current blob af4d1e58d28fa9450bfc6a80fbacc75ca28c2220 it appears as though an equals sign =
or a pound hash sign #
would cause it to silently continue and skip parsing that line of the config file.
/* Make comments invisible */
if((p = strchr(buf, '#')))
*p = (char)NULL;
/* Ignore malformed lines and comments */
if(strchr(buf, '=') == (char *)NULL) continue;
I would still like to see an authoritative answer on the subject or a definitive reference to documentation.
answered Jan 17 '17 at 21:52
Jeff PuckettJeff Puckett
195114
195114
add a comment |
add a comment |
You can use the following workaround:
- feed the password directly in the command line argument
ssmtp -ap "Hash#Password" ...
- alternatively put the password in an environment variable.
ssmtp -ap $PASSWD ...
Hope it helped.
add a comment |
You can use the following workaround:
- feed the password directly in the command line argument
ssmtp -ap "Hash#Password" ...
- alternatively put the password in an environment variable.
ssmtp -ap $PASSWD ...
Hope it helped.
add a comment |
You can use the following workaround:
- feed the password directly in the command line argument
ssmtp -ap "Hash#Password" ...
- alternatively put the password in an environment variable.
ssmtp -ap $PASSWD ...
Hope it helped.
You can use the following workaround:
- feed the password directly in the command line argument
ssmtp -ap "Hash#Password" ...
- alternatively put the password in an environment variable.
ssmtp -ap $PASSWD ...
Hope it helped.
answered May 21 at 14:34
Hugo TrentesauxHugo Trentesaux
1066
1066
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f826875%2fwhat-characters-are-illegal-in-password-in-ssmtp-conf%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown