Engineered for Mass Email Runs
Stop copying and pasting email attachments. Configure local SMTP, write your template body, and let the background queue run.
Secure SMTP & Resend API
Configure Gmail SMTP, company servers, or Resend API. PayslipGen sends emails directly without intermediate servers.
Smart Queue Throttling
Configure interval delays between messages to prevent spam folder flags and honor provider sending limits.
Encrypted Attachments
Every email contains a personalized, password-locked PDF. Ensures only the intended recipient can read the pay stub.
Bulk Emailing Payslips Safely Without Spam Blocks
Learn how to hook up local SMTP parameters, integrate transactional APIs, configure throttle parameters, and pass spam filters.
1. Local SMTP vs. Modern Transactional APIs
Traditional email servers (like Gmail or Outlook) restrict hourly bulk dispatches (usually capped at 100-500 messages daily). Exceeding this limit will freeze your account.
For teams with 100+ employees, PayslipGen integrates with developer APIs like **Resend**. Rather than using SMTP, it translates payroll reports into high-speed JSON calls, achieving instantaneous mail delivery.
2. Throttling and Anti-Spam Safeguards
Spam guards track delivery frequency. If a single IP sends 200 emails with file attachments in 2 seconds, mail client networks flag it as malicious.
PayslipGen lets you specify a custom sending delay. Setting a 1500ms delay between dispatches spaces out emails naturally to avoid spam folders.
Local SQLite Dispatch Logs
Unlike online SaaS dispatch tools that expose delivery history log files to third-party databases, PayslipGen records all delivery status stubs inside an offline local SQL database on your computer.
Queue Status
Track pending, dispatched, and failed items on an active UI console.
Error Diagnostics
Immediate log reporting for authentication errors or bad SMTP ports.
Resend/Retry Actions
Retry failing employee email records without running the whole batch again.
Email Authentication: SPF & DKIM Records
When sending pay slips using an external corporate domain (e.g. hr@mycompany.com), verify that your domain has proper authentication records in place:
SPF (Sender Policy Framework): Defines which mail server IPs are authorized to dispatch emails on your domain's behalf.
DKIM (DomainKeys Identified Mail): Adds a digital cryptographic signature to header logs to verify the email wasn't spoofed in transit.
DMARC compliance: Instructs receiving servers on how to handle messages that fail SPF or DKIM checks, ensuring employee stubs are never intercepted.
Manual Emailing vs Automated Dispatch Queue
Estimate the monthly work hours saved by running our local multi-threaded mailing queue.
Manual Email Time
1.3 hours
PayslipGen Send Time
30 seconds
Hours Saved Per Run
1.2 hours
SMTP Integration & Send Queue
Initialize and verify mail settings in under 5 minutes without writing a single line of script.
Configure Credentials
Add your server credentials, SMTP host, port, TLS settings, or Resend token. Details are encrypted locally.
Send Test Email
Verify your email settings with a single test-dispatch to your inbox before sending to all employees.
Batch Queue Run
Start the bulk dispatcher. Monitor the delivery status queue of each slip in real time with error logs.
Local Email Dispatch vs. Cloud SaaS
Granular analysis of email server access controls, credential storage safety, and API throttling.
| Feature | Manual Docs | Cloud SaaS | PayslipGen |
|---|---|---|---|
| Send Mechanism | Manual email creation | Transmits to SaaS server first | Sends directly from your machine |
| Attachment Encryption | Requires manual lock per file | Varies (often unencrypted) | AES-256 automated lock |
| Throttling & Delays | Hard to manage manually | Sends simultaneously (bulk flag) | Custom milliseconds delay config |
| Audit Delivery Logs | Check Sent folder | Cloud audit console | Offline SQLite database log |