Connections refused after editing master.cf file

Hi:
I just got done editing (successfully, I thought) the master.cf file using TextEdit in order to add Port 587 to the list of smtp ports available for users to send.
I tried both ways suggested by various posters, including uncommenting the submission line and adding a new line with 587 as the service.
No luck. Great....
I returned a copy of the original master.cf file to the /etc/postfix folder (and set the permissions to allow the owner system to read and write, group wheel to read only and others to read only) and restarted, now no user can get or send mail. All connections are refused, both via Mail.app and telnet x.x.x.x 25 (or 587, or...).
The firewall is fine and not the issue. The failure occurs even if the firewall is down.
What am I missing?
How can I edit the file properly. I simply deleted one character at the start of a line and saved as plain text.
Do I just have to archive and install the OS X Server software? And if so, will I lose what's in the users' mailboxes?
Need lotsa help..and fast.
Thanks,
mm

And now it works, 20 minutes later. Suddenly. For no apparent reason. Who knows why. I left the mail service off for a few minutes, started up, and off we go, using the master.cf file with the submission line uncommented.
So now mail goes out over either ports 25 or 587. Hooray.
Do I score points?
mm

Similar Messages

I am trying to install software for iTwin Connect, but after downloading the dmg file and launching the program, I receive a message saying the file can't open and to check my internet connection. Any ideas?

I am trying to install software for iTwin Connect, but after downloading the dmg file and launching the program, I receive a message saying the file can't open and to check my internet connection. Any ideas?

Many Thanks, Kurt.
I knew I'd seen the solution you've provided somewhere - either in MacWorld or MacFormat - but couldn't remember the Gatekeeper bit!
I shall save it somewhere VERY safe now in case this happens again …
You have made an old man very happy and saved me from worrying that senile decay had suddenly set in. (I was 70 last week so you might understand the situation from that.)
Best wishes
OllyanDinah

PS CS3 crashes at "Save as" after editing Hasselblad DNG file

Hi,
Soliciting some net wisdom on this one.
Went mad an got myself a H2D-39. Am now experiencing intermittent crashes when saving files from Photoshop.
I import the H2D files as DNG using the latest version of FlexColor 4.8.6, then select image in Bridge, do raw conversion in Bridge and send to PS for final edit. When I try to save the file (Save As), PS crashes roughly every second time before the File menu opens, crash info:
Problem signature:Problem Event Name: APPCRASH
Application Name: Photoshop.exe
Application Version: 10.0.1.0
Application Timestamp: 470fd6cb
Fault Module Name: Photoshop.exe
Fault Module Version: 10.0.1.0
Fault Module Timestamp: 470fd6cb
Exception Code: c00000fd
Exception Offset: 00b37f90
OS Version: 6.0.6001.2.1.0.256.6
Locale ID: 1035
Additional Information 1: 5e09
Additional Information 2: d7242649f4a55a851fcce331718e8c37
Additional Information 3: 373d
Additional Information 4: 7d7265066cfe4fecec0e1f61b91a462e
Running Vista SP1, all latest Updates, 4GB machine, (still) plenty of disk. No problems when working on smaller files (from my 10Mpix camera). Tried as best I can all means of saving and optimizing memory use as suggested in KB etc. Any suggestions?
Thanks, Håkan

I think my problem may be solved. Yesterday I installed the latest driver for my elderly Epson 3200 scanner, and now PS seems to be working again. I just read another thread about PS3 crashes where Chris Cox said "(buggy drivers are why we no longer install the TWAIN plugin by default -- too many bad drivers, and no way for Photoshop to know until they crash)".
Replacing the TWAIN that came with the old scanner driver which may have not been compatible with Leopard may have been the solution...at least I hope so.

CS3 file will not open in CS3 after editing in CS6?!?

Pardon the exclamations but we're creative folks not techies. After editing a CS3 file in CS6 we are unable to open it in CS3. Looks like CS6 will only save back to CS4? So once edited in CS6 then I can no longer use CS3 to work with the files? Can anybody confirm this for me? We also tried to export to IDML but CS3 would not read it.

When you open an older version of InDesign file within a newer version and edit them, the older version of file is first converted using some required plugins of the newer version of InDesign and then a consolidated new file is generated including the required plugins. Now, if you try to open this newer version of file back in an older version, the older version of InDesign looks for the required plugins used to edit the file and fails because InDesign older version did not use those plugins to create your file.
Please let me know if that explanation helped understanding why this behavior occurs.
-Shushobhan

