OTRS cannot get emails from MS Exchange server - exchange-server

I configured OTRS for getting emails from Exchange
But I get an error :
Backend ERROR: OTRS-CGI-59 Perl: 5.10.1 OS: linux Time: Tue Apr 15 18:01:56 2014
Message: IMAP: Auth for user user/domain.local failed! RemoteAddress: 192.168.176.33 RequestURI: /otrs/index.pl?Action=AdminMailAccount;Subaction=Run;ID=1;ChallengeToken=0KoFVsy4z8DHo2IDkWWbdegGhIZyizZT;
Traceback (1635): Module: Kernel::System::MailAccount::IMAP::_Fetch (OTRS 3.3.6) Line: 124
Module: Kernel::System::MailAccount::IMAP::Fetch (OTRS 3.3.6) Line: 77
Module: Kernel::System::MailAccount::MailAccountFetch (OTRS 3.3.6) Line: 427
Module: Kernel::Modules::AdminMailAccount::Run (OTRS 3.3.6) Line: 64
Module: Kernel::System::Web::InterfaceAgent::Run (OTRS 3.3.6) Line: 871
Module: ModPerl::ROOT::ModPerl::Registry::opt_otrs_bin_cgi_2dbin_index_2epl::handler (unknown version) Line: 41 Module: (eval) (v1.99) Line: 204
Module: ModPerl::RegistryCooker::run (v1.99) Line: 204
Module: ModPerl::RegistryCooker::default_handler (v1.99) Line: 170
Module: ModPerl::Registry::handler (v1.99) Line: 31
I don't have access to a Exchange sever. How to deal with it.

I get success with fetching mail from gmail.
So, my settings for gmail are:
menu like Administrators->email accounts for PostMaster:
Type: POP3S (it means gmail use port 995)
login: bla-bla
password:****
server: pop.gmail.com
then actually I'm not sure, it need to read the manual
trusted: yes
redirect: ..by selected queue
actuality: actual
It confirmed that system fetch mail, than I will discuss with a Exchange administrator.

Related

AWX Automation Error sending notification webhook: 400

