February 25, 201511 yr I've been pretty quiet in the forums for a while now. Mainly lurking. I also have been enjoying the fruits of everyone's labor very much so (unraid, dynamix, plugins, dockers, etc.). Even with its quirks, V6 is shaping up to be everything I wanted in my NAS. However, respectfully... I understand that escaping certain characters while passing around strings to different coding languages is a pain. But it's 2015. Telling a user not to use a special character in a password, pretty much accepted everywhere else is IMHO a defect, not a feature. Code some sanitizing functions and use it everywhere or something ... Yes, in the grand scheme of things, it's not like I lost data or anything. But it's extremely annoying that the recommendation I'm given is to update my password in every single location that I use google services b/c unraid can't handle a '#' sign... It's weird - I'm accepting of so much of the "work-in-progress" nature of the v6 betas, but this password thing makes me come out of hibernation... anyways, thanks for letting me rant ...
February 25, 201511 yr It's not so much a limitation of unRAID, but a shortcoming of sSMTP which is used as the mail application. It is a known issue; sSMTP treats every line with a # character in it as comment, this means it won't set your password if it has this character included somewhere. Will they correct the issue, that's unknown! Hence the warning in unRAID to avoid unpleasant surprises.
February 25, 201511 yr it's extremely annoying that the recommendation I'm given is to update my password in every single location that I use google services b/c unraid can't handle a '#' sign... I agree with your premise, however I think you may be tilting at windmills. I would recommend setting up a disposable gmail account with a password like unraidssmptpasswordhandlingsucks or something like that, and use the forwarding and filtering rules to accomplish what you need.
February 25, 201511 yr it's extremely annoying that the recommendation I'm given is to update my password in every single location that I use google services b/c unraid can't handle a '#' sign... I agree with your premise, however I think you may be tilting at windmills. I would recommend setting up a disposable gmail account with a password like unraidssmptpasswordhandlingsucks or something like that, and use the forwarding and filtering rules to accomplish what you need. I want to also second this. You should not use a primary account for this. If nothing else you should be using two factor on your primary account and this requires that you don't do that.
February 25, 201511 yr I've been pretty quiet in the forums for a while now. Mainly lurking. I also have been enjoying the fruits of everyone's labor very much so (unraid, dynamix, plugins, dockers, etc.). Even with its quirks, V6 is shaping up to be everything I wanted in my NAS. However, respectfully... I understand that escaping certain characters while passing around strings to different coding languages is a pain. But it's 2015. Telling a user not to use a special character in a password, pretty much accepted everywhere else is IMHO a defect, not a feature. Code some sanitizing functions and use it everywhere or something ... Yes, in the grand scheme of things, it's not like I lost data or anything. But it's extremely annoying that the recommendation I'm given is to update my password in every single location that I use google services b/c unraid can't handle a '#' sign... It's weird - I'm accepting of so much of the "work-in-progress" nature of the v6 betas, but this password thing makes me come out of hibernation... anyways, thanks for letting me rant ... We all have things like this that just grinds our gears, so totally appreciate where you're coming from on this and thanks for reporting. That said, as Ronald has indicated, this isn't a function of unRAID itself as much as a function of the sSMTP component.
February 25, 201511 yr Author thanks everyone, I did not know that about sSMTP. I especially liked jonathanm's suggestion and will most likely just follow it. before I go back to lurking, having been called quixotic my fair share of times, I'd like to pass on this link: https://bugs.debian.org/544018 the pertinent thing being doing a "sendmail -v -ap my#password" appears to work... I say this while ducking , but assuming this also applies to unraid, perhaps how it's called can be updated? lol, ok. I'll shut up now... thx! -alex
February 26, 201511 yr thanks everyone, I did not know that about sSMTP. I especially liked jonathanm's suggestion and will most likely just follow it. before I go back to lurking, having been called quixotic my fair share of times, I'd like to pass on this link: https://bugs.debian.org/544018 the pertinent thing being doing a "sendmail -v -ap my#password" appears to work... I say this while ducking , but assuming this also applies to unraid, perhaps how it's called can be updated? lol, ok. I'll shut up now... thx! -alex Thanks for sharing that link! Probably something we won't have time to address before 6.0 final, but now that it's here in the forum, we can investigate this a little further down the road.
Archived
This topic is now archived and is closed to further replies.