[Support] Poste.io Free version


Recommended Posts

TLS had been working fine for over a year, all of a sudden the renewal of the LE certificate is failing:

 

[2022-03-29 12:54:06] LEScript.INFO: Getting list of URLs for API
[2022-03-29 12:54:06] LEScript.INFO: Requesting new nonce for client communication
[2022-03-29 12:54:07] LEScript.INFO: Account already registered. Continuing.
[2022-03-29 12:54:07] LEScript.INFO: Sending registration to letsencrypt server
[2022-03-29 12:54:07] LEScript.INFO: Sending signed request to https://acme-v02.api.letsencrypt.org/acme/new-acct
[2022-03-29 12:54:07] LEScript.INFO: Account: https://acme-v02.api.letsencrypt.org/acme/acct/40602749
[2022-03-29 12:54:07] LEScript.INFO: Starting certificate generation process for domains
[2022-03-29 12:54:07] LEScript.INFO: Requesting challenge for mail.mydomain.co.uk, mydomain.co.uk
[2022-03-29 12:54:07] LEScript.INFO: Sending signed request to https://acme-v02.api.letsencrypt.org/acme/new-order
[2022-03-29 12:54:08] LEScript.INFO: Sending signed request to https://acme-v02.api.letsencrypt.org/acme/authz-v3/90548435960
[2022-03-29 12:54:08] LEScript.INFO: Got challenge token for mail.mydomain.co.uk
[2022-03-29 12:54:08] LEScript.INFO: Token for mail.mydomain.co.uk saved at /opt/www//.well-known/acme-challenge/akZUnvxNdL9EXgkFS5YWO2fu9LJ0Fw5THsfeUcDezw0 and should be available at http://mail.mydomain.co.uk/.well-known/acme-challenge/akZUnvxNdL9EXgkFS5YWO2fu9LJ0Fw5THsfeUcDezw0
[2022-03-29 12:56:08] LEScript.INFO: Sending request to challenge
[2022-03-29 12:56:08] LEScript.INFO: Sending signed request to https://acme-v02.api.letsencrypt.org/acme/chall-v3/90548435960/h6x7Ww
[2022-03-29 12:56:09] LEScript.ERROR: 400 {   "type": "urn:ietf:params:acme:error:badNonce",   "detail": "JWS has an invalid anti-replay nonce: \"0002InMSGQXI1y_s6I4aFptyXnicZcW84BFuTLTuOaE4hCs\"",   "status": 400 }
[2022-03-29 12:56:09] LEScript.ERROR: #0 /opt/admin/vendor/analogic/lescript/Lescript.php(544): Analogic\ACME\Client->curl('POST', 'https://acme-v0...', '{"protected":"e...')
[2022-03-29 12:56:09] LEScript.ERROR: #1 /opt/admin/vendor/analogic/lescript/Lescript.php(422): Analogic\ACME\Client->post('https://acme-v0...', '{"protected":"e...')
[2022-03-29 12:56:09] LEScript.ERROR: #2 /opt/admin/vendor/analogic/lescript/Lescript.php(165): Analogic\ACME\Lescript->signedRequest('https://acme-v0...', Array)
[2022-03-29 12:56:09] LEScript.ERROR: #3 /opt/admin/src/Base/Handler/LeHandler.php(62): Analogic\ACME\Lescript->signDomains(Array)
[2022-03-29 12:56:09] LEScript.ERROR: #4 /opt/admin/src/Base/Controller/LeController.php(71): App\Base\Handler\LeHandler->renew(true)
[2022-03-29 12:56:09] LEScript.ERROR: #5 /opt/admin/vendor/symfony/http-kernel/HttpKernel.php(158): App\Base\Controller\LeController->issueAction(Object(Symfony\Component\HttpFoundation\Request))
[2022-03-29 12:56:09] LEScript.ERROR: #6 /opt/admin/vendor/symfony/http-kernel/HttpKernel.php(80): Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object(Symfony\Component\HttpFoundation\Request), 1)
[2022-03-29 12:56:09] LEScript.ERROR: #7 /opt/admin/vendor/symfony/http-kernel/Kernel.php(201): Symfony\Component\HttpKernel\HttpKernel->handle(Object(Symfony\Component\HttpFoundation\Request), 1, true)
[2022-03-29 12:56:09] LEScript.ERROR: #8 /opt/admin/public/index.php(25): Symfony\Component\HttpKernel\Kernel->handle(Object(Symfony\Component\HttpFoundation\Request))
[2022-03-29 12:56:09] LEScript.ERROR: #9 {main}

 

Do I need to change how I get the Certificate?

 

Thanks

Link to comment
  • 3 weeks later...
On 10/12/2021 at 9:46 PM, tmor2 said:

Ever since I updated poste.io container in August 2021, all of my emails are being quarantined.  In order to IMAP retrieve emails from server to my phone, I need to log in into webUI as admin, go to "Quarantine" tab and click "deliver" next to EACH email. This is very tedious.

 