ENVIRONMENT:
AWX version: 21.4.0 AWX
install method: operator 0.26.0 AWX
deployment target: k3s + ( awx-on-k3s )
Operating System: redhat
enterprise linux 8
Web Browser: google chrome
Hello team, I am configuring notifications and I have the following error.
If anyone can help I would be grateful!!
Traceback (most recent call last):
File "/var/lib/awx/venv/awx/lib64/python3.9/site-packages/awx/main/tasks/system.py", line 290, in send_notifications
sent = notification.notification_template.send(notification.subject, notification.body)
File "/var/lib/awx/venv/awx/lib64/python3.9/site-packages/awx/main/models/notifications.py", line 185, in send
return backend_obj.send_messages([notification_obj])
File "/var/lib/awx/venv/awx/lib64/python3.9/site-packages/awx/main/notifications/webhook_backend.py", line 81, in send_messages
raise Exception(smart_str(_("Error sending notification webhook: {}").format(r.status_code)))
Exception: Error sending notification webhook: 400```

php spark serve error unable to write cache

Yesterday my app is fine, and today when i try to command
php spark serve
in git bash, i get this error :
CodeIgniter CLI Tool - Version 4.0.4 - Server-Time: 2021-09-15 13:52:28pm
An uncaught Exception was encountered
Type: CodeIgniter\Cache\Exceptions\CacheException
Message: Cache unable to write to C:\xampp\htdocs\prosold\writable\cache/
Filename: C:\xampp\htdocs\prosold\vendor\codeigniter4\framework\system\Cache\Exceptions\CacheException.php
Line Number: 55
Backtrace:
-78 - C:\xampp\htdocs\prosold\vendor\codeigniter4\framework\system\Cache\Handlers\FileHandler.php::forUnableToWrite
-84 - C:\xampp\htdocs\prosold\vendor\codeigniter4\framework\system\Cache\CacheFactory.php::__construct
-123 - C:\xampp\htdocs\prosold\vendor\codeigniter4\framework\system\Config\Services.php::getHandler
-123 - C:\xampp\htdocs\prosold\vendor\codeigniter4\framework\system\Config\BaseService.php::cache
-115 - C:\xampp\htdocs\prosold\vendor\codeigniter4\framework\system\Config\Services.php::getSharedInstance
-102 - C:\xampp\htdocs\prosold\vendor\codeigniter4\framework\system\Common.php::cache
-629 - C:\xampp\htdocs\prosold\vendor\codeigniter4\framework\system\CodeIgniter.php::cache
-298 - C:\xampp\htdocs\prosold\vendor\codeigniter4\framework\system\CodeIgniter.php::displayCache
-86 - C:\xampp\htdocs\prosold\vendor\codeigniter4\framework\system\CLI\Console.php::run
-57 - C:\xampp\htdocs\prosold\spark::run
What should i do?

Ruby Mail Gem Relay Access from Localhost to Postfix

I'm on a workstation that doesn't have a FQDN. I'm developing in Ruby and using the mail gem. I host my own mail server on the LAN. I want to forward outgoing emails to this server, off to a gmail recipient (example).
Due to the fact I'm on my workstation (localhost), it not being recognized as part of one of my LAN domains (I have a static IP), it isn't being recognized by Postfix (from my mail server log):
Mar 25 08:44:30 machine.mydomain1.com postfix/smtpd[9653]: sacl_check: mbr_user_name_to_uuid(mygmail#gmail.com) failed: No such file or directory
Mar 25 08:44:30 machine.mydomain1.com postfix/cleanup[9657]: sacl_check: mbr_user_name_to_uuid(mygmail#gmail.com) failed: No such file or directory
Mar 25 08:44:30 machine.mydomain1.com postfix/smtp[9658]: 92946D63CD4: to=<mygmail#gmail.com>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.14, delays=0.01/0.01/0/0.11, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as AE8ECD63CDA)
Mar 25 08:44:31 machine.mydomain1.com postfix/smtp[9661]: AE8ECD63CDA: to=<mygmail#gmail.com>, relay=gmail-smtp-in.l.google.com[173.194.195.26]:25, delay=0.52, delays=0/0.01/0.34/0.16, dsn=5.7.1, status=bounced (host gmail-smtp-in.l.google.com[173.194.195.26] said: 550-5.7.1 [206.248.184.17 11] Our system has detected that this message is 550-5.7.1 not RFC 5322 compliant: 550-5.7.1 'From' header is missing. 550-5.7.1 To reduce the amount of spam sent to Gmail, this message has been 550-5.7.1 blocked. Please visit 550-5.7.1 https://support.google.com/mail/?p=RfcMessageNonCompliant 550 5.7.1 and review RFC 5322 specifications for more information. a2si7453997iog.10 - gsmtp (in reply to end of DATA command))
Mar 25 08:56:42 machine.mydomain1.com postfix/smtpd[9764]: NOQUEUE: reject: RCPT from unknown[192.168.1.4]: 554 5.7.1 <mygmail#gmail.com>: Relay access denied; from=<alpha#mydomain3.ca> to=<mygmail#gmail.com> proto=ESMTP helo=<mydomain3.ca>
I can use the mail gem properly on another box that has a FQDN just fine. I just can't seem to get it to work on my workstation. As it states in the mail server log:
'From' header is missing. 550-5.7.1 To reduce the amount of spam sent to Gmail, this message has been 550-5.7.1 blocked.
I'm assuming this is the machine name from, and not the email sender from. How can I tell the mail server that I'm not localhost? I've messed with the relay and other directives in postfix to no avail. So I'm trying to modify the Ruby syntax to make the server recognize me.
Any insight appreciated as to how I can get this to work. It's my development box and it's working on my production server, but I'd like to have it working on my dev box.
Adding the following fixed it, a config item for the gem:
mail.header['From'] = 'machine.mydomain.com'
Also making sure the relay information in postfix is set properly.

logging syslog-ng logs Windows logs in multiple lines

I have a problem with logging my Windows server by syslog-ng Agent for Windows v5.0.7 to my Main Syslog server with installed Syslog-ng PE v5.0.
Logs from the agent walks in a multiline shape, see below.
Has anyone had a similar problem? Is there a configuration option, so that the logs went in one line? Or some rewrite configuration?
I thank you all
Configuration for Windows logs in syslog.conf at syslog server and multiple log:
filter f_syslog_win_exc { host("(11.22.33.44)"); };
destination d_syslog_win_exc { file("/var/nsm/windows_syslog/test/exch/$HOST-$R_YEAR$R_MONTH$R_DAY.log"); };
log { source(remote_windows); filter(f_syslog_win_exc); destination(d_syslog_win_exc); };
Jun 9 14:51:33 11.22.33.44 1084 <133>1 2015-06-09T14:51:33+02:00 win_server_2k8 Microsoft_Windows_security_auditing. 508 - [win#18372.4 EVENT_CATEGORY="User Account Management" EVENT_FACILITY="16" EVENT_ID="4725" EVENT_LEVEL="0" EVENT_NAME="Security" EVENT_REC_NUM="210139" EVENT_SID="N/A" EVENT_SOURCE="Microsoft Windows security auditing." EVENT_TASK="User Account Management" EVENT_TYPE="Success Audit" EVENT_USERNAME="win_server_2k8\\syslog-user"][meta sequenceId="3" sysUpTime="14899"]
Jun 9 14:51:33 4725 Security win_server_2k8\syslog-user User Success Audit win_server_2k8 User Account Management A user account was disabled.
Jun 9 14:51:33 11.22.33.44 Subject:
Jun 9 14:51:33 11.22.33.44 Security ID: win_server_2k8\test
Jun 9 14:51:33 11.22.33.44 Account Name: test
Jun 9 14:51:33 11.22.33.44 Account Domain: win_server_2k8 210139 A user account was disabled.
Jun 9 14:51:33 11.22.33.44 Subject:
Jun 9 14:51:33 11.22.33.44 Security ID: win_server_2k8\test
Jun 9 14:51:33 11.22.33.44 Account Name: test
By default the syslog-ng Windows Agent sends logs using the new, RFC5424 protocol. The receiving side seems to use the legacy syslog protocol. You should use a syslog() source instead of tcp() on the receiving side, and that takes proper care of multi-line messages.

Cannot install socket.io on windows Error: connect EACCESS

I am new to what I'm doing now (Node.js,socket.io).
I've already installed Node.js and now I'm trying to install socket.io but I am having this EACCESS error. Thank you for the help!
I'm using Windows 7 x64
I ran cmd with privileges.
and then
npm install socket.io
Here is the log:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\\\node.exe',
1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'install',
1 verbose cli 'socket.io' ]
2 info using npm#1.3.14
3 info using node#v0.10.22
4 verbose node symlink C:\Program Files\nodejs\\node.exe
5 verbose cache add [ 'socket.io', null ]
6 verbose cache add name=undefined spec="socket.io" args=["socket.io",null]
7 verbose parsed url { protocol: null,
7 verbose parsed url slashes: null,
7 verbose parsed url auth: null,
7 verbose parsed url host: null,
7 verbose parsed url port: null,
7 verbose parsed url hostname: null,
7 verbose parsed url hash: null,
7 verbose parsed url search: null,
7 verbose parsed url query: null,
7 verbose parsed url pathname: 'socket.io',
7 verbose parsed url path: 'socket.io',
7 verbose parsed url href: 'socket.io' }
8 silly lockFile 71475bfd-socket-io socket.io
9 verbose lock socket.io C:\Users\Bobby\AppData\Roaming\npm-cache\71475bfd-socket- io.lock
10 silly lockFile 71475bfd-socket-io socket.io
11 silly lockFile 71475bfd-socket-io socket.io
12 verbose addNamed [ 'socket.io', '' ]
13 verbose addNamed [ null, '*' ]
14 silly lockFile c03de861-socket-io socket.io#
15 verbose lock socket.io# C:\Users\Bobby\AppData\Roaming\npm-cache\c03de861-socket- io.lock
16 silly addNameRange { name: 'socket.io', range: '*', hasData: false }
17 verbose url raw socket.io
18 verbose url resolving [ 'https://registry.npmjs.org/', './socket.io' ]
19 verbose url resolved https://registry.npmjs.org/socket.io
20 info trying registry request attempt 1 at 09:33:49
21 http GET https://registry.npmjs.org/socket.io
22 info retry will retry, error on last attempt: Error: connect EACCES
23 info trying registry request attempt 2 at 09:34:00
24 http GET https://registry.npmjs.org/socket.io
25 info retry will retry, error on last attempt: Error: connect EACCES
26 info trying registry request attempt 3 at 09:35:00
27 http GET https://registry.npmjs.org/socket.io
28 silly lockFile c03de861-socket-io socket.io#
29 silly lockFile c03de861-socket-io socket.io#
30 error Error: connect EACCES
30 error at errnoException (net.js:901:11)
30 error at Object.afterConnect [as oncomplete] (net.js:892:19)
30 error { [Error: connect EACCES] code: 'EACCES', errno: 'EACCES', syscall: 'connect' }
31 error Please try running this command again as root/Administrator.
32 error System Windows_NT 6.1.7601
33 error command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "socket.io"
34 error cwd C:\node
35 error node -v v0.10.22
36 error npm -v 1.3.14
37 error syscall connect
38 error code EACCES
39 error errno EACCES
40 error stack Error: connect EACCES
40 error stack at errnoException (net.js:901:11)
40 error stack at Object.afterConnect [as oncomplete] (net.js:892:19)
41 verbose exit [ 1, true ]
EACCES means socket.io can't access a port. It might be because you don't have the privileges or the port is already used by another application. You should run this command as an administrator and/or close any process using the port socket.io is trying to access to.
I think it's:
runas /noprofile /root:Administrator npm install socket.io

Resources