Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #24484 > unrolled thread
| Started by | Ferannia <ferannia@mouse-potato.com> |
|---|---|
| First post | 2018-09-12 01:16 -0700 |
| Last post | 2018-09-23 20:12 +0000 |
| Articles | 16 on this page of 36 — 14 participants |
Back to article view | Back to comp.os.linux.misc
Health related - linux please help Ferannia <ferannia@mouse-potato.com> - 2018-09-12 01:16 -0700
Re: Health related - linux please help The Natural Philosopher <tnp@invalid.invalid> - 2018-09-12 11:53 +0100
Re: Health related - linux please help Joe Beanfish <joebeanfish@nospam.duh> - 2018-09-12 13:37 +0000
Re: Health related - linux please help "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2018-09-12 08:28 -0400
Re: Health related - linux please help Jean-David Beyer <jeandavid8@verizon.net> - 2018-09-12 09:21 -0400
Re: Health related - linux please help Dan Espen <dan1espen@gmail.com> - 2018-09-12 09:22 -0400
Re: Health related - linux please help "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2018-09-12 11:06 -0400
Re: Health related - linux please help Eli the Bearded <*@eli.users.panix.com> - 2018-09-12 18:11 +0000
Re: Health related - linux please help Dan Espen <dan1espen@gmail.com> - 2018-09-12 15:35 -0400
Re: Health related - linux please help Sylvain Robitaille <syl@alcor.concordia.ca> - 2018-09-12 15:31 +0000
Re: Health related - linux please help "Carlos E. R." <robin_listas@es.invalid> - 2018-09-12 12:14 -0400
Re: Health related - linux please help "Carlos E. R." <robin_listas@es.invalid> - 2018-09-12 16:50 -0400
Re: Health related - linux please help Joe Beanfish <joebeanfish@nospam.duh> - 2018-09-13 13:41 +0000
Re: Health related - linux please help The Natural Philosopher <tnp@invalid.invalid> - 2018-09-14 06:18 +0100
Re: Health related - linux please help Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2018-09-12 13:27 -0400
Re: Health related - linux please help "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2018-09-12 15:12 -0400
Ping Dave Hodgins (was Re: Health related - linux please help) Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2018-09-12 20:24 -0400
Re: Health related - linux please help Jean-David Beyer <jeandavid8@verizon.net> - 2018-09-12 20:40 -0400
Re: Health related - linux please help "Carlos E. R." <robin_listas@es.invalid> - 2018-09-12 21:36 -0400
Re: Health related - linux please help "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2018-09-13 02:41 -0400
Re: Health related - linux please help "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2018-09-13 02:45 -0400
Re: Health related - linux please help Rich <rich@example.invalid> - 2018-09-13 11:25 +0000
Re: Health related - linux please help "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2018-09-13 08:16 -0400
Re: Health related - linux please help Jean-David Beyer <jeandavid8@verizon.net> - 2018-09-13 11:01 -0400
Re: Health related - linux please help Wouter Verhelst <w@uter.be> - 2018-09-14 11:14 +0200
Re: Health related - linux please help Richard Kettlewell <invalid@invalid.invalid> - 2018-09-13 16:08 +0100
Re: Health related - linux please help "Carlos E. R." <robin_listas@es.invalid> - 2018-09-13 22:51 -0400
Re: Health related - linux please help Eli the Bearded <*@eli.users.panix.com> - 2018-09-14 06:28 +0000
Re: Health related - linux please help "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2018-09-14 06:07 -0400
Re: Health related - linux please help Eli the Bearded <*@eli.users.panix.com> - 2018-09-14 21:35 +0000
Re: Health related - linux please help Jean-David Beyer <jeandavid8@verizon.net> - 2018-09-14 20:20 -0400
Re: Health related - linux please help Eli the Bearded <*@eli.users.panix.com> - 2018-09-15 18:36 +0000
Re: Health related - linux please help "Carlos E. R." <robin_listas@es.invalid> - 2018-09-14 16:37 -0400
Re: Health related - linux please help Eli the Bearded <*@eli.users.panix.com> - 2018-09-14 21:45 +0000
Re: Health related - linux please help tom <tom@0.0.0.0> - 2018-09-23 11:39 -0700
Re: Health related - linux please help Rich <rich@example.invalid> - 2018-09-23 20:12 +0000
Page 2 of 2 — ← Prev page 1 [2]
| From | "David W. Hodgins" <dwhodgins@nomail.afraid.org> |
|---|---|
| Date | 2018-09-13 02:45 -0400 |
| Message-ID | <op.zo9o2pg4a3w0dxdave@hodgins.homeip.net> |
| In reply to | #24502 |
On Thu, 13 Sep 2018 02:41:14 -0400, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote: > I wrote the script (appended), tested it with email within my lan, > decided to test it sending to gmail, but that failed. After switching > from nail to nc, to sendmail, realized it had been a long time since Should add, that the script as shown doesn't work as I was in the middle of changing it to use sendmail when it occurred to me that I man now have output port 25 blocked. Regards, Dave Hodgins -- Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for email replies.
[toc] | [prev] | [next] | [standalone]
| From | Rich <rich@example.invalid> |
|---|---|
| Date | 2018-09-13 11:25 +0000 |
| Message-ID | <pndhf9$uod$1@dont-email.me> |
| In reply to | #24502 |
David W. Hodgins <dwhodgins@nomail.afraid.org> wrote: > sendmail "$DestEmailList" << EOF > HELO $DestEmailHostName > MAIL FROM: $FromUser@$FromHostName > RCPT TO: $DestEmailUser@$DestEmailHostName > DATA > SUBJECT: $MailSubject > > $MailMessage > . > QUIT > EOF This is another reason for the failure. The userland sendmail binary accepts a "message" (as in RFC822 format), not SMTP. Your script is attempting to talk SMTP to the sendmail binary, which will not work correctly. Also, this requires that a local MTA (sendmail/postfix/qmail) is configured and operational (unlikely on the computer for which this script is intended). Does the eldery gentleman normally send/receive emails. If so does he use gmail (likely, since it seems gmail's taken over pretty much). If so, you might want to adapt an expect script (such as the example here: https://petervibert.com/wp/expect-smtp-script/) possibly with an https proxy in order to get TLS and use googles smtp login (which will likely be on something like port 525 or some such, check google's docs) to send the email when a timeout on the dialog occurs. You'd need his gmail password to let the script log in as him, but you'd not need to configure a MTA on his system either.
[toc] | [prev] | [next] | [standalone]
| From | "David W. Hodgins" <dwhodgins@nomail.afraid.org> |
|---|---|
| Date | 2018-09-13 08:16 -0400 |
| Message-ID | <op.zo94dqhla3w0dxdave@hodgins.homeip.net> |
| In reply to | #24504 |
On Thu, 13 Sep 2018 07:25:30 -0400, Rich <rich@example.invalid> wrote: > This is another reason for the failure. The userland sendmail binary > accepts a "message" (as in RFC822 format), not SMTP. Your script is > attempting to talk SMTP to the sendmail binary, which will not work > correctly. As per the following comment, I'd started changing the script from using nail, and then nc, to using sendmail when it occurred to me to check and see if port 25 outbound was being blocked. > Does the eldery gentleman normally send/receive emails. If so does he > use gmail (likely, since it seems gmail's taken over pretty much). I have no idea. The op, Ferannia, hasn't posted since the original request. No response to the questions posted. Regards, Dave Hodgins -- Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for email replies.
[toc] | [prev] | [next] | [standalone]
| From | Jean-David Beyer <jeandavid8@verizon.net> |
|---|---|
| Date | 2018-09-13 11:01 -0400 |
| Message-ID | <pndu4h02pe7@news4.newsguy.com> |
| In reply to | #24507 |
On 09/13/2018 08:16 AM, David W. Hodgins wrote:
> As per the following comment, I'd started changing the script from
> using nail, and then nc, to using sendmail when it occurred to me
> to check and see if port 25 outbound was being blocked.
Mostly, it is. Try port 465 instead.
urd 465/tcp smtps # URL Rendesvous Directory for SSM /
# SMTP over SSL (TLS)
igmpv3lite 465/udp # IGMP over UDP for SSM
My ISP (verizon.net, now run by AOL) uses port 465, but demands a login
and password, using SSL/TLS. You can tell sendmail what port to use.
https://www.sendmail.org/%7Eca/email/starttls.html
--
.~. Jean-David Beyer Registered Linux User 85642.
/V\ PGP-Key:166D840A 0C610C8B Registered Machine 1935521.
/( )\ Shrewsbury, New Jersey http://linuxcounter.net
^^-^^ 10:50:01 up 8 days, 1:59, 2 users, load average: 4.55, 4.71, 4.67
[toc] | [prev] | [next] | [standalone]
| From | Wouter Verhelst <w@uter.be> |
|---|---|
| Date | 2018-09-14 11:14 +0200 |
| Message-ID | <3pas6f-p9p.ln1@gangtai.home.grep.be> |
| In reply to | #24508 |
On 9/13/18 5:01 PM, Jean-David Beyer wrote: > On 09/13/2018 08:16 AM, David W. Hodgins wrote: >> As per the following comment, I'd started changing the script from >> using nail, and then nc, to using sendmail when it occurred to me >> to check and see if port 25 outbound was being blocked. > > Mostly, it is. Try port 465 instead. Which is the nonstandard SMTP over TLS (in the same way that 443 is HTTP over TLS, except that that *is* standardized). There is a standardized version of SMTP with STARTTLS, too, and a standardization of "submit", where you speak SMTP on port 587, but which should not allow you to do anything unless you log on first. Might want to try that too.
[toc] | [prev] | [next] | [standalone]
| From | Richard Kettlewell <invalid@invalid.invalid> |
|---|---|
| Date | 2018-09-13 16:08 +0100 |
| Message-ID | <87zhwlph9a.fsf@LkoBDZeT.terraraq.uk> |
| In reply to | #24504 |
Rich <rich@example.invalid> writes:
> David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:
>> sendmail "$DestEmailList" << EOF
>> HELO $DestEmailHostName
>> MAIL FROM: $FromUser@$FromHostName
>> RCPT TO: $DestEmailUser@$DestEmailHostName
>> DATA
>> SUBJECT: $MailSubject
>>
>> $MailMessage
>> .
>> QUIT
>> EOF
>
> This is another reason for the failure. The userland sendmail binary
> accepts a "message" (as in RFC822 format), not SMTP. Your script is
> attempting to talk SMTP to the sendmail binary, which will not work
> correctly.
Exim can accept ‘batch SMTP’, which would work with the above
syntax.
When sending mail from a sccript I usually use the following sendmail
options:
-t to get recipients from the headers rather than
having to specify them on the command line
-oee to get sensible error handling (i.e. bounce xor non-zero exit
status)
-oi to stop ‘.’ being magic (i.e. terminate input at EOF)
-odb to request background delivery
> Also, this requires that a local MTA (sendmail/postfix/qmail) is
> configured and operational (unlikely on the computer for which this
> script is intended).
If you’re writing an entire mail client then doing a client SMTP
implementation is fair enough, but re-inventing the wheel for every
little script that sends mail is a waste of time.
--
https://www.greenend.org.uk/rjk/
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2018-09-13 22:51 -0400 |
| Message-ID | <g00m1gF57plU1@mid.individual.net> |
| In reply to | #24509 |
On 13/09/2018 11.08, Richard Kettlewell wrote:
> Rich <rich@example.invalid> writes:
>> David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:
>> Also, this requires that a local MTA (sendmail/postfix/qmail) is
>> configured and operational (unlikely on the computer for which this
>> script is intended).
>
> If you’re writing an entire mail client then doing a client SMTP
> implementation is fair enough, but re-inventing the wheel for every
> little script that sends mail is a waste of time.
Common! It is not that difficult, mailx is quite sophisticated. It can
send using gmail on its own.
*How to Send Email from mailx Command in Linux Using Gmail’s SMTP*
<https://www.systutorials.com/1411/sending-email-from-mailx-command-in-linux-using-gmails-smtp/>
Example:
$ mailx -v -s "$EMAIL_SUBJECT" \
-S smtp-use-starttls \
-S ssl-verify=ignore \
-S smtp-auth=login \
-S smtp=smtp://smtp.gmail.com:587 \
-S from="$FROM_EMAIL_ADDRESS($FRIENDLY_NAME)" \
-S smtp-auth-user=$FROM_EMAIL_ADDRESS \
-S smtp-auth-password=$EMAIL_ACCOUNT_PASSWORD \
-S ssl-verify=ignore \
$TO_EMAIL_ADDRESS
There are other methods there, like writing the settings to the mailx
configuration settings. Then sending is as simple as:
$ echo "The mail content" | \
mail -v -s "$EMAIL_SUBJECT" $TO_EMAIL_ADDRESS
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Eli the Bearded <*@eli.users.panix.com> |
|---|---|
| Date | 2018-09-14 06:28 +0000 |
| Message-ID | <eli$1809140216@qaz.wtf> |
| In reply to | #24511 |
In comp.os.linux.misc, Carlos E. R. <robin_listas@es.invalid> wrote: > Common! It is not that difficult, mailx is quite sophisticated. It can > send using gmail on its own. I don't know what mailx you are using, but it's not mine. > *How to Send Email from mailx Command in Linux Using Gmail's SMTP* > <https://www.systutorials.com/1411/sending-email-from-mailx-command-in-linux-using-gmails-smtp/> > > > Example: > > > $ mailx -v -s "$EMAIL_SUBJECT" \ > -S smtp-use-starttls \ I have three versions of mailx handy (one is "nail"), none of them have a documented -S switch. One of them, I know the source code quite well, and I know it doesn't have an undocumented -S switch. (It's clear that -S just acts like the "set" command, so not hard to implement.) But someone has rewitten the backend mailer portion in that version. Mine just hands mail off to the system MTA, and can't speak SMTP at all. The classic design of an MUA is that it hands mail off to a local MTA, and then the MTA handles the network aspects, including retries if a remote MTA can't be reached immediately. Disconnected servers with no local MTA have changed the common case, and that version of mailx has clearly followed. Elijah ------ there's a "copyright 1978" in mail.c in his mailx source
[toc] | [prev] | [next] | [standalone]
| From | "David W. Hodgins" <dwhodgins@nomail.afraid.org> |
|---|---|
| Date | 2018-09-14 06:07 -0400 |
| Message-ID | <op.zpbs2bl0a3w0dxdave@hodgins.homeip.net> |
| In reply to | #24513 |
On Fri, 14 Sep 2018 02:28:19 -0400, Eli the Bearded <*@eli.users.panix.com> wrote:
> In comp.os.linux.misc, Carlos E. R. <robin_listas@es.invalid> wrote:
>> Common! It is not that difficult, mailx is quite sophisticated. It can
>> send using gmail on its own.
>
> I don't know what mailx you are using, but it's not mine.
> I have three versions of mailx handy (one is "nail"), none of them have
> a documented -S switch. One of them, I know the source code quite well,
> and I know it doesn't have an undocumented -S switch. (It's clear that
> -S just acts like the "set" command, so not hard to implement.) But
> someone has rewitten the backend mailer portion in that version. Mine
> just hands mail off to the system MTA, and can't speak SMTP at all.
[dave@x3 ~]$ man nail|grep tls
imap-use-starttls
imap-use-starttls-user@host
Activates imap-use-starttls for a specific account.
pop3-use-starttls
pop3-use-starttls-user@host
Activates pop3-use-starttls for a specific account.
smtp-use-starttls
encrypt a session after it has been initiated, but before any user-related data has been sent; see smtp-use-starttls
Selects a SSL/TLS protocol version; valid values are `ssl2', `ssl3', and `tls1'. If unset, the method is selected auto‐
set imap-use-starttls
set pop3-use-starttls
[dave@x3 ~]$ rpm -q -i nail|grep -e^Source -e ^URL
Source RPM : nail-12.4-14.mga6.src.rpm
URL : http://heirloom.sourceforge.net/mailx.html
[dave@x3 ~]$ nail -h
nail: option requires an argument -- h
Usage: nail -eiIUdEFntBDNHRV~ -T FILE -u USER -h hops -r address -s SUBJECT -a FILE -q FILE -f FILE -A ACCOUNT -b USERS -c USERS -S OPTION users
[dave@x3 ~]$ nail -V
12.4 7/29/08
Regards, Dave Hodgins
--
Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
email replies.
[toc] | [prev] | [next] | [standalone]
| From | Eli the Bearded <*@eli.users.panix.com> |
|---|---|
| Date | 2018-09-14 21:35 +0000 |
| Message-ID | <eli$1809141735@qaz.wtf> |
| In reply to | #24514 |
In comp.os.linux.misc, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:
> On Fri, 14 Sep 2018 02:28:19 -0400, Eli the Bearded <*@eli.users.panix.com> wrote:
> > I have three versions of mailx handy (one is "nail"), none of them have
> > a documented -S switch. One of them, I know the source code quite well,
> > and I know it doesn't have an undocumented -S switch. (It's clear that
> > -S just acts like the "set" command, so not hard to implement.) But
> > someone has rewitten the backend mailer portion in that version. Mine
> > just hands mail off to the system MTA, and can't speak SMTP at all.
> [dave@x3 ~]$ man nail|grep tls
Yeah, I wasn't doubting that. But using -S to set settings is not
documented in the version I have:
SYNOPSIS
nail [-BDdFintv~] [-s subject] [-a attachment ] [-c cc-addr] [-b bcc-
addr] [-r from-addr] [-h hops] [-A account] to-addr . . .
nail [-BDdeHiInNRv~] [-T name] [-A account] -f [name]
nail [-BDdeinNRv~] [-A account] [-u user]
And in the online manpage for heirloom mail:
http://heirloom.sourceforge.net/mailx/mailx.1.html
SYNOPSIS
mailx [-BDdEFintv~] [-s subject] [-a attachment ] [-c cc-addr] [-b bcc-addr] [-r from-addr] [-h hops] [-A account] [-S variable[=value]] to-addr . . .
mailx [-BDdeEHiInNRv~] [-T name] [-A account] [-S variable[=value]] -f [name]
mailx [-BDdeEinNRv~] [-A account] [-S variable[=value]] [-u user]
Notice how -S has been added.
When you are using new features of VERY old programs, you probably should
mention the version you are using. I'm not sure how to get nail to
report it's version without an mbox to read to force entry to reading
mode, but with that: `nail -f mboxfile` and look at the first line of
the output. On my copy of nail, it is "11.25 7/29/05", which is old, but
not too old in the grand scheme of "mail".
> [dave@x3 ~]$ rpm -q -i nail|grep -e^Source -e ^URL
> Source RPM : nail-12.4-14.mga6.src.rpm
> URL : http://heirloom.sourceforge.net/mailx.html
I'm trying to follow the checkout procedure there to get a copy of the
source, but it's spent over ten minutes on "waiting for anoncvs_nail's
lock in /cvsroot/nail/nail"
Elijah
------
can't figure out when -S was added without source code history
[toc] | [prev] | [next] | [standalone]
| From | Jean-David Beyer <jeandavid8@verizon.net> |
|---|---|
| Date | 2018-09-14 20:20 -0400 |
| Message-ID | <pnhj9802sfu@news3.newsguy.com> |
| In reply to | #24517 |
On 09/14/2018 05:35 PM, Eli the Bearded wrote: > n comp.os.linux.misc, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote: >> On Fri, 14 Sep 2018 02:28:19 -0400, Eli the Bearded <*@eli.users.panix.com> wrote: >>> I have three versions of mailx handy (one is "nail"), none of them have >>> a documented -S switch. One of them, I know the source code quite well, >>> and I know it doesn't have an undocumented -S switch. (It's clear that >>> -S just acts like the "set" command, so not hard to implement.) But >>> someone has rewitten the backend mailer portion in that version. Mine >>> just hands mail off to the system MTA, and can't speak SMTP at all. >> [dave@x3 ~]$ man nail|grep tls > Yeah, I wasn't doubting that. But using -S to set settings is not > documented in the version I have: > > SYNOPSIS > nail [-BDdFintv~] [-s subject] [-a attachment ] [-c cc-addr] [-b bcc- > addr] [-r from-addr] [-h hops] [-A account] to-addr . . . > nail [-BDdeHiInNRv~] [-T name] [-A account] -f [name] > nail [-BDdeinNRv~] [-A account] [-u user] On mine it does: > SYNOPSIS > mailx [-BDdEFintv~] [-s subject] [-a attachment ] [-c cc-addr] [-b bcc- > addr] [-r from-addr] [-h hops] [-A account] [-S vari- > able[=value]] to-addr . . . > mailx [-BDdeEHiInNRv~] [-T name] [-A account] [-S variable[=value]] -f > [name] > mailx [-BDdeEinNRv~] [-A account] [-S variable[=value]] [-u user] > -S variable[=value] > Sets the internal option variable and, in case of a string > option, assigns value to it. Note, that when setting from vari- > able, domain name of host is automatically added if value does > not contain any. If you want to enter from address with owner’s > name, you can use, for example, following format: -S "from=Sys- > tem User <DoNotReply>" This is from this rpm: mailx-12.4-8.el6_6.x86_64 and my system is running: Red Hat Enterprise Linux Server release 6.10 (Santiago) Chances are a naive user is not running this. ;-) -- .~. Jean-David Beyer Registered Linux User 85642. /V\ PGP-Key:166D840A 0C610C8B Registered Machine 1935521. /( )\ Shrewsbury, New Jersey http://linuxcounter.net ^^-^^ 20:15:01 up 1 day, 4:40, 3 users, load average: 4.45, 4.49, 4.50
[toc] | [prev] | [next] | [standalone]
| From | Eli the Bearded <*@eli.users.panix.com> |
|---|---|
| Date | 2018-09-15 18:36 +0000 |
| Message-ID | <eli$1809151436@qaz.wtf> |
| In reply to | #24517 |
In comp.os.linux.misc, Eli the Bearded <*@eli.users.panix.com> wrote: >> Source RPM : nail-12.4-14.mga6.src.rpm >> URL : http://heirloom.sourceforge.net/mailx.html > I'm trying to follow the checkout procedure there to get a copy of the > source, but it's spent over ten minutes on "waiting for anoncvs_nail's > lock in /cvsroot/nail/nail" I've let the CVS checkout attempt run overnight now AND IT STILL waits on that lock. Fuckers, why can't they use a system that actually works? Elijah ------ found a two year old checkout copied to github
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2018-09-14 16:37 -0400 |
| Message-ID | <g02kg8FhlskU1@mid.individual.net> |
| In reply to | #24513 |
On 14/09/2018 02.28, Eli the Bearded wrote:
> In comp.os.linux.misc, Carlos E. R. <robin_listas@es.invalid> wrote:
>> Common! It is not that difficult, mailx is quite sophisticated. It
>> can send using gmail on its own.
>
> I don't know what mailx you are using, but it's not mine.
>
>> *How to Send Email from mailx Command in Linux Using Gmail's SMTP*
>> <https://www.systutorials.com/1411/sending-email-from-mailx-command-in-linux-using-gmails-smtp/>
>>
>>
>>
>>
Example:
>>
>>
>> $ mailx -v -s "$EMAIL_SUBJECT" \ -S smtp-use-starttls \
>
> I have three versions of mailx handy (one is "nail"), none of them
> have a documented -S switch. One of them, I know the source code
> quite well, and I know it doesn't have an undocumented -S switch.
> (It's clear that -S just acts like the "set" command, so not hard to
> implement.) But someone has rewitten the backend mailer portion in
> that version. Mine just hands mail off to the system MTA, and can't
> speak SMTP at all.
>
> The classic design of an MUA is that it hands mail off to a local
> MTA, and then the MTA handles the network aspects, including retries
> if a remote MTA can't be reached immediately. Disconnected servers
> with no local MTA have changed the common case, and that version of
> mailx has clearly followed.
>
> Elijah ------ there's a "copyright 1978" in mail.c in his mailx
> source
>
I understand (Heirloom) mailx was written this century.
And:
As mailx is a mail user agent, it provides only basic SMTP
services. If it fails to contact its upstream
SMTP server, it will not make further attempts to transfer the
message at a later time, and it does not
leave other information about this condition than an error
message on the terminal and a `dead.letter'
file. This is usually not a problem if the SMTP server is
located in the same local network as the com-
puter on which mailx is run. However, care should be taken when
using a remote server of an ISP; it might
be better to set up a local SMTP server then which just acts as a
proxy.
Mailx immediately contacts the SMTP server (or
/usr/lib/sendmail) even when operating in disconnected
mode. It would not make much sense for mailx to defer outgoing
mail since SMTP servers usually provide
much more elaborated delay handling than mailx could perform as
a client. Thus the recommended setup for
sending mail in disconnected mode is to configure a local SMTP
server such that it sends outgoing mail as
soon as an external network connection is available again,
i.e. to advise it to do that from a network
startup script.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Eli the Bearded <*@eli.users.panix.com> |
|---|---|
| Date | 2018-09-14 21:45 +0000 |
| Message-ID | <eli$1809141745@qaz.wtf> |
| In reply to | #24516 |
In comp.os.linux.misc, Carlos E. R. <robin_listas@es.invalid> wrote: > On 14/09/2018 02.28, Eli the Bearded wrote: >> there's a "copyright 1978" in mail.c in his mailx source > I understand (Heirloom) mailx was written this century. If the checkout ever succeeds from http://heirloom.sourceforge.net/mailx/ I bet that mail.c will look very similar to what I have. The rest of source might not. Things like popen() are now in standard libraries. > As mailx is a mail user agent, it provides only basic SMTP > services. If it fails to contact its upstream SMTP server, > it will not make further attempts to transfer the message at a > later time, and it does not leave other information about this > condition than an error message on the terminal and a > `dead.letter' file. This is usually not a problem if the SMTP > server is located in the same local network as the com- puter on > which mailx is run. However, care should be taken when using a > remote server of an ISP; it might be better to set up a local > SMTP server then which just acts as a proxy. Certainly very relevant for this proposed deadman email sender task. Elijah ------ now on twenty minutes "waiting for anoncvs_nail's lock"
[toc] | [prev] | [next] | [standalone]
| From | tom <tom@0.0.0.0> |
|---|---|
| Date | 2018-09-23 11:39 -0700 |
| Message-ID | <20180923113946.6a9700a3@viridi> |
| In reply to | #24498 |
On Wed, 12 Sep 2018 15:12:34 -0400
"David W. Hodgins" <dwhodgins@nomail.afraid.org> wrote:
> On Wed, 12 Sep 2018 04:16:10 -0400, Ferannia
> <ferannia@mouse-potato.com> wrote:
>
> > Please, does it exist ? For ex. mailer's pop-up dialog which he'll
> > have to hit and close within 10 hours after it shows up on his
> > screen. If he doesn't hit OK button, an email message will be sent
> > to couple of his relatives to check up on him.
>
> Not so simple any more due to spammers using infected windows boxes to
> send their spam. I've just found out that my isp now blocks direct
> outgoing connections to tcp port 25 (i.e. smtp or email).
>
> So in order to send the mail I have to relay it through another
> service, which requires logging into that service.
>
> Given the description of the intended user, it's highly likely to be
> the case for him too, which makes sending email using a script much
> more difficult.
>
> Regards, Dave Hodgins
>
Ugh, I hate when ISPs think that helps the spam situation any better.
That's like treating a laceration on your leg with an amputation.
Anyways, because of this a lot of mail providers still accept mail on
port 587 (submission) STARTTLS. If port 25 is blocked and your ISP
won't unblock it after you call them try port 587.
--
________________________________________
/ Patriotism is the last refuge of a \
| scoundrel. |
| |
| -- S. Johnson, "The Life of Samuel |
| Johnson" by J. Boswell |
| |
| In Dr. Johnson's famous dictionary |
| patriotism is defined as the last |
| resort of the scoundrel. With all due |
| respect to an enlightened but inferior |
| lexicographer I beg to submit that it |
| is the first. |
| |
| -- Ambrose Bierce |
| |
| When Dr. Johnson defined patriotism as |
| the last refuge of a scoundrel, he |
| ignored the enormous possibilities of |
| the word reform. |
| |
| -- Sen. Roscoe Conkling |
| |
| Public office is the last refuge of a |
| scoundrel. |
| |
\ -- Boies Penrose /
----------------------------------------
\
\
/\ /\
//\\_//\\ ____
\_ _/ / /
/ * * \ /^^^]
\_\O/_/ [ ]
/ \_ [ /
\ \_ / /
[ [ / \/ _/
_[ [ \ /_/
[toc] | [prev] | [next] | [standalone]
| From | Rich <rich@example.invalid> |
|---|---|
| Date | 2018-09-23 20:12 +0000 |
| Message-ID | <po8s3c$8n3$2@dont-email.me> |
| In reply to | #24527 |
tom <tom@0.0.0.0> wrote: > On Wed, 12 Sep 2018 15:12:34 -0400 > "David W. Hodgins" <dwhodgins@nomail.afraid.org> wrote: >> Not so simple any more due to spammers using infected windows boxes to >> send their spam. I've just found out that my isp now blocks direct >> outgoing connections to tcp port 25 (i.e. smtp or email). > > Ugh, I hate when ISPs think that helps the spam situation any better. > That's like treating a laceration on your leg with an amputation. But, from the ISPs point of view, it is an 'effective' blunt instrument. All their customers windows pc's that are infected with spam sending botnets can no longer send spam with impunity. And since the ratio of "infected windows pc user" to "knowledgable user" for most ISPs is likely on the order of 5000:1 or better, they see the blunt instrument of "block outgoing port 25 connections" as saving themselves a lot of help desk hassle. Also, by blocking port 25 they also gain the ability to offer that 1 in 5000 knowledgeable user their /special/ extra-cost service option where that user can pay more for what used to be included in the basic package.
[toc] | [prev] | [standalone]
Page 2 of 2 — ← Prev page 1 [2]
Back to top | Article view | comp.os.linux.misc
csiph-web