Networking – Extremely slow WiFi speeds on Lubuntu 19.04?

Recently re-installed Lubuntu 19.04 on a new SSD because the old one failed. However, with the updated versions of Lubuntu I get extremely slow WiFi speeds. This was not a problem with the previous installation of 17.10. After some research, I found on 18:04 several posts to Intel Wi-Fi adapters. However, my lspci-sourced chipset is a Ralink RT5392 chipset, so solutions to Intel adapters did not help. Checking the normal Internet speed on other computers in the house is only possible on Lubuntu computers. Any suggestions?

EDIT: and now it seems unreliable to show the networks as available, sometimes the network icon disappears and needs to be restarted etc. Strange, because it's a fresh install a few hours ago with a new image from today.

Networking – Postfix tries to contact a wrong server when sending emails?

I'm new to Linux servers and trying to set up a Drupal site.

However, if the site sends an email, Postfix / SMTP attempts to connect to the local Web server and the connection is rejected.

I've been sticking to it for a while and my sysadmin is also unsure why it accesses the webserver (which shares the name of the local domain).

June 17 14:47:59 localhost postfix / pickup[13138]: 310FD1049166: uid = 48 from =


June 17 14:47:59 localhost postfix / cleanup[17148]: 310FD1049166: message-id =
<20190617044759.310FD1049166@outlook.mydomain.com.au>


June 17 14:47:59 localhost postfix / qmgr[13139]: 310FD1049166: from =
, size = 2608, nrcpt = 1 (queue active)



June 17 14:47:59 localhost postfix / error[17149]: 310FD1049166: to =
Relay = none, delay = 0.13, delays = 0.09 / 0.01 / 0 / 0.03,
dsn = 4.4.1, status = deferred (delivery temporarily suspended: connection to
mydomain.com.au[webServerIP]: 25: connection denied)

This is the mail log of an email attempt.

I have never explicitly defined the webServerIP (although it comes from mydomain.com.au)

I have this in my php.ini file:

[mail function]







SMTP = outlook.mydomain.com.au

smtp_port = 25

And that in my postfix / main.cf:

myhostname = outlook.mydomain.com.au

Any help would be appreciated.

TO EDIT:
My full main.cf:

# Global Postfix configuration file. This file lists only a subset
# of all parameters. For the syntax and for a complete parameter
# List can be found in the manual page of postconf (5) (command: "man 5 postconf").
#
# For general configuration examples, see BASIC_CONFIGURATION_README
# and STANDARD_CONFIGURATION_README. Use to find these documents
# the command "postconf html_directory readme_directory" or go to
# http://www.postfix.org/.
#
# For best results, do not change more than 2-3 parameters at the same time.
# and test if Postfix still works after each change.

# SOFT BOUNCE
#
# The soft_bounce parameter provides a limited safety net for
# test. When soft_bounce is enabled, emails remain queued
# would bounce otherwise. This parameter disables locally generated
# skips and prevents the SMTP server from permanently rejecting emails
# (by changing 5xx answers in 4xx answers). However, soft_bounce
# is not a cure for address rewrite errors or e-mail forwarding.
#
#soft_bounce = no

# LOCAL PATH NAME INFORMATION
#
# The queue_directory directory specifies the location of the postfix queue.
# This is also the root of Postfix daemons that are chrooted.
# For information on setting up Postfix chroot, see the files in examples / chroot-setup
# Environments on different UNIX systems.
#
Queue directory = / var / spool / postfix

# The command_directory parameter specifies the location of all
# postXXX commands.
#
command_directory = / usr / sbin

# The daemon_directory parameter specifies the location of all Postfix
# Daemon programs (that is, programs listed in the master.cf file). These
The # directory must be owned by root.
#
daemon_directory = / usr / libexec / postfix

# The data_directory parameter specifies the location of Postfix-writable
# Data files (caches, random numbers). This directory must be owned
# from the mail_owner account (see below).
#
Data directory = / var / lib / postfix

