Yasa Webmail lets you use an existing Nexus-hosted email mailbox in your browser. Start with your shared Yasa sign-in, then open the mailbox with its full email address and mailbox password. Once connected to Yasa Webmail, you can read conversations, organise folders, compose messages and manage the mailbox settings available to you.
This gives everyday email a clear place within the wider platform. You can work with hosted mail without opening infrastructure administration. However, the mailbox must already exist: registering a Yasa profile does not create an email address or grant access to somebody else’s messages.
Where Yasa Webmail fits in the ecosystem
The Webmail entry page provides browser access to email hosted through Nexus. Its mail interface uses Roundcube. The hosting service manages the mailbox resource, while Webmail gives its authorised user a practical way to work with the messages inside it.
Our Yasa Ecosystem overview explains how the services fit together. For hosting accounts and assigned infrastructure, read the Yasa Nexus guide. Those administration permissions are separate from the credentials needed to read an existing mailbox.
In particular, a Nexus administration invitation is not required simply to open Webmail. A hosted mailbox and its valid credentials are still necessary. If your business needs a new address, ask the mailbox administrator to arrange it through the appropriate hosting process before trying to sign in.
Sign in to your Yasa Webmail mailbox
First, open Webmail from the ecosystem menu or its normal address. Complete the Yasa sign-in when requested. Then enter the full mailbox email address and its own password in the mailbox form. Wait for the folders and messages to finish loading before deciding whether anything is missing.
The hosted Webmail sign-in guide explains the access sequence. Shared identity and mailbox identity can have different roles. Our Yasa Account guide covers the shared profile and supported sign-in methods; it does not replace the mailbox’s own credentials.
Check the active mailbox before reading, composing or changing a setting, especially when you work with several addresses. If access is refused, verify the exact address with its administrator. Repeatedly changing the shared Account password will not resolve a problem with a separate mailbox password.
Find messages before changing or removing them
Begin with the folder and search scope. Open the relevant folder, then narrow the sender, subject or other available criteria. Review Spam or Junk when an expected message is absent. A selected folder, unread filter or narrow search can hide a message that remains safely stored elsewhere.
Use the available move, flag and read-state controls to organise work after finding the intended message. The message organisation guide explains the basic sequence. For example, a project folder can collect a conversation while a flag identifies a reply that still needs attention.
Settings and Folders lets you inspect the existing hierarchy and supported folder controls. Folder subscriptions determine which available folders appear in the mailbox view. Hiding a folder does not delete its messages, so inspect subscriptions before using removal as a remedy for a missing folder.
Also review the configured special folders before changing where Sent, Drafts, Spam or Trash are stored. The folder settings guide covers those choices. Follow your organisation’s retention rules and preserve the intended content before deleting a folder or emptying messages.
Compose, reply and attach with a clear recipient list
Open a new message or reply to the intended conversation. Review every recipient, including the wider audience of a reply-all action. Next, attach the correct file and wait for its upload to finish. Check the sender identity and message contents before choosing Send once.
Afterward, inspect the resulting confirmation or Sent folder. The compose and attachment guide explains this workflow. A recorded send and successful delivery to every recipient are different stages; keep any delivery failure or bounce available for investigation.
For a useful signature, open Settings and Identities, then select the intended sender. Review the allowed name and signature fields, save, and check a new draft. The sender identity guide explains the controls. Editing a signature does not create an alias or permission to send as another person.
Keep Yasa Webmail preferences tied to the mailbox
Settings and Preferences groups the available display, composition, mailbox and contact choices. Change the setting you need, save it, then reopen the affected view. Responses provides reusable text for supported compose controls. Review that text in the actual draft before sending it to a real recipient.
A saved response is different from an automatic reply or forwarding rule. The preferences and responses guide explains the distinction. Ask the mailbox administrator about a server-side feature when the interface does not offer it, instead of assuming an optional plugin is available.
New-message alerts also belong to the mailbox interface. Review the browser, desktop or sound options currently offered and use the adjacent Test control when available. The notification guide covers browser permissions and device restrictions. These choices are separate from Account notification emails or marketing preferences.
Archive and download for different purposes
Archive moves selected messages to the configured archive destination within the mailbox. Check the result in that folder, including relevant subfolders when searching later. The archive guide explains destination settings and folder visibility. Moving mail between folders in the same account does not itself free storage.
Downloads serve a different purpose. Use an attachment’s download control, Download all attachments when offered, or the supported message export action. Choose the format for the tool that will read it. The message download guide covers available selections and smaller batches when an export reaches a limit.
Check that the browser completed the download and that the intended files are usable before relying on them. Keep confidential exports in an appropriate private location. An attachment ZIP is not a full mailbox backup, and downloading selected messages does not remove the originals from the hosted account.
Handle contacts and imports deliberately
Contacts provides the address books and groups available to the selected mailbox. Search existing entries before adding another, and verify each address before saving. The contacts guide explains group membership and read-only directories. A contact group organises recipients; it does not create their mailboxes.
For supported contact imports or exports, review the selected address book, format and duplicate-handling choices. Then inspect the result. The contact transfer guide covers that workflow. Keep downloaded address-book files private and transfer only information you are permitted to handle.
Saved email uses a separate import process into an intended mailbox folder. Check the offered format, size guidance and available quota, submit once, and inspect accepted messages before retrying a failed portion. The message import guide explains why this does not transfer an entire service configuration or guarantee compatibility with another program’s ZIP.
Manage mailbox credentials and investigate problems
Where available, Settings and Password changes the hosted mailbox credential. Follow the displayed requirements, inspect the confirmation and update other authorised mail apps that use that mailbox. The mailbox password guide explains the process. This signed-in setting is separate from shared Account credentials and is not a recovery form for a locked-out user.
For missing email, check identity, folders, search filters and Spam first. For a sending problem, inspect the error and whether a Sent copy exists. Also check available quota information or ask the administrator. The mail troubleshooting guide separates access, submission and recipient delivery.
An administrator can investigate more effectively with the approximate time, mailbox address, recipient domain and non-sensitive error details. Keep passwords and confidential message contents out of support requests. If a send outcome is uncertain, check that attempt before repeatedly resending the same private material.
Make hosted email part of a practical website handover
Imagine a small business preparing a new website and a hosted contact mailbox. The project owner identifies the address and who needs to use it. The hosting administrator arranges the mailbox and delivery setup, while its user receives the correct sign-in information through the agreed private route.
The user can then enter Yasa Webmail, check the mailbox identity and prepare the intended signature. This illustrative handover keeps infrastructure responsibilities and everyday email use clear. Our website planning and launch guide explains why domain, mailbox and external-service dependencies belong in the brief.
Start with the mailbox task you need
Use Yasa Webmail for the hosted address you are authorised to access, then choose the relevant message, folder or setting. Review the accepted result before continuing. That keeps everyday correspondence manageable while shared identity, hosting administration and mailbox access retain their own clear roles.
Use the public Webmail help guides for current instructions. If you need a hosted mailbox or help with an existing one, contact Yasa with the service and a non-sensitive description of the task. Keep mailbox passwords and private message contents out of the enquiry.
