public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: cygport announce fails unable to find mailserver
Date: Sat, 24 Oct 2020 22:37:58 -0600	[thread overview]
Message-ID: <b932d639-68db-35c9-8e70-e121a6cffad9@SystematicSw.ab.ca> (raw)
In-Reply-To: <626a5647-2771-d42a-d31b-68f00e43ebd1@dronecode.org.uk>

On 2020-10-24 17:50, Jon Turney wrote:
> On 25/10/2020 00:19, Brian Inglis wrote:
>> On 2020-10-24 16:21, Brian Inglis wrote:
>>> On 2020-10-24 15:42, Ken Brown via Cygwin-apps wrote:
>>>> On 10/24/2020 4:53 PM, Brian Inglis wrote:
>>>>> Do any/some/many of you use cygport ...cygport announce to generate your
>>>>> update
>>>>> announcements, and does it work successfully?
>>>>
>>>> I use it.  You have to set several SMTP_* variables in your
>>>> ~/.cygport.conf.  If
>>>> you don't already have that file, copy /etc/cygport.conf to ~/.cygport.conf and
>>>> edit it.
>>>
>>> Thanks, already set up with SMTP_SERVER=smtp which is all I need from my home
>>> ISP connection for all SMTP clients (POP3, web, mobile needs user and password).
>>> Nothing else is required (yet)!
>>
>> Hacked out the perl code into a file and got it running and failing.
>> Added Net:SMTP() Debug parameter and set it.
>> Problem is ISP SMTP MX will not accept localhost.localdomain as EHLO/HELO
>> maildomain!
> 
> Whatever you are doing it spamming cygwin-announce with messages which are
> (fortunately) being held due to 'Message has implicit destination'.
> 
> I rejected all the held mails, but please stop.

Sorry about that; trying to diagnose, debug, and fix failures and content issues
with cygport ... announce; hacking without any real background knowledge of
SMTP, Perl, or cygport; still trying to track down issues with generated message
content: sorry about those that made it thru; I'll do my best to ensure future
tests are directed elsewhere.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

  reply	other threads:[~2020-10-25  4:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-24 20:53 Brian Inglis
2020-10-24 21:42 ` Ken Brown
2020-10-24 22:21   ` Brian Inglis
2020-10-24 23:19     ` Brian Inglis
2020-10-24 23:50       ` Jon Turney
2020-10-25  4:37         ` Brian Inglis [this message]
2020-10-25 16:18           ` Brian Inglis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b932d639-68db-35c9-8e70-e121a6cffad9@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).