My turn.

Somehow, at some point the -g .skipgoto?=hello switch in my /etc/systemd/system/webcit-http.service and webcit-https.service files got reverted on my main machine - but also when I reran the easyinstall on the new VM.


After modifying these two files with vi - both versions were failing, saying that the ports (8916 and 443) were already bound.


I eventually resorted to re-running /usr/local/webcit/setup.


It saw webcit-http.service on port 2000. I have *never* set it on that port.

I reverted it in setup to 8916.


I accepted the default for HTTPS.


Now webcit is starting, both on 8916 and 443... but in the logs, I'm seeing this over and over again when connecting via HTTPS.

Apr 28 21:09:50 secure webcit[2151]: webcit[2151]: Can't bind: Address already in use
Apr 28 21:09:50 secure webcit[2151]: Can't bind: Address already in use
Apr 28 21:09:50 secure systemd[1]: webcit-https.service: Main process exited, code=exited, status=101/n/a
Apr 28 21:09:50 secure systemd[1]: webcit-https.service: Failed with result 'exit-code'.

Although it IS connecting on the default HTTPS port - you can check that here...

https://secure.wallofhate.com


It is almost like there are multiple copies of webcit being called and they're in port contention with themselves - like there are two instances running on port 443 and the one instance is exiting "failed with result 'exit-code'" because the other one already has that port bound?


Something is most definitely wrong. It is running. 

So, this morning I looked at the webcit-https.service config, and it was pointing at a different port than :443. 

I changed it back to :443, and the issue immediately reoccurred. 
Changing it back to its previous setting didn't restore https: connectivity to the board, even with a reboot, and even going into setup. 

That led me to lsof -i :443 

Which showed me that webcit WAS listening on port :443, despite not responding. 

I killed that PID, and restarted the webcit service. 

Now it is working fine. BUT the webcit-https.service has the port listed as 4916 now 


And sure enough - Citadel will render a page on 443 *or* 4916, and webcit is running twice, once on 443 and once on 4916 (and also on 8916 in regular HTTP). 

Is there somewhere else in the config that launches webcit other than the config in systemd/system 

Now it isn't restarting and failing in syslog - but it is running twice, on either port. 

I'll copy the logs from console, I'm not on that machine now. 

root@secure:/etc/systemd/system# sudo lsof -i :443
COMMAND PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
webcit  313 root    6u  IPv6  15532      0t0  TCP *:https (LISTEN)
root@secure:/etc/systemd/system# sudo lsof -i :8916
COMMAND PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
webcit  317 root    6u  IPv6  15529      0t0  TCP *:8916 (LISTEN)


They're both there, and listening - but PID 313 is refusing to respond on the web.

root@secure:/etc/systemd/system# sudo kill 313
root@secure:/etc/systemd/system# sudo lsof -i :443
root@secure:/etc/systemd/system# sudo service webcit restart
root@secure:/etc/systemd/system# sudo lsof -i :443
COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
webcit  2219 root    6u  IPv6  41814      0t0  TCP *:https (LISTEN)

Now it is back, as PID 2219 - and it is responding.

BUT...


PID 2185 is also launched - by /etc/systemd/system/webcit-https.service and ALSO listening for SSL connections

root@secure:/etc/systemd/system# sudo lsof -i :4916
COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
webcit  2185 root    6u  IPv6  40818      0t0  TCP *:4916 (LISTEN)


The bind errors aren't causing webcit to constantly exit and restart - so - this is good - but I'm wondering why it is launching twice, and what will happen in a reboot or restart at this point. 

Any thougts on this ? still not possible to send mail from mail client, don't want to use webcit for repliying forever ....

Regards,

Bart

Mon Apr 19 2021 18:14:53 EDT from bartv Subject: Re: SMTP authentication problem from outlook

been testing with different style usernames and passwords - still no connection.

I'm not 100% sure if that's the reason or if i misinterpreted things, but since my testing i cannot get my phone to connect to smtp either, so it is not limited to outlook.

Bart

 

Fri Apr 16 2021 02:55:45 EDT from chrisskhc Subject: Re: SMTP authentication problem from outlook

