SMTP mailtrap error on send if configure MAIL_FROM_ADDR

[itamarperdomo]

I setup mailtrap configuration and always gives error if i changed MAIL_FROM_ADDR, and if i just leave comment does not log anything and reports that "mail was send".. in resume no matter i try never send anything but it reports that was send the mail .. this is my setup

Snipe-IT version: v8.2.1 build 19068 (g6ca49a20c)
PHP Version: 8.3.23
Laravel Version: 11.44.1
Mail From Address: smtp@mailtrap.io
Mail Reply-To Address: smtp@mailtrap.io
Table Storage:localStorage

Problem is that since in current configuration .env configuration I changed MAIL_ variables to mailtrap integrations

MAIL_MAILER=smtp
MAIL_HOST=live.smtp.mailtrap.io
MAIL_PORT=587
MAIL_USERNAME=api
MAIL_PASSWORD=<akypaikey>

The i clear cache and cofig and recached config, so try to send test email and i got an UI error but no log error

 Mail could not be sent.
No additional error message provided. Check your mail settings and your app log.

This will attempt to send a test mail to smtp@mailtrap.io.

Try to run the artisan command php artisan config:show mail for mail and gives me this:

  mail ....................................................  
  default ............................................ smtp  
  mailers ⇁ smtp ⇁ transport ......................... smtp  
  mailers ⇁ smtp ⇁ host ............. live.smtp.mailtrap.io  
  mailers ⇁ smtp ⇁ port ............................... 587  
  mailers ⇁ smtp ⇁ username ........................... api  
  mailers ⇁ smtp ⇁ password  //////akpikeyher//////////////  
  mailers ⇁ smtp ⇁ timeout ............................. 30  
  mailers ⇁ smtp ⇁ encryption ......................... tls  
  mailers ⇁ smtp ⇁ verify_peer ....................... true  
  mailers ⇁ ses ⇁ transport ........................... ses  
  mailers ⇁ postmark ⇁ transport ................. postmark  
  mailers ⇁ resend ⇁ transport ..................... resend  
  mailers ⇁ sendmail ⇁ transport ................. sendmail  
  mailers ⇁ sendmail ⇁ path ..... /usr/sbin/sendmail -bs -i  
  mailers ⇁ log ⇁ transport ........................... log  
  mailers ⇁ log ⇁ channel ............................ null  
  mailers ⇁ array ⇁ transport ....................... array  
  mailers ⇁ failover ⇁ transport ................. failover  
  mailers ⇁ failover ⇁ mailers ⇁ 0 ................... smtp  
  mailers ⇁ failover ⇁ mailers ⇁ 1 .................... log  
  mailers ⇁ roundrobin ⇁ transport ............. roundrobin  
  mailers ⇁ roundrobin ⇁ mailers ⇁ 0 .................. ses  
  mailers ⇁ roundrobin ⇁ mailers ⇁ 1 ............. postmark  
  mailers ⇁ mailgun ⇁ transport ................... mailgun  
  from ⇁ address ......................... smtp@mailtrap.io  
  from ⇁ name ........................................ null  
  markdown ⇁ theme ................................ default  
  markdown ⇁ paths ⇁ 0 ........ resources/views/vendor/mail  
  reply_to ⇁ address ..................... smtp@mailtrap.io  
  reply_to ⇁ name .................................... null

[snipe]

It's possible that mailtrap needs you to have a confirmed email address or a whitelisted email address (to prevent people using their services to spoof emails.) I'd check your mail trap account and make sure the address you have your MAIL_FROM_ADDR is allowed as a sender.

[itamarperdomo]

hi @snipe as i know that is not necesary.. inclusive the mailtrap doc doe snot mentioned anything you sait.. just said that fill the ENV vars and just start to use it

mailtrap is not a sender per se, just take all the outgoin mail and moved to the mailtrap interface.. was used a lot of times with the laravel and as i noted snipeit is laravel in the core

[snipe]

Then I don't really know what to tell you. We use the standard Laravel mail configs.

[itamarperdomo]

i mean i raised the log level to debug and there is nothing.. i only gave an error when i put a string in FROM and REPLYTO

i tested with a normal stqandar template from zero of laravel and it worked but in a fresh install of snipeit just only two scenarios are happened:

1. if you fill the string environment of MAIL_FROM_ADDR and MAIL_REPLYTO_ADDR with valid mails address a full error log are write
2. if you leave the string environment of MAIL_FROM_ADDR and MAIL_REPLYTO_ADDR with only a email adress but no name (no matter use quotes or not) no error are written to log

in the second scenario there is no mail delivered

[mselavarasan]

Try the below method to see, if it helps you

Clear config cache
php artisan config:clear
php artisan cache:clear

Test with Tinker
php artisan tinker

use Illuminate\Support\Facades\Mail;

Mail::raw('Test mail from Snipe-IT', function ($message) {
$message->to('your-email@example.com')->subject('Test Email');
});

[itamarperdomo]

changed to what you said.. got error that said mail from mailtrap is not allowed .. but mailtraop is not the offender cos its specially made for

CONFIRMED IS A BUG

why? well i tested in clean laravel and this are enought (i mean no need to configure MAIL_FROM_ADDRES) but you guys in snipeit seems need this variable to be filled with a value.. if you try to put something no log will be dumped in laravel.log

HOW I CAN CHECK IT AND WHY

also change to use api direclty as mailtrap sugested and this is the log:

