- Can I install lasso/vmail-bundle in a Laravel application?
- No. Despite being listed among Laravel/PHP packages, lasso/vmail-bundle is a Symfony 2 bundle: it registers services into a Symfony DI container and exposes configuration under app/config/config.yml. It ships no Laravel ServiceProvider, facade, publishable config, or migrations, and its PSR-0 autoloading will not boot inside a Laravel app without a full port. Treat it as non-integratable as-is and evaluate it only as a source of domain design.
- What does lasso/vmail-bundle actually do?
- It is an implementation of Postfix virtual users, most likely a Doctrine-backed data model for virtual domains, mailboxes, and aliases, plus console commands and possibly an admin surface. It emits or maintains the lookup tables Postfix reads through virtual_mailbox_domains, virtual_mailbox_maps, and virtual_alias_maps. The durable asset is the schema and its semantics, not the PHP code.
- Is lasso/vmail-bundle still maintained?
- No. The last release was 2014-07-08, with one star, zero dependents, and a low package score. That means no security patching, no CVE monitoring, no issue triage, no CI, and no community memory when something breaks. Mail infrastructure is a high-value attack surface, so an unmaintained component in that path is a material exposure.
- Which PHP and Symfony versions does lasso/vmail-bundle require?
- It targets PHP 5.x and Symfony 2.x, which are both end-of-life. Expect PSR-0 autoloading, deprecated container APIs, and password-hashing choices that predate modern defaults. None of that is compatible with a modern Laravel 10 or 11 application on PHP 8.2+.
- What database schema does lasso/vmail-bundle provide for Postfix virtual users?
- The bundle almost certainly maps Doctrine entities onto the standard virtual domains, mailboxes, and aliases tables that Postfix queries when resolving virtual_mailbox_domains, virtual_mailbox_maps, and virtual_alias_maps. Because Postfix can read MySQL or PostgreSQL directly, your Laravel app only needs to own those tables rather than the bundle's code. To recover exact column semantics, read the Doctrine mappings and console commands in the repository source.
- How do I set up Postfix virtual users in Laravel without this bundle?
- Rebuild the schema as Laravel migrations with explicit column types, utf8mb4 collation, and indexes on every column Postfix filters on, then model it with Eloquent. Point Postfix at the same database so it performs lookups directly, and keep quota and alias logic in your application layer. Alternatively, run the legacy Symfony app as an isolated sidecar that owns the tables, though that inherits an end-of-life runtime.
- Is lasso/vmail-bundle safe to run in production?
- Not as-is. It has been abandoned since 2014, targets PHP 5.x and Symfony 2.x, and has no tests, no documentation, and no maintenance history to lean on. Combined with the fact that mail infrastructure is routinely targeted for auth bypass, open relay, and address spoofing, adopting it directly is a serious risk. Reimplement the data contract instead of running the original code.
- How do I test a Laravel Postfix virtual user integration?
- Write feature tests that assert the exact lookup queries Postfix will run, then cover the edge cases: catch-all addresses, aliases pointing to other aliases, per-domain quotas, address case-folding, and IDN or UTF-8 local parts. Test with Postfix itself in a container by sending real mail and confirming delivery and rejection behavior. Each of these is a silent mail-loss bug if handled incorrectly, and the original bundle has no tests to guide you.
- Does lasso/vmail-bundle work with Dovecot SASL password hashes?
- Unknown, and that is the problem. The bundle predates modern hashing defaults, so you cannot assume compatibility with bcrypt, SHA512-CRYPT, or ARGON2 without reading the source. Before committing engineering time, confirm which hashing scheme it stores and whether it matches your Dovecot or SASL auth path. If not, plan to rehash credentials during migration.
- Can I fork and reuse the lasso/vmail-bundle schema in a new Laravel project?
- Only after checking the license terms, since you need explicit permission to fork, reuse, or relicense the schema and code. If the license permits it, extracting the table design and lookup semantics is reasonable, but porting the bundle itself to Laravel is not: you pay the full rewrite cost and still inherit 2014-era assumptions. The cleaner path is to treat the bundle as a specification and write your own migrations.