How can users send email ?

Is it possible via a third party service like Brevo ?

You can't send email with any old sender address. Or you can, but any proper email server will reject the email if the domain's SPF records don't match the sending server. If they blindly accepted all emails, anyone could spoof anyone's email address.

If your customers have their own domain names, they'd have to update their DNS to whitelist whatever SMTP server you're using to send emails. That's a hard sell. And if they have something like a gmail.com address, you're out of luck.

Thinking about this further.. Vincent, please, work with a senior dev/mentor before creating something like you're attempting to right now.

A lot of the posts you've created recently, really feels like whatever app you're building has been built by the community here. This in itself isn't bad, OSS is exactly this, however, it's clear from the questions and direction you're thinking regarding credentials, that you could do with a hand in regards to building secure software for consumption from others.

We all need to learn. Back in 2000, I built a forum as my second ever PHP project. When I look back at the code and see stuff like:

"select * from users where user_id = {$_GET['user_id']};"

I cringe and am thankful that I didn't have my entire DB and/or application compromised (would likely be very different in today's landscape)... and also thankful that over the years, I have learned a lot and recognise just how bad the code is.

I'm sincerely not trying to dishearten you, or criticise you etc etc, but I would strongly advise thinking about what you're trying to achieve with the current knowledge that you have. By all means, build and experiment.. this is how we learn.. but please don't publish this stuff on the open (or closed in a company) network.

To send emails in Laravel using the user's own email address as the sender without revealing the SMTP address, you'll need to adjust the way the email is sent.

Here’s how you can do that:

1. Use SMTP for the email but with the user's email address as the "from" address.

Instead of sending the email with your Gmail SMTP credentials and having the email show the Gmail address, you can configure the email to send on behalf of the user, like they are sending the email from their own address.

2. Update the .env file to allow dynamic "From" address configuration:

Your .env configuration for SMTP should look like this (using Gmail as an example):

MAIL_MAILER=smtp
MAIL_HOST=smtp.gmail.com
MAIL_PORT=587
[email protected]
MAIL_PASSWORD=your-email-password
MAIL_ENCRYPTION=tls
[email protected]
MAIL_FROM_NAME="${APP_NAME}"

Here, MAIL_USERNAME and MAIL_PASSWORD are the credentials for your Gmail account, which will be used to send the email, but we will modify the "From" address dynamically in the code.

3. Dynamically set the "From" address when sending the email:

When sending an email, you can set the sender address dynamically to match the user’s email address. For example:

use Illuminate\Support\Facades\Mail;

$user = Auth::user(); // or any method to get the logged-in user

Mail::send('emails.example', ['data' => $data], function($message) use ($user) {
    $message->from($user->email, $user->name); // User's email address
    $message->to('[email protected]');
    $message->subject('Your Subject');
});

This way, the from email address will be the user’s own email, not your Gmail SMTP address.

4. Ensure the SMTP server allows sending from different addresses:

For Gmail, by default, Gmail will allow you to send emails from other email addresses (like the one the user is using), but the user must have the email address verified in their Gmail account.

If you are using Gmail, the user’s email address must be added as a "Send mail as" alias in the Gmail account associated with your MAIL_USERNAME.

5. Optional: Verify DKIM and SPF for your domain:

If you're using a custom domain for sending email, it's recommended to configure DKIM (DomainKeys Identified Mail) and SPF (Sender Policy Framework) records to prevent your emails from being marked as spam. For more information on how to verify DKIM for your domain, you can follow the steps outlined in this Verify DKIM.

6. Ensure your SMTP provider allows sending as different users:

Some email service providers might restrict the ability to send emails on behalf of others. Be sure that your SMTP provider (like Gmail, SendGrid, etc.) allows this. With Gmail, you'll need to make sure the user has configured the "Send mail as" feature.

Conclusion:

• The key here is to ensure that you're dynamically setting the "From" address in the mail send method, so it uses the user’s email rather than your Gmail address.
• You'll also need to verify that the SMTP server you're using allows sending as other email addresses (Gmail can do this with "Send mail as" configuration).

This should give the effect that the user is sending the email as though they are sending it from their own account.