Hello,

 

I have exactly the same problem since I updated to build 931 via easyinstall.

Everything works fine except the mail client connection to the SMTP.

 

I would also be very grateful for targeted tips on troubleshooting.

 

chrisskhc

 

 

Tue Apr 13 2021 09:56:56 EDT from bartv Subject: Re: SMTP authentication problem from outlook

 

Fri Apr 09 2021 06:07:11 EDT from bartv Subject: SMTP authentication problem from outlook

Hello all,

 

Could not find search function in this forum, so apologies if this is a recurring question.

 

Installed Citadel on my PI4, and most of it is working, except i have problems connecting outlook.

I have setup citadel as my mailserver, and i can send and receive email to external accounts (work, gmail, etc). (Test via Webcit)

 

I'm using outlook 2016 and connect via POP3/SMTP.

Outlook collects mail via POP3 fine from the server, using account settings either on port 110 and 995 no problem.

But is keeps asking for my credentials when using SMTP - controlpanel/mailsettings - test account setting - tries to send a test mail.

Tried SMTP via port 25 no encryption, but also using port 465 - with SSL enabled - keeps popping credentials question and port 587 STARTTLS - credentials quesions

'Your email server rejected your login. Verify your user name and password"

email server rejects login using username/password. But they work fine for POP3 logon......

 

Using the same credentials, sending from my Galaxy S10 via wifi on internal network using builtin mailclient using port 465 and SSL is no problem.

So Citadel & Pi should be configured correctly...

 

I'm lost. Any suggestions ?

 

Tnx

 

Bart

 

[Edit]

i've been testing  but no luck yet.

syslog has this error : bad password specified for <> Service <SMTP-MTA>

Should the username not be within those emty brackets ? that would mean the username is not forwarded by outlook to citedal ????

this is the log of one session , as you can see the pop3 session is ok....

Apr 13 15:18:18 raspix citserver[32694]: citserver[32694]: context: session (POP3) started from Laborix.bartscorner.local (192.168.1.117) uid=-1

Apr 13 15:18:18 raspix citserver[32694]: context: session (POP3) started from Laborix.bartscorner.local (192.168.1.117) uid=-1

Apr 13 15:18:18 raspix citserver[32694]: citserver[32694]: user_ops: <bartver> logged in

Apr 13 15:18:18 raspix citserver[32694]: user_ops: <bartver> logged in

Apr 13 15:18:18 raspix citserver[32694]: citserver[32694]: context: [12718]SRV[POP3] Session ended.

Apr 13 15:18:18 raspix citserver[32694]: context: [12718]SRV[POP3] Session ended.

Apr 13 15:18:18 raspix citserver[32694]: citserver[32694]: context: session (SMTP-MTA) started from Laborix.bartscorner.local (192.168.1.117) uid=-1

Apr 13 15:18:18 raspix citserver[32694]: context: session (SMTP-MTA) started from Laborix.bartscorner.local (192.168.1.117) uid=-1

Apr 13 15:18:18 raspix citserver[32694]: citserver[32694]: user_ops: bad password specified for <> Service <SMTP-MTA> Port <25> Remote <Laborix.bartscorner.local / 192.168.1.117>

Apr 13 15:18:18 raspix citserver[32694]: user_ops: bad password specified for <> Service <SMTP-MTA> Port <25> Remote <Laborix.bartscorner.local / 192.168.1.117>

Apr 13 15:18:18 raspix citserver[32694]: SMTP: client disconnected: ending session.

Apr 13 15:18:18 raspix citserver[32694]: citserver[32694]: SMTP: client disconnected: ending session.

Apr 13 15:18:18 raspix citserver[32694]: citserver[32694]: context: [12719]SRV[SMTP-MTA] Session ended.

 

 

 

 

 

Hi,
some (long) time ago I expressed my interest in trying out Citadel within a Docker container and someone here pointed me to some repository where some sort of "prototype" was available. Now, I have lost that particular link and am now asking if anyone here can (once more) provide it to me?

Thank you,

Niels

Ah, found it here: code.citadel.org

Mon May 03 2021 07:19:01 AM EDT from megagumbo Subject: Citadel in Docker (prototype repo URL?)

