Does this work for a multisite?

Not sure what was so bad about the markup on that message. Hopefully, this one will come out better.

Yes vote on the multisite options below, too.

• The ability to set a default smtp at the network level.
• Add a setting from network level that will let us enable whether each site can override and use their own smtp server.
• Turn off the notices on the dashboard if a site is using the network default.

Just a note on the smtp default set up, my gmail settings in developer console don’t like working with my different subsite subdomain names. I have the network domain working well with the mydomain.com set up. But when I want to turn it on for sitea.mydomain.com it appears I am going to have to create a new client ID for that subdomain. Not sure I want to have to do that each time.

But when I want to turn it on for sitea.mydomain.com it appears I am going to have to create a new client ID.

That’s right, Client IDs are generated per URL. So if you have a different URL you need a different Client ID.

The idea with the site-wide Client ID on a multisite install is that all subsites would use the configuration of the primary site, so only one Client ID would be needed in that case, as everything is shared, even the mailbox. But this is not implemented yet, I haven’t had demand for it up until a week ago.

@ipstenu @macmanx @t-p Could I have a forum mod clear up the markup problem in the above post please? Thx

@jasonhendriks All fixed. Next time, please tag the thread as “modlook” instead of pinging three mods separately.

https://codex.www.ads-software.com/Forum_Welcome#Reporting_Threads

Much obliged James, and thanks for the link. Couldn’t find that info anywhere.

You’re welcome!

Hi Jason,

I have read through all the posts above and am glad that you are looking into multisite too ??

As a quick fix, would the same settings not work on every site if the following 2 fields could be edited: (For Gmail API)

Authorized JavaScript origins
Authorized redirect URI

Also, if I just use ordinary SMTP for Gmail, what values must be selected for the security and authentication fields?

Many thanks,

Grant

As a quick fix, would the same settings not work on every site if the following 2 fields could be edited: (For Gmail API)

Unfortunately, no. That’s part of OAuth 2.0’s security. These URLs are used to redirect back to Postman so that a grant code can be exchanged for an auth token.

Also, if I just use ordinary SMTP for Gmail, what values must be selected for the security and authentication fields?

The wizard will do this for you.

With port 587, use STARTTLS security.
With port 465, use SMTPS security.

For authentication, use PLAIN, LOGIN or OAUTH2

Thanks for the quick response & clarity Jason! Much appreciated ??

So in the meantime I will use OAuth for the main site and ordinary SMTP for all new sites created and which is done using New Blog Templates from premium.wpmudev.org (settings are automatically populated)

For the authentication field I have selected “Plain” and which is working for Gmail SMTP. (Not sure where you would use “Login”?)

If you create a global settings OAuth feature for multisite I will be very keen to use such functionality and even if you make this a premium add-on.

I have previously used another well know SMTP plugin and a “hacker” managed to intercept / grab the login credentials. I am not convinced that the hacker got access to my database but obtained the credentials through the transmission process, so I am really wanting to move completely to OAuth.

but obtained the credentials through the transmission process

That’s very unlikely, unless you had security set to NONE. Moving to OAuth2 is a good idea anyway. I noticed that Mail.app on my Mac recently switched from passwords to OAuth2 almost completely transparently.

FYI This plugin does not work with WPMU 4.2.2 and you might save someone time by letting people know up-front. Symptom is no menu after activating. Would be glad to test it again when you make it Network friendly, thanks.

This plugin does not work with WPMU 4.2.2

@raincity that’s quite a bold claim. Unfortunately, my very own site https://www.codingmonkey.ca is a WPMU 4.2.2 site. and most likely everyone else in this very thread is also running 4.2.2.

Symptom is no menu after activating

Then you have a badly coded plugin or theme on your site interfering with the Postman menu. And with the sparse details you’ve given me, there is nothing I can do about it.

Would be glad to test it again when you make it Network friendly, thanks.

In multisite there is two options for activating the plugins: network activate and per-site activate.
When a plugin is network activated it is activate in all of the subsites and the site-admins cannot deactivate it (they cannot even see it in their plugins menu)
When a plugin is not network activated, the site admins can see it in their plugins menu and activate it, and if it is active they can deactivate it.
Based on the above, I think if the plugin is network activated, the menu of the plugin must show up in the network admin (not in subsites) and only the super admin can set the options and see the notifications, and the settings are used network-wide; but if the plugin is not network activated, if it is active in a subsite the site admin can see and set the options as a single site.

@webnashr, great suggestion, thanks!

One more for multiste admin configuration on postman! Nice plugin ??