Tag Info

Hot answers tagged

11

That would be highly inadvisable, or, to put it simply, just plain wrong. Just because the secondary server can connect to the primary doesn't mean one or more legitimate SMTP clients can connect to the primary. Multiple MX servers are primarily designed to handle routing and connectivity issues (and the weighting parameter is there to help hint at the ...


5

You cannot compel others to filter their incoming mail based on SPF and DKIM, or indeed any other criteria at all. If google chooses to ignore SPF, so be it; you've done your bit, all you can do now is sit tight and ignore any complaints from people who don't filter on SPF. That said, having a valid SPF record does tend to reduce backscatter, because a ...


4

You're confusing open relaying and authenticated relaying. All email servers support authenticated relaying, which is when a user authenticates to the server for the purpose of sending email to external recipients. The server says "OK, you're allowed to use me to send that email for you because you've been authenticated." (otherwise nobody would ever be able ...


3

Something weird is going on on my mail server. I was mailing a friend and my mail bounced because the IP of my server had been blacklisted. It appears like my server is being used for relaying spam mails. (see excerpt from log below) Yes it is I've checked my settings and they shouldn't allow relaying (see below). I've also checked with several ...


2

When you relearn SpamAssassin that a message should be spam it should flip the message over from ham to spam or spam to ham. The problem is that SpamAssassin learns about the message on your relay host, but when it is forwarded to your Exchange server the headers have changes since an addition Received line was added. You could give it a try by adding the ...


2

Removal of dynamic IP addresses from the Spamhaus blocklist is not desirable. The RFCs support such blocking, and these blocks allow a lot of spam to be blocked. Spamhaus documentation covers this blocking set. I commend your ISP on providing their dynamic IP addresses to Spamhaus and putting a block on their removal. Properly configured mail servers ...


2

I've battled with a couple of these (or similar) scenarios on servers with hundreds of applications, and found the easiest way to narrow/track them down was using Sysinternals Process Monitor: Find the smoking gun: Open Process Monitor and have it show only Network Activity Filter for process name w3wp.exe (if running .NET or ASP applications) If you ...


1

In the case you've described, the mails did not originate at your mail server, so they will not affect your mail server's reputation. The SPF record allows any mail server which is configured to check them to reject such messages or mark them as spam, but not all mail servers check SPF records, and some which do check them don't actually do anything with ...


1

It can be a brute force mail address scan: someone is trying thousands of destination email addresses in the hope to distinguish non-existent emails addresses (for example, due to destination mail server replying with "unknow user" error) from existent (and active) ones.


1

In general it is not possible to easily determine why a particular message has been marked as spam by the Google Mail spam filters. Having said that however one item that is an easy test is to check whether admin@domain.com is in your recipients contact list. Contacts are far less likely to have their emails marked as spam. You should also review the bulk ...


1

Your DMARC record should be under _dmarc.procrastination.com. This is a new specification and not widely supported. If you want reports you also need a TXT record containing v=DMARC1 at *._report._dmarc.procrastination.com or procrastination.com._report_dmarc.procrastination.com. You will know this is working when you start getting reports. Both Google ...


1

I realize this is a very old question, but here's some advice for anyone else Googling this. What I was able to do years ago within Google Apps was create a group with the name that you want to have the email bounce. For example, if you want to have emails bounce that are addressed to user@domain.com, create a group called "user". Under roles and ...


1

I was having the same problem using PHPMailer, and here's what fixed the problem for me: set the Sender (this is different and distinct from the "From") to a valid email account for the domain you are sending the email from. This causes PHPMailer to properly set the "envelope-from" information so that the email passes SPF and Sender-ID validation. Without ...



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