Connection refused--while executing (HttpConnection) Connector.open(url);

Hi,
i'm using netbeans mobility 5.0
as i was new to this mobile programming i'm getting the output as "Connection Refused"
plz plz plz plz....... help me out from this problem
here is my code..
code:_
import javax.microedition.midlet.*;
import javax.microedition.lcdui.*;
import javax.microedition.io.*;
import java.io.*;
public class FileViewer extends MIDlet implements CommandListener
private Display display; // Reference to Display object
private TextBox tbViewer; // View file contents in a textbox
private Command cmView; // Command to view file
private Command cmExit; // Command to exit
private String url = "http://www.corej2me.com/midpbook_v1e1/scratch/fileViewer.hlp";
public FileViewer()
display = Display.getDisplay(this);
// Define commands
cmView = new Command("View", Command.SCREEN, 2);
cmExit = new Command("Exit", Command.EXIT, 1);
tbViewer = new TextBox("Viewer", "", 250, TextField.ANY);
tbViewer.addCommand(cmView);
tbViewer.addCommand(cmExit);
tbViewer.setCommandListener(this);
public void startApp()
display.setCurrent(tbViewer);
private void viewFile() throws IOException
HttpConnection http = null;
InputStream iStrm = null;
try
http = (HttpConnection) Connector.open(url);
// Client Request
// 1) Send request method
http.setRequestMethod(HttpConnection.GET);
// 2) Send header information (this header is optional)
http.setRequestProperty("User-Agent", "Profile/MIDP-1.0 Configuration/CLDC-1.0");
// 3) Send body/data - No data for this request
// Server Response
// 1) Get status Line
System.out.println("Msg: " + http.getResponseMessage());
System.out.println("Code: " + http.getResponseCode());
// 2) Get header information
if (http.getResponseCode() == HttpConnection.HTTP_OK)
// 3) Get data (show the file contents)
iStrm = http.openInputStream();
int length = (int) http.getLength();
if (length > 0)
byte serverData[] = new byte[length];
iStrm.read(serverData);
tbViewer.setString(new String(serverData));
finally
if (iStrm != null)
iStrm.close();
if (http != null)
http.close();
public void pauseApp()
public void destroyApp(boolean unconditional)
public void commandAction(Command c, Displayable s)
if (c == cmView)
try
viewFile();
catch (Exception e)
System.out.println(e.toString());
else if (c == cmExit)
destroyApp(false);
notifyDestroyed();
output*
build.xml(debug)*
some....
Application descriptor does not declare any MIDlet. Direct execution is not allowed.
Generated "C:\Documents and Settings\Lakshmi Narayan J\jlnexample\dist\jlnexample.jar" is 2655 bytes.
post-jar:
debug:
C:\Documents and Settings\Lakshmi Narayan J\jlnexample\src\.timestamp
Starting emulator in debug server mode on port 1469
com.sun.kvem.midletsuite.InvalidJadException: Reason = 22
The manifest or the application descriptor MUST contain the attribute: MIDlet-1
nbdebug:
KdpDebugTask connecting to debugger 1 ..
KdpDebugTask connecting to debugger 2 ..
KdpDebugTask connecting to debugger 3 ..
KdpDebugTask connecting to debugger 4 ..
KdpDebugTask connecting to debugger 5 ..
Connecting JPDA Debugger to emulator timed out after 5 attempts and 31 seconds.
C:\Documents and Settings\Lakshmi Narayan J\jlnexample\nbproject\build-impl.xml:306: The following error occurred while executing this line:
C:\Documents and Settings\Lakshmi Narayan J\jlnexample\nbproject\build-impl.xml:311: Connecting JPDA Debugger to emulator timed out after 5 attempts and 31 seconds.
BUILD FAILED (total time: 43 seconds)
Debugger console:
Attaching to localhost:1469
Connection refused.
Edited by: LAKSHMI_NARAYAN_J on Jun 23, 2008 9:54 AM

It's called potential deadlock. The emulator blocks your app 'cause any connection and commandAction needs its own thread. So I suggest use a new thread with this http connection then your program will be run successful.

OVMAPI_6000E Internal Error: Connection refused Connection refused - OVM

