mackov83

Hi, I can confirm that this is now working as expected. Thanks for looking into it.

Yes, I had "Save Emails to Sent Items" enabled so that I could tell whether the messages were being received by the sending mailbox or not. It appears like it could be working now. I will wait and see later today whether emails are still being received. I believe one of the services sometimes needs restarting which can impact mail settings? From what I remember it updates every 5 minutes by default?

I have upgraded to 9735 and it still doesn't work. There is nothing in the release notes about a fix... Exchange Online test emails still work. Anything to do with email templates still fail.

Thanks for the update, I look forward to the next release and hopefully this is resolved for good. I did mention multiple times in this thread that Exchange Online and SMTP should be completely independent of one another. Therefore, I find it a little strange that you would leave the SMTP details in place during testing. As an independent contractor with my own business, if you want to hire me for testing I would be open to it

After removing SMTP details Email notifications have stopped completely - as they are based on the email templates. From what I have seen, if the "Email Test" on the templates fails, email notifications do not work. The only way that I have found that allows the test emails to be sent successfully (without SMTP settings) from within the templates is to specify a delivery address as per below: To be clear: All users have an email address visible in Passwordstate With SMTP settings specified, emails work as expected

Hi Support, This build has resolved the need to enter the server name, however, test emails sent from email templates are not sent or delivered according to Exchange Online message trace function. Passwordstate however shows a black banner at the bottom of the screen stating the email has been successfully sent. Test emails triggered from the Exchange Online system settings are working. Therefore, this continues to look like the email templates were hard coded for SMTP and the fixes being put in place are slowly removing these barriers. It does however make me question your testing procedures. It seems you only fix the issues being highlighted without testing the entire flow...

@support In build 9708 changelog you mention the following: "Fixed an issue on the Email Templates screen where it was not possible to test templates when using Exchange Online email option". I would say that this is not properly fixed and you still have some flaws. While I no longer have to specify the SMTP 'Server Host Name' if you also remove the 'Send From Email Address' value in the SMTP configuration, you now end up with the following error: As I mentioned previously, Exchange Online and SMTP should be two completely independent options. When using Exchange Online exclusively, there should be no reliance on any SMTP configuration. At least this is the case with build 9715.

While I am a long-time user of Passwordstate, I am new to the mobile app / appserver side of the application. I have installed the main server and app server on the same machine with different ports - main server is 443 and appserver is 8443. I can connect, view and sync passwords without an issue. However, once I try to access a website and have the app autofill passwords, nothing happens. If I click in the fields (username and password) I see either or both of the following: A key icon with the credentials - this doesn't do anything when selected Passwordstate logo with the message 'verify identity' - this prompts me to login to Passwordstate app, and takes me directly to the credentials for that webpage, but selecting this also does nothing. I have enabled the autofill option through device settings - I have a Galaxy S20 FE 5G with Android 13 Have tried with both Google Chrome and MSFT Edge with same results Has anybody else actually had the apps work? I did try this on my wife's iPhone and everything except the OTP was possible. In case it helps, my setup is as follows: Main server: pw.example.com > CloudFlare free edition (DNS and basic WAF) > firewall > HA Proxy > Passwordstate server:443 App Server: pwapp.example.com > CloudFlare free edition (DNS and basic WAF) > firewall > HA Proxy > Passwordstate server:8443

@support at this point I am using the Passwordstate free version as I am a small business of one person. As a result, I don't believe I get support for your product? For the record, I think your product is fantastic and has many more features that the likes of LastPass, Bitwarden etc. I have used it for years in a previous company which is why I am using it now, though I have learnt much more about it recently having had my own instance to experiment with.

