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 eve
> (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 /etc/mai
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 "d
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 tim
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
> 10€ for the project :-)
Haha, I'm sure a clever lawyer would have arguments for either of us already
winning that bet.
> Hm, maybe you need a "application password".
>
> Try
> # smtpd -dv -Ttransfer
>
> There will be the line "mta: 0x: >>> AUTH PLAIN SomeBase64Code
>
> $ echo YourBase64
Looks good.
I bet money that the username:password pair in is just wrong :-)
How much would you like to wager? :)
10€ for the project :-)
I copied and pasted the info into a weblogin and it worked (unfortunately?)
Hm, maybe you need a "application password".
Try
# smtpd -dv -Ttransfer
> Looks good.
> I bet money that the username:password pair in is just wrong :-)
How much would you like to wager? :)
I copied and pasted the info into a weblogin and it worked (unfortunately?)
The format of my secrets file is:
my_relay sender:PASSWORD
> Don't forget to run
> # smtpctl update
For the server I am trying to connect, I was told to use 587 if 25 didn't work,
so I've been trying both.
You should use 587.
Here is the smtpd.conf now:
Looks good.
I bet money that the username:password pair in is just wrong :-)
Don't forget to run
# smtpctl update table secrets
after y
> What happened "late March"? Did you reboot the system or did smtpd crash?
I think I rebooted after applying these patches:
015: SECURITY FIX: March 22, 2019 All architectures
A state in pf could pass ICMP packets to a destination IP address that did not
match the state.
A source code patch e
==
/etc/mail/smtpd.conf diffs (-OLD +NEW)
==
--- /var/backups/etc_mail_smtpd.conf.current Fri Feb 22 01:30:23 2019
+++ /etc/mail/smtpd.conf Fri Mar 15 20:49:37 2019
@@ -17,3 +17,5 @@
# match from any for domain "example.org" action "local"
match for local action "local"
ma
Am 05.04.2019 um 05:58 schrieb Juan Trippe:
What's the alternative? Did you make an update?
I don't know, it was about a month ago. I was trying to get the relay working so
I was making changes to the smtpd.conf file. AFAIK I was restarting smtpd after
each edit and stopped when it worked.
Wh
> What's the alternative? Did you make an update?
I don't know, it was about a month ago. I was trying to get the relay working so
I was making changes to the smtpd.conf file. AFAIK I was restarting smtpd after
each edit and stopped when it worked.
Here are the diff's for my smtpd.conf from befo
Yes, I know it's hard to believe, maybe I forget to reload smtpd.conf after I
made the edit, but I don't think so.
What's the alternative? Did you make an update?
Yes, secrets exists and has valid login info. I tested the info with Thunderbird
on a client and was able to send an email
(Assu
Hello Thomas,
Yes, I know it's hard to believe, maybe I forget to reload smtpd.conf after I
made the edit, but I don't think so.
Yes, secrets exists and has valid login info. I tested the info with Thunderbird
on a client and was able to send an email
Thanks
> -- Original Message -
"Is it possible to resend without all the html?"
Oh boy, sorry about that, hope this is better
Hello,
I'm just starting out with OpenBSD and I wanted to relay email with OpenSTMP. I
was able to follow the example on the stmpd.conf man page:
https://man.openbsd.org/smtpd.conf
I got the relay
Hello,
action “relay” relay user username host smtp+tls://b...@smtp.example.com
auth
It worked fine until late March.
Hard to believe, since it is a syntax error.
smtpd -n was ok after user [username] was removed but the relay no
longer functioned. The main cause seems to be a lack of a
19 matches
Mail list logo