Hi,
Test environment, as per this doc
http://www.oracle.com/technetwork/server-storage/vm/template-1482544.html
Running the above OVMs on virtual box version 4.2.10
OVM is version 3.1.1.365
I setup my environment and was ready to import VM templates. Following a reboot of the server I can no longer login to the Manager.
Error is: Unexpected error during login (com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_6000E Internal Error: Connection refused Connection refused
After some investigation in the App logs I found this error:
ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
(------------- lsnrctl service shows this ----------)
LSNRCTL for Linux: Version 11.2.0.2.0 - Production on 20-APR-2013 22:58:31
Copyright (c) 1991, 2011, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC_FOR_XE)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
The command completed successfully
(-----------) - This is just a test environment, but I would really appreciate if someone could tell me why this error is occurring and how I can fix it, I've tried restarting services, still no joy. This issue seems to occur after I setup the server pool \ Storage resources, etc
Thanks for all your help!

You need to learn how to start an oracle database. The database does not start automatically if you're using the database that comes with the VM Manager.
ps -ef | grep pmon
will tell you if the database is running and mounted.
ps -ef | grep tns
will tell you if the database listener is running
OR
You could use 3.2.2 and use the MYSQL database that come with the VM Manager
OR
you could load the enterprise version of Oracle Database and use cluster services to automatically start and stop the database. You get a single use license with the VM Manger that allows you either use standard of enterprise edition of the Oracle Database.

Java.lang.Exception: IOException is sending Request :: Connection refused

Hi, everybody.
Oracle Database Control 10g displays on the home page the following message
-- java.lang.Exception: IOException is sending Request :: Connection refused
after killing some database lock that is impeding the users to successfully carry out their daily activities.
What could be the reason ?

agent come with db was not working on that time

Decision Service calls failing with connection refused

Hi All,
Breifing of the bpel process - Async bpel process XX_BPEL_ASYNC_002 calls decision services and a sync bpel process XX_BPEL_SYNC_001.
We have moved to cluster 10.1.3.5.0 from 10.1.3.3.0 and the deployement of the bpel process and the decision service done on two nodes i.e., node51 and node55.
But the bpel process is able to call the decision service only when the node 51 is UP and running, but if node 51 is down and node 55 is up and running it is failing with connection refused error. It is also working when 55 is DOWN and 051 is UP.
the exact error is:
exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Connection refused.
We are using file based repository.
It is failing when it tries to call particular url:
http://loadbalancerurl:7777/orabpel/domain001/XX_BPEL_ASYNC_002/1.0/decisionservices.decs
Can anyone please help me or advice me for finding some solution.
Thanks
Sreejit

Hi Fatsah,
It has been a while since we resolved this problem. But these were the basic steps that we had taken.
The receiver was configured a File adatpter with FTP:
Port: 10021
Connection security : FTPS (FTP using SSL/TLS) for Control and Data Connection
Command Order: AUTH TLS,USER,PASS,PBSZ,PROT
Problem: The message was blocked in our firewall.
FTPS in this case used 10021 as the control port and the firewall allowed to pass the control request.
Once the connection was accepted at the control level, it generated a random port number to pass data on the channel.
This random port number was blocked in the firewall.
We monitored the data port numbers generated at firewall. Then we configured the firewall to open any port number between the specific IP addresses of the sender and the receiver. That resolved the problem.
Hope this helps!
Please give points if this is helpful.
Thank you.
Dharmasiri Amith

Connection refused in Mission control

Hi !
I created a simple application just for demo and I start it with
java prim.Prim 100000000 -XX:+UnlockCommercialFeatures -XX:+FlightRecorder
But I can't connect, when doing 'Start jmx-console' I get connection refused after a while.
The same problem when starting the application in NetBeans .

At least that makes sense (JConsole not working either). Okay, so something is messed up regarding local attach on your machine. Let's try not using local attach. What happens if you try adding the following to the command line, and then set up a connection in JMC manually (click the "new custom connection" icon in the JVM Browser)?
-Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=7091 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false

Lion Server postfix mail not being delivered to mailboxes. "SMTP restriction `reject_invalid_helo_hostname' after `permit' is ignored" and "connect to private/policy: Connection refused" errors.