Hi,
some (long) time ago I expressed my interest in trying out Citadel within a Docker container and someone here pointed me to some repository where some sort of "prototype" was available. Now, I have lost that particular link and am now asking if anyone here can (once more) provide it to me?

Thank you,

Niels

Ok... I figured out part of the mystery on my pre and post login redirect.


This is what I had in my webcit-https.service config:

more webcit-https.service
[Unit]
Description=Citadel web service
After=citadel.target
[Service]
ExecStart=/usr/local/webcit/webcit -p8916 -g/dotgoto?room=hello uds /usr/local/c
itadel
ExecReload=/bin/kill
KillMode=process
Restart=always
RestartSec=3
[Install]
WantedBy=multi-user.target

So, that is why it was failing to startup. It was attempting to assign the https on port 8916, which is already selected as the http port.


But... it is ALSO launching it on port 443. And in either case, it is not redirecting to the "hello" room with the ExecStart command line above.

If I change the webcit-https to 4916 I get this error in Firefox connecting to locahost:4916

Secure Connection Failed

An error occurred during a connection to 127.0.0.1:4916. SSL received a record that exceeded the maximum permissible length.

Error code: SSL_ERROR_RX_RECORD_TOO_LONG

    The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
    Please contact the website owners to inform them of this problem.

Set for localhost:443 - I just get the lobby - no redirect.

Should I be using service webcit restart or systemctl restart webcit to restart the service?

And is it possible in Debian 10 that Citadel is launching somewhere else, then also being called again in systemd, potentially in conflict with itself - with 4 instances of Webcit running, or maybe 3... one on 8916, one on 4916 and one on 443?

Ok... so I've confirmed that I have /etc/systemd/system/webcit-https.service set correctly for port 443

I"ve ran setup in citadel and webcit

I get this

root@secure:/usr/local/webcit# netstat -ltnp

Active Internet connections (only servers)

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      466/sshd            

tcp        0      0 0.0.0.0:23              0.0.0.0:*               LISTEN      460/inetd           

tcp        0      0 0.0.0.0:504             0.0.0.0:*               LISTEN      8562/citserver      

tcp        0      0 0.0.0.0:5222            0.0.0.0:*               LISTEN      8562/citserver      

tcp6       0      0 :::80                   :::*                    LISTEN      481/apache2         

tcp6       0      0 :::8916                 :::*                    LISTEN      8872/webcit         

tcp6       0      0 :::4916                 :::*                    LISTEN      8711/webcit         

tcp6       0      0 :::22                   :::*                    LISTEN      466/sshd            

tcp6       0      0 :::443                  :::*                    LISTEN      8875/webcit         

root@secure:/usr/local/webcit# kill 8711

root@secure:/usr/local/webcit# netstat -ltnp

Active Internet connections (only servers)

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      466/sshd            

tcp        0      0 0.0.0.0:23              0.0.0.0:*               LISTEN      460/inetd           

tcp        0      0 0.0.0.0:504             0.0.0.0:*               LISTEN      8562/citserver      

tcp        0      0 0.0.0.0:5222            0.0.0.0:*               LISTEN      8562/citserver      

tcp6       0      0 :::80                   :::*                    LISTEN      481/apache2         

tcp6       0      0 :::4916                 :::*                    LISTEN      8925/webcit         

tcp6       0      0 :::8916                 :::*                    LISTEN      8872/webcit         

tcp6       0      0 :::22                   :::*                    LISTEN      466/sshd            

tcp6       0      0 :::443                  :::*                    LISTEN      8875/webcit         

root@secure:/usr/local/webcit# kill 8925

root@secure:/usr/local/webcit# netstat -ltnp

Active Internet connections (only servers)

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      466/sshd            

tcp        0      0 0.0.0.0:23              0.0.0.0:*               LISTEN      460/inetd           

tcp        0      0 0.0.0.0:504             0.0.0.0:*               LISTEN      8562/citserver      

tcp        0      0 0.0.0.0:5222            0.0.0.0:*               LISTEN      8562/citserver      

tcp6       0      0 :::80                   :::*                    LISTEN      481/apache2         