# QUEUE AND PROCESS OWNERSHIP
#
# The mail_owner parameter specifies the owner of the postfix queue
# and most postfix daemon processes. Enter the name of a user
# account THIS DOES NOT SHARE HIS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT HAS NO OTHER FILES OR PROCESSES ON THE SYSTEM. in the
# In particular, no one or demon may be specified. PLEASE USE A PARTICULAR
# USERS.
#
mail_owner = postfix

# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to an external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT CALL A PRIVILEGED USER OR THE POSTFIX OWNER.
#
#default_privs = nobody

# INTERNET HOST AND DOMAIN NAME
#
# The myhostname parameter specifies the Internet host name
# Mail system. By default, the fully qualified domain name is used
# from gethostname (). $ myhostname is used as the default for many
# other configuration parameters.
#
myhostname = outlook.mydomain.com.au
#myhostname = virtual.domain.tld

# The mydomain parameter specifies the local Internet domain name.
# By default, $ myhostname minus the first component is used.
# $ mydomain is used as the default for many other configurations
# parameter.
#
#mydomain = domain.tld

# SEND MESSAGES
#
# The myorigin parameter specifies the domain that was deployed locally
# mail seems to come from. By default, $ myhostname is appended.
# That's fine for small websites. If you operate a domain with several
# machines, you should (1) change this to $ mydomain and set up (2)
# a domain-wide alias database that aliass each user
# user@that.users.mailhost.
#
# To ensure consistency between sender and recipient addresses,
# myorigin also gives the appended default domain name
# to recipient addresses that do not have a @ domain part.
#
#myorigin = $ myhostname
#myorigin = $ mydomain

# RECEIVED FROM MAILS

# The parameter inet_interfaces specifies the network interface
# Addresses under which this mail system receives mail. By default,
# The software claims all active interfaces on the machine. The
The parameter # also controls the delivery of e-mails to users @[ip.address],
#
# See also the parameter proxy_interfaces for network addresses, which
# are forwarded to us through a proxy or network address translator.
#
# Note: You must stop / start Postfix if this parameter changes.
#
#inet_interfaces = all
#inet_interfaces = $ myhostname
#inet_interfaces = $ myhostname, localhost
inet_interfaces = localhost

# Enable IPv4 and IPv6, if supported
inet_protocols = all

# The proxy_interfaces parameter specifies the network interface
# Addresses under which this mail system receives mail via
# Proxy or network address translation unit. This setting will be expanded
# the address list specified with the parameter inet_interfaces.
#
# You must specify your proxy / NAT addresses if your system is a
# Back up MX host for other domains, otherwise mail delivery loops
# occurs when the primary MX host is down.
#
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4

# The parameter mydestination specifies the list of domains to which this applies
# machine considers itself the final destination for.
#
# These domains will be redirected to the deliverer specified with
# local_transport parameter setting. By default, this is UNIX
# Compatible delivery agent, which looks for all recipients in / etc / passwd
# and / etc / aliases or their equivalent.
#
# The default is $ myhostname + localhost. $ Mydomain. On a mail domain
# gateway you should also specify $ mydomain.
#
# Do not specify the names of the virtual domains - these are domains
# specified elsewhere (see VIRTUAL_README).
#
# Do not include the names of the domains where this computer is Backup MX
# Host for. Specify these names using the relay_domains for settings
# the smtp server, or use permit_mx_backup if you are lazy (see
# STANDARD_CONFIGURATION_README).
#
# The local computer is always the final destination for the addressed e-mail
# to user @[the.net.work.address] an interface that the mail system
# receives mail at (see parameter inet_interfaces).
#
# Specify a list of host or domain names, / file / name or type: table
# Pattern, separated by commas and / or spaces. A / file / name
# Pattern is replaced by its content; A type: table is reconciled when
# A name corresponds to a search key (the right side is ignored).
# Continue long lines by starting the next line with spaces.
#
# See also below, section "MAIL REJECTION FOR UNKNOWN LOCAL USERS".
#
mydestination = $ myhostname, localhost. $ mydomain, localhost
#mydestination = $ myhostname, localhost. $ mydomain, localhost, $ mydomain
#mydestination = $ myhostname, localhost. $ mydomain, localhost, $ mydomain,
# mail. $ mydomain, www. $ mydomain, ftp. $ mydomain