All, Im stumped. In fact I have been on the phone with Apple Support and this has been escalated to the top engineers, as I think its got them too..
Anyway, here is my problem..
I'm running an Mac Mini with OS X 10.7.4 Server. I have had mail running on it for 2 months or so, without any issues. The mail was actually migrated from 10.6 in March, and It actually went smoothly. I have 3 domains which all recieve mail and they all work (or did up until 2 weeks ago)..
So the story is this.. I can send mail from my domains, without issue. imap and dovecot must be working.. cause all the stored mail, can be read with the mail IMAP client.. I can even transfer mail messages from one mailbox to another with Mail client. Sending mail is a breeze, it still works and the recipients still recieve their mail. But I noticed I wasnt getting any mail at all from those mailboxes... no mail, no spam, nothing.. which is unusal. I fired up Server admin and checked out the SMTP log, and this is what it showed for every email recieved: (xxxxxx is just me hiding sensitive info)
Jul 21 14:25:20 xxxxxxxx postfix/postscreen[65857]: CONNECT from [17.158.233.225]:41909
Jul 21 14:25:26 xxxxxxxx postfix/postscreen[65857]: PASS OLD [17.158.233.225]:41909
Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: connect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: warning: restriction `reject_invalid_helo_hostname' after `permit' is ignored
Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: NOQUEUE: reject: RCPT from nk11p03mm-asmtp994.mac.com[17.158.233.225]: 451 4.3.5 Server configuration problem; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<nk11p99mm-asmtpout004.mac.com>
Jul 21 14:25:28 azathoth postfix/smtpd[65858]: disconnect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
Ok, now what is odd, is these rejected messages are not even appearing in the mail queue in Server Admin. I have no idea why there are not being delivered
Ive checked my postfix main.cf file and master.cf files they both look ok.. Ive even replaced them with the main.cf.defualt.10.7 and master.cf.default.10.7 files and to no avail... same problem..
So in summary
I can send mail out
IMAP is working on the client end (thus dovecot is) exsisting stored emails can be accessed, read, moved unread etc..
mail is coming into the sever, but its being rejected. there is NO rejection email sent back to the sender.
mail is recieved by postfix, but cyrus isnt doing anything with it.. I have no idea where it goes...
Could anyone shed light on this...
my main.cf file:
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
# The general format of each line is: parameter = value. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
# POSTFIX STILL WORKS AFTER EVERY CHANGE.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
# soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /private/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 (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = _postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
azathoth:postfix root#
azathoth:postfix root# less main.cf
azathoth:postfix root# more main.cf
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
# The general format of each line is: parameter = value. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
# POSTFIX STILL WORKS AFTER EVERY CHANGE.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
# soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /private/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 (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = _postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
# Note: you need to stop/start Postfix when this parameter changes.
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4
# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups 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 include $mydomain.
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see VIRTUAL_README).
# Do not specify the names of domains that this machine is backup MX
# host for. Specify those names via the relay_domains settings for
# the SMTP server, or use permit_mx_backup if you are lazy (see
# STANDARD_CONFIGURATION_README).
# The local machine is always the final destination for mail addressed
# to user@[the.net.work.address] of an interface that the mail system
# receives mail on (see the inet_interfaces parameter).
# Specify a list of host or domain names, /file/name or type:table
# patterns, separated by commas and/or whitespace. A /file/name
# pattern is replaced by its contents; a type:table is matched when
# a name matches a lookup key (the right-hand side is ignored).
# Continue long lines by starting the next line with whitespace.
# See also below, section "REJECTING MAIL 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
# REJECTING MAIL FOR UNKNOWN LOCAL USERS
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination, $inet_interfaces or $proxy_interfaces.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown local users. This parameter is defined by default.
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery. You need to update the
# 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 $mydestination domain recipients in
#   the $virtual_mailbox_maps files.
# - You redefine the local delivery agent in master.cf.
# - You redefine the "local_transport" setting in main.cf.
# - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
#   feature of the Postfix local delivery agent (see local(8)).
# Details are described in the LOCAL_RECIPIENT_README file.
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify a bare username, an @domain.tld
# wild-card, or specify a [email protected] 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 when a recipient domain matches $mydestination or
# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
# and the recipient address or address local-part is not found.
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# 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 relay mail
# through Postfix. See the smtpd_recipient_restrictions parameter
# in postconf(5).
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this does works correctly only with interfaces specified
# with the "ifconfig" command.
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network. Instead, specify an explicit
# mynetworks list by hand, as described below.
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
#mynetworks_style = class
#mynetworks_style = subnet
#mynetworks_style = host
# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
# Specify an explicit list of network/netmask patterns, where the
# 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
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side 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 restricts what destinations this system will
# relay mail to. See the smtpd_recipient_restrictions description in
# postconf(5) for detailed information.
# By default, Postfix relays mail
# - 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 relay_domains value is $mydestination.
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces or $proxy_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need 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 whitespace. Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction description in postconf(5).
#relay_domains = $mydestination
# INTERNET OR INTRANET
# The relayhost parameter specifies the default host to send mail to
# when no entry is matched in the optional transport(5) table. When
# no relayhost is given, mail is routed directly to the destination.
# On an intranet, specify the organizational domain name. If your
# internal DNS uses no MX records, specify the name of the intranet
# gateway host instead.
# In the case of SMTP, specify a domain, host, host:port, [host]:port,
# [address] or [address]:port; the form [host] turns off MX lookups.
# If you're connected via UUCP, see also the default_transport parameter.
#relayhost = $mydomain
#relayhost = [gateway.my.domain]
#relayhost = [mailserver.isp.tld]
#relayhost = uucphost
#relayhost = [an.ip.add.ress]
# REJECTING 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, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a [email protected] address.
#relay_recipient_maps = hash:/etc/postfix/relay_recipients
# INPUT RATE CONTROL
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 100 SMTP server process
# limit, this limits the mail inflow to 100 messages a second more
# than the number of messages delivered per second.
# Specify 0 to disable the feature. Valid delays are 0..10.
#in_flow_delay = 1s
# ADDRESS REWRITING
# The ADDRESS_REWRITING_README document gives information about
# address masquerading or other forms of address rewriting including
# username->Firstname.Lastname mapping.
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
# The VIRTUAL_README document gives information about the many forms
# of domain hosting that Postfix supports.
# "USER HAS MOVED" BOUNCE MESSAGES
# See the discussion in the ADDRESS_REWRITING_README document.
# TRANSPORT MAP
# See the discussion in the ADDRESS_REWRITING_README document.
# ALIAS DATABASE
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
# It will take a minute or so before changes become visible. Use
# "postfix reload" to eliminate the delay.
#alias_maps = dbm:/etc/aliases
#alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases
# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi". This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control 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 (e.g., user+foo)
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5

