Getting Started

1Logging in for the first time

Your welcome email contains a link to the client portal and your initial login credentials. The portal is at cloudserverforemail.com/billing/clientarea.php. On first login you will be prompted to set a new password.

The portal is the operational centre for everything that follows. Billing, ticket support, IP management, SMTP credential rotation, and Postmaster Tools status all flow through it. Bookmark the URL on first login — password resets work but slow down operational changes when they happen during incidents. The session timeout is 8 hours of inactivity; production users should expect to re-authenticate at the start of each working day.

2Locating your SMTP credentials

In the portal navigate to Services → Your Active Service → SMTP Credentials. You will find your SMTP hostname, username, password, and available ports (587 STARTTLS, 465 SSL, 25 if enabled).

Three port notes worth carrying into the integration phase. Port 587 with STARTTLS is the default for application-to-MTA traffic and the right choice for MailWizz, sendmail, or custom application sending. Port 465 with implicit TLS is appropriate for legacy systems that do not support STARTTLS negotiation properly. Port 25 is unblocked on CSE infrastructure but blocked at most residential ISPs and many cloud providers (AWS, Azure, GCP) outbound — not because of CSE policy, because of the originating network. If port 25 fails from your application server, the path between your network and CSE is the cause, not the SMTP credentials.

3Your IP pool allocation

Navigate to Services → IP Management to see your IPs. Each will show current warm-up status, daily volume allocation, and blacklist status checked against 50+ DNSBLs. Multiple IPs are automatically rotated — no manual configuration needed.

The allocation matters for capacity planning more than for daily operations. The IP Management view shows your sustained capacity per IP — typically 500K-1M messages per day per warmed IP at major ISPs, lower during warming. Total programme capacity is the sum minus any IPs currently in warming or on hold. The DNSBL check runs every 30 minutes against Spamhaus ZEN/SBL/CSS, SpamCop, Barracuda, SORBS, and 45 other lists. Listings produce an automated alert and a triage path that does not wait for client action.

The /24 block these IPs sit in is also tracked because reputation propagates across adjacent IPs in the same block. CSE OÜ maintains clean /24 ranges in the Tornimae 5 datacenter; you can verify the block reputation at Spamhaus and Talos Intelligence from the IP Management page links.

4What your account manager does in the first 48 hours

Within 48 hours, your account manager will review your use case, configure your IP warming schedule, verify PTR records, set up Postmaster Tools monitoring, and send you your warming schedule with daily volume caps. Contact them directly if you haven't received this within 48 hours.

The use-case review affects everything downstream. Cold email, bulk marketing, and transactional traffic each have different IP requirements, different complaint thresholds, and different warming pace. The account manager's review categorises your traffic and aligns the infrastructure to it — mixing categories on the same IPs damages all three, so the categorisation matters even if your operation runs only one type today. PTR records (reverse DNS) are configured to match the sending domain because both Gmail and Microsoft check reverse-DNS-to-forward consistency in their authentication scoring.

Postmaster Tools enrolment happens during this window. Your sending domain gets added to Google Postmaster Tools v2, Microsoft SNDS (via Bing Webmaster), and Yahoo Sender Hub. The dashboards start populating data 24-72 hours after the first real send; your account manager will share the access during this period and review the first week of metrics together with you.