Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #61874

Re: Using pythons smtp server

Show all headers | View raw

On Fri, 13 Dec 2013 11:27:00 -0700, Vincent Davis
<vincent@vincentdavis.net> declaimed the following:

>Grant, Chris
>Thanks !!!
>I guess in the end this is a bad idea, (for my purposes) I should just use
>my gmail account smtp server.
>

	Better, if you don't want to work with the potential hazzard of an ISP
that blocks passthrough SMTP; gmail is probably not using the regular SMTP
port. Original SMTP would accept mail from any sender, for any receiver...
Now known as an "open relay", and a source of much spam. Closed SMTP
requires that mail either come from an "inside" IP address (the DHCP
address issued to your connection by your ISP would be "inside" to the ISP
SMTP) or be addressed TO an address known by the SMTP (which is how your
ISP can send to some other network server -- it only sends to addresses on
that server, and multi-address messages will be sent to each domain as a
separate message).


	Back in my Amiga days, the first MTA I had /did/ attempt to connect
directly to the destination domain (but I suspect did not use MX record
lookup). Problem -- if it couldn't connect, that message would hang for
retry later... AND that hanging message blocked all subsequent queued
messages.

	My second client used ISP relay, leaving the headache of actually
delivering the message to my ISP to resolve. Problem: it extracted
destination addresses from the "To:" header of the message, and ignored
both "CC:" and "BCC:" headers (and, for all I know, even transmitted the
"BCC:" list to any "To" recipient).

	About then, I discovered the first two significant books on Python at
Computer Literacy, and that an Amiga binary was available (Python 1.4, I
think -- thanks, Irmin). In less than a week I'd hashed together an SMTP
sending program run as a daemon relaying through my ISP and properly
extracting SENDTO from To/CC/BCC headers [and removing the BCC from the
message], and an ARexx script used as the queuing module for AmigaELM. I
used this set-up for a few years until a fancier Amiga email program
arrived that handled sending and receiving internally (AmigaELM also
required an external POP3 fetchmail program -- the mail client only
accessed local mailbox files).
-- 
	Wulfraed                 Dennis Lee Bieber         AF6VN
    wlfraed@ix.netcom.com    HTTP://wlfraed.home.netcom.com/

Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Using pythons smtp server Vincent Davis <vincent@vincentdavis.net> - 2013-12-12 18:01 -0700
  Re: Using pythons smtp server Grant Edwards <invalid@invalid.invalid> - 2013-12-13 16:40 +0000
    Re: Using pythons smtp server Vincent Davis <vincent@vincentdavis.net> - 2013-12-13 10:13 -0700
    Re: Using pythons smtp server Chris Angelico <rosuav@gmail.com> - 2013-12-14 05:15 +1100
    Re: Using pythons smtp server Vincent Davis <vincent@vincentdavis.net> - 2013-12-13 11:27 -0700
      Re: Using pythons smtp server Grant Edwards <invalid@invalid.invalid> - 2013-12-13 20:33 +0000
    Re: Using pythons smtp server Chris Angelico <rosuav@gmail.com> - 2013-12-14 05:29 +1100
    Re: Using pythons smtp server Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2013-12-13 19:46 -0500
      Re: Using pythons smtp server Irmen de Jong <irmen.NOSPAM@xs4all.nl> - 2013-12-14 16:48 +0100
        Re: Using pythons smtp server Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2013-12-14 12:59 -0500

csiph-web