Ok 1st one. The warning restriction message relates to this line in main.cf:
smtpd_helo_restrictions = permit_sasl_authenticated permit_mynetworks check_helo_access hash:/etc/postfix/helo_access reject_non_fqdn_hostname reject_invalid_hostname permit reject_invalid_helo_hostname
The last reject occurs after the single word "permit" and is ignored.
However, that's not the problem.
I'm not exactly sure what's happening, but this might be a clue.
It would appear that either postfix is not being able to create the socket for private/policy or it's somehow created with the wrong permissions. You might need to ramp up the debug level to get a better idea.
You could check if it's being created by "netstat -a | grep private/policy" in terminal.
My guess is that it's not being created because there is no setup statement in your master.cf file, but I don't understand why postfix would be looking for it if it isn't set up. Private/policy I think relates to grey listing. Maybe gives you a hint.

How to sync two excel files, the content is the same in both files after edit.

I have two excel files, which are data and edit by multi users, how can I sync the master files to the copy files after edit?
Is this operation required VBA? marco?

Hi,
Your request could be done via VBA code. Here are two ideas.
One:
Syncing the data from master file to the copy file without opening copy file. Sample code
Private Sub Worksheet_Change(ByVal Target As Range)
If Target.Count > 1 Then Exit Sub
Dim cnn As Object, SQL$, s$
Select Case True
Case Target.Value = ""
s = "null"
Case IsDate(Target.Value)
s = "#" & Target.Value & "#"
Case IsNumeric(Target.Value)
s = Target.Value
Case Else
s = "'" & Target.Value & "'"
End Select
Set cnn = CreateObject("ADODB.Connection")
cnn.Open "provider=microsoft.jet.oledb.4.0;extended properties='excel 8.0;hdr=no';data source=" & ThisWorkbook.Path & "\test folder\Book2.xls"
SQL = "update [Sheet1$" & Target.Address(0, 0) & ":" & Target.Address(0, 0) & "] set f1=" & s
cnn.Execute (SQL)
cnn.Close
Set cnn = Nothing
End Sub
Two:
Saving the master file as copy file before closing. Reference:
https://msdn.microsoft.com/en-us/library/office/ff194765.aspx?f=255&MSPPError=-2147217396
If you have any further question about coding, I recommend you post the question to the MSDN forum for Excel
http://social.msdn.microsoft.com/Forums/en-US/home?forum=exceldev&filter=alltypes&sort=lastpostdesc
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Regards,
George Zhao
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].