# MAIL REJECTION FOR UNKNOWN LOCAL USERS
#
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local in terms of respect
# to $ mydestination, $ inet_interfaces or $ proxy_interfaces.
#
# If this parameter is defined, the SMTP server rejects
# Mail for unknown local users. This parameter is defined by default.
#
# To disable local recipient scanning on the SMTP server, specify
# local_recipient_maps = (that is, empty).
#
# The default setting requires that you use the default postfix local
# Delivery for on-site delivery. You have to update this
# local_recipient_maps setting if:
#
# - You define $ mydestination domain recipients in files other than
# / etc / passwd, / etc / aliases or the $ virtual_alias_maps files.
For example, you define the $ mydestination domain recipient in
# the $ virtual_mailbox_maps files.
#
# - Redefine the local delivery agent in master.cf.
#
# - Define the "local_transport" setting in main.cf.
#
# - You are using "luser_relay", "mailbox_transport" or "fallback_transport"
# Function of the local Postfix delivery agent (see local (8)).
#
# Details are described in the file LOCAL_RECIPIENT_README.
#
# Warning: If the Postfix SMTP server is chrooted, you probably have
# to access the passwd file through the Proxymap service
# Overcome chroot restrictions. The alternative, a copy of
# The System Passwd file in Chroot Prison is simply not practical.
#
# The right side of the lookup tables is expediently ignored.
# Indicate a simple username on the left, a @ domain.tld
# Wildcard or specify a user@domain.tld address.
#
#local_recipient_maps = unix: passwd.byname $ alias_maps
#local_recipient_maps = proxy: unix: passwd.byname $ alias_maps
#local_recipient_maps =

# The unknown_local_recipient_reject_code specifies the SMTP server
# Response code if a recipient domain matches $ mydestination or
# $ {proxy, inet} _interfaces while $ local_recipient_maps is not empty
# and the recipient address or local part of the address was not found.
#
# The default is 550 (reject email), but launch is more secure
# with 450 (try again later) until you are sure yours
# local_recipient_maps settings are OK.
#
unknown_local_recipient_reject_code = 550

# TRUST AND RELAY CONTROL

# The mynetworks parameter specifies the list of "trusted" SMTP
# Clients that have more privileges than "strangers".
#
# In particular, "trusted" SMTP clients are allowed to forward emails
# by Postfix. See the parameter smtpd_recipient_restrictions
# in the postconf (5).
#
# You can manually set the list of "trusted" network addresses
# or let Postfix do this for you (this is the default).
#
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# Clients on the same IP subnet as the local computer.
# Under Linux, this only works properly with the specified interfaces
# with the command "ifconfig".
#
# Specify "mynetworks_style = class" if you want Postfix to "trust" SMTP
# Clients on the same IP class A / B / C networks as the local computer.
# Do not do this with a dial-up site - it would cause Postfix to "trust"
# the network of your entire provider. Specify an explicit instead
# mynetworks list by hand as described below.
#
# Specify "mynetworks_style = host" if you want Postfix to "trust".
# only the local machine.
#
#mynetworks_style = class
#mynetworks_style = subnet
#mynetworks_style = host

# Alternatively, you can manually specify the mynetworks list in
# In this case, Postfix ignores the setting of mynetworks_style.
#
# Specify an explicit list of network / netmask patterns
# mask specifies the number of bits in the network part of a host
# Address.
#
# You can also specify the absolute pathname of a pattern file instead
# the collection of patterns here. Specify type: table for table-based searches
# (the value in the table on the right is not used).
#
#mynetworks = 168.100.189.0/28, 127.0.0.0/8
#mynetworks = $ config_directory / mynetworks
#mynetworks = hash: / etc / postfix / network_table

