Re: [qmailtoaster] Emails to Spam folder

2019-08-28 Thread ChandranManikandan 
Hi Friends,

I have updated SPF and DMARC record into my DNS server after that the email
is delivered to inbox instead spam/junk folder.

Please try to create SPF and DMARC record in your DNS servers

On Wed, Aug 28, 2019 at 11:39 AM ChandranManikandan 
wrote:

> Hi Friends,
>
> As per Andrew stats, i have checked all those points in my server.
> I have installed letsencrypt certificate in past two years without any
> issue and spf record validated and configured on the DNS server.
> DKIM also installed on my server well.
>
> When users send an email to gmail, some emails are going to inbox and some
> going to spam with the same my domain.
>
> I have no clue to setup the dmarc record in the dns server.
>
> Could anyone help me for the process of creating dmarc record.
> Do i need to create my server or dns server.
>
> My domain result for the reputation.
>
> MEDIUM REPUTATION
>
> Not suspicious. We have not seen any direct references to this email
> address, but the sender domain is highly reputable, and the email is
> deliverable. We've observed no malicious or suspicious activity from this
> address.
>
>
>
> curl emailrep.io/m...@panasiagroup.net
>
> {
>
> "email": "x...@xxx.net",
>
> "reputation": "medium",
>
> "suspicious": false,
>
> "references": 0,
>
> "details": {
>
> "blacklisted": false,
>
> "malicious_activity": false,
>
> "malicious_activity_recent": false,
>
> "credentials_leaked": false,
>
> "credentials_leaked_recent": false,
>
> "data_breach": false,
>
> "first_seen": "never",
>
> "last_seen": "never",
>
> "domain_exists": true,
>
> "domain_reputation": "high",
>
> "new_domain": false,
>
> "days_since_domain_creation": 5524,
>
> "suspicious_tld": false,
>
> "spam": false,
>
> "free_provider": false,
>
> "disposable": false,
>
> "deliverable": true,
>
> "accept_all": false,
>
> "valid_mx": true,
>
> "spoofable": true,
>
> "spf_strict": true,
>
> "dmarc_enforced": false,
>
> "profiles": []
>
> }
>
> }
>
>
> Appreciate of all your supporting.
>
> On Wed, Aug 28, 2019 at 8:49 AM Andrew Swartz 
> wrote:
>
>> This seems an issue mostly with server "suspiciousness", of which
>> reputation is a component.
>>
>> Of the factors effecting suspiciousness, only two are local to the smtp
>> server:
>> 1.  DKIM signatures
>> 2.  TLS certificates
>>
>> To address these, confirm that both are working properly:
>> 1.  DKIM: send an email to a "dkim reflector" and then examine the email
>> you get back.  This pages discusses:
>>
>> https://www.cisco.com/c/en/us/support/docs/security/email-security-appliance/118571-technote-esa-00.html
>>
>> 2.  Use a proper TLS certificate.  By proper, I mean one that verifies.
>> Therefore you need to either purchase one or use "Let's Encrypt".  I've
>> been using Lets Encrypt certs for the last year without any problems.
>> Setting up the client is not difficult, and it subsequently auto-renews
>> every 60 days.
>>
>> The remaining factors are outside your server, but just as important:
>> 1.  Reverse-DNS yields same result as the domain MX record.  This is
>> known as FCRDNS (forward-confirmed reverse DNS).  Additionally, that
>> result must not resemble a dynamic IP address (i.e. have the IP address
>> in the domain name).
>> 2.  SPF is properly set up.
>> 3.  DMARC set up and working properly.
>> 4.  Age of the domain name.  If created recently, that looks bad.
>> 5.  Presence of IP on blacklists.  That is not hard to check.  If you
>> acquired an IP recently, it's former owner may have earned it a place on
>> a blacklist.  Easiest fix for that seems to be to get a different IP.
>>
>> I'm curious to hear what others might add to this.
>>
>> A good place for ideas is to browse through the spamdyke.conf file and
>> think about all of the things it checks.  Gmail is certainly using
>> similar data points, but with neural network analysis rather than simple
>> pass/fail rules.
>>
>> For those who have set up a second server to test things, there is a
>> good chance something above is not set up or does not support the new
>> server.  Gone are the days when you can bring a new parallel server
>> online and start sending mails immediately.  There are lots of "i's" to
>> dot and "t's" to cross before other servers will confidently accept your
>> mail.
>>
>> Another thought:
>> https://emailrep.io/ will give you a report about an email ADDRESS's
>> reputation.  It is interesting.  Here is the result for mine (I replaced
>> my email address for posting):
>>
>> curl emailrep.io/first.l...@example.tld
>> {
>>  "email": "first.l...@example.tld",
>>  "reputation": "low",
>>  "suspicious": true,
>>  "references": 1,
>>  "details": {
>>  "blacklisted": false,
>>  "malicious_activity": false,
>>  "malicious_activity_recent": false,
>>

Re: [qmailtoaster] Qmail Toaster Repos Timing Out

2019-08-28 Thread Roxanne Sandesara 
CentOS 7

$ cat /etc/yum.repos.d/qmt.repo
[qmt-current]
# Qmailtoaster current repository
name=QMT Current Repository
mirrorlist=https://www.qmailtoaster.org/qmt-mirrorlist-current
#mirrorlist=https://raw.githubusercontent.com/qmtoaster/mirrorlist/master/qmt-mirrorlist-current
#mirrorlist=file:///etc/yum.repos.d/qmt-mirrorlist-current
#baseurl=ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/$releasever/current/$basearch/
enabled=1
gpgcheck=0
priority=7


$ cat /etc/yum.repos.d/qmt-mirrorlist-current
ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/$releasever/current/$basearch/
ftp://toaster.phoenixmail.com/pub/repo/qmt/CentOS/$releasever/current/$basearch/
ftp://qmtmirror.rm.ht/pub/repo/qmt/CentOS/$releasever/current/$basearch/
ftp://qmt-server.carlc.com/pub/repo/qmt/CentOS/$releasever/current/$basearch/
ftp://server.lhotkanet.cz/pub/repo/qmt/CentOS/$releasever/current/$basearch/


On Aug 28, 2019, at 11:07 AM, Eric Broch  wrote:

What OS are you using? CentOS 5?
Can you post your yum repo file?

On Mon, Aug 26, 2019 at 6:42 PM Roxanne Sandesara mailto:roxie.sil...@gmail.com>> wrote:
When I attempt to update, I continue to see these messages:

http://qtp.qmailtoaster.com/repos/nodist/repodata/repomd.xml 
: [Errno 12] 
Timeout on http://qtp.qmailtoaster.com/repos/nodist/repodata/repomd.xml 
: (28, 
'Connection timed out after 30002 milliseconds’)

What do we need to do to overcome this?



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com 

For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Emails to Spam folder

2019-08-28 Thread Eric Broch 
The very email I'm replying to ended up in my spam folder with this message:

Be careful with this message

Gmail could not verify that it actually came from kand...@gmail.com. Avoid
clicking links, downloading attachments, or replying with personal
information.
Report spamReport phishing

As do most email that come from kand...@gmail.com


On Tue, Aug 27, 2019 at 10:05 PM ChandranManikandan 
wrote:

> Hi Friends,
>
> As per Andrew stats, i have checked all those points in my server.
> I have installed letsencrypt certificate in past two years without any
> issue and spf record validated and configured on the DNS server.
> DKIM also installed on my server well.
>
> When users send an email to gmail, some emails are going to inbox and some
> going to spam with the same my domain.
>
> I have no clue to setup the dmarc record in the dns server.
>
> Could anyone help me for the process of creating dmarc record.
> Do i need to create my server or dns server.
>
> My domain result for the reputation.
>
> MEDIUM REPUTATION
>
> Not suspicious. We have not seen any direct references to this email
> address, but the sender domain is highly reputable, and the email is
> deliverable. We've observed no malicious or suspicious activity from this
> address.
>
>
>
> curl emailrep.io/m...@panasiagroup.net
>
> {
>
> "email": "x...@xxx.net",
>
> "reputation": "medium",
>
> "suspicious": false,
>
> "references": 0,
>
> "details": {
>
> "blacklisted": false,
>
> "malicious_activity": false,
>
> "malicious_activity_recent": false,
>
> "credentials_leaked": false,
>
> "credentials_leaked_recent": false,
>
> "data_breach": false,
>
> "first_seen": "never",
>
> "last_seen": "never",
>
> "domain_exists": true,
>
> "domain_reputation": "high",
>
> "new_domain": false,
>
> "days_since_domain_creation": 5524,
>
> "suspicious_tld": false,
>
> "spam": false,
>
> "free_provider": false,
>
> "disposable": false,
>
> "deliverable": true,
>
> "accept_all": false,
>
> "valid_mx": true,
>
> "spoofable": true,
>
> "spf_strict": true,
>
> "dmarc_enforced": false,
>
> "profiles": []
>
> }
>
> }
>
>
> Appreciate of all your supporting.
>
> On Wed, Aug 28, 2019 at 8:49 AM Andrew Swartz 
> wrote:
>
>> This seems an issue mostly with server "suspiciousness", of which
>> reputation is a component.
>>
>> Of the factors effecting suspiciousness, only two are local to the smtp
>> server:
>> 1.  DKIM signatures
>> 2.  TLS certificates
>>
>> To address these, confirm that both are working properly:
>> 1.  DKIM: send an email to a "dkim reflector" and then examine the email
>> you get back.  This pages discusses:
>>
>> https://www.cisco.com/c/en/us/support/docs/security/email-security-appliance/118571-technote-esa-00.html
>>
>> 2.  Use a proper TLS certificate.  By proper, I mean one that verifies.
>> Therefore you need to either purchase one or use "Let's Encrypt".  I've
>> been using Lets Encrypt certs for the last year without any problems.
>> Setting up the client is not difficult, and it subsequently auto-renews
>> every 60 days.
>>
>> The remaining factors are outside your server, but just as important:
>> 1.  Reverse-DNS yields same result as the domain MX record.  This is
>> known as FCRDNS (forward-confirmed reverse DNS).  Additionally, that
>> result must not resemble a dynamic IP address (i.e. have the IP address
>> in the domain name).
>> 2.  SPF is properly set up.
>> 3.  DMARC set up and working properly.
>> 4.  Age of the domain name.  If created recently, that looks bad.
>> 5.  Presence of IP on blacklists.  That is not hard to check.  If you
>> acquired an IP recently, it's former owner may have earned it a place on
>> a blacklist.  Easiest fix for that seems to be to get a different IP.
>>
>> I'm curious to hear what others might add to this.
>>
>> A good place for ideas is to browse through the spamdyke.conf file and
>> think about all of the things it checks.  Gmail is certainly using
>> similar data points, but with neural network analysis rather than simple
>> pass/fail rules.
>>
>> For those who have set up a second server to test things, there is a
>> good chance something above is not set up or does not support the new
>> server.  Gone are the days when you can bring a new parallel server
>> online and start sending mails immediately.  There are lots of "i's" to
>> dot and "t's" to cross before other servers will confidently accept your
>> mail.
>>
>> Another thought:
>> https://emailrep.io/ will give you a report about an email ADDRESS's
>> reputation.  It is interesting.  Here is the result for mine (I replaced
>> my email address for posting):
>>
>> curl emailrep.io/first.l...@example.tld
>> {
>>  "email": "first.l...@example.tld",
>>  "reputation": "low",
>>  "suspicious": true,
>>  "references": 1,
>>

Re: [qmailtoaster] Qmail Toaster Repos Timing Out

2019-08-28 Thread Eric Broch 
What OS are you using? CentOS 5?
Can you post your yum repo file?

On Mon, Aug 26, 2019 at 6:42 PM Roxanne Sandesara 
wrote:

> When I attempt to update, I continue to see these messages:
>
> http://qtp.qmailtoaster.com/repos/nodist/repodata/repomd.xml: [Errno 12]
> Timeout on http://qtp.qmailtoaster.com/repos/nodist/repodata/repomd.xml:
> (28, 'Connection timed out after 30002 milliseconds’)
>
> What do we need to do to overcome this?
>
>
>
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>
>