[2025-07-29 13:52:33] production.ERROR: Symfony\Component\Mailer\Exception\UnexpectedResponseException: Expected response code "250" but got code "550", with message "550 5.7.1 Sending from domain mailtrap.io is not allowed". in /usr/share/webapps/snipeit/Devel/snipeitapp/vendor/symfony/mailer/Transport/Smtp/SmtpTransport.php:342
Stack trace:
#0 /usr/share/webapps/snipeit/Devel/snipeitapp/vendor/symfony/mailer/Transport/Smtp/SmtpTransport.php(198): Symfony\Component\Mailer\Transport\Smtp\SmtpTransport->assertResponseCode()
#1 /usr/share/webapps/snipeit/Devel/snipeitapp/vendor/symfony/mailer/Transport/Smtp/EsmtpTransport.php(134): Symfony\Component\Mailer\Transport\Smtp\SmtpTransport->executeCommand()
#2 /usr/share/webapps/snipeit/Devel/snipeitapp/vendor/symfony/mailer/Transport/Smtp/SmtpTransport.php(263): Symfony\Component\Mailer\Transport\Smtp\EsmtpTransport->executeCommand()
#3 /usr/share/webapps/snipeit/Devel/snipeitapp/vendor/symfony/mailer/Transport/Smtp/SmtpTransport.php(215): Symfony\Component\Mailer\Transport\Smtp\SmtpTransport->doMailFromCommand()
#4 /usr/share/webapps/snipeit/Devel/snipeitapp/vendor/symfony/mailer/Transport/AbstractTransport.php(69): Symfony\Component\Mailer\Transport\Smtp\SmtpTransport->doSend()
#5 /usr/share/webapps/snipeit/Devel/snipeitapp/vendor/symfony/mailer/Transport/Smtp/SmtpTransport.php(138): Symfony\Component\Mailer\Transport\AbstractTransport->send()

IT seems that the MAIL_FROM_ADDRES must mach from the configured domain in mailtrap but you guys suggested that this env variable must be set.. but in vanilla laravel it can be empty not the same in snipeit laravel

You’re sending an email with FROM: {anything}@mydomain.com, but in Mailtrap, you’ve verified anotherdomain.com. The verified domain and FROM: domain in your emails should match.

so due lack of documentation and cos vanilla laravel dont need that (we assume same domain) mail spoofing is not allowed but you guys assumed it can be made..

Documentation must be updated and variables must be only filled if you have own mail server

[itamarperdomo]

also when i confiugued no log is dumped.. that is also a bug, onoy i found with your complicated setup @snipe in last message, so is another bug that complicates the things for us

[snipe]

I’m not sure what it is you want me to tell you here. I can certainly add some notes to the docs, but nothing reported here is an actual bug. If you’re not getting logs, it means your permissions are jacked. That’s not a bug, that’s user error.

[snipe]

If you have something useful to contribute, I welcome your PR.

[mckaygerhard]

hi @snipe i got this problem too.. and i try to explain in other way..

According to the Laravel documentation, you can configure an email with only 6 of the 8 variables in the env file. it means you can omit MAIL_FROM_ADDRES in larabvel and mailtrap or mailgun will work.. but not in snipeit

Now another problem, there is a special mode of delivering called spoofing headers (Email spoofing), that allows the email being sent to act as if it were another email.

First, the documentation doesn't say if this is supported, and it doesn't seem to be possible to do it in any way with snipeit. This Email spoofing mode happened if you set MAIL_FROM_ADDRES in a different value rather than the real email mailbox address account. that is happened by casuallity to our camarada @itamarperdomo

Second, what the friend says is true; seems is a bug cos if you correctly configure Mailtrap or Mailgun, which are mass mailing systems, they write error logs. However, I confirm that in the case of snipeit, no logs are written. Only if you use API mode but, if you use SMTP mode, nothing is written when something is wrong.

i hope this helps to clear to all of us the current situation.. i was thinking i was the only guy with this problem cos it worked in vanilla laravel configs..

[itamarperdomo]

Yes, also there is no log, permissions of directories are correct 777 in ultimate last..

cd /usr/share/webapps/snipeit/Devel/snipeitapp

php artisan config:cache

   INFO  Configuration cached successfully.  

php artisan tinker

Psy Shell v0.12.7 (PHP 8.3.23 — cli) by Justin Hileman
> use Illuminate\Support\Facades\Mail;
> 
> Mail::raw('Test mail from Snipe-IT', function ($message) {
. $message->to('itamarperdomo@gmail.com')->subject('Test Email');
. });
= Illuminate\Mail\SentMessage {#8824}

> 
> 

i received = Illuminate\Mail\SentMessage {#8824} and no error but there is no log neither problems from my side

[snipe]

why? well i tested in clean laravel and this are enought (i mean no need to configure MAIL_FROM_ADDRES) but you guys in snipeit seems need this variable to be filled with a value.. if you try to put something no log will be dumped in laravel.log

This is not a vanilla Laravel install though, so we're not always going to behave the way a new laravel site does. There are many different ways to send email using the notification system within Laravel and we use a few different methods.

Now another problem, there is a special mode of delivering called spoofing headers (Email spoofing), that allows the email being sent to act as if it were another email.

Spoofed emails will almost never get delivered as they are generally blocked at the receiving email server level.

Sending from domain mailtrap.io is not allowed".

The error "Sending from domain mailtrap.io is not allowed" indicates that you're trying to send emails using a domain that hasn't been properly set up and verified with Mailtrap. To resolve this, you need to ensure you're using a sending domain that has been added and verified within your Mailtrap account.

[snipe]

There's more info on how to send email with Mailtrap here: https://mailtrap.io/blog/send-email-in-laravel/

Mailtrap

Laravel Send Email: Tutorial with Code Snippets [2025]

Learn how to send emails in Laravel using SMTP or API: plain text, HTML, with attachments, and more. Find out how to send and test emails using Mailtrap.