# The relay_domains parameter limits what targets this system should achieve
Forward # mail to. See the description of smtpd_recipient_restrictions in
# postconf (5) for detailed information.
#
# By default, Postfix forwards emails
# - from "trusted" clients (IP address matches $ mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $ relay_domains or
# Subdomains thereof, except addresses with sender specified routing.
# The default value for relay_domains is $ mydestination.
#
# In addition, the Postfix SMTP server accepts emails by default
# that Postfix is ​​the final destination for:
# - targets that match $ inet_interfaces or $ proxy_interfaces,
# - Goals that match $ mydestination
# - Targets that match $ virtual_alias_domains
# - Targets that match $ virtual_mailbox_domains.
# These goals do not have to be listed in $ relay_domains.
#
# Specify a list of hosts or domains, / file / name patterns, or type: name
# Lookup tables, separated by commas and / or spaces. Continue
# long lines by starting the next line with spaces. A file name
# is replaced by its content; A type: name table is reconciled if a
The (parent) domain is displayed as a search key.
#
# NOTE: Postfix does not automatically redirect emails to domains that
# List this system as primary or backup MX host. See the
# permit_mx_backup Description of the restriction in postconf (5).
#
#relay_domains = $ mydest

# INTERNET OR INTRANET

# The relayhost parameter specifies the default host to which e-mail should be sent
# if no entry was found in the optional transport table (5). When
If no relay host is specified, the emails are forwarded directly to the destination.
#
# Enter the organization domain name on an intranet. If your
# Internal DNS does not use MX records. Enter the name of the intranet
# instead gateway host.
#
# For SMTP, specify a domain, host, host: [host]:Port,
# [address] or [address]:Port; form [host] turns off MX lookups.
#
# If you are connected via UUCP, also read the parameter default_transport.
#
#relayhost = $ mydomain
#relayhost = [gateway.my.domain]
#relayhost = [mailserver.isp.tld]
#relayhost = uucphost
#relayhost = [an.ip.add.ress]

# REJUDE UNKNOWN RELAY USERS
#
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $ relay_domains.
#
# If this parameter is defined, the SMTP server rejects
# Mail for unknown relay users. This feature is disabled by default.
#
# The right side of the lookup tables is expediently ignored.
# Enter or specify an @ domain.tld placeholder on the left side
# a user@domain.tld address.
#
#relay_recipient_maps = hash: / etc / postfix / relay_recipients

# INPUT RATE CONTROL
#
# The configuration parameter in_flow_delay implements the e-mail input
# Flow control. This feature is enabled by default
# needs to be further developed (is disabled due to changes in SCO UNIX)
# on a SCO error).
#
# A postfix process stops before $ in_flow_delay seconds
# Accept a new message if the message arrival rate exceeds the allowed value
# Message delivery rate. With the standard 100 SMTP server process
# limit, this limits the inbox to 100 messages per second more
# as the number of messages delivered per second.
#
# Enter 0 to disable the feature. Valid delays are 0..10.
#
#in_flow_delay = 1s

# WRITE ADDRESS
#
# The document ADDRESS_REWRITING_README contains information about
# Address Masquerading or other forms of address rewriting, including
# Username-> firstname.lastname mapping.

# ADDRESS TRANSFER (VIRTUAL DOMAIN)
#
# The document VIRTUAL_README contains information about the many forms
Number of domain hosting supported by Postfix.

# "USER HAS MOVED" BOUNCE NEWS
#
# See the discussion in the ADDRESS_REWRITING_README document.

# TRANSPORT CARD
#
# See the discussion in the ADDRESS_REWRITING_README document.

# ALIAS DATABASE
#
#
#alias_maps = dbm: / etc / aliases
alias_maps = hash: / etc / alias
#alias_maps = hash: / etc / aliases, nis: mail.aliases
#alias_maps = netinfo: / aliases

# The alias_database parameter specifies the appropriate alias databases
# are created with "newaliases" or "sendmail -bi". This is a separate one
# Configuration parameters, since alias_maps (see above) can specify
# Tables that are not necessarily all controlled by Postfix.
#
#alias_database = dbm: / etc / aliases
#alias_database = dbm: / etc / mail / aliases
alias_database = hash: / etc / aliases
#alias_database = hash: / etc / aliases, hash: / opt / majordomo / aliases

# ADDRESS EXTENSIONS (eg user + foo)
#
#
#recipient_delimiter = +

# DELIVERY TO MAILBOX
#
# ALIAS MAIL FOR ROOT TRANSDS TO A REAL USER.
#
#mailbox_command = / some / where / procmail
#mailbox_command = / some / where / procmail -a "$ EXTENSION"

