RT5 and Postfix


I am having issues with setting up RT5 to use Postfix to send emails to users. I am able to send successfully, however, they do not show up in the inbox.

When sending a command like echo "This is a test" | mail -s "Testing" username@domain.com, I am able to receive the email. However, when Request Tracker uses the sendmail command, it says, according to /var/log/mail.log that the emails were sent and queued for delivery but they do not show up in the inbox. There doesn’t appear to be any errors in the logs that I found regarding SMTP.


What do you see in the Postfix logs? Also do you have a custom sendmail config setup or just whatever the default is?

To my understanding, Postfix uses the /var/log/mail.log for all syslog stuff. All I see in the mail.log is the emails being sent to the smtp server defined in the RT_SiteConfig.pm. My config sets the $MAILCOMMAND to sendmailpipe with some sendmailarguments.

Set( $rtname, ‘domain . com’);
Set( $Organization, ‘domain . com’ );
Set( $WebDomain, ‘ticketing . domain . org’ );
Set( $UserAutocreateDefaultsOnLogin, { Privileged => 1 } );
Set( $AutoCreateNonExternalUsers, 1);

Set($MailCommand , ‘sendmailpipe’);
Set($SendmailPath, “/usr/sbin/sendmail” );
Set($SendmailArguments,"-oi -ODeliveryMode=b -OErrorMode=m");

Here is what I see in the mail.log:

It looks from the log (bearing in mind we don’t use postfix!) that the mail was relayed to Outlook.com for delivery. So can you (or you mail administrator) see anything at the Microsoft end of the pipe? Is it being treated as spam or bulk mail or something by Outlook.com?

Yeah since the logs suggest it is leaving your postfix server and accepted by the remote end (Microsoft), it is an issue on the other end. But this is common for self-hosted SMTP systems emailing the big hosters. If you haven’t already, look into DKIM, SPF and DMARC. Those things go a long way to convincing the large providers that you are legit and can avoid the spam/bulk mail detection.

Other times it can be your IP address has a bad reputation either from someone else historically, or if it’s part of a range considered residential / has been repurposed from another use.

Looks like it was our Spam Filter policies in Office 365. I had to edit the filters to allow emails through as they were getting marked as Spam. It works now.

Thanks for all your help!

1 Like