tcp6       0      0 :::8916                 :::*                    LISTEN      8872/webcit         

tcp6       0      0 :::22                   :::*                    LISTEN      466/sshd            

tcp6       0      0 :::443                  :::*                    LISTEN      8875/webcit         

root@secure:/usr/local/webcit# netstat -ltnp

Active Internet connections (only servers)

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      466/sshd            

tcp        0      0 0.0.0.0:23              0.0.0.0:*               LISTEN      460/inetd           

tcp        0      0 0.0.0.0:504             0.0.0.0:*               LISTEN      8562/citserver      

tcp        0      0 0.0.0.0:5222            0.0.0.0:*               LISTEN      8562/citserver      

tcp6       0      0 :::80                   :::*                    LISTEN      481/apache2         

tcp6       0      0 :::4916                 :::*                    LISTEN      8946/webcit         

tcp6       0      0 :::8916                 :::*                    LISTEN      8872/webcit         

tcp6       0      0 :::22                   :::*                    LISTEN      466/sshd            

tcp6       0      0 :::443                  :::*                    LISTEN      8875/webcit

No matter what I do... Webcit respawns on 4916. 

I guess I can try a reboot of the server. 

And here is something interesting... when webcit-https.service is spawning on 443, I get "Error Code: SSL_ERROR_RX_RECORD_TOO_LONG" with a fully formed URL in Firefox... 

e.g., https://127.0.0.1 or https://secure.wallofhate.com 

even if I specific the port... 

:443

but... if I change the URL in the address bar to 

http://secure.wallofhate.com:443 

It resolves fine. 

I was wondering if there is a way to run a DOSbox in a permanent post... 

Like, if you set up a Wiki room, with a single post, and in that post, you had it executing a .js DOSbox - you could then run Cit-86 or Asgard-86 in that DosBOX instance - and those Citadels support classic ASCII BBS doors and door games. 

Wed May 05 2021 00:34:20 EDT from ASCII Express

Speaking of the text mode, I wrote a politically incorrect door game in the '90s, and wanted to find a way to let my users play it. I looked in the citadel.rc but didn't find a way to run an external program. Does Citadel allow this? Have SysOps rigged up some other way to run some doors?

Wed May 05 2021 01:17:52 EDT from ParanoidDelusions

I was wondering if there is a way to run a DOSbox in a permanent post... 

Like, if you set up a Wiki room, with a single post, and in that post, you had it executing a .js DOSbox - you could then run Cit-86 or Asgard-86 in that DosBOX instance - and those Citadels support classic ASCII BBS doors and door games. 

 

I am itching to figure out how to do this. Something tells me that if I want to run the infocom frotz emu, all I need to do is pipe the i/o somehow. 

So, plan 1: learn how to pipe stuff. 

 

 

Some guy figured out how to put emulators on a web page...If I could figure out how to put this on a static page, blammo...

its called pcjs .... and

https://www.pcjs.org/ shows you what the project is about.

 

I figured you might be the one to crack this problem. 

There is a .js thing that is published that allows you to run dosbox programs in a webpage. I linked to it somewhere. 

https://js-dos.com/

I think it might be instrumental in achieving what we want. 

Wed May 05 2021 18:32:00 EDT from smashbot64

 

Wed May 05 2021 01:17:52 EDT from ParanoidDelusions

I was wondering if there is a way to run a DOSbox in a permanent post... 

Like, if you set up a Wiki room, with a single post, and in that post, you had it executing a .js DOSbox - you could then run Cit-86 or Asgard-86 in that DosBOX instance - and those Citadels support classic ASCII BBS doors and door games. 

 

I am itching to figure out how to do this. Something tells me that if I want to run the infocom frotz emu, all I need to do is pipe the i/o somehow. 

So, plan 1: learn how to pipe stuff. 

 

 

Some guy figured out how to put emulators on a web page...If I could figure out how to put this on a static page, blammo...

its called pcjs .... and

https://www.pcjs.org/ shows you what the project is about.

 

 

Hi

New to Citadel and having a problem with emails being sent to spam messages on Gmail, hotmail accounts.