How can I edit lightroom 5 smart previews on mac book pro (mbp) when the lightroom 5 master image files are on my external hard drive is disconnected from the mbp

How can I edit lightroom 5 smart previews on mac book pro (mbp) when the lightroom 5 master image files are on my external hard drive is disconnected from the mbp? So far when I try to disconnect the external HD from the mbp, I get the following pop up window: The disk "external hard drive A" couldn't be ejected because "Lightroom" is using it. Quit that application and try to eject this disk again. When I do that and restart Lightroom 5, the Adobe Photoshop Lightroom - Select Catalog screen pops up but doesn't list my external hard drive A as a choice.
I've reviewed Adobe's Lightroom Help | Smart Previews Lightroom 5 web page and still haven't been able to figure what I'm doing wrong. Any help would be appreciated.

Your internal HDD. by default, is named 'Macintosh HD'. From what information you supplied, it looks like there is already a Lightroom catalog installed on you local (internal) HDD using the standard naming convention Adobe uses as well as a Lightroom catalog on your external drive which you created. To be sure of which catalog Lightroom is loading when it starts up, To do this, start Lightroom as you normally would. After it starts, select the Lightroom menu item, then select the Catalog Preferences item and finally, navigate to the General tab. The Location information will tell you exactly what catalog Lightroom is opening by default. This will likely be the Photography Mac Book Pro Versions catalog on your external HDD. Once that is confirmed, you are ready to proceed. As an additional test/verification, you can shut down Lightroom and, this time, start Lightroom while holding down the ALT/OPTION key. This will cause Lightroom to pause and display a screen which will allow you to chose a different catalog to open. Navigate to the /Users/[user name]/Pictures/Lightroom folder and select the Lightroom 5 Catalog.lrcat file. When Lightroom comes up, there should be no previews or folders as this catalog should be empty. Now you can be certain which catalog is being used and which catalog has all your data and you are ready to migrate your current catalog. Shut down Lightroom.
To migrate your current catalog, use Finder to locate your Photography Mac Book Pro Versions folder on your external drive. Select the folder and select COPY from the context menu. Next, use Finder to navigate to the /Users/[user name]/Pictures/Lightroom folder on you internal HDD. You can start at the Macintosh HD level and work your way down by opening each level (Macintosh HD/Users/[user name]/Pictures). Select the /Pictures folder and then select PASTE... from the context menu. When the COPY/PASTE is complete, you should see the following files on the Macintosh HD:
Macintosh HD/Users/[user name]/Pictures/Lightroom/ and
Macintosh HD/Users/[user name]/Pictures/Photography Mac Book Pro Versions
The Macintosh HD/Users/[user name]/Pictures/Lightroom folder will contain the empty default catalog the Adobe created when Lightroom was installed and Macintosh HD/Users/[user name]/Pictures/Photography Mac Book Pro Versions will contain a copy of the catalog you created on your external HDD.
You are almost done now. Make sure your external drive is still attached for this step. Restart Lightroom using the ALT/OPTION key again. When the Select Catalog screen appears, select the Choose a Different Catalog button (lower left side). When you do, a Finder window will open to allow you to navigate to a catalog of your choosing. Navigate to Macintosh HD/Users/[user name]/Pictures/Photography Mac Book Pro Versions and select the file Photography Mac Book Pro Version.lrcat. This is the copy you just created. Select the Open button and Lightroom should start. You should see all of your previews and settings just as before. Also, in the left hand panel, all of your folder should show up and none of them should be dimmed and none of your previews should display a small exclamation point badge. Either a dimmed folder name or an exclamation point badge indicates that Lightroom can't find the associated image file. If everything looks good, go to the Lightroom menu, select Preferences and then select the General tab. Under Default Catalog, select an option to either load the LAST catalog opened or select the Users/[user name]/Pictures/Photography Mac Book Pro Versions catalog from the drop down. Shut down Lightroom and then restart it normally. This time, when Lightroom starts, you should be viewing the new copy of your catalog. You can confirm this by looking at the General tab on the Catalog Preferences screen (Lightroom/Catalog Preferences menu items). Shut down Lightroom once again and this time, eject your external drive before restarting. This time, your folders in the left hand panel will be dimmed but you should be able to work with your smart previews. If Lightroom should display a Select Catalog screen with the external drive detached, double check your settings as it indicates Lightroom is still looking at the copy of the catalog on the external drive rather than the new copy you made.
Finally, if you are seeing dimmed folders and/or exclamation point badges with the external drive attached, this indicates a problem. You can select any folder and select Update Folder Location from the context menu. This will allow you to navigate to the copy on the external drive and select it. Lightroom will then update the catalog (select to synchronize the content). This will not only clear the dimmed folder problem but also remove the exclamation point badges for all photos in that missing folder. However, it may indicate that not all went well with the copy of the catalog so make sure to verify all went well. You can use the Get Info option on the two folders. You should see the same number of files/folders for both the copy on the internal drive as well as on the external drive but you can't rely on the byte count because of the possibility of differences between the geometry of the two drives. Hope this all helps!