Does anyone have this problem?

 

Also, under "Blacklist/Whitelist---->Karma Records", all IP addresses are marked as "Bad" connection. The only workaround to manually "delivering" each quarantined email, is whitelisting all incoming IP addresses. That's quite risky.

 

Disabling "Spam Check" and "Antivirus" check didn't solve problem.

 

Any ideas?

 

Did you ever find an answer for this?  I have a friend having a similar problem, trying to figure out why.

 

Thanks

Link to comment
  • 1 month later...

Hi,

 

Just installed the docker container and paired with swag. I can see the logon web UI screen but I was not able to find the default admin logon username and password. The original document webpage is very poor, no information about the web UI at all.

I tried to look into some file in the container config but found nothing. Except a users.db file with an insert into users statement, but the content is not the correct username and password.

So anybody know how to move forward after the docker container is up and running?

Link to comment
  • 2 weeks later...
On 10/12/2021 at 10:46 PM, tmor2 said:

Ever since I updated poste.io container in August 2021, all of my emails are being quarantined.  In order to IMAP retrieve emails from server to my phone, I need to log in into webUI as admin, go to "Quarantine" tab and click "deliver" next to EACH email. This is very tedious.

 

Does anyone have this problem?

 

Also, under "Blacklist/Whitelist---->Karma Records", all IP addresses are marked as "Bad" connection. The only workaround to manually "delivering" each quarantined email, is whitelisting all incoming IP addresses. That's quite risky.

 

Disabling "Spam Check" and "Antivirus" check didn't solve problem.

 

Any ideas?

 

On 2/7/2022 at 8:14 PM, Mad Llama said:

I'm having the same issue suddenly today. Did you ever figure out why it was happening?

 

On 4/14/2022 at 9:52 PM, Vilhjalmr said:

 

Did you ever find an answer for this?  I have a friend having a similar problem, trying to figure out why.

 

Thanks

 

I'm now having this same issue. It started about the middle of last month, and I'm just now noticing I had to go manually release a bunch of emails from quarantine. No emails come through automatically, and go there instead.

 

Anyone figure it out?

Edited by carnivorebrah
Link to comment
  • 2 weeks later...
On 6/5/2022 at 12:10 PM, Vilhjalmr said:

My friend just deleted all karma records and that seemed to fix it.  His server had only been running a couple days though.

 

Thanks. I tried this, but it's still happening. Whenever I receive an email, the sender is automatically added to the Karma records, and the email is sent to quarantine. Not sure how to fix that.

 

I even tried deleting and reinstalling the container.

 

Looking in the delivery logs, it just says "250 Quarantined!" when I receive an email.

Edited by carnivorebrah
Link to comment
On 6/15/2022 at 9:13 PM, carnivorebrah said:

 

Thanks. I tried this, but it's still happening. Whenever I receive an email, the sender is automatically added to the Karma records, and the email is sent to quarantine. Not sure how to fix that.

 

I even tried deleting and reinstalling the container.

 

Looking in the delivery logs, it just says "250 Quarantined!" when I receive an email.

 

As another troubleshooting step, I completely started over from scratch by changing the data directory and setting everything back up.

 

However, I still have the issue with emails going straight to quarantine, and the sender being added to the karma records.

 

I can send emails without issues. All of the connection diagnostics pass as well.

 

I'm not sure what else to try at this point.

Link to comment
  • 3 weeks later...

Hello there sorry for the disturb *specially at this hours eh* 
But i got an error after have setuped my domain name who work nicely, when he test for the Let's encrypt challenge i just got an error i have search an hours for fix that and didn't found anything, so if someone got to know how to fix that :/
image.thumb.png.dbb3e0aa402e889007adc975453ae14b.png

Link to comment
  • 3 weeks later...

Having issues with TLS Let's Encrypt.

 