I have producted a private and Public certification file with a DNS record which i have put in the name server for my domain, but I can not file the public / private files to replace.

The instalation is a PI4, 2gb, 2tb HDD, fresh Ras OS lite, and citadel easy installed. I can not find where the cerification files need to be placed to replace the selfcert files.

Any help please.

Peter G

what's the point of a support forum if nobody is answering....

It's a shame, i really liked citadel

Bart

Fri Apr 30 2021 02:44:39 EDT from bartv Subject: Re: SMTP authentication problem from outlook

Any thougts on this ? still not possible to send mail from mail client, don't want to use webcit for repliying forever ....

Regards,

Bart

 

Mon Apr 19 2021 18:14:53 EDT from bartv Subject: Re: SMTP authentication problem from outlook

been testing with different style usernames and passwords - still no connection.

I'm not 100% sure if that's the reason or if i misinterpreted things, but since my testing i cannot get my phone to connect to smtp either, so it is not limited to outlook.

Bart

 

Fri Apr 16 2021 02:55:45 EDT from chrisskhc Subject: Re: SMTP authentication problem from outlook

Hello,

 

I have exactly the same problem since I updated to build 931 via easyinstall.

Everything works fine except the mail client connection to the SMTP.

 

I would also be very grateful for targeted tips on troubleshooting.

 

chrisskhc

 

 

Tue Apr 13 2021 09:56:56 EDT from bartv Subject: Re: SMTP authentication problem from outlook

 

Fri Apr 09 2021 06:07:11 EDT from bartv Subject: SMTP authentication problem from outlook

Hello all,

 

Could not find search function in this forum, so apologies if this is a recurring question.

 

Installed Citadel on my PI4, and most of it is working, except i have problems connecting outlook.

I have setup citadel as my mailserver, and i can send and receive email to external accounts (work, gmail, etc). (Test via Webcit)

 

I'm using outlook 2016 and connect via POP3/SMTP.

Outlook collects mail via POP3 fine from the server, using account settings either on port 110 and 995 no problem.

But is keeps asking for my credentials when using SMTP - controlpanel/mailsettings - test account setting - tries to send a test mail.

Tried SMTP via port 25 no encryption, but also using port 465 - with SSL enabled - keeps popping credentials question and port 587 STARTTLS - credentials quesions

'Your email server rejected your login. Verify your user name and password"

email server rejects login using username/password. But they work fine for POP3 logon......

 

Using the same credentials, sending from my Galaxy S10 via wifi on internal network using builtin mailclient using port 465 and SSL is no problem.

So Citadel & Pi should be configured correctly...

 

I'm lost. Any suggestions ?

 

Tnx

 

Bart

 

[Edit]

i've been testing  but no luck yet.

syslog has this error : bad password specified for <> Service <SMTP-MTA>

Should the username not be within those emty brackets ? that would mean the username is not forwarded by outlook to citedal ????

this is the log of one session , as you can see the pop3 session is ok....

Apr 13 15:18:18 raspix citserver[32694]: citserver[32694]: context: session (POP3) started from Laborix.bartscorner.local (192.168.1.117) uid=-1

Apr 13 15:18:18 raspix citserver[32694]: context: session (POP3) started from Laborix.bartscorner.local (192.168.1.117) uid=-1

Apr 13 15:18:18 raspix citserver[32694]: citserver[32694]: user_ops: <bartver> logged in

Apr 13 15:18:18 raspix citserver[32694]: user_ops: <bartver> logged in

Apr 13 15:18:18 raspix citserver[32694]: citserver[32694]: context: [12718]SRV[POP3] Session ended.

Apr 13 15:18:18 raspix citserver[32694]: context: [12718]SRV[POP3] Session ended.

Apr 13 15:18:18 raspix citserver[32694]: citserver[32694]: context: session (SMTP-MTA) started from Laborix.bartscorner.local (192.168.1.117) uid=-1

Apr 13 15:18:18 raspix citserver[32694]: context: session (SMTP-MTA) started from Laborix.bartscorner.local (192.168.1.117) uid=-1

