vignesh/cdkinfracode
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

chore: update mail server hostname from mail.tiproemail.com to mail.tipro.in in configuration and documentation

Browse source
This commit is contained in:
vickytechkey 2026-08-06 17:41:10 +05:30
parent 31dfa6057c
commit 34dcbefea0
2 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
aws_cdk/lib/aws_cdk-stack.ts
View file

@ -126,10 +126,10 @@ export class AwsCdkStack extends cdk.Stack {
'git clone https://github.com/mailcow/mailcow-dockerized.git mailcow',
'cd mailcow',
'# Run generate_config.sh non-interactively for mail.tiproemail.com, timezone UTC',
'export MAILCOW_HOSTNAME="mail.tiproemail.com"',
'export MAILCOW_HOSTNAME="mail.tipro.in"',
'export MAILCOW_TZ="Asia/Kolkata"',
'# Pipe answers to generate_config.sh: Hostname (mail.tiproemail.com), Timezone (Asia/Kolkata), Stable Branch (1)',
'echo -e "mail.tiproemail.com\nAsia/Kolkata\n1" | ./generate_config.sh',
'# Pipe answers to generate_config.sh: Hostname (mail.tipro.in), Timezone (Asia/Kolkata), Stable Branch (1)',
'echo -e "mail.tipro.in\nAsia/Kolkata\n1" | ./generate_config.sh',
'',
'# Apply Memory Optimizations for t4g.medium (4GB RAM)',
'# Disable ClamAV (Saves ~1.5 GB RAM)',

8
dns_setup_instructions.md
View file

@ -18,13 +18,13 @@ This points your mail subdomain to your EC2 instance's Elastic IP address.
---
### Step 2: Route Emails (MX Record)
This specifies that incoming emails sent to `@yourdomain.com` should be routed to Mailcow.
This specifies that incoming emails sent to `@tipro.in` should be routed to Mailcow.
1. Check your existing DNS records in Hostinger and delete any default/old **MX** records first.
2. Add a new record:
- **Type:** `MX`
- **Name (Host):** `@`
- **Points to (Mail Server):** `mail.yourdomain.com` *(Replace "yourdomain.com" with your actual domain, e.g., "tiproemail.com")*
- **Points to (Mail Server):** `mail.tipro.in`
- **Priority:** `10`
- **TTL:** `14400` (or default)
3. Click **Add Record**.
@ -59,9 +59,9 @@ This policy dictates how receiving servers should handle emails that fail SPF/DK
This adds a digital signature to outgoing emails to verify they were sent by you.
1. Deploy your EC2 instance and wait for Mailcow to start up.
2. Log into the Mailcow web interface at: `https://mail.yourdomain.com` (Default login: Username: `admin` / Password: `moohoo` — **Change this password immediately!**).
2. Log into the Mailcow web interface at: `https://mail.tipro.in` (Default login: Username: `admin` / Password: `moohoo` — **Change this password immediately!**).
3. Navigate to **Configuration** > **ARC/DKIM**.
4. In the "Domain" field, enter your domain name (e.g. `yourdomain.com`).
4. In the "Domain" field, enter your domain name (e.g. `tipro.in`).
5. Choose a selector (default is `dkim`).
6. Click **Add** (or **Generate**). Mailcow will display a long public key string.
7. Go back to your **Hostinger DNS Zone Editor** and add a new record: