Re: [GTALUG] help with Rogerrs SMTP
I think Rogers is using Yahoo or Hotmail (Microsoft) behind the scene. My sendmail/fetchmail/procmail used to work for Yahoo, until about a year ago. I gave up. I'm now using Thunderbird. You can tell by the way paragraph is mangled in my post. :-( --William On 12/1/21 8:24 PM, Ariel Burton via talk wrote: Hi everyone, I'm trying to get outgoing SMTP email to work with Rogers, and would appreciate any help. I am not looking for a full solution; all I need is for outgoing email to work from the command line in my user account. I don't need a system-wide solution, or a solution that works with GUI email readers. See below for a sample use-case. I used to have a solution that had lines like this in my $HOME/.mailrc: BEGINS set smtp=smtp.nl.rogers.com:587 set smtp-auth-user=MY-ROGERS-EMAIL-ADDRESS set smtp-auth-password=ROGERS-DEVICE-SPECIFIC-PASSWORD set replyto="Ariel Burton " set smtp-use-starttls set ssl-verify=ignore ENDS Something like this worked for many years, but stopped working a while ago. Earlier versions differed slightly, e.g., using "from" or "sender" in place of "replyto", or different port numbers. This is a transcript of how it fails: BEGINS /home/me> mail MY-OTHER-EMAIL-ADDRESS Subject: test test . EOT % smtp-server: 550 Request failed; Mailbox unavailable "/home/me/dead.letter" 12/365 . . . message not sent. ENDS Can anyone see what am I doing wrong, and how to fix it? Thanks, Ariel == --- Post to this mailing list talk@gtalug.org Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk --- Post to this mailing list talk@gtalug.org Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk
[GTALUG] ssh in Windows Cmd and PowerShell
FYI... While doing "back to office" setups, I noticed that you can do ssh in Windows Cmd and PowerShell. Traditional way was to install WSL (Windows Subsystem for Linux) and do ssh from Ubuntu. One hassle was that Ubuntu can't go into Windows network drives. Now, you can go into network drive in "cmd" and "powershell", and do ssh from there directly. This means, I no longer need my Chromebook. Its original and replacement batteries both died, so I removed it from Chromebook. I use it for SSH terminal mainly. --William --- Post to this mailing list talk@gtalug.org Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk
Re: [GTALUG] help with Rogerrs SMTP
On 2021-12-01 8:24 p.m., Ariel Burton via talk wrote: I'm trying to get outgoing SMTP email to work with Rogers, and would appreciate any help. [snip] BEGINS set smtp=smtp.nl.rogers.com:587 set smtp-auth-user=MY-ROGERS-EMAIL-ADDRESS set smtp-auth-password=ROGERS-DEVICE-SPECIFIC-PASSWORD [snip] Something like this worked for many years, but stopped working a while ago. [snip] /home/me> mail MY-OTHER-EMAIL-ADDRESS Subject: test test . EOT % smtp-server: 550 Request failed; Mailbox unavailable "/home/me/dead.letter" 12/365 . . . message not sent. That error makes me think the mail is going to the wrong server. Are you sure about the SMTP serverdetails? That doesn't look right to me. When I used to send email out via the Rogers servers it was going to smtp.broadband.rogers.com on port 465. -- Cheers! Kevin. http://www.ve3syb.ca/ | "Nerds make the shiny things that https://www.patreon.com/KevinCozens | distract the mouth-breathers, and | that's why we're powerful" Owner of Elecraft K2 #2172 | #include | --Chris Hardwick --- Post to this mailing list talk@gtalug.org Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk
Re: [GTALUG] help with Rogerrs SMTP
On Wed, 1 Dec 2021 at 20:25, Ariel Burton via talk wrote: > Hi everyone, > > I'm trying to get outgoing SMTP email to work with Rogers, > and would appreciate any help. > > > /home/me> mail MY-OTHER-EMAIL-ADDRESS > Subject: test > test > . > EOT > % smtp-server: 550 Request failed; Mailbox unavailable > "/home/me/dead.letter" 12/365 > . . . message not sent. > > As a starting point, I would suggest using the "-v" switch to enable verbose mode. Then you will see the details of the actual message delivery and protocol conversations which may provide you some hints about what's going on. --- Post to this mailing list talk@gtalug.org Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk
Re: [GTALUG] a solved problem unsolved itself: WordPress, MySQL, UTF-8
On 01/12/2021 08:05, Stewart C. Russell via talk wrote:
On 2021-11-29 16:25, Jamon Camisso via talk wrote:
Another thing to try is using mysqli_set_charset("UTF8"); somewhere in
your site's code. Substitute in different character sets until you
find the correct one ...
Thanks, Jamon, but there isn't a valid encoding for what my database
seems to be holding. It was UTF-8, and now it's seemingly UTF-8 decoded
to CP1252 bytes re-encoded to UTF-8 characters again.
If WordPress were using Python (it's not), if my db held the 4
character, 6 byte UTF-8 string, the equivalent Python code to end up in
the mess I'm in is:
>>> bytes(bytes("côté",encoding='utf-8').decode(encoding='cp1252'),
encoding='utf-8')
b'c\xc3\x83\xc2\xb4t\xc3\x83\xc2\xa9'
or 6 characters / 10 bytes of gibberish ('côté').
Since that encoding is reversible, can you attempt it on some of the
corrupted posts/pages? e.g.
>>> bytes(bytes('côté', encoding='utf-8').decode(),
encoding='cp1252').decode()
'côté'
Since this happened in the last month or so, it's not really a legacy
encoding issue. Perfectly good UTF-8 got destroyed with no input/changes
from me.
I'd been fairly careful with backups for the first decade of running
this blog, but the process got wearing after a while, especially since
every update went flawlessly so the manual backup process was a waste of
time. Wordpress offers automatic updates without forcing a backup
checkpoint, which I think is wrong.
Is it a managed Wordpress? That's terribly bad sounding if it is. Worse
I suppose if Wordpress itself just did it.
Do any of the casting suggestions on that link that I sent fix it? Or
are you going to have to dump each row and run them through that
double-decoding process?
Jamon
---
Post to this mailing list talk@gtalug.org
Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk
[GTALUG] help with Rogerrs SMTP
Hi everyone, I'm trying to get outgoing SMTP email to work with Rogers, and would appreciate any help. I am not looking for a full solution; all I need is for outgoing email to work from the command line in my user account. I don't need a system-wide solution, or a solution that works with GUI email readers. See below for a sample use-case. I used to have a solution that had lines like this in my $HOME/.mailrc: BEGINS set smtp=smtp.nl.rogers.com:587 set smtp-auth-user=MY-ROGERS-EMAIL-ADDRESS set smtp-auth-password=ROGERS-DEVICE-SPECIFIC-PASSWORD set replyto="Ariel Burton " set smtp-use-starttls set ssl-verify=ignore ENDS Something like this worked for many years, but stopped working a while ago. Earlier versions differed slightly, e.g., using "from" or "sender" in place of "replyto", or different port numbers. This is a transcript of how it fails: BEGINS /home/me> mail MY-OTHER-EMAIL-ADDRESS Subject: test test . EOT % smtp-server: 550 Request failed; Mailbox unavailable "/home/me/dead.letter" 12/365 . . . message not sent. ENDS Can anyone see what am I doing wrong, and how to fix it? Thanks, Ariel == --- Post to this mailing list talk@gtalug.org Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk
Re: [GTALUG] a solved problem unsolved itself: WordPress, MySQL, UTF-8
On 2021-11-29 16:25, Jamon Camisso via talk wrote:
Another thing to try is using mysqli_set_charset("UTF8"); somewhere in
your site's code. Substitute in different character sets until you find
the correct one ...
Thanks, Jamon, but there isn't a valid encoding for what my database
seems to be holding. It was UTF-8, and now it's seemingly UTF-8 decoded
to CP1252 bytes re-encoded to UTF-8 characters again.
If WordPress were using Python (it's not), if my db held the 4
character, 6 byte UTF-8 string, the equivalent Python code to end up in
the mess I'm in is:
>>> bytes(bytes("côté",encoding='utf-8').decode(encoding='cp1252'),
encoding='utf-8')
b'c\xc3\x83\xc2\xb4t\xc3\x83\xc2\xa9'
or 6 characters / 10 bytes of gibberish ('côté').
Since this happened in the last month or so, it's not really a legacy
encoding issue. Perfectly good UTF-8 got destroyed with no input/changes
from me.
I'd been fairly careful with backups for the first decade of running
this blog, but the process got wearing after a while, especially since
every update went flawlessly so the manual backup process was a waste of
time. Wordpress offers automatic updates without forcing a backup
checkpoint, which I think is wrong.
cheers,
Stewart
---
Post to this mailing list talk@gtalug.org
Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk
