G-Lock EasyMail is a bulk-email production system that keeps contact lists, message templates, sending accounts and campaign history on an EasyMail server. Staff work through a desktop client or an optional browser interface. It is not an email delivery network by itself: the administrator connects it to an SMTP server or a supported relay service that accepts and transmits the messages.
Server owns the data
The EasyMail Server stores groups, templates, drafts, accounts, sent mail and bounce settings. The Client connects to that service and edits the shared material. A single computer can run both parts, while an office can place the Server on an always-on machine and install clients on individual workstations.
This split matters during outages. Closing a desktop client does not erase server data, but shutting down or disconnecting the Server prevents other users from reaching their workplaces and can stop scheduled work. Backups must cover the server data rather than only the files on a user’s workstation.
Workplaces separate campaigns
An administrator creates users and assigns them to workplaces. Each workplace contains its own sending accounts, templates, contact groups, sent messages and Bounce Handler. One person can operate with one workplace, while a team can divide brands or departments without mixing their campaign material.
A workplace is more than a visual folder. Assigning a user to the wrong one exposes the wrong accounts and lists in that session. Permission planning should happen before several people begin importing contacts, because moving established campaign data later requires more care than creating the intended separation at the start.
Delivery needs a relay
G-Lock EasyMail can send through a third-party SMTP server or a connected service. The account settings need the server address, port, authentication details and verified sender information required by that provider. Some services use SMTP credentials that differ from their normal account or API credentials.
The provider still controls daily quotas, maximum send rate and sender verification. A campaign queued in G-Lock EasyMail can fail when the relay rejects a sender or reaches its allowance. The campaign size and speed must therefore match the sending account, not merely the number of contacts stored locally.
Contacts need clean fields
CSV import turns columns into contact fields that can drive names, personal links, dates and individual attachments. Merge tags insert those values into a subject or message. Previewing several recipients catches a column mapped to the wrong field before one mistake is repeated across the entire group.
Missing data needs an explicit fallback. A personalized greeting that assumes every row has a first name can expose an empty tag. G-Lock EasyMail can also run scripts over field values, but a script acts during sending, so it should be tested on a small group before it touches a large campaign.
Templates carry files
Templates can enter or leave the program as EML files or ZIP archives. For ZIP import, the HTML file inside must share the archive’s base name. Local images can travel with an exported template, while images already loaded from a website remain remote references.
An imported design can look correct in the editor yet fail in a recipient’s mail reader. Uploading images to a reachable web server and sending a test to several mail services exposes blocked images, unsupported CSS and a broken unsubscribe link before the main send.
Automation follows events
Follow-up sequences can send after a subscriber joins a group or after a defined delay. A separate action can respond to a click with a reminder or another message. These sequences depend on the contact’s status and timing records, so duplicate imports or an incorrect time interval can trigger mail at the wrong moment.
Unsubscribe processing belongs in the same workflow. The message needs a working unsubscribe link, and external contact stores need their exclusion data synchronized before another campaign. G-Lock EasyMail can create the rule, but it cannot correct a list that an administrator reimports without preserving the exclusions.
Upgrades need migration
The current product generation does not install directly over older major generations. The startup guide directs existing users to choose a new directory and import their contacts. Installing over the old location risks mixing components that do not share the same data layout.
A new installation also begins with server connection and activation steps. The first administrator should replace the default password and store the new credential safely. Losing server access can stop every connected workplace, so the password and a tested server backup belong in the deployment record.