Hi, I have done a lot of digging into this and would be very interested to get feedback from ClickStudios about my findings... Please refer to following screenshot: As this was a new implementation, I had zero settings in place for SMTP (number 3) and reading the documentation I expect this should be correct. After all, when you click the drop-down menu (number 1) it is Either Exchange Online or SMTP. So I should only need to configure one or the other right? As I don't have an SMTP server (or relay) in my case and with security in mind, Exchange Online using OAUTH seems the best approach. With Exchange Online details (number 2) only configured results were: Test emails = successful Self destruct = successful Email templates = failure, and testing not available (see further down) SMTP Email Test = failure (expected as not configured) Out of curiosity, I added the SMTP settings for outlook.office.com, specified the TLS port 587, and entered the same shared mailbox - this time as the name (unlike for Exchange Online which is an Object ID). Results with the extra SMTP config in place: Test emails = successful Self destruct = successful Email templates = successful (progress!) SMTP Test = failure (more or less expected as only a partial config) As mentioned earlier, the Test Email button is greyed out for all Email Templates unless you specify SMTP details: Conclusions: Documentation clearly requires some updates - not enough detail regarding email configuration unless I am reading the wrong one: Passwordstate Security Administrators Manual (clickstudios.com.au). I suspect it is correct as the detail around O365 configuration is all there. It seems that Email Templates rely on SMTP configuration in order to work - surely this should not be the case and needs to be fixed? P.S. I will state that I do use CodeTwo for email signatures, though the shared mailbox that I am using to send emails has been disabled from having an email signature applied. Just in case there are known issues with CodeTwo.

Upgrade to 9700 - no change.

I should that the account being used to send the emails is a sharedmailbox account. However, when replacing that with my own email account (which is Global Admin) the emails are also not received. As you can also see I checked the box to 'Save Emails to Sent Items'. There is nothing being recorded as sent in this mailbox, except for the test emails.

I recently started configuring PasswordState to send emails out. I have the following configuration in place: The settings above map to an Azure AD application called Passwordstate, and I have given permissions for this application to send as any user: I can successfully receive test emails as proven below: Test email from Passwordstate. If you have received this email, but are still not receiving other emails from Passwordstate as expected, you can check the following things: 1. Check to see if there are any 'Email Templates' disabled 2. Check to see if there are any disabled emails for 'Email Notification Groups' 3. Check to see if the user has disabled email notifications as per their 'Preferences' 4. Check with Application Event Log on your web server for any errors. No matter what I do, I cannot receive emails from Passwordstate actions as I should be. Are there any other reasons why this would fail if the test emails are successful? I have followed through the steps in the manual, as well as the troubleshooting steps in the test email (as shown above). For the record I am on build 9665 and I don't see any fixes for this in 9700...

I just wanted to update and advise that I figured out the issue. I misinterpreted section 2.1 for the Hosts addition to be the Administration > Authorized Web Servers. Once I added the VM name under the required Hosts menu item it worked as per the documentation. Hopefully this helps somebody else if they have the same issue

Further to this, having upgraded our production environment to 9611 today, the process seemed to work perfectly fine for a domain joined PasswordState instance. Therefore interested to know if anybody has successfully created the backup account for a standalone machine.

FYI I have now also disabled Azure AD SAML based auth and have switched back to local basic auth for the time being I have taken the load balancer / WAF out of the way - issue still remains

Hi, have been using PasswordState in our corporate environment for many years and am quite familiar with how the product works. Some time back I setup the free version for personal use and training purposes. As I plan to make my personal version available publicly behind a WAF, I did not join this machine to the domain as I saw no strong reason to, and with the design I had in mind would make it more secure this way. Up until now, I have performed VM level backups and performed upgrades manually using the zip file approach which has worked ok. However, to perform GUI based backups, it seems I must enable backups and this is not working so well. When I follow the instructions: 2.1 Add Passwordstate Server into Passwordstate - this was already complete 2.2 Create Password List with the Enabled for Resets Option Selected - this part is and complete 2.3 Create Password Record - this is where things don't work. I cannot select the hostname via search button. I can type in the hostname, but I cannot save it. Saving the record without the hostname also doesn't work as hostname seems to be a required filed, even though it is not marked with the red * In my case the URL I use to access PasswordState is different to the hostname considering I have a load balancer / WAF in front - though WAF functionality is disabled while I troubleshoot. Hoping somebody may know how to resolve?