Additions:
======Concepts » 1. The Basics======
===One user, one message===
By design, a single message is only sent to any user once. In other words, if an admin sends the same message to multiple lists (which share the same users), each user in these lists would only get that message once.
===Double Opt-In===
By default (unless the admin approves them manually), users do not receive messages until they **confirm** their membership. This means that as soon as they sign-up for a list they receive a Confirmation Request to the e-mail address they mentioned. They must then click the link that was included in the email to acknowledge and confirm it was actually them who filled the online sign-up form.
While some users are bound not to confirm their registration, due to the passing of time or newbie confusion, this lowers the risk of flagging your messages as spam (because it tries to make sure users really did register for themselves).
===Single Opt-Out===
For the same reason, opt-out is only a single step. This is a mandatory requirement in the rules of many ISPs which otherwise may flag your messages (to still subscribed users) as spam.
A semi double opt-out procedure could be accomplished though by asking for passwords (see [[PhpListConfiguration]]), assuming the users already have ones.
===Misc===
===One user, one message===
By design, a single message is only sent to any user once. In other words, if an admin sends the same message to multiple lists (which share the same users), each user in these lists would only get that message once.
===Double Opt-In===
By default (unless the admin approves them manually), users do not receive messages until they **confirm** their membership. This means that as soon as they sign-up for a list they receive a Confirmation Request to the e-mail address they mentioned. They must then click the link that was included in the email to acknowledge and confirm it was actually them who filled the online sign-up form.
While some users are bound not to confirm their registration, due to the passing of time or newbie confusion, this lowers the risk of flagging your messages as spam (because it tries to make sure users really did register for themselves).
===Single Opt-Out===
For the same reason, opt-out is only a single step. This is a mandatory requirement in the rules of many ISPs which otherwise may flag your messages (to still subscribed users) as spam.
A semi double opt-out procedure could be accomplished though by asking for passwords (see [[PhpListConfiguration]]), assuming the users already have ones.
===Misc===
Deletions:
By design, a single Message is only sent to any User once.
By default Users do not receive Messages until they **Confirm** their List membership. (as an Admin you are able to override this) This means that as soon as they sign-up for a List they receive a Confirmation Request (email). They must then click the link that was included in the email to acknowledge and agree to List membership.
Additions:
====Users & Lists====
{{image class="right" alt="users and subscriptions" url="http://pizzabytheslice.com/phplist/pbts_xtra/images/users-lists.gif" }}
phpList employs a very flexible “membership” concept.
A **User** is an email address plus some **Preferences**, such as "I always want HTML emails", and, optionally, some **Attributes** ("my name is Bob", "I'm a Pastafarian").
A **List** is a grouper around some theme. It has Messages and Members.
A User may be a Member of (or Subscriber to) multiple Lists.
If you **Import** Users, from a CSV file for example, you have the option of automatically adding them to any of your Lists.
This "Many-to-Many" between Lists and Users (each List may have many Users; each User may belong to many Lists) may seem odd, but, oh, say you have a "Bathroom Safety", "Fishing Tips", and "Lounger Living" mailings. Well, you could setup these three Lists and allow your Users to Subscribe to any or all of your Lists they wish.
Many sites using phpList only have one List, and all Users should be Members of that, so it seems odd, this extra flexibility. You'll find that you can customize messages fairly well to remove any possible confusion for you or your Users.
====Messages & Templates====
{{image class="right" alt="DVD logo" title="An Image Link" url="http://pizzabytheslice.com/phplist/pbts_xtra/images/mona-lisa-template.jpg" }}
Now the other side of the system, Messages & Templates.
A **Message** is a single email (event) sent to the Members of one or more Lists (yes, targeting multiple lists is allowed)
A Message may use a [[TemplatesInfo Template]] or you may enter the Message Content in a "one-off" fashion, entering your HTML directly.
A Template must contain a CONTENT [[Placeholders Placeholder]]. This defines an area within your email design that will be filled with the Message Content, allowing you to have a consistent look to your pages, while the content changes with each mailing.
Other Placeholders allow you to include a unique URL for each User that allows them to change their Preferences or Unsubscribe. You may also use any of the optional Attributes you defined.
====System Behaviors====
Here are a few built-in behaviors of phpList. Love 'em. Hate 'em. Either way, live with 'em.
By design, a single Message is only sent to any User once.
By default Users do not receive Messages until they **Confirm** their List membership. (as an Admin you are able to override this) This means that as soon as they sign-up for a List they receive a Confirmation Request (email). They must then click the link that was included in the email to acknowledge and agree to List membership.
There are lots more features (some would say quirks, but all have a reason for being there once you see the Big Picture), so explore the documentation.
CategoryDocumentation
{{image class="right" alt="users and subscriptions" url="http://pizzabytheslice.com/phplist/pbts_xtra/images/users-lists.gif" }}
phpList employs a very flexible “membership” concept.
A **User** is an email address plus some **Preferences**, such as "I always want HTML emails", and, optionally, some **Attributes** ("my name is Bob", "I'm a Pastafarian").
A **List** is a grouper around some theme. It has Messages and Members.
A User may be a Member of (or Subscriber to) multiple Lists.
If you **Import** Users, from a CSV file for example, you have the option of automatically adding them to any of your Lists.
This "Many-to-Many" between Lists and Users (each List may have many Users; each User may belong to many Lists) may seem odd, but, oh, say you have a "Bathroom Safety", "Fishing Tips", and "Lounger Living" mailings. Well, you could setup these three Lists and allow your Users to Subscribe to any or all of your Lists they wish.
Many sites using phpList only have one List, and all Users should be Members of that, so it seems odd, this extra flexibility. You'll find that you can customize messages fairly well to remove any possible confusion for you or your Users.
====Messages & Templates====
{{image class="right" alt="DVD logo" title="An Image Link" url="http://pizzabytheslice.com/phplist/pbts_xtra/images/mona-lisa-template.jpg" }}
Now the other side of the system, Messages & Templates.
A **Message** is a single email (event) sent to the Members of one or more Lists (yes, targeting multiple lists is allowed)
A Message may use a [[TemplatesInfo Template]] or you may enter the Message Content in a "one-off" fashion, entering your HTML directly.
A Template must contain a CONTENT [[Placeholders Placeholder]]. This defines an area within your email design that will be filled with the Message Content, allowing you to have a consistent look to your pages, while the content changes with each mailing.
Other Placeholders allow you to include a unique URL for each User that allows them to change their Preferences or Unsubscribe. You may also use any of the optional Attributes you defined.
====System Behaviors====
Here are a few built-in behaviors of phpList. Love 'em. Hate 'em. Either way, live with 'em.
By design, a single Message is only sent to any User once.
By default Users do not receive Messages until they **Confirm** their List membership. (as an Admin you are able to override this) This means that as soon as they sign-up for a List they receive a Confirmation Request (email). They must then click the link that was included in the email to acknowledge and agree to List membership.
There are lots more features (some would say quirks, but all have a reason for being there once you see the Big Picture), so explore the documentation.
CategoryDocumentation
Deletions:
Revision [1249]
Edited on 2007-06-30 05:05:54 by Oo6IenAdditions:
====Users
Deletions:
{{image class="right" alt="users and subscriptions" url="http://pizzabytheslice.com/phplist/pbts_xtra/images/users-lists.gif" }}
phpList employs a very flexible “membership” concept.
A **User** is an email address plus some **Preferences**, such as "I always want HTML emails", and, optionally, some **Attributes** ("my name is Bob", "I'm a Pastafarian").
A **List** is a grouper around some theme. It has Messages and Members.
A User may be a Member of (or Subscriber to) multiple Lists.
If you **Import** Users, from a CSV file for example, you have the option of automatically adding them to any of your Lists.
This "Many-to-Many" between Lists and Users (each List may have many Users; each User may belong to many Lists) may seem odd, but, oh, say you have a "Bathroom Safety", "Fishing Tips", and "Lounger Living" mailings. Well, you could setup these three Lists and allow your Users to Subscribe to any or all of your Lists they wish.
Many sites using phpList only have one List, and all Users should be Members of that, so it seems odd, this extra flexibility. You'll find that you can customize messages fairly well to remove any possible confusion for you or your Users.
====Messages & Templates====
{{image class="right" alt="DVD logo" title="An Image Link" url="http://pizzabytheslice.com/phplist/pbts_xtra/images/mona-lisa-template.jpg" }}
Now the other side of the system, Messages & Templates.
A **Message** is a single email (event) sent to the Members of one or more Lists (yes, targeting multiple lists is allowed)
A Message may use a [[TemplatesInfo Template]] or you may enter the Message Content in a "one-off" fashion, entering your HTML directly.
A Template must contain a CONTENT [[Placeholders Placeholder]]. This defines an area within your email design that will be filled with the Message Content, allowing you to have a consistent look to your pages, while the content changes with each mailing.
Other Placeholders allow you to include a unique URL for each User that allows them to change their Preferences or Unsubscribe. You may also use any of the optional Attributes you defined.
====System Behaviors====
Here are a few built-in behaviors of phpList. Love 'em. Hate 'em. Either way, live with 'em.
By design, a single Message is only sent to any User once.
By default Users do not receive Messages until they **Confirm** their List membership. (as an Admin you are able to override this) This means that as soon as they sign-up for a List they receive a Confirmation Request (email). They must then click the link that was included in the email to acknowledge and agree to List membership.
There are lots more features (some would say quirks, but all have a reason for being there once you see the Big Picture), so explore the documentation.
CategoryDocumentation
Additions:
==Concepts » 1. the Basics==
====Users & Lists====
{{image class="right" alt="users and subscriptions" url="http://pizzabytheslice.com/phplist/pbts_xtra/images/users-lists.gif" }}
phpList employs a very flexible “membership” concept.
A **User** is an email address plus some **Preferences**, such as "I always want HTML emails", and, optionally, some **Attributes** ("my name is Bob", "I'm a Pastafarian").
A **List** is a grouper around some theme. It has Messages and Members.
A User may be a Member of (or Subscriber to) multiple Lists.
If you **Import** Users, from a CSV file for example, you have the option of automatically adding them to any of your Lists.
This "Many-to-Many" between Lists and Users (each List may have many Users; each User may belong to many Lists) may seem odd, but, oh, say you have a "Bathroom Safety", "Fishing Tips", and "Lounger Living" mailings. Well, you could setup these three Lists and allow your Users to Subscribe to any or all of your Lists they wish.
Many sites using phpList only have one List, and all Users should be Members of that, so it seems odd, this extra flexibility. You'll find that you can customize messages fairly well to remove any possible confusion for you or your Users.
====Messages & Templates====
{{image class="right" alt="DVD logo" title="An Image Link" url="http://pizzabytheslice.com/phplist/pbts_xtra/images/mona-lisa-template.jpg" }}
Now the other side of the system, Messages & Templates.
A **Message** is a single email (event) sent to the Members of one or more Lists (yes, targeting multiple lists is allowed)
A Message may use a [[TemplatesInfo Template]] or you may enter the Message Content in a "one-off" fashion, entering your HTML directly.
A Template must contain a CONTENT [[Placeholders Placeholder]]. This defines an area within your email design that will be filled with the Message Content, allowing you to have a consistent look to your pages, while the content changes with each mailing.
Other Placeholders allow you to include a unique URL for each User that allows them to change their Preferences or Unsubscribe. You may also use any of the optional Attributes you defined.
====System Behaviors====
Here are a few built-in behaviors of phpList. Love 'em. Hate 'em. Either way, live with 'em.
By design, a single Message is only sent to any User once.
By default Users do not receive Messages until they **Confirm** their List membership. (as an Admin you are able to override this) This means that as soon as they sign-up for a List they receive a Confirmation Request (email). They must then click the link that was included in the email to acknowledge and agree to List membership.
There are lots more features (some would say quirks, but all have a reason for being there once you see the Big Picture), so explore the documentation.
CategoryDocumentation
====Users & Lists====
{{image class="right" alt="users and subscriptions" url="http://pizzabytheslice.com/phplist/pbts_xtra/images/users-lists.gif" }}
phpList employs a very flexible “membership” concept.
A **User** is an email address plus some **Preferences**, such as "I always want HTML emails", and, optionally, some **Attributes** ("my name is Bob", "I'm a Pastafarian").
A **List** is a grouper around some theme. It has Messages and Members.
A User may be a Member of (or Subscriber to) multiple Lists.
If you **Import** Users, from a CSV file for example, you have the option of automatically adding them to any of your Lists.
This "Many-to-Many" between Lists and Users (each List may have many Users; each User may belong to many Lists) may seem odd, but, oh, say you have a "Bathroom Safety", "Fishing Tips", and "Lounger Living" mailings. Well, you could setup these three Lists and allow your Users to Subscribe to any or all of your Lists they wish.
Many sites using phpList only have one List, and all Users should be Members of that, so it seems odd, this extra flexibility. You'll find that you can customize messages fairly well to remove any possible confusion for you or your Users.
====Messages & Templates====
{{image class="right" alt="DVD logo" title="An Image Link" url="http://pizzabytheslice.com/phplist/pbts_xtra/images/mona-lisa-template.jpg" }}
Now the other side of the system, Messages & Templates.
A **Message** is a single email (event) sent to the Members of one or more Lists (yes, targeting multiple lists is allowed)
A Message may use a [[TemplatesInfo Template]] or you may enter the Message Content in a "one-off" fashion, entering your HTML directly.
A Template must contain a CONTENT [[Placeholders Placeholder]]. This defines an area within your email design that will be filled with the Message Content, allowing you to have a consistent look to your pages, while the content changes with each mailing.
Other Placeholders allow you to include a unique URL for each User that allows them to change their Preferences or Unsubscribe. You may also use any of the optional Attributes you defined.
====System Behaviors====
Here are a few built-in behaviors of phpList. Love 'em. Hate 'em. Either way, live with 'em.
By design, a single Message is only sent to any User once.
By default Users do not receive Messages until they **Confirm** their List membership. (as an Admin you are able to override this) This means that as soon as they sign-up for a List they receive a Confirmation Request (email). They must then click the link that was included in the email to acknowledge and agree to List membership.
There are lots more features (some would say quirks, but all have a reason for being there once you see the Big Picture), so explore the documentation.
CategoryDocumentation
Deletions:
Revision [1093]
Edited on 2007-04-20 06:17:47 by EqbFau (unregistered user)Additions:
==Concepts
Deletions:
====Users & Lists====
{{image class="right" alt="users and subscriptions" url="http://pizzabytheslice.com/phplist/pbts_xtra/images/users-lists.gif" }}
phpList employs a very flexible “membership” concept.
A **User** is an email address plus some **Preferences**, such as "I always want HTML emails", and, optionally, some **Attributes** ("my name is Bob", "I'm a Pastafarian").
A **List** is a grouper around some theme. It has Messages and Members.
A User may be a Member of (or Subscriber to) multiple Lists.
If you **Import** Users, from a CSV file for example, you have the option of automatically adding them to any of your Lists.
This "Many-to-Many" between Lists and Users (each List may have many Users; each User may belong to many Lists) may seem odd, but, oh, say you have a "Bathroom Safety", "Fishing Tips", and "Lounger Living" mailings. Well, you could setup these three Lists and allow your Users to Subscribe to any or all of your Lists they wish.
Many sites using phpList only have one List, and all Users should be Members of that, so it seems odd, this extra flexibility. You'll find that you can customize messages fairly well to remove any possible confusion for you or your Users.
====Messages & Templates====
{{image class="right" alt="DVD logo" title="An Image Link" url="http://pizzabytheslice.com/phplist/pbts_xtra/images/mona-lisa-template.jpg" }}
Now the other side of the system, Messages & Templates.
A **Message** is a single email (event) sent to the Members of one or more Lists (yes, targeting multiple lists is allowed)
A Message may use a [[TemplatesInfo Template]] or you may enter the Message Content in a "one-off" fashion, entering your HTML directly.
A Template must contain a CONTENT [[Placeholders Placeholder]]. This defines an area within your email design that will be filled with the Message Content, allowing you to have a consistent look to your pages, while the content changes with each mailing.
Other Placeholders allow you to include a unique URL for each User that allows them to change their Preferences or Unsubscribe. You may also use any of the optional Attributes you defined.
====System Behaviors====
Here are a few built-in behaviors of phpList. Love 'em. Hate 'em. Either way, live with 'em.
By design, a single Message is only sent to any User once.
By default Users do not receive Messages until they **Confirm** their List membership. (as an Admin you are able to override this) This means that as soon as they sign-up for a List they receive a Confirmation Request (email). They must then click the link that was included in the email to acknowledge and agree to List membership.
There are lots more features (some would say quirks, but all have a reason for being there once you see the Big Picture), so explore the documentation.
CategoryDocumentation
Additions:
A Message may use a [[TemplatesInfo Template]] or you may enter the Message Content in a "one-off" fashion, entering your HTML directly.
A Template must contain a CONTENT [[Placeholders Placeholder]]. This defines an area within your email design that will be filled with the Message Content, allowing you to have a consistent look to your pages, while the content changes with each mailing.
A Template must contain a CONTENT [[Placeholders Placeholder]]. This defines an area within your email design that will be filled with the Message Content, allowing you to have a consistent look to your pages, while the content changes with each mailing.
Deletions:
A Template must contain a CONTENT **[[Placeholders Placeholder]]**. This defines an area within your email design that will be filled with the Message Content, allowing you to have a consistent look to your pages, while the content changes with each mailing.
Revision [605]
Edited on 2006-07-17 16:27:59 by HernoLAdditions:
[[PhplistDocumentation phplist Documentation]]
Deletions:
Revision [483]
Edited on 2006-02-06 05:42:44 by BuzCarterAdditions:
A Template must contain a CONTENT **[[Placeholders Placeholder]]**. This defines an area within your email design that will be filled with the Message Content, allowing you to have a consistent look to your pages, while the content changes with each mailing.
Deletions:
Revision [462]
Edited on 2006-02-06 03:42:31 by BuzCarterAdditions:
====System Behaviors====
There are lots more features (some would say quirks, but all have a reason for being there once you see the Big Picture), so explore the documentation.
There are lots more features (some would say quirks, but all have a reason for being there once you see the Big Picture), so explore the documentation.
Deletions:
Revision [461]
Edited on 2006-02-06 03:38:18 by BuzCarterAdditions:
If you **Import** Users, from a CSV file for example, you have the option of automatically adding them to any of your Lists.
====Loose Ends====
Here are a few built-in behaviors of phpList. Love 'em. Hate 'em. Either way, live with 'em.
By design, a single Message is only sent to any User once.
By default Users do not receive Messages until they **Confirm** their List membership. (as an Admin you are able to override this) This means that as soon as they sign-up for a List they receive a Confirmation Request (email). They must then click the link that was included in the email to acknowledge and agree to List membership.
CategoryDocumentation
====Loose Ends====
Here are a few built-in behaviors of phpList. Love 'em. Hate 'em. Either way, live with 'em.
By design, a single Message is only sent to any User once.
By default Users do not receive Messages until they **Confirm** their List membership. (as an Admin you are able to override this) This means that as soon as they sign-up for a List they receive a Confirmation Request (email). They must then click the link that was included in the email to acknowledge and agree to List membership.
CategoryDocumentation
Deletions:
Revision [459]
Edited on 2006-02-06 02:47:07 by BuzCarterAdditions:
PhplistDocumentation
----
==Concepts » 1. the Basics==
====Users & Lists====
====Messages & Templates====
----
==Concepts » 1. the Basics==
====Users & Lists====
====Messages & Templates====
Deletions:
===Messages & Templates===
Revision [457]
Edited on 2006-02-06 02:38:20 by BuzCarterAdditions:
A **User** is an email address plus some **Preferences**, such as "I always want HTML emails", and, optionally, some **Attributes** ("my name is Bob", "I'm a Pastafarian").
A **List** is a grouper around some theme. It has Messages and Members.
This "Many-to-Many" between Lists and Users (each List may have many Users; each User may belong to many Lists) may seem odd, but, oh, say you have a "Bathroom Safety", "Fishing Tips", and "Lounger Living" mailings. Well, you could setup these three Lists and allow your Users to Subscribe to any or all of your Lists they wish.
A **Message** is a single email (event) sent to the Members of one or more Lists (yes, targeting multiple lists is allowed)
A Message may use a **Template** or you may enter the Message Content in a "one-off" fashion, entering your HTML directly.
A Template must contain a CONTENT **Placeholder**. This defines an area within your email design that will be filled with the Message Content, allowing you to have a consistent look to your pages, while the content changes with each mailing.
A **List** is a grouper around some theme. It has Messages and Members.
This "Many-to-Many" between Lists and Users (each List may have many Users; each User may belong to many Lists) may seem odd, but, oh, say you have a "Bathroom Safety", "Fishing Tips", and "Lounger Living" mailings. Well, you could setup these three Lists and allow your Users to Subscribe to any or all of your Lists they wish.
A **Message** is a single email (event) sent to the Members of one or more Lists (yes, targeting multiple lists is allowed)
A Message may use a **Template** or you may enter the Message Content in a "one-off" fashion, entering your HTML directly.
A Template must contain a CONTENT **Placeholder**. This defines an area within your email design that will be filled with the Message Content, allowing you to have a consistent look to your pages, while the content changes with each mailing.
Deletions:
A List is a grouper around some theme. It has Messages and Members.
This Many-to-Many between Lists and Users may seem odd, but, oh, say you have a "Bathroom Safety", "Fishing Tips", and "Lounger Living" mailings. Well, you could setup these three Lists and allow your Users to Subscribe to any or all of your Lists they wish.
A Message is a single email (event) sent to the Members of one or more Lists (yes, targeting multiple lists is allowed)
A Message may use a Template or you may enter the Message Content in a "one-off" fashion, entering your HTML directly.
A Template must contain a CONTENT Placeholder. This defines an area within your email design that will be filled with the Message Content, allowing you to have a consistent look to your pages, while the content changes with each mailing.
Revision [456]
Edited on 2006-02-06 02:36:26 by BuzCarterAdditions:
===Users & Lists===
===Messages & Templates===
===Messages & Templates===
Deletions:
==Messages & Templates==