Apr 13 15:18:18 raspix citserver[32694]: citserver[32694]: user_ops: bad password specified for <> Service <SMTP-MTA> Port <25> Remote <Laborix.bartscorner.local / 192.168.1.117>

Apr 13 15:18:18 raspix citserver[32694]: user_ops: bad password specified for <> Service <SMTP-MTA> Port <25> Remote <Laborix.bartscorner.local / 192.168.1.117>

Apr 13 15:18:18 raspix citserver[32694]: SMTP: client disconnected: ending session.

Apr 13 15:18:18 raspix citserver[32694]: citserver[32694]: SMTP: client disconnected: ending session.

Apr 13 15:18:18 raspix citserver[32694]: citserver[32694]: context: [12719]SRV[SMTP-MTA] Session ended.

 

 

 

 

 

 

Have you tried using Telnet to connect to your SMTP server and seeing what happens there when you compose the e-mail? 

https://www.itgeared.com/articles/1102-smtp-commands-how-to-send-email-using/

If you haven't - that might give you better insight into what is happening. 

Citadel is in a very active development phase - with a LOT of team testing going on - and a major rewrite of the underlying code and distribution model taking place. 


The end result should be a more supportable core application, that is easier to install, maintain and repair, that runs leaner with tighter code. 

A lot of the problems in Citadel right now are legacy issues - and figuring out what is causing them, our guess is often as good as the developers. I've upset the developers with flooding this forum with "questions," which really amounted to me working through the issues myself and figuring out my own answers. 

I think part of it is that the development team could spend time building labs and trying to recreate and fix problems on older versions of Citadel that won't be relevant to the next major production rc of Citadel - because the code is changing so much... 

Or they can put that time into getting that rc to us and providing us a more stable Citadel that is more supportable for them. 

Keeping in mind, that Citadel is a FOSS volunteer supported project and team that doesn't even suggest a patreon or other compensation. I've never seen any of the developers "pass the plate". 

Most of the issues I experience with Citadel are a combination of it being poorly documented/documentation being out of date - and operator error in configuring or setup. I end up spending a lot of time reverse engineering what Citadel is doing and learning a TON about Linux and suddenly a light is revealed on what I've done wrong that caused my issue. Mail is a complex and difficult to manage service/platform in general - one of the harder servers in any data-center to administer. There are a lot of different moving parts, it still relies on some fairly low-level protocols and is very picky about having everything running optimal at your network layer and security layer, it is *super* important to people and it is a favorite vector of attack - and it generally relies on some sort of back-end database - so it is one of the most "multi-discipline" servers in the DC that a person can manage. And - because it is kind of a utility server - not seen as a critical line of business application server but instead a kind of support role - it generally doesn't get the attention it deserves. Lots of IT staff in lots of IT departments manage e-mail servers without understanding how to test SMTP from a telnet session by hand-crafting an email there the old fashioned way, or the importance of correct reverse lookup records, or a billion other complexities of making an email server work right. 

Personally - I just run Citadel as a BBS - and I've got the internet mail disabled. Running your own mail server is a royal pain-in-the-ass that is difficult to manage and secure and requires you to be at the top of your IT game - and if you read through this room - you'll see the vast majority of the questions have to do with people attempting to host their own e-mail servers.

But I suspect the next version of Citadel will be a major step forward in making this all easier and also more supportable - so I recommend you stick with Citadel. I've administered Exchange for corporations, I've managed SMTP servers, I've provided support for clients running mail servers linked into VoIP voice-mail systems. Citadel is one of the *best* mail-server solutions out there. Easy to comprehend, configure, administer and backup. But it is still e-mail... one of the earliest internet protocols/apps invented and one of the LEAST changed from the start. 

Fri May 07 2021 04:13:43 EDT from bartv Subject: SMTP authentication problem

what's the point of a support forum if nobody is answering....

It's a shame, i really liked citadel

Bart

Fri Apr 30 2021 02:44:39 EDT from bartv Subject: Re: SMTP authentication problem from outlook

Any thougts on this ? still not possible to send mail from mail client, don't want to use webcit for repliying forever ....

Regards,

Bart

 

Mon Apr 19 2021 18:14:53 EDT from bartv Subject: Re: SMTP authentication problem from outlook

