Hot answers tagged

11

Honestly, indexing data of any sort from multiple places in multiple formats is a recipe for disaster. You would be better off setting up your own internal email server, switching to a provider that offers indexing features, or adding a proxy-email server are pretty much your best options. All three of those suggestions come with their own pros and cons. ...


3

Spoofing sender addresses is a common spoofing technique. As you have control of the domain adding a SPF record with a '-all' final policy should discourage spoofing addresses in the domain. If there are email addresses in the domain then a policy of "v=spf1 mx -all" would be appropriate, otherwise use a policy like "v=spf1 -all". Given that neither of ...


2

99% of the time, email is delivered via the MX record mechanism. The MX record designates which server is authoritatively responsible for accepting email for a given domain. But that doesn't mean that this server is also the server where the recipients mailbox is. The MX record only designates which server to deliver the email to, it doesn't designate which ...


2

This statement is not accurate: " Email delivery is done by Sender's Mail Server sending E-Mail directly to Receiptent's Domain Mail-Server" For example, at my firm, when I send an email from my mail client, I might not have an externally-facing SMTP server at my site. Mail might be routed within my company's Exchange infrastructure. Then, it might ...


2

You almost got it, but I believe the formatting has to be: v=spf1 a mx ip4:111.111.111.111 ip4:222.222.222.222 include:_spf.example.net ~all With the "a" and "mx" at the beginning. Edit: ~all is fine to use, but it's recommended to use -all for SPF to work more effectively.


2

It really depends on the domain you're sending to. Different rules for different domains. Most Domains will Greylist you for a period of time, blacklisting usually occurs when users mark your emails as spam or is mal-ware is detected.


2

I think you may be looking for a service or appliance such as the Barracuda Message Archiver. I use the appliance version and it indexes all mail as it is sent / received.


1

The only requirement for incoming email is that you have an MX record that is an A record. That MX record could be any hostname, and it doesn't even have to be a subdomain of your domain. So, there's no problem with using abc.example.com. With regard to the website showing when accessed by mail.example.com, that really depends on how you have your webserver ...


1

Yes, it should work, because you specifically list such server as allowed through the a: specification.


1

Well I fixed the problem by installing iRedMail package on my CentOS 6. I also bought SSL certificate from Comondo Positive SSL so emails are trusted. Not to forget, OpendKIM and SPF records MUST BE ADDED to DNS records. If you do this then there is no way google will reject your email. Also make sure your domain is not added to blacklist, you can check that ...


1

First, just to be sure: The highest priority is the one with the lowest preference value. Second: Naturally, the first contact for your mail (hightest priority) needs to be your actual mail server, not the web server. Also, you should only list the web server at all as an MX if it is configured to actually handle incoming mail in a meaningful way.


1

The signed header fields (the h-tag) in the DKIM signature is empty. According to the RFC 6376 it must however contain at least one header name. The recommended header fields to sign are described in section 5.4 of the RFC. Probably the DKIM_SIGN_HEADERS variable contains something invalid. dkim_sign_headers according to the Exim specification: ...


1

It turns out I shouldn't have had the below enabled as well as a mis configuration in the DNS record pointed out by eranga dkim_sign_headers = DKIM_SIGN_HEADERS


1

if you want all the emails being sent via gmail, you have to set relayhost to smtp.gmail.com:587 as you wrote. This is not enough, though. You need to create and edit the file /etc/postfix/sasl_passwd Write a line in it like below: smtp.gmail.com:587 user@example.com:password where: user@example.com is a valid username in your gmail hosted domain ...



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