Laravel developer: custom SMTP configuration for multiple websites

Laravel + React Developer Needed for Dynamic SMTP Integration in a Multi-Business Portal Technology: Laravel + React Engagement: Hourly Project Overview We are looking for an experienced Laravel and React developer to implement dynamic SMTP integration in our existing multi-business portal. Currently, the portal uses a single SMTP configuration stored in the .env file. This means emails for all businesses are sent through the same default email address. We now need to allow each business to use its own SMTP configuration so that emails related to its operations can be sent using its own business email address and sender name. The portal has two types of users: • Businesses: The primary business accounts using the portal. • Business customers: Customers associated with individual businesses. SMTP configuration should be available at the business level only, not for individual business customers. Scope of Work 1. Dynamic SMTP Configuration Add an email configuration section under: Settings → Email Settings The configuration should support the following fields: • SMTP Host • SMTP Port • SMTP Username • SMTP Password • Encryption type (SSL/TLS) • From Name • From Email Address Each business should have its own SMTP configuration. For now, businesses will contact our support team for assistance with generating SMTP credentials and configuring the settings. The implementation should support this assisted setup process. 2. SMTP Connection Testing and Activation Provide a Test SMTP Connection / Send Test Email option within the same settings form. Expected behaviour: • Businesses should be able to test their SMTP configuration. • SMTP settings should only become active after a successful test. • If any SMTP details are changed, the configuration must be tested and successfully validated again before activation. • Businesses should be able to update or remove their SMTP configuration. 3. Dynamic Email Sending Logic The portal should dynamically select the appropriate SMTP configuration based on the business associated with the email. Expected email behaviour: A. Business operational emails Emails related to a business's customers and business workflows should be sent using that business's configured SMTP settings. Examples include: • Order creation emails. • Order-related notifications. • Business workflow emails. • Other business-related transactional emails. B. Platform-level emails Emails related to the business's own platform account should continue using the portal's default SMTP configuration. Examples include: • Business registration emails. • Forgot password and password reset emails for business accounts. • Other platform-level account and security emails. C. Default SMTP behaviour If a business has not configured its own SMTP settings, the portal should continue using the existing default SMTP configuration. 4. SMTP Failure Handling • If an email cannot be sent using a business's SMTP configuration, the relevant business administrator should receive an in-portal notification about the failure. • The system should capture the necessary error details for internal troubleshooting. • SMTP credentials and sensitive information must not be exposed in error messages or notifications. 5. Database and Security Currently, SMTP credentials are maintained through the .env configuration. With this implementation: • Store business-specific SMTP configurations in the database. • Encrypt SMTP passwords and other sensitive credentials at rest. • Never expose SMTP passwords in API responses or the frontend. • Ensure credentials are handled securely when creating, updating, testing, and using SMTP configurations. • Maintain the existing default SMTP configuration as a fallback when a business has not configured its own SMTP. 6. Email Logs The system should maintain necessary email delivery and failure information in the database for internal troubleshooting. Email logs do not need to be displayed in the business panel. 7. Development and Testing • Implement the functionality in the existing Laravel + React codebase. • Ensure existing email functionality continues to work. • Test business-specific SMTP selection and default SMTP behaviour. • Test successful and unsuccessful SMTP configurations. • Test configuration updates, removal, and revalidation. • Verify that business emails and platform-level emails use the correct SMTP configuration. • Follow the existing project architecture and coding standards. Expected Deliverables 1. Complete dynamic SMTP integration in the existing codebase. 2. Database changes and any required migrations. 3. Frontend changes under Settings → Email Settings. 4. Secure SMTP credential storage and handling. 5. Dynamic SMTP selection for relevant outgoing emails. 6. SMTP testing and activation functionality. 7. Failure notification handling. 8. Tested and committed code in the development repository. Important: This task covers development and code changes in the development repository only. Production deployment and server configuration are not included in the current scope. Required Skills • Strong experience with Laravel and PHP. • Experience with React. • SMTP integration and email delivery systems. • Laravel mail configuration and dynamic mail transport handling. • Database design and secure credential management. • Experience working with existing multi-tenant or multi-business applications. Proposal Requirements Please include the following in your proposal: • Your relevant Laravel and SMTP integration experience. • Your proposed technical approach. • Estimated development hours. • Your hourly rate. • Any questions or technical concerns about the proposed implementation.