been testing with different style usernames and passwords - still no connection.

I'm not 100% sure if that's the reason or if i misinterpreted things, but since my testing i cannot get my phone to connect to smtp either, so it is not limited to outlook.

Bart

 

Fri Apr 16 2021 02:55:45 EDT from chrisskhc Subject: Re: SMTP authentication problem from outlook

Hello,

 

I have exactly the same problem since I updated to build 931 via easyinstall.

Everything works fine except the mail client connection to the SMTP.

 

I would also be very grateful for targeted tips on troubleshooting.

 

chrisskhc

 

 

Tue Apr 13 2021 09:56:56 EDT from bartv Subject: Re: SMTP authentication problem from outlook

 

Fri Apr 09 2021 06:07:11 EDT from bartv Subject: SMTP authentication problem from outlook

Hello all,

 

Could not find search function in this forum, so apologies if this is a recurring question.

 

Installed Citadel on my PI4, and most of it is working, except i have problems connecting outlook.

I have setup citadel as my mailserver, and i can send and receive email to external accounts (work, gmail, etc). (Test via Webcit)

 

I'm using outlook 2016 and connect via POP3/SMTP.

Outlook collects mail via POP3 fine from the server, using account settings either on port 110 and 995 no problem.

But is keeps asking for my credentials when using SMTP - controlpanel/mailsettings - test account setting - tries to send a test mail.

Tried SMTP via port 25 no encryption, but also using port 465 - with SSL enabled - keeps popping credentials question and port 587 STARTTLS - credentials quesions

'Your email server rejected your login. Verify your user name and password"

email server rejects login using username/password. But they work fine for POP3 logon......

 

Using the same credentials, sending from my Galaxy S10 via wifi on internal network using builtin mailclient using port 465 and SSL is no problem.

So Citadel & Pi should be configured correctly...

 

I'm lost. Any suggestions ?

 

Tnx

 

Bart

 

[Edit]

i've been testing  but no luck yet.

syslog has this error : bad password specified for <> Service <SMTP-MTA>

Should the username not be within those emty brackets ? that would mean the username is not forwarded by outlook to citedal ????

this is the log of one session , as you can see the pop3 session is ok....

Apr 13 15:18:18 raspix citserver[32694]: citserver[32694]: context: session (POP3) started from Laborix.bartscorner.local (192.168.1.117) uid=-1

Apr 13 15:18:18 raspix citserver[32694]: context: session (POP3) started from Laborix.bartscorner.local (192.168.1.117) uid=-1

Apr 13 15:18:18 raspix citserver[32694]: citserver[32694]: user_ops: <bartver> logged in

Apr 13 15:18:18 raspix citserver[32694]: user_ops: <bartver> logged in

Apr 13 15:18:18 raspix citserver[32694]: citserver[32694]: context: [12718]SRV[POP3] Session ended.

Apr 13 15:18:18 raspix citserver[32694]: context: [12718]SRV[POP3] Session ended.

Apr 13 15:18:18 raspix citserver[32694]: citserver[32694]: context: session (SMTP-MTA) started from Laborix.bartscorner.local (192.168.1.117) uid=-1

Apr 13 15:18:18 raspix citserver[32694]: context: session (SMTP-MTA) started from Laborix.bartscorner.local (192.168.1.117) uid=-1

Apr 13 15:18:18 raspix citserver[32694]: citserver[32694]: user_ops: bad password specified for <> Service <SMTP-MTA> Port <25> Remote <Laborix.bartscorner.local / 192.168.1.117>

Apr 13 15:18:18 raspix citserver[32694]: user_ops: bad password specified for <> Service <SMTP-MTA> Port <25> Remote <Laborix.bartscorner.local / 192.168.1.117>

Apr 13 15:18:18 raspix citserver[32694]: SMTP: client disconnected: ending session.

Apr 13 15:18:18 raspix citserver[32694]: citserver[32694]: SMTP: client disconnected: ending session.

Apr 13 15:18:18 raspix citserver[32694]: citserver[32694]: context: [12719]SRV[SMTP-MTA] Session ended.