{#name#} vs {#loginname#} for stored email password

User discussion and information resource forum for Image products.
Post Reply
rseiler
Posts: 70
Joined: Sat May 05, 2012 10:29 pm

{#name#} vs {#loginname#} for stored email password

Post by rseiler »

I notice in IFW's manual that {#loginname#} is used in some of the examples but that {#name#} appears in more places so is probably what's intended. Both work and appear to do the same thing, so I guess it doesn't matter unless one of them goes away in the future.

Is it intentional?
TeraByte Support(PP)
Posts: 1646
Joined: Fri Aug 12, 2011 12:51 am

Re: {#name#} vs {#loginname#} for stored email password

Post by TeraByte Support(PP) »

You can use either one, but you're not limited to those. You would use whatever name you use for the saved password. If you save it as "mysavedpassword" then you would use {#mysavedpassword#} or if saved as "emailpswd" you would use {#emailpswd#}, etc. Stored passwords can be managed on the Password tab of IFW settings.
rseiler
Posts: 70
Joined: Sat May 05, 2012 10:29 pm

Re: {#name#} vs {#loginname#} for stored email password

Post by rseiler »

I missed that tab entirely, concentrating only on the Email tab.

Since the Email tab is the only place I entered a password, is that meant to be a form of "stored" password as well, retrievable with either of the above names? Or did I just get lucky? I can easily create a formal stored password with a custom name now that I know about it, but I'm curious.
TeraByte Support(PP)
Posts: 1646
Joined: Fri Aug 12, 2011 12:51 am

Re: {#name#} vs {#loginname#} for stored email password

Post by TeraByte Support(PP) »

It can be either a plain text password or a stored password. If stored password you would use the {#name#} format.
Post Reply