[2022-08-01 15:40:07] LEScript.INFO: Getting list of URLs for API
[2022-08-01 15:40:07] LEScript.INFO: Requesting new nonce for client communication
[2022-08-01 15:40:08] LEScript.INFO: Account already registered. Continuing.
[2022-08-01 15:40:08] LEScript.INFO: Sending registration to letsencrypt server
[2022-08-01 15:40:08] LEScript.INFO: Sending signed request to https://acme-v02.api.letsencrypt.org/acme/new-acct
[2022-08-01 15:40:08] LEScript.INFO: Account: https://acme-v02.api.letsencrypt.org/acme/acct/656824306
[2022-08-01 15:40:08] LEScript.INFO: Starting certificate generation process for domains
[2022-08-01 15:40:08] LEScript.INFO: Requesting challenge for ctuning.se
[2022-08-01 15:40:08] LEScript.INFO: Sending signed request to https://acme-v02.api.letsencrypt.org/acme/new-order
[2022-08-01 15:40:09] LEScript.INFO: Sending signed request to https://acme-v02.api.letsencrypt.org/acme/authz-v3/137072252896
[2022-08-01 15:40:09] LEScript.INFO: Got challenge token for ctuning.se
[2022-08-01 15:40:09] LEScript.INFO: Token for ctuning.se saved at /opt/www//.well-known/acme-challenge/tl2Yeb_5abIUPYyRhDMJeLyJow5D5MdxfWrC2IZB7r4 and should be available at http://ctuning.se/.well-known/acme-challenge/tl2Yeb_5abIUPYyRhDMJeLyJow5D5MdxfWrC2IZB7r4
[2022-08-01 15:40:09] LEScript.ERROR: Please check http://ctuning.se/.well-known/acme-challenge/tl2Yeb_5abIUPYyRhDMJeLyJow5D5MdxfWrC2IZB7r4 - token not available
[2022-08-01 15:40:09] LEScript.ERROR: #0 /opt/admin/src/Base/Handler/LeHandler.php(62): Analogic\ACME\Lescript->signDomains(Array)
[2022-08-01 15:40:09] LEScript.ERROR: #1 /opt/admin/src/Base/Controller/LeController.php(71): App\Base\Handler\LeHandler->renew(true)
[2022-08-01 15:40:09] LEScript.ERROR: #2 /opt/admin/vendor/symfony/http-kernel/HttpKernel.php(158): App\Base\Controller\LeController->issueAction(Object(Symfony\Component\HttpFoundation\Request))
[2022-08-01 15:40:09] LEScript.ERROR: #3 /opt/admin/vendor/symfony/http-kernel/HttpKernel.php(80): Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object(Symfony\Component\HttpFoundation\Request), 1)
[2022-08-01 15:40:09] LEScript.ERROR: #4 /opt/admin/vendor/symfony/http-kernel/Kernel.php(201): Symfony\Component\HttpKernel\HttpKernel->handle(Object(Symfony\Component\HttpFoundation\Request), 1, true)
[2022-08-01 15:40:09] LEScript.ERROR: #5 /opt/admin/public/index.php(25): Symfony\Component\HttpKernel\Kernel->handle(Object(Symfony\Component\HttpFoundation\Request))
[2022-08-01 15:40:09] LEScript.ERROR: #6 {main}

Anyone have any ideas?

Link to comment
  • 4 weeks later...
On 6/21/2022 at 2:47 AM, carnivorebrah said:

 

As another troubleshooting step, I completely started over from scratch by changing the data directory and setting everything back up.

 

However, I still have the issue with emails going straight to quarantine, and the sender being added to the karma records.

 

I can send emails without issues. All of the connection diagnostics pass as well.

 

I'm not sure what else to try at this point.

 

I have the same issue, has it been solved?

  • Like 1
Link to comment
On 8/1/2022 at 10:56 PM, HKruger3324 said:

Morning,

 

Take a look at this link. This is how I set it up:

https://mattlapaglia.com/self-hosted-email-server-with-unraid-and-poste-io/

 

Mapping the cert files from Swag fixed it! Thank you!

 

On 8/26/2022 at 1:32 PM, Monnier Adrien said:

 

I have the same issue, has it been solved?

 

Yes! See the above post to map the cert files. That worked for me just now.

 

Although, I'm using Swag, which uses a different path for the files:

/mnt/user/appdata/swag/keys/letsencrypt/

 

instead of:

/mnt/user/appdata/NginxProxyManager/letsencrypt/live/npm-33/

 

Edited by carnivorebrah
Link to comment
6 hours ago, carnivorebrah said:

 

Mapping the cert files from Swag fixed it! Thank you!

 

 

Yes! See the above post to map the cert files. That worked for me just now.

 

Although, I'm using Swag, which uses a different path for the files:

/mnt/user/appdata/swag/keys/letsencrypt/

 

instead of:

/mnt/user/appdata/NginxProxyManager/letsencrypt/live/npm-33/

 

Thank you but I moved to another mail server solution

 

My certificate is good but i also encounter the problem.

 

After several tests with poste.io, I realized that the problem probably comes from the DNSBL function with zen.spamhaus.org because I have the same problem when I activate it on Docker-mailserver, all incoming mails are rejected.

Link to comment
On 8/30/2022 at 6:25 AM, Monnier Adrien said:

Thank you but I moved to another mail server solution

 

My certificate is good but i also encounter the problem.

 

After several tests with poste.io, I realized that the problem probably comes from the DNSBL function with zen.spamhaus.org because I have the same problem when I activate it on Docker-mailserver, all incoming mails are rejected.


Someone has fixed this issue ?
Poste.IO send everything to quarantine 😞

Andres

Link to comment
  • 1 month later...
  • 3 months later...
  • 3 months later...
  • 3 months later...

After UNRAID update from 6.11 to 6.12.3, poste.io is not working any longer.

When I try to start the container, I get pop-up error (in UNRAID GUI): "Execution Error, Server error"

I can't access the logs from UNRAID->Docker->Click on poste icon-> select "Logs"

 

Does anyone have a solution to this issue?

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.