-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: failed to verify token... renewing #32
Comments
It should work, i see the code there, though i haven't used it in a while. |
Hi bro, |
What is the error?
How did you configure it? Env variables? Or properties.json?
…On Thu, Aug 20, 2020, 21:37 Vastelo ***@***.***> wrote:
It should work, i see the code there, though i haven't used it in a while.
How are you configuring it?
And why not just use the token? I left this backdoor mostly for backwards
compatibility with automation systrms in a place i worked for a long time
ago...
Hi bro,
Great tool you made there, but I’m having the same issue ... not working
really ..
Any chance you’re helping an Israeli out ? ;)
hhhhhh I’m about to give up on this lol ..
I can hire your services , just need to fix it , hehe
Rak bibi
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#32 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFTF65QWIO777P7ZAWJBER3SBVUNTANCNFSM4QETPDFA>
.
|
Ok now I see it’s fine , it was ports issue I mean some setting on the env so it’ll allow all |
No... It was this way initally, i had to make it specific because it was
exploited by spammers as a mail relay.
So it only accepts emails where the recipient is on these domains. And
won't allow relaying otherwise...
But you can fork the code and remkve the check quite easily.
Its in the smtp.js file under server.
…On Thu, Aug 20, 2020, 22:29 Vastelo ***@***.***> wrote:
What is the error? How did you configure it? Env variables? Or
properties.json?
… <#m_5109917104518087944_>
Ok now I see it’s fine , it was ports issue
But now I have a question ...
If I set 2 domains, to the same ip (dns settings) , including Mx etc ...
Is there a way to have it work as “catch all” ? Depending on the url I’m
coming from ?
I mean some setting on the env so it’ll allow all
Domains and not just specific ones
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#32 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFTF65Q7J7G2D3GAERXM623SBV2QZANCNFSM4QETPDFA>
.
|
I can see that the emails are received, although it doesn’t let me enter to the second domain mailbox .. So if I have two domains pointed at: xx ip Wether I go from domain1 or domain2 |
Check serveraddress/api/properties, see that the server recognizes all the
domains in a json array?
…On Fri, Aug 21, 2020, 00:02 Vastelo ***@***.***> wrote:
No... It was this way initally, i had to make it specific because it was
exploited by spammers as a mail relay. So it only accepts emails where the
recipient is on these domains. And won't allow relaying otherwise... But
you can fork the code and remkve the check quite easily. Its in the smtp.js
file under server.
… <#m_-3194045365004997194_>
I can see that the emails are received, although it doesn’t let me enter
to the second domain mailbox ..
So if I have two domains pointed at: xx ip
Wether I go from domain1 or domain2
It always gets to the same inbox ..
And only domain 1 is getting the emails
Although I can see in the logs the mails are received
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#32 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFTF65UJFVQHYNQYC6GPABLSBWFN7ANCNFSM4QETPDFA>
.
|
bro, maybe I give you access and you help ? lol ive been breaking my head about this for the past 5 hours .. seems like you know how to fix it .. lol |
@Vastelo I have it working with receiving emails for multiple domains. |
Hello,
Not sure why I am getting this error. The docs state that jwtExpiresIn:-1 will not enforce authentication..not sure what else to do at this point.
The text was updated successfully, but these errors were encountered: