Tag Info

Hot answers tagged

16

I'm looking forward to seeing other answers to this question, but my feeling is that if you're catching compromised mail accounts after only 40 spams have got through, you're doing really well. I'm not sure I could detect similar abuse so quickly, and the prospect worries me. But I'm appalled that seven sets of credentials were stolen in the past week ...


6

We mitigated the same issue by using an outside vendor as our e-mail gateway (in our case, Exchange Online Protection but there's many other comparable services). We then configured all our e-mail sending services to use that as the smarthost. Now, all our outgoing messages are associated with the reputation of the external e-mail gateway. Because of that, ...


2

On Debian, MTAs including Exim4 are configured to get the canonical domain from /etc/mailname. Mail clients (like mutt) are also supposed to read this file. This means that you can have a sensible hostname and still get your mail sent out with your desired From: header field. Beware of having more than one host with the same value in their /etc/mailname ...


2

I would not recommend trying to hide your e-mail structure. If it breaks, you will likely be missing the appropriate information to fix the problem. It is Google is blocking the message, so the problem may be with your server. If your email structure is not well done (fixed IP address, valid rDNS, SPF, DKIM, and optionnally DMARC records), then Google ...


1

WP should be configured to send messages via SMTP protocol. Usually local submission performed via socket/LMTP where local user the web-server owner is used as sender. When it is the www@localhost MTAs become very strict.


1

I have a VPS hosting multiple domains on Ubuntu 14.04 and wanted to make sure the email headers being sent only included the IP or the FQDN of the virtual host. I first started with this guide on Linode. Afterwards I performed the following steps: Create a file - /etc/exim4/mailhelo and using the syntax of domain.com: helodomain.com produce something ...


1

Ok, so for anyone else stumbling upon this problem: The MySQL expansion somehow adds whitespace (even though in the database are clearly none). To solve the problem, encapsulate your MySQL expansion inside a substr with the length of your hashes. An example for sha256-crypt hashes would be: ${substr{0}{63}{${lookup mysql{ Then it should work.


1

You didn't give a lot of detail in your question, so I'll provide a list of general things to look at. 1) A common issue is that the php script is not readable and/or executable by the exim user. Test by setting the php script to mode 755 and resend. 2) Make sure the bang path in the script is correct. Typically this will be #!/usr/bin/php You should be ...


1

First and foremost, if your system is generating messages that are ending up in your queue because they are to email addresses that are not deliverable, it's FAR better to detect it during injection instead of only after attempting to deliver the email. Big email providers negatively colour your sending reputation if you are sending to too many invalid ...


1

You cannot change this from any configuration settings; it is hardcoded into the source code. If you want to change the output of the bounce message, you will have to edit the print_address_information() function in src/deliver.c and rebuild a local copy of exim. If you really think about it though, that will leave you with a confusing message: This ...



Only top voted, non community-wiki answers of a minimum length are eligible