On 4/7/19 4:54 AM, Juan Trippe wrote:
Hello Peter,
Good morning.
1. When you attempt to relay through Bell's smtp relay are you sending
mail as y...@bell.ca or
any of the domains that falls under bell's domains? Perhaps they
implemented a block that
prevents you@home.local, or better
> (That is what you find when you search for smtphm. The .co.jp-part
> doesn't really anonymise it. You should have used the original from the
> get go.)
Oh ok, thanks, never used a mailing list before, wasn't really sure what the
protocol was
> Do you have
> root: wt...@bell.net
> in
Hello Peter,
> 1. When you attempt to relay through Bell's smtp relay are you sending
> mail as y...@bell.ca or
>
> any of the domains that falls under bell's domains? Perhaps they
> implemented a block that
>
> prevents you@home.local, or better even y...@anythingotherthanbell.ca.
> What
This is my host and the source of the connection info I use:
https://support.bell.ca/internet/email/how-to-use-bell-mail?step=5
(That is what you find when you search for smtphm. The .co.jp-part
doesn't really anonymise it. You should have used the original from the
get go.)
I get local
Hi,
I'd like to help you, but I'm late to the thread and some parts were
deleted by me by accident.
I think we may need to clear up some things first:
1. When you attempt to relay through Bell's smtp relay are you sending
mail as y...@bell.ca or
any of the domains that falls under bell's
> Can you authenticate with openssl?
No, I got the user and password prompts but auth failed.
> Ok, lets rethink this. Assuming it stopped working the moment the system
> got rebooted. Than there once was a working configuration, that can be
> recreated. But if it stopped working around the
The format of my secrets file is:
my_relay sender:PASSWORD
Any strange glyph to be concerned about?
At one point I was trying to connect to the server with openssl and when I used
"
perl -MMIME::Base64 -e 'print encode_base64("SomeBase64Code");' " for my
password it was truncating because of
