cancel
Showing results for 
Search instead for 
Did you mean: 

smtp delay

replabrobin
Interested
Posts: 1
Registered: ‎08-09-2018

smtp delay

I am attempting to use relay.plus.net to send notifications from a home server, but I find that there are large delays between the message being accepted and when it finally gets delivered here is an obfuscated example that was sent 13:40 on Saturday and arrived at 10:12 on Sunday ie 17 hours later. I am using python to send to the relay. Is there anything I can do to eliminate the delay? By comparison webmail is almost instantaneous. It is needless to say that this doesn't happen if I use smtp.google.com to do the relay. What causes this delay?

 

 

Delivered-To: *********@gmail.com
Received: by 2002:a4a:d030:0:0:0:0:0 with SMTP id w16-v6csp1385733oor;
Sun, 9 Sep 2018 02:12:51 -0700 (PDT)
X-Google-Smtp-Source: ANB0VdbZcvjAXn332a2j6TJgWm3OK96AY5hVDYhl9fDRQPP8cnr50swcg0pIdt07jvZdlJrafxxQ
X-Received: by 2002:a63:2fc6:: with SMTP id v189-v6mr16740130pgv.61.1536484370995;
Sun, 09 Sep 2018 02:12:50 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1536484370; cv=none;
d=google.com; s=arc-20160816;
b=wdPIvNmSNPeuILmtBgtNztIAPyFBdwQLB7EtVEUpvLovMXofk3886qdBBbHU3aa+Cy
3+MAxhl9ysdUuEa+Wev9iZSBAU1rvlLHC+gkmfrP0qBOrO8yyMiYeQYjStohv0REzKhc
tdICE7Wqg3T0yyZrybPmv6/eUAwFWZPqyMdlqmruUn7h4pj5pUoNGOgCLukwJrGpONo0
6yJ81jVjMJKDAza2V4FPj4yFOv4gIFO5ourDWoAgdBAbeDvMCTa28+dPD0yR2saxX0py
xa1wox9CvVJFTgIX9jOMv7Q3c92kbvaPBxCg/YuyKE1sGnxWWW0iz1T/sb3IL7rbYwXh
lcxQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
h=to:from:subject:content-transfer-encoding:mime-version:message-id
:date;
bh=ZGUG0DJtoSAYnuAA8mX7W87NM6pzwwwKPawioDZvxrc=;
b=TpJ53uU0KAXWcJoD4fXUftRpCe9Vy2rZS2O1f9pulFGnVdZrHPNdPnk4j2z9LWRBsI
6kt2KLhi4kaCkx6ydJCGwZfDFnL8ZW/foWtKMU6MbGrVJIck/HsU1FN9ftjbN2jS2gVm
f7FdXRkil9uVLS4cdYkMVGsfHeo01y2Id9R6JiNNAe2tr1ucchY8MyWc9jo/9YqznSPz
dlkJ//Rxa9+qvLsVj1ZwZFAHoXHk5p8Wr/IofPvdQg9fzObRf5L1caWtSHMQWMI2C22G
a3BscJccXXiVotG70OejeiwywKdvVhLGgosKuwnhVIYJ8Rpkjwl1LVj5BQfvDGV9zcZf
ioDw==
ARC-Authentication-Results: i=1; mx.google.com;
spf=neutral (google.com: 84.93.230.227 is neither permitted nor denied by best guess record for domain of myhostname@myhostname.plus.com) smtp.mailfrom=myhostname@myhostname.plus.com
Return-Path: <myhostname@myhostname.plus.com>
Received: from avasout01.plus.net (avasout01.plus.net. [84.93.230.227])
by mx.google.com with ESMTPS id t9-v6si14524313pfi.221.2018.09.09.02.12.50
for <*********@gmail.com>
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Sun, 09 Sep 2018 02:12:50 -0700 (PDT)
Received-SPF: neutral (google.com: 84.93.230.227 is neither permitted nor denied by best guess record for domain of myhostname@myhostname.plus.com) client-ip=84.93.230.227;
Authentication-Results: mx.google.com;
spf=neutral (google.com: 84.93.230.227 is neither permitted nor denied by best guess record for domain of myhostname@myhostname.plus.com) smtp.mailfrom=myhostname@myhostname.plus.com
Date: Sun, 09 Sep 2018 02:12:50 -0700 (PDT)
Message-Id: <5b94e412.1c69fb81.a9922.6318SMTPIN_ADDED_MISSING@mx.google.com>
Received: from [192.168.0.9] ([46.208.32.97]) by smtp with ESMTP id ycXFfpJzAOoVfycXGfp6NT; Sat, 08 Sep 2018 13:40:22 +0100
X-CM-Score: 0.00
X-CNFS-Analysis: v=2.3 cv=E9rjW5Vl c=1 sm=1 tr=0 a=dEOCMtrx01Nys0x69oMJTA==:117 a=dEOCMtrx01Nys0x69oMJTA==:17 a=kj9zAlcOel0A:10 a=Z-MfXuEaLEQB589wnc0A:9 a=CjuIK1q_8ugA:10
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: testing Sat
8 Sep 13:40:20 BST 2018
From: myhostname@myhostname.plus.com
To: *********@gmail.com
X-CMAE-Envelope: MS4wfJthYWrv+giz8Bhmizfhz+4gQ/GEfl+5IV8SsN8aZkdAKzm8XkwRuoKXkOD3esoflQkyVwrR59kda1unyfsx3CxDt7bnC4R6XjGRdQOs7qh59aV+0zyv KCSUncPWBnIPLXE2oc0ITgORrksJZh72dJQdCKqzlCN7Nfc6phIYuN+pVecACHHyRa6C5HYQkTwoBw==

testing Sat 8 Sep 13:40:20 BST 2018

1 REPLY 1
SpendLessTime
Aspiring Hero
Posts: 2,997
Thanks: 925
Fixes: 86
Registered: ‎21-09-2009

Re: smtp delay