# The mailbox_transport specifies the optional transport in master.cf
# for use after processing aliases and .forward files. This parameter
# takes precedence over mailbox_command, fallback_transport and
# luser_relay parameters.
#
# Specify a form transport string: nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
#: The next part is optional. Further details can be found in sample transport
# Configuration file.
#
# NOTE: If you use this feature for accounts that are not in the UNIX password
# File, then you need to update the "local_recipient_maps" setting to
# The file main.cf, otherwise the SMTP server rejects emails for
# Non-UNIX accounts with "User in local recipient table unknown".
#
# Cyrus IMAP on LMTP. Specify `` lmtpunix cmd = 'lmtpd'
# listen = "/ var / imap / socket / lmtp" prefork = 0 & # 39; & # 39; in the cyrus.conf.
#mailbox_transport = lmtp: unix: / var / lib / imap / socket / lmtp

# If you use the cyrus-imapd IMAP server, send local emails to the IMAP
# Server with LMTP (Local Mail Transport Protocol), this is preferred
# deliver over the older Cyrus program by setting the
# mailbox_transport as follows:
#
# mailbox_transport = lmtp: unix: / var / lib / imap / socket / lmtp
#
# The efficiency of LMTP deployment for cyrus-imapd can be improved
# these settings.
#
# local_destination_recipient_limit = 300
# local_destination_concurrency_limit = 5
#
#
# Cyrus IMAP from the command line. Comment out the "cyrus ... pipe" and out
# subsequent line in master.cf.
#mailbox_transport = cyrus

# The fallback_transport indicates the optional transport in master.cf
# for use by recipients who are not in the passwd UNIX database.
# This parameter takes precedence over the luser_relay parameter.
#
# Specify a form transport string: nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
#: The next part is optional. Further details can be found in sample transport
# Configuration file.
#
# NOTE: If you use this feature for accounts that are not in the UNIX password
# File, then you need to update the "local_recipient_maps" setting to
# The file main.cf, otherwise the SMTP server rejects emails for
# Non-UNIX accounts with "User in local recipient table unknown".
#
#fallback_transport = lmtp: unix: / var / lib / imap / socket / lmtp
#fallback_transport =

# The parameter luser_relay specifies an optional destination address
# for unknown recipients. Default mail for unknown @ $ mydestination,
# unknown @[$inet_interfaces] or unknown @[$proxy_interfaces] returned
# as undeliverable.
#
# The following extensions are made for luser_relay: $ user (recipient
# username), $ shell (recipient shell), $ home (recipient home directory),
# $ recipient (full recipient address), $ extension (recipient address)
# extension), $ domain (recipient domain), $ local (entire recipient)
# localpart), $ recipient_delimiter. Enter $ {name? Value} or on
# $ {name: value} to expand the value only if $ name exists (does not exist).
#
# luser_relay only works for the local Postfix default delivery agent.
#
# NOTE: If you use this feature for accounts that are not in the UNIX password
# File, then you have to specify "local_recipient_maps =" (ie empty) in
# The file main.cf, otherwise the SMTP server rejects emails for
# Non-UNIX accounts with "User in local recipient table unknown".
#
#luser_relay = $user@other.host
#luser_relay = $local@other.host
#luser_relay = admin + $ local

# JUNK MAIL CONTROLS
#
# The controls listed here are just a very small subset. The file
# SMTPD_ACCESS_README provides an overview.

# The parameter header_checks specifies an optional table with patterns
# that every logical message header is matched, including
# Headers that span multiple physical lines.
#
# By default, these patterns also apply to MIME headers and to the
# Header of attached messages. With older Postfix versions, MIME and
# Attached message headers were treated as message body.
#
# For details, see "man header_checks".
#
#header_checks = regular expression: / etc / postfix / header_checks

# FAST ETRN SERVICE
#
# Postfix manages target-specific log files with information about
# Moved e-mails to allow e-mails to be quickly deleted using SMTP
# Command "ETRN domain.tld" or by executing "sendmail -qRdomain.tld".
# For a detailed description, see the ETRN_README document.
#
# The parameter fast_flush_domains controls the goals
# Claim to this service. By default, these are all domains that
# This server is ready to forward emails.
#
#fast_flush_domains = $ relay_domains

