VayloMailSee pricingHow these tools read a mailbox
Each of these tools can connect to a mailbox over IMAP. Their documentation describes the following.
- n8n uses an Email Trigger (IMAP) node with an IMAP credential. It can fetch only the messages that match custom rules, mark each message as read when n8n receives it or leave it unread, and force a reconnection at a set interval.
- Make uses its IMAP connection. It asks for the incoming server address, a port from 1 to 65535, a secure connection (TLS) option, your email address as the user name, and your password.
- Zapier uses IMAP by Zapier. Its New Email trigger starts a Zap when new mail arrives. It asks for the server host, username, password and a port, either 143 (the default) or 993.
None of the pages checked gives a polling interval for an IMAP trigger, so check the setting that applies to your plan. Zapier's help article says that Email by Zapier uses a third-party service with no guarantee over when a Zap triggers, and it suggests IMAP by Zapier for time-sensitive mail.
Why consumer mailboxes cause trouble
Consumer mailboxes such as Gmail have per-account limits that automation can reach. Google's documentation describes the following. The examples are Gmail's. This page does not check other providers.
- Client limits. Google says you can add Gmail to up to 15 email clients at a time per account. Google's help page describes the problem that arises when many email clients get messages from Gmail at the same time, and suggests closing or signing out of clients you are not using.
- App approval for OAuth. Google says IMAP, POP and SMTP access uses the https://mail.google.com/ scope, and an app must show full use of that scope to be approved. Restricted-scope verification can take several weeks, and an unverified app can be limited to a set number of users.
- Polling and reconnects. Several automations on one account can each take up a client slot, so one mailbox can reach the client limit sooner than expected. The tool sets how often it checks or reconnects. The n8n option to force a reconnection at a set interval is one example.
VayloMail publishes no fixed cap on simultaneous IMAP connections for a dedicated server. Capacity still depends on the workload, so see the next section before you rely on it.
What to check in a mailbox before you automate it
- Encrypted access on standard ports: IMAP on 993 with TLS, and SMTP submission on 587 with STARTTLS and login.
- What the provider says about simultaneous IMAP connections. A connection limit and a measured throughput result are different things.
- Whether the server is dedicated to you or shared with other customers.
- Sending rules: whether there is a fixed sending cap, and which other limits apply.
- Backups: how often they run and how long they are kept.
- Whether the provider states an uptime commitment.
- Which protocols are offered. Check that the protocol your tool uses, usually IMAP, is on the list.
Connecting a VayloMail mailbox
Use the hostname and credentials supplied for your own server. Port numbers are not login credentials. Verify the TLS certificate against the supplied hostname.
| Setting | Value |
|---|---|
| Incoming mail (IMAP) | Your server hostname, port 993, TLS |
| Outgoing mail (SMTP submission) | Your server hostname, port 587, STARTTLS, with login |
| Login | The credentials supplied for your own server |
| Server-side filters | ManageSieve on port 4190 |
| Webmail | Read mail in a browser, without a desktop client |
Keep the password out of workflow text and logs. Set reconnects with a bounded backoff rather than retrying in a tight loop, and reuse connections where the tool allows it.
VayloMail advertises concurrent IMAP automation without a fixed service-level connection cap. Finite CPU, memory, storage and mailbox indexing still limit throughput. Before you run several automations in parallel, tell support your peak connections, message arrival rate, mailbox size and typical IMAP commands. See IMAP for automation.
What VayloMail does not do
- It does not run automations or provide a workflow builder. The automation tool connects to the mailbox.
- It does not promise a particular third-party integration, or compatibility with every automation tool.
- It publishes no fixed number of simultaneous IMAP connections and no measured concurrency benchmark.
- POP3 is not among the supported connections. The supported connections are IMAP, SMTP submission, ManageSieve and webmail.
- It sets no fixed sending cap. Server, recipient and acceptable-use limits still apply.
- It does not include unlimited storage, guaranteed inbox placement, an uptime SLA, migration, or calendar, document or video features.
Questions, answered
Can n8n, Make or Zapier read a VayloMail mailbox?
Yes, over IMAP. Each of the three tools can connect to a mailbox over IMAP. VayloMail's IMAP service is on port 993 with TLS, and you use the credentials supplied for your own server.
Why not use a Gmail mailbox for automation?
Gmail allows up to 15 email clients to be connected at a time per account, and several automations sharing one account can reach that limit. An OAuth app that uses Gmail needs Google's approval of the https://mail.google.com/ scope, and restricted-scope verification can take several weeks. This page checks Gmail only.
Is there a fixed limit on IMAP connections on VayloMail?
No fixed cap on simultaneous IMAP connections is published. Capacity depends on the server and the workload, and no measured concurrency benchmark is published. Give support your peak connections, message rate and mailbox size before you start.
Does VayloMail run the automations?
No. VayloMail provides the mailbox over standard protocols. The automation tool connects to it, and VayloMail does not promise compatibility with any particular tool.