On 17 February 2014 10:58, Revant Nandgaonkar revant.one@gmail.com wrote:

I am new to mail servers.

my domain name is revant.me (you can know ip/smtp/rdns ptr etc. now)

I bought static IP from MTNL Mumbai and they also changed Reverse DNS for me recently (Week ago)

I have recently configured mailserver (postfix/dovecot/roundcube), email domain and mailbox with IPConfig3 on my Server

My server is running debian amd64 stable, the LAMP is ON since May 2013.

With my recently configured mail server I can receive emails.

When I send email from my server to gmail, hotmail, facebook, yahoo I get "Undelivered Mail Returned to Sender" or similar email message:

Example Gmail error: 550-5.7.1 [my static IP] The IP you're using to send mail is not authorized to 550-5.7.1 send email directly to our servers. Please use the SMTP relay at your service provider instead. Learn more at 550 5.7.1 http://support.google.com/mail/bin/answer.py?answer=10336 vb2si7620646pbc.217

• gsmtp (in reply to end of DATA command)

From the support link:

"In order to prevent spam, Gmail refuses mail from IP addresses that are not authorized to send mail. The determination of whether or not an IP address is authorized to send mail is made by the ISP that provides you with the IP address. This list typically contains consumer IP ranges offered for dialup, DSL, or other broadband access."

The IP is listed in a few DNSBL.

http://mxtoolbox.com/SuperTool.aspx?action=blacklist%3a59.181.134.100&ru...

You can try requesting each one of those lists to remove your IP, especially Spamhaus.

-Avinash.

On Mon, Feb 17, 2014 at 11:15 AM, Avinash Sultanpur grokavi@gmail.comwrote:

The IP is listed in a few DNSBL.

http://mxtoolbox.com/SuperTool.aspx?action=blacklist%3a59.181.134.100&ru...

You can try requesting each one of those lists to remove your IP, especially Spamhaus.

I applied to remove my IP from Spamhaus PBL It worked! Thank You.

I tried sending email to gmail and yahoo, works fine. For hotmail it went in junk.

Revant

On Mon, Feb 17, 2014 at 2:30 PM, Avinash Sultanpur grokavi@gmail.comwrote:

You can try adding the SPF records and use DKIM which was also pointed by another poster to this thread, it should definitely help.

I've TXT records set in Godaddy Panel

v=spf1 a ip4:59.181.134.100 include:server.revant.me -all v=spf1 a mx ptr -all

I think one of it is redundant.

And for DKIM I'm reading.

Revant

On Mon, Feb 17, 2014 at 3:52 PM, Revant Nandgaonkar revant.one@gmail.com wrote:

On Mon, Feb 17, 2014 at 1:30 PM, Sachin Divekar ssd532@gmail.com wrote:

...

Hi Revant,

If you have dns control you should configure DKIM and SPF. It's not that hard to setup. SPF and DKIM help other mail servers to understand that you are genuine mail server and not a spam.

Refer following resource from Google,

https://support.google.com/mail/answer/180707?hl=en

SPF, I already have, I've 2 TXT records at godaddy

v=spf1 a ip4:59.181.134.100 include:server.revant.me -all v=spf1 a mx ptr -all

What I grasped about DKIM keys is, it should be generated on server and reflected in TXT/SPF records at godaddy? Am I right?

I have found that you are using Postfix on Debian. I haven't set up DKIM in such set up. But in short you will have to do following.

1. Create a public and private key pair required for signing. You can use openssl to generate the key pair. 2. Install and configure openDKIM 3. Modify Postfix to use OpenDKIM for signing mails. 4. Now you will publish the public key using TXT record in your DNS config.

Google keywords for set up guide: debian postfix dkim

Regards, Sachin Divekar

On Mon, Feb 17, 2014 at 5:38 PM, Sachin Divekar ssd532@gmail.com wrote:

I have found that you are using Postfix on Debian. I haven't set up DKIM in such set up. But in short you will have to do following.

1. Create a public and private key pair required for signing. You can

use openssl to generate the key pair. 2. Install and configure openDKIM 3. Modify Postfix to use OpenDKIM for signing mails. 4. Now you will publish the public key using TXT record in your DNS config.

Google keywords for set up guide: debian postfix dkim

Regards, Sachin Divekar

I used amavisd-new with IPConfig 3 and a patch -> details http://blog.schaal-24.de/?p=2223&lang=en command "sudo amavisd-new testkey" says:

default._domainkey.revant.me => pass

I've set TXT record default.domainkey at godaddy -> v=DKIM1; t=s; p=Public-KEY http://dkimcore.org/c/keycheck says valid key

Yet when I tried sending email I cannot! No errors, Roundcube/email client says email sent but nothing happens! recipient doesn't receive message.

I got send/receive working back again without DKIM by editing following lines from edited postfix's main.cf

--------- Edited As per blog's instructions (not working) ----------- smtpd_sender_restrictions = check_sender_access regexp:/etc/postfix/tag_as_originating.re permit_mynetworks permit_sasl_authenticated check_sender_access mysql:/etc/postfix/mysql-virtual_sender.cf, regexp:/etc/postfix/tag_as_foreign.re

Note: /etc/postfix/tag_as_originating.re has a line "/^/ FILTER amavis:[127.0.0.1]:10026" and /etc/postfix/tag_as_foreign.re has a line "/^/ FILTER amavis:[127.0.0.1]:10024"

--------- Edited As per blog's instructions (not working) -----------

instead I set it to just as before.

-----Default Working Settings------- smtpd_sender_restrictions = check sender access mysql:/etc/postfix/ mysql-virtual_sender.cf -----Default Working Settings-------

I've no DKIM but mail works. I am confused with amavisd-new ports 10024, 10025, 10026, 10027 and so is my server! Any Idea?

Revant