# DISPLAY SOFTWARE VERSION OR NOT
#
# The smtpd_banner parameter specifies the text following the 220
# Code in the welcome banner of the SMTP server. Some people like to see it
# the announced mail version. By default, Postfix does not display a version.
#
# You MUST specify $ myhostname at the beginning of the text. That is a
# RFC request. Postfix itself does not care.
#
#smtpd_banner = $ myhostname ESMTP $ mail_name
#smtpd_banner = $ myhostname ESMTP $ mail_name ($ mail_version)

# PARALLEL DELIVERY TO THE SAME TARGET
#
# How many parallel deliveries to the same user or domain? With local
# Delivery, it does not make sense to carry out a mass parallel delivery
# to the same user as the mailbox updates must be done sequentially,
# and expensive pipelines in .forward files can lead to disasters, though
# too many are executed at the same time. For SMTP deliveries 10
# simultaneous connections to the same domain might be enough to
# Raise eyebrows.
#
# Every message delivery transport has its XXX_target_limit limit
# Parameters. The default value is $ default_destination_concurrency_limit for
# most delivery transports. For the local deliverer, the default is 2.

#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 20

# DEBUGGING CHECK
#
# The debug_peer_level parameter specifies the increment in detail
# Logging level if an SMTP client or server has the host name or address
# matches a pattern in the debug_peer_list parameter.
#
debug_peer_level = 2

# The debug_peer_list parameter specifies an optional list of domains
# or network pattern, / file / name pattern or type: name tables. When
# The name or address of an SMTP client or server is a pattern.
# Increase verbose logging level by the specified amount
# debug_peer_level parameter.
#
#debug_peer_list = 127.0.0.1
#debug_peer_list = some.domain

# The debugger_command command specifies the external command that is being executed
# When running a Postfix daemon program with the -D option.
#
# Use "command .. & sleep 5" to allow the debugger to connect first
# The process is progressing. If you use an X-based debugger, you should definitely do this
# Set up your XAUTHORITY environment variable before starting Postfix.
#
debugger_command =
PATH = / bin: / usr / bin: / usr / local / bin: / usr / X11R6 / bin
ddd $ daemon_directory / $ process_name $ process_id & sleep 5

# If you can not use X, use this option to capture the call log if: a
# Daemon crashes. The result is in a file in the configuration
# Directory and is named after the process name and the process ID.
#
# debugger_command =
# PATH = / bin: / usr / bin: / usr / local / bin; export PATH; (echo cont;
# echo where) | gdb $ daemon_directory / $ process_name $ process_id 2> & 1
#> $ config_directory / $ process_name. $ process_id.log & sleep 5
#
# Another way is to run gdb under a separate screen session.
# To attach to the screen session, run su root and "screen -r"
# " from where  clearly matches one of the detached ones
# Sessions (from "screen -list").
#
# debugger_command =
# PATH = / bin: / usr / bin: / sbin: / usr / sbin; export PATH; screen
# -dmS $ process_name gdb $ daemon_directory / $ process_name
# $ process_id & sleep 1

# INSTALLATION TIME CONFIGURATION INFORMATION
#
# The following parameters are used when installing a new Postfix version.
#
# sendmail_path: The full pathname of the postfix sendmail command.
# This is the Sendmail-compatible mailing interface.
#
sendmail_path = /usr/sbin/sendmail.postfix

# newaliases_path: The full pathname of the postfix newaliases command.
# This is the Sendmail-compatible command to create alias databases.
#
newaliases_path = /usr/bin/newaliases.postfix

# mailq_path: The full pathname of the postfix mailq command. These
# is the Sendmail-compatible command for listing e-mail queues.
#
mailq_path = /usr/bin/mailq.postfix

# setgid_group: The group for sending e-mails and managing queues
# Commands. This must be a group name with a numeric group ID
# will not be shared with other accounts, not even the Postfix account.
#
setgid_group = postdrop

# html_directory: The location of the Postfix HTML documentation.
#
html_directory = no

# manpage_directory: The location of the online manual pages of Postfix.
#
manpage_directory = / usr / share / man

