in reply to Replacing a module dependency

We user MIME::Lite to do the sending and use the default send mechanism which is sendmail as it is a Linux server.

But we are having some issues with deliverability. So, I decided to switch to using SMTP instead to see if that works more reliably.

Probably not. Delivery issues aren't between you and your mail transfer agent; unless there's something seriously wrong with sendmail on the shared hosting, switching to SMTP to connect to the same MTA won't make any difference. Most likely, the target hosts (mail delivery agents) don't like your shared host as a mail transfer agent, and that's a problem you probably won't be able to solve. (You might get an improvement by switching to a different mail provider as your mail transfer agent and using SMTP to connect to them, but the difference is not in the protocol, but in the host.)

They say it's because of spam, but a nice side effect of being a big mail provider and blocking anyone you don't like is your market share increasing when people give up on non-monopolist mail providers and switch over to you. Malice or incompetence? Why not both?

Replies are listed 'Best First'.
Re^2: Replacing a module dependency
by Bod (Parson) on Apr 27, 2022 at 11:17 UTC

    Thanks for the information. I don't really understand what happens to email once it gets passed to either sendmail or Net::SMTP.

    The reason I was thinking SMTP may improve deliverability is that I can set the authentication account using SMTP. With sendmail accessed through MIME::Lite I don't have that control. This is an add-on domain in cPanel and I was thinking that the DKIM header in the email may not match the right parts of the authenticated sender. It's a bit of guesswork and clutching at straws really...

    I do know the issue is not entirely with other mail providers blocking mail from my mailhost. I can send automated emails to two different addresses with different domains which are both my add-on domains within cPanel and one fails and one succeeds. They are (presumably) going through the same mail filtering software and I cannot imagine the milhost blocking mail that originated with itself.