How to send a file without getting Connection Refused??

Hello everyone!
I'm developing a FTP (Client and Server) program as a project and I have 2 main problems:
1. The program can't connect to computers with router (Connection Refused error)
2. If a computer with router connects to me, the program will not transfer the file (Connection Refused error again). but if it does, my friend's internet is suddenly disconnect after one transfer
what should i do?!? : //
everything is working well on one computer, but when i'm trying to work on 2 computers its screwed
***FOR EVERY TRANSFER I OPEN A DIFFERENT SOCKET AND CLOSE IT (AND ALL THE OTHER STREAMS) IN CASE OF EXCEPTION OR COMPLETION
Thanks!!

cotton.m wrote:
Oron wrote:
lol
sorry..just want you to notice
so how the other ftp programs transfer files? : //
i have a test up against 2 testers and my program will not transfer files between 2 computers : ///Are these two computers on the same network? Aka behind the same router? If so then there is another problem, which is either a bug in your program and/or a firewall on one or both of the computers.
How does FTP work normally? Well in most cases you are talking to a server that is on the internet. This server has been configured to be behind or on a network where the routers are not blocking requests to connect to FTP ports (among other services). So nothing different other than it is configured correctly.
I do suspect your program may have some bugs as well. For example when you talk about it dropping the connection after one transfer. That doesn't sound too great.when i checked the program...no
in the test...yes
so the server has no blocking ports, but what about a client with a router?..how do the programs pass the client blocking?
when i checked the program with a friend (i have a modem and i was the server) all the data was perfectly transfered (moving among folders, deleting files, creation of folders-->all these actions on the server..sending codes, strings and stuff), but when i tried to transfer a file it did connection refused :S
i can bring a link to the file that do the transfer and if you have patience to read

Photoshop cc is turning my raw files into jpg after editing

photoshop is turning my raw files into jpg after editing with out flatten the layers instead of psd files. when I go to save they are jpg. This started 2 days ago - no problems before that

How are you doing the save? Just choosing File - Save?
Photoshop remembers the last "master file" format you saved something in. If the current document is capable of being saved in that format, it will default to that format for the next save.
What happens if you do the following:
1. Open your raw file, and edit it.
2. File - Save As, and in the Save as type field choose Photoshop (*.PSD;*.PDD).
3. Complete the save operation.
I'm betting that will result in your having saved a PSD format file.
In summary, change your habit to use File - Save As to save your master document and you can't go wrong.
-Noel

Why does pages suddenly refuse to save a document back to our server after editing?

why does pages suddenly refuse to save a document back to our server after editing?
and can i specify a default save-as location?

The default save location is the one used to open the document.
The default save_to location is the last used one.
Both are stored in memory and written in the application's preferences file when we close it.
It's quite easy to change the defaults in the preferences file but we must do that before opening the app and if we use an other location once the app is open, we will lost the defined default location.
From my point of view, the best scheme is to use an Applescript to save.
Yvan KOENIG (VALLAURIS, France) lundi 4 juillet 2011 23:50:27 iMac 21”5, i7, 2.8 GHz, 4 Gbytes, 1 Tbytes, mac OS X 10.6.8
Please : Search for questions similar to your own before submitting them to the community
To be the AW6 successor, iWork MUST integrate a TRUE DB, not a list organizer !

Connections refused after editing master.cf file

Similar Messages

Maybe you are looking for