# sample_directory: The location of the sample Postfix configuration files.
# This parameter is deprecated from Postfix 2.1.
#
sample_directory = /usr/share/doc/postfix-2.10.1/samples

# readme_directory: The location of the Postfix README files.
#
readme_directory = /usr/share/doc/postfix-2.10.1/README_FILES

Many Thanks!

Networking – Jupyter notebook does not open – General solutions do not work

When I try to open my Jupyter notebook, the following error message appears again and again.

Can not bind to localhost if 127.0.0.1 is used as the default IP
[Errno 49] The requested address can not be assigned

After the online search, the most common solution is to start the notebook with the following command:

jupyter notebook –ip = 127.0.0.1

However, if I try this, an error message will still be displayed

[Errno 49] The requested address can not be assigned

I think it's a kind of network configuration issue, but I'm not sure where to start looking for it. I checked mine etc / host File and it looks like it was never manipulated. Again, I'm not sure where to look otherwise, so any help is appreciated.

I have a MacBook Pro 2011 running 10.13.3.

Networking – Problems with RD, RT-Import and RT-Export in MPLS VPN and BGP

I am learning MPLS VPN with MP-BGP and I have difficulty finding the RD value and the RT import and export values.

After what I already understood, RD (distance stopper) Identifies the VRFs from a network that makes up the same virtual network and changes the routing information between them. Import RT indicates which VRFs in a network are known to the local VRF and Export RT is sent to identify the information from the local VRF.
To decide in which VRF the router will be installed, if a package will come into the PE, if the RT export has the package and the RT import has our VRF the sameit adds the route to the VRF, otherwise it clears it.

I do not know if everything I've written is right. But I do not understand it right when I find something like that.

Let's talk about the locations PE1, PE2, PE3 and PEC (Central PE).

Which sites does PE3 know?

Is it true that PE3 knows no other network? Because when it sends information to PEC and then PEC compares the RT export of PE3 and its RT import, they do not match.

Which websites does PEC know?

I think PEC knows PE1 and PE2 because the RT export of PE1 and PE2 matches the RT import of PEC.

Am I right? Please, I need help to understand it.

phpSocial – social networking platform

The administrator has submitted a new resource:

phpSocial – social networking platform – phpSocial – social networking platform

See Appendix 13390

In case you do not want to get any further

phpSocial is a social networking platform similar to Facebook that allows users to interact with each other by chatting live, sending messages, making comments, sharing …

phpSocial – social networking platform

Networking – Can two connected sockets listen to each other?

I am dealing with the situation where both the client and the server must respond to different events of the user and have to notify each other about these events. However, with socket communication, only one (the server) is calling socket.listen () it can not initiate communication, but only reply on messages from the client. What if the server has to inform the client about a specific event? The only solution is to open two outlets on two different ports so they can both simultaneously Listen()? Thanks in advance.

Networking – Graphical Ettercap Error (Ubuntu 19.04)

I USE THIS NETWORK WITH MY OWN EQUIPMENT EASILY FOR THE TESTING. If this is still not allowed, delete this post.

I only post it here because this bug is likely to occur only on Ubuntu and Ettercap is more compatible with Kali Linux. It's the fastest responding forum I've ever used.

When I launch Ettercap, this message appears on the console and it's probably why Ettercap is not working.

For the SSL decomposition, a valid script is & # 39; redir_command_on & # 39; required in the file etter.conf

Ettercap may not work properly. / proc / sys / net / ipv6 / conf / all / use_tempaddr is not set to 0.

Ettercap may not work properly. / proc / sys / net / ipv6 / conf / wlo1 / use_tempaddr is not set to 0.

Authorizations filed on EUID 65534 EGID 65534 …

The other articles I found are very confusing, old or use the CL version of Ettercap.

Any help on how to fix it?

Networking – Simulates a connection between a VM network card

There are network devices that can be placed in the path of a network, detect network activity on the IN-Nic card, and route packets to the OUT-Nic card. Suppose, "without changing it". Do you know how to achieve a similar setup using one of the most important virtualization tools available (eg VirtualBox)?
There are two VMs communicating with each other and another between them to capture network activity and send the packets to their intended destination.