Solved issue with Bridge locking up

If anyone is having a problem with Bridge locking up when clicking on Bridge Home, Adobe Photographers Directory, etc., and you have Opera 9.5 installed, the solution is to remove Opera 9.5.

It seems to be the latest version (9.5). I used Time Machine to go back before I installed the update. For me, that was June 4. I used AppZapper to find everything that was involved and restored it with Time Machine's restore feature. I also found and zapped everything to do with the Opera beta.
It's working now. Thanks for the heads up!

Similar Messages

Camera RAW update issue with Bridge CS6

Hi folks,
I recently installed a routine update for Camera RAW 8.4 and now have a bunch of issues with Bridge including -
- No previews or ratings showing
- Ratings filter not working
- Can't open images directly into Camera RAW without first opening Photoshop (ie - keyboard shortcut not working and File menu command "Open in Camera raw" not available)
- Can't access or open Camera RAW preferences
I've tried resetting Bridge to default settings but didn't help and ACR still works fine opening in PS. I've attached two screenshots to show the problem better.
Anyone else having these problems? Any solutions?

This should fix it: Camera Raw 8.4 | No metadata or Camera Raw edit

I just had another issue with cs6 locking up.

I just had another issue with cs6 locking up. This time, I was in cs6 beta working on an image, I went to file/open to open another existing file in photoshop, and when the finder window popped up to select a .jpg to open up, the cursor wouldn't respond to the finder window that was opened up, and I couldn't close it out, and I had to force quite cs6.

If I'm reading this correctly, your last kernel panic (that's what these are called) occured six months ago. Is that correct? It probably does not have anything to do with the number of windows you have open; I suspect it has to do with one of the third party kexts or non-apple hardware. My guess would be something with parallels (is the software up to date?), but if you're only getting panics at 6 month intervals it's really hard to diagnose.
Kernel panics aren't fun, but they aren't the end of the world. make sure you keep regular backups, and if you can figure out how to replicate the panic at a more frequent interval we can figure it out.

We recently switched ISPs. To connect to the new ISP our Airport Extreme has to be in bridge mode. Now our Nintendo Wii won't connect to the Airport. Is it an issue with bridge mode that is causing this?

We recently switched ISPs. To connect to the new ISP our Airport Extreme has to be in bridge mode. Now our Nintendo Wii won't connect to the Airport. Is it an issue with bridge mode that is causing this? We're running two Macs wirelessly with no problems. And the Wii did connect before the switch.

Hello and thanks for the reply. I gave this a try, turned off Airport on one of the computers and tried the Wii again. Still no connection. I should say that we're also running an old G4 (wired) off the Airport as well, with no problems. I've tried many things to make the Wii to work, including power cycling the Airport, turning off the security settings in the Airport, resetting the Airport to it's default and redoing the network, resetting the network setting on the Wii (several times), moved the Airport closer to the Wii, all with no luck. The Wii "sees" the Airport but won't connect to it. I'm at a loss for anything else to try, so any help is appreciated.

I baked up my iphone and when i had issues with sim lock i got it to finally work isynced my phone with i tunes and lost all apps recently downloaded how do i get it back

i had to get an internet conection from a friend to download akll my apps evrytime i sync with my pc wich already had itunes all apps except statup are gone only thing left was an i tunes song i brought from itunes each time i use my apple id pass word it tells me to retry i do this 4 to 5 times and some times have no success my latest issue was my sim locking buy itself then asking me to put in a sim without a lock , i only have 1 sim i brought 2 phones and have had no issues with the other phone and when i do have the original startup apps i can not move or arange them thru itunes apps and i cannot use sim from other iphone pls help evry1 i ask wouldnt have a clue because there having there own dificulties

If you also backed up to your computer - you can restore from that backup - to retrieve the files. As far as I know- that should have no bearing on deleting them from iCloud - they should still be in that backup.
If you used iOS file sharing with your computer - and saved the files to your computer - you can retrieve them from there.
if the only place that the files were saved to was iCloud, I know of no way to get them back.

Workflow issue with Bridge and everything else

Short and sweet. Well, not really.
I use windows - so as a result, for some reason unknown to man (after a decade of waiting), I still cannot see "previews" of most, if not all of any adobe software in the windows dialogue boxes.
think PDF's and the registry hacks we have to do to "enable" previews. But on a mac I can?
So I have to use bridge - a lot.
Now when I have a linked image in illustrator (or whatever) and choose "reveal in bridge" it will hunt and drill down through a multitude of folders and display the image in it's native folder - which I can then open in photoshop for instance - edit it - and Illustrator will detect the change and update. Awesome.
But aside from running a script to send a batch job to a program, it really doesn't "do" anything else that one would expect a "bridge" to do;
     I cannot create a "project" portfolio that would track a client project and all it's related documents.
     Or collaborate with a team.
     I cannot have non destructive edits of a document (such as using an instance of a file like lightroom does) - or "send copy to photoshop" and have Bridge stack the results.
     I cannot combine and tag collections of documents (make a database of stuff).
     I cannot ask Bridge to tell me which documents have placed documents, or (vice versa) which documents are placed into other documents - that would be so cool.
          imagine being able to select a jpeg or psd file and have the option to "Find documents using this file"
          or looking at a "project" and having a list of all first level documents with all their subsequent "placed content" listed all drop down expandable
So my beef today is that I finally spent an hour messing about thinking I had something "wrong" and went through Bridge CS6 with a fine tooth comb trying to find out if anything had changed.
and nope - it still doesn't behave as one would think it would.
Currently, I have some documents that require monthly changes to images, which for the most part came from one photo shoot, and all have essentially the same perspective, appearance, lighting and shading, but all different products and I have a folder of "preformatted images". So monthly I really only need to update the images, and a bit of text. Being posters, InDesign whines a bit for vector art manipulation, so I stick to Illustrator for this job.
But in Illustrator, I cannot choose another image to replace my linked image - without either;
     a: (reveal in bridge), select new replacement image - place as a new image, which then needs to be manipulated as the "old" image was, "remaking" all the adjustments, and then finally deleting the original linked image.
     b: (reveal in bridge) keep bridge open on the image I need (and it's name), go back to illustrator to open the "relink" windows dialogue and "blindly" browse till I find the image I want as shown in bridge.
     c: simply relink and browse blindly to find a file you can't see a preview of and guess, or drag and drop, or all the other non practical ways to replace the image.
Option B gives the desired end result where the image I have in a clipping mask, buried in a document in a certain way, with certain effects, is simply replaced without impacting anything else.
     But this takes quite some time when there are a lot of images.
So Bridge and its promised workflow functionality still isn't living up to it's purpose exactly.
Bridge isn't bridging.
With indesign, it's the same issue - you can't "relink" by revealing in bridge, choosing a "replacement" image and "update"
Maybe a "relink with Bridge" choice in the Links menu?
and in bridge, since Illustrator triggered the request, a button appears to "Replace" - once you finish browsing and highlighting the replacement image you need, just click it and it's done.
So two issues -
Why can't previews of adobe files be shown in windows explorer (still)?
     if they did, I'd really have no use for Bridge.
Why isn't bridge actually communicating with the apps connecting to it?
- and yes, I understand that I cannot ask bridge to go find a placed file and replace it with "this" file, but when illustrator "asks" for "this", bridge should be able to "respond" and give "that" since the app initiated the request.
Bridge should be a workflow tool as advertised - it should literally be able to be a proper workflow hub for all things adobe (and be able to catalogue and track all design file type previews - corel files, cad, 3d, etc)... but as it stands it's just a glorified windows explorer without workflow options.
Bridge hasn't been altered in years, and it's still lingering around - I think - so that we can simply see thumbnails, rather than just allowing each adobe program to make "previews" windows needs.
I can change metadata in windows, I can use freeware to change it extensively.
So aside from the "open in" options and the ability to browse all adobe file types, what's the point?

I couldn't read all through your post as I am jetting out of here.
Buy this:
http://www.fastpictureviewer.com/codecs/
and install it. It's relatively cheap. Screen shot is from Windows Explorer.
Handles ID, PSD, etc., files as well. Though the preview uses greeked text for the most part for the ID files.
Take care, Mike

How I solved issues with Mail.app and Spotlight

Even though my upgrade from Tiger 10.4.10 to Leopard was painless, the new OS X did have a few issues that had bothered me:
*Mail.app: * Every now and then, the app would behave like on its first startup, saying it needs to import my mail before I can work with it. What's more, at times I've had the phenomen that messages would appear empty on the preview pane and sometimes even when being opened.
*Spotlight: * Even though I let the indexing finish on the first day of working under Leopard, every now and then it seemed to start all over. First, I thought it's the NAS being indexed but it just went on to restart indexing each time I thought I had let it finish.
*Free disk space: * I tried to bring the usage of my homedirectory down so I would have enough free disk space to switch FileVault off and then back on so I could start using TimeMachine. But whatever I did, the free disk space just wouuldn't inrease - it just stayed the same (yes, I did let the system recover space on shutdown).
The *free disk space* issue made me think there was a problem with my disk but repeated runs with the Disk Utility yielded nothing...not for about a month. Yesterday I got some warnings about 'damaged but not repaired' but according to an Apple doc those could be safely ignored.
Somebody suggested to apply the combo update for 10.5.1 as that could solve some issues so I went ahead - after all, the update had already been applied earlier so just re-installing wouldn't hurt much, right?
Wrong.
The install of the combo update went smoothly, FileVault recovered some space on shutdown but upon restart I couldn't log in anymore: My homedirectory was damaged. The friendly OS X Leopard offered to repair it but soon later reported back that it failed doing so.
Now, to cut a long story short - deleting the affected user's account and using a different user on the same machine (without FileVault) solved any issues I've had. Mail now works like a charm (despite 40k+ messages with attachments), spotlight doesn't restart all it's indexing and disk space is shown correctly again. Also the odd corrupt file copy I had experienced occasionally (especially with large files) was gone.
My advise to anyone who didn't de-activate FileVault under Tiger to make the switch to Leopard: Even if you think it worked, switch it off and let Leopard set it up again. You may think things went right...but the above shows that there may be issues with it that you may blame other apps for...but they're probably not guilty at all.
I don't think the combo update actually caused FileVault to turn corrupt, it was just what broke the camel's neck. While it's no fun to lose your homedirectory, I'm glad the underlying issue finally came to light.

Thanks to this thread, it's been solved.
https://bbs.archlinux.org/viewtopic.php?id=97653

Weird issue with Bridge CC and vector masked TIFF files

For some reason in Bridge CC my vector masked transparent backgrounds in my tiff files are showing. I didnt have this issue with CS6. only way to fix it is for me to flatten my image and resave it as a tiff without the mask. Any option i need to click on?

We don't even know what platform (Mac or Win) or version of the OS you are running.
Also: Are you aware that the latest version of Photoshop is not "CC" but CC2014v14.2.2 ?
BOILERPLATE TEXT:
Note that this is boilerplate text.
If you give complete and detailed information about your setup and the issue at hand,
such as your platform (Mac or Win),
exact versions of your OS, of Photoshop (not just "CS6", but something like CS6v.13.0.6) and of Bridge,
your settings in Photoshop > Preference > Performance
the type of file you were working on,
machine specs, such as total installed RAM, scratch file HDs, total available HD space, video card specs, including total VRAM installed,
what troubleshooting steps you have taken so far,
what error message(s) you receive,
if having issues opening raw files also the exact camera make and model that generated them,
if you're having printing issues, indicate the exact make and model of your printer, paper size, image dimensions in pixels (so many pixels wide by so many pixels high). if going through a RIP, specify that too.
A screen shot of your settings or of the image could be very helpful too,
etc.,
someone may be able to help you (not necessarily this poster, who is not a Windows user).
Please read this FAQ for advice on how to ask your questions correctly for quicker and better answers:
http://forums.adobe.com/thread/419981?tstart=0
Thanks!

Solved issues with my Macbook Pro freezing

My Macbook Pro would freeze from time to time. I could move the mouse and I could hit return with success but couldn't click the mouse at all. I would have to manually power down and restart to solve the issue. I tried all sorts of things to solve this. Thought it was iTunes, Outlook, videos. But there was nothing consistent.
It just happened again and of couse I was crazily clicking anything when I realized I could "right click" and see drop downs. I just couldn't use the mouse to make a selection. I could possibly arrow over and hit return but could not click. It made me wonder if it was my mouse or trackpad. (Be easy on me. I'm not a Mac expert by a long shot.)
During my crazy random right-clicking, I hovered over the bluetooth connections and noticed my mouse which made me think. I never had a problem while at home (aka no mouse) AND at work my wireless mouse was always there - a constant. So I removed the batteries and voila, my clicking issues were solved.
I am adding this to the forum in case there are others like myself searching for solutions. It's just one more thing to try before you lose it.

Just tried that and it didn't help. I actually was having so many issues with Safari that I downloaded Firefox. It ran a bit better but I still have issues with sluggishness...
I'm actually using Firefox right now.

Is there a fix coming for the iPad Air's issues with rotation locking???

The iPad Air has an annoying glitch in its occasional (frequent) shift to landscape mode, and locking in that position. Is this a known/reported issue with a fix coming?
This didn't occur with the older version of the iPad.
Thx.

iPhone, iPad or iPod screen will not rotate, fix http://appletoolbox.com/2013/03/iphone-ipad-or-ipod-screen-will-not-rotate-fix/
iOS Screen Does Not Rotate
http://support.apple.com/kb/ts3805
 Cheers, Tom

I had issues with bridge and uninstalled it, now I can not reinstall bridge

I had issues with using Bridge it would be slow and unresponsive. I am using a pc with windows 7. I have the CC subscription for Photoshop. I uninstalled bridge and now can not reinstall it or open CC. I would like to get bridge back it was so much easier to look at all the photos on the camera before choosing to edit them. Thanks and cheers

As Peru Bob mentioned run the Cleaner Tool first.
I'll add signing out of your CC desktop account and signing back in under Preferences.
Hopefully it updates the CC Desktop to where you have the install option for Bridge CC.

[solved] Issue with conky and Kde 4

I have a small issue with conky and KDE 4.2. I start conky with a script which I stored under ~/.kde/Autostart. The script is simple and looks like this..
conky -c ~/.conkyrc_kde4
This works fine. But when I restart the first KDE and check with ps, I have 2 instances of conky running. The instances keep on growing with the number of restarts.
I think kde tries to restart all the apps which were running when the session was terminated. Is there a way to change this behavior in general or all the programs or for only a specific program like conky ?
Last edited by rangalo (2009-07-28 19:02:17)

I did
Systemsettings > Advanced > Session Manager > Start with an empty session
and put everything you want in Autostart

[SOLVED]Issue with Postfix sending to external mail addresses

I'm having a very silly issue with Postfix. I followed the wiki article at [link]https://wiki.archlinux.org/index.php/Postfix[/link], and everything seems to work properly, however I cannot send to emails outside of my domain.
I get the error:
550 5.1.1 <[email protected]>: Recipient address rejected: Local delivery only!
Here is what the logs say:
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: connect from localhost.localdomain[127.0.0.1]
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: 091E011E3C: client=localhost.localdomain[127.0.0.1]
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: 091E011E3C: reject: RCPT from localhost.localdomain[127.0.0.1]: 550 5.1.1 <[email protected]>: Recipient address rejected: Local delivery only!; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<sendingdomain.com>
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: lost connection after RCPT from localhost.localdomain[127.0.0.1]
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: disconnect from localhost.localdomain[127.0.0.1]
May 08 16:05:14 my.dns.stuff.org sudo[31476]: me : TTY=pts/0 ; PWD=/etc/postfix ; USER=root ; COMMAND=/usr/bin/journalctl
main.cf
# Global Postfix configuration file. This file lists only a subset
# of all parameters. For the syntax, and for a complete parameter
# list, see the postconf(5) manual page (command: "man 5 postconf").
# For common configuration examples, see BASIC_CONFIGURATION_README
# and STANDARD_CONFIGURATION_README. To find these documents, use
# the command "postconf html_directory readme_directory", or go to
# http://www.postfix.org/BASIC_CONFIGURATION_README.html etc.
# For best results, 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 = /var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/bin
# 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/lib/postfix
# The data_directory parameter specifies the location of Postfix-writable
# data files (caches, random numbers). This directory must be owned
# by 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 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 = mail.sendingdomain.com
# 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 = www.sendingdomain.com
# 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
append_dot_mydomain = no
# 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 = loopback-only
#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
#mydestination = localhost
# 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]
default_transport = error: Local delivery only!
# 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
alias_maps = hash:/etc/postfix/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
alias_database = $alias_maps
# 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) for the effects this has on
# aliases, canonical, virtual, relocated and .forward file lookups.
# Basically, the software tries user+foo and .forward+foo before
# trying user and .forward.
#recipient_delimiter = +
# DELIVERY TO MAILBOX
# The home_mailbox parameter specifies the optional pathname of a
# mailbox file relative to a user's home directory. The default
# mailbox file is /var/spool/mail/user or /var/mail/user. Specify
# "Maildir/" for qmail-style delivery (the / is required).
#home_mailbox = Mailbox
home_mailbox = Maildir/
# The mail_spool_directory parameter specifies the directory where
# UNIX-style mailboxes are kept. The default setting depends on the
# system type.
#mail_spool_directory = /var/mail
#mail_spool_directory = /var/spool/mail
# The mailbox_command parameter specifies the optional external
# command to use instead of mailbox delivery. The command is run as
# the recipient with proper HOME, SHELL and LOGNAME environment settings.
# Exception: delivery for root is done as $default_user.
# Other environment variables of interest: USER (recipient username),
# EXTENSION (address extension), DOMAIN (domain part of address),
# and LOCAL (the address localpart).
# Unlike other Postfix configuration parameters, the mailbox_command
# parameter is not subjected to $parameter substitutions. This is to
# make it easier to specify shell syntax (see example below).
# Avoid shell meta characters because they will force Postfix to run
# an expensive shell process. Procmail alone is expensive enough.
# IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
# ALIAS THAT FORWARDS MAIL FOR ROOT 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
# to use after processing aliases and .forward files. This parameter
# has precedence over the mailbox_command, fallback_transport and
# luser_relay parameters.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
# Cyrus IMAP over LMTP. Specify ``lmtpunix cmd="lmtpd"
# listen="/var/imap/socket/lmtp" prefork=0'' in cyrus.conf.
#mailbox_transport = lmtp:unix:/var/imap/socket/lmtp
# Cyrus IMAP via command line. Uncomment the "cyrus...pipe" and
# subsequent line in master.cf.
#mailbox_transport = cyrus
# The fallback_transport specifies the optional transport in master.cf
# to use for recipients that are not found in the UNIX passwd database.
# This parameter has precedence over the luser_relay parameter.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#fallback_transport = lmtp:unix:/file/name
#fallback_transport = cyrus
#fallback_transport =
# The luser_relay parameter specifies an optional destination address
# for unknown recipients. By default, mail for unknown@$mydestination,
# unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned
# as undeliverable.
# The following expansions are done on 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. Specify ${name?value} or
# ${name:value} to expand value only when $name does (does not) exist.
# luser_relay works only for the default Postfix local delivery agent.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must specify "local_recipient_maps =" (i.e. empty) in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#luser_relay = [email protected]
#luser_relay = [email protected]
#luser_relay = admin+$local
# JUNK MAIL CONTROLS
# The controls listed here are only a very small subset. The file
# SMTPD_ACCESS_README provides an overview.
# The header_checks parameter specifies an optional table with patterns
# that each logical message header is matched against, including
# headers that span multiple physical lines.
# By default, these patterns also apply to MIME headers and to the
# headers of attached messages. With older Postfix versions, MIME and
# attached message headers were treated as body text.
# For details, see "man header_checks".
#header_checks = regexp:/etc/postfix/header_checks
# FAST ETRN SERVICE
# Postfix maintains per-destination logfiles with information about
# deferred mail, so that mail can be flushed quickly with the SMTP
# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
# See the ETRN_README document for a detailed description.
# The fast_flush_domains parameter controls what destinations are
# eligible for this service. By default, they are all domains that
# this server is willing to relay mail to.
#fast_flush_domains = $relay_domains
# SHOW SOFTWARE VERSION OR NOT
# The smtpd_banner parameter specifies the text that follows the 220
# code in the SMTP server's greeting banner. Some people like to see
# the mail version advertised. By default, Postfix shows no version.
# You MUST specify $myhostname at the start of the text. That is an
# RFC requirement. Postfix itself does not care.
#smtpd_banner = $myhostname ESMTP $mail_name
#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
# PARALLEL DELIVERY TO THE SAME DESTINATION
# How many parallel deliveries to the same user or domain? With local
# delivery, it does not make sense to do massively parallel delivery
# to the same user, because mailbox updates must happen sequentially,
# and expensive pipelines in .forward files can cause disasters when
# too many are run at the same time. With SMTP deliveries, 10
# simultaneous connections to the same domain could be sufficient to
# raise eyebrows.
# Each message delivery transport has its XXX_destination_concurrency_limit
# parameter. The default is $default_destination_concurrency_limit for
# most delivery transports. For the local delivery agent the default is 2.
#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 20
# DEBUGGING CONTROL
# The debug_peer_level parameter specifies the increment in verbose
# logging level when an SMTP client or server 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 domain
# or network patterns, /file/name patterns or type:name tables. When
# an SMTP client or server host name or address matches a pattern,
# increase the verbose logging level by the amount specified in the
# debug_peer_level parameter.
#debug_peer_list = 127.0.0.1
#debug_peer_list = some.domain
# The debugger_command specifies the external command that is executed
# when a Postfix daemon program is run with the -D option.
# Use "command .. & sleep 5" so that the debugger can attach before
# the process marches on. If you use an X-based debugger, be sure to
# 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't use X, use this to capture the call stack when 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 possibility is to run gdb under a detached screen session.
# To attach to the screen sesssion, su root and run "screen -r
# <id_string>" where <id_string> uniquely matches one of the detached
# 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
# INSTALL-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 mail posting interface.
sendmail_path = /usr/bin/sendmail
# newaliases_path: The full pathname of the Postfix newaliases command.
# This is the Sendmail-compatible command to build alias databases.
newaliases_path = /usr/bin/newaliases
# mailq_path: The full pathname of the Postfix mailq command. This
# is the Sendmail-compatible mail queue listing command.
mailq_path = /usr/bin/mailq
# setgid_group: The group for mail submission and queue management
# commands. This must be a group name with a numerical group ID that
# is not shared with other accounts, not even with the Postfix account.
setgid_group = postdrop
# html_directory: The location of the Postfix HTML documentation.
html_directory = no
# manpage_directory: The location of the Postfix on-line manual pages.
manpage_directory = /usr/share/man
# sample_directory: The location of the Postfix sample configuration files.
# This parameter is obsolete as of Postfix 2.1.
sample_directory = /etc/postfix/sample
# readme_directory: The location of the Postfix README files.
readme_directory = /usr/share/doc/postfix
inet_protocols = ipv4
#virtual_mailbox_domains = sendingdomain.com
virtual_alias_maps = hash:/etc/postfix/virtual_alias, mysql:/etc/postfix/mysql_virtual_forwards.cf
virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_domains.cf
virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailboxes.cf
virtual_mailbox_base = /home/vmailer
virtual_uid_maps = static:5003
virtual_gid_maps = static:5003
virtual_minimum_uid = 5003
virtual_mailbox_limit = 51200000
Any help would be appreciated. Thank you.
Last edited by nadman10 (2014-05-14 14:36:10)

Your main.cf seems redundant.
For example:
if you specify:
virtual_alias_maps = hash:/etc/postfix/virtual_alias, mysql:/etc/postfix/mysql_virtual_forwards.cf
you don't need this:
alias_maps = hash:/etc/postfix/aliases
and i think you have a lot of more options you don't need.
This is my main.cf on my vps and everything works great (sending and receiving emails from/to most common mail server: gmail, hotmail etc etc)
smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
biff = no
# appending .domain is the MUA's job.
append_dot_mydomain = no
readme_directory = no
# TLS parameters
smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
smtpd_use_tls=yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
message_size_limit = 4194304
virtual_mailbox_domains = mysql:/etc/postfix/mysql-virtual-mailbox-domains.cf
virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-mailbox-maps.cf
virtual_alias_maps = mysql:/etc/postfix/mysql-virtual-alias-maps.cf
virtual_transport = dovecot
dovecot_destination_recipient_limit = 1
it is very simple (no dkim, no forced tls, no mailbox limits and so on) and it can be improved but it works..
as I suggested you just try spending some hour wiping postfix installation and giving a look to this guide

Issues with file locking when reading a file using RollingFile Appender

Hi,
I am facing a file Rotation Issue with log4j. I want a way to read one file from two diff apps.
Intro: App A is writing a file F using log4j rolling file appender and app B is reading the same file F using new BufferedReader(new InputStreamReader(new FileInputStream(_file))).
Issue: App A is not able to roll the file. Because it is having a handle on the same file F.
Please let me know how can I handle this issue.

If you have the file open for reading when log4j tries to rename it, the rename will fail. Solution: don't have the file open for reading.
I want to read the feed of such rolling logs without closing any handle.I gave you a solution to that too.
If I am closing the handle after every read then there will be no way to determine where I left.Nobody suggested that.
Is there any possible solution for this?What part of the solution I have already posted didn't you understand?

Networking issues with bridged connection

So in my network I have a netgear C6300 with a Motorola surfboard(modem/router also with dhcp turned off) connected via Ethernet to provide a separate wifi network on the other side of the house. I've been having frequent connection drops that last for about
10 seconds. I figured out my wireless adapter(netgear a6210) is bridged to the Motorola(see screenshot) and I'm wondering how to disable this bridge because I think it might be causing the connection issues. But when I try to remove the bridge is says gives
an error. If I disable the Network bridge my adapter stops working. Any ideas?
Note: before it was saying Motorola... under the enabled, bridged.
Edit:
This: I also noticed it switched from Motorola like the picture below to NETGEAR58-5G(like above)

Hi slycoder127,
If yo uare currently running Windows 10 build 10049, then you should take a look at the thread below:
No access to Internet Protocol (v4 or v6) in 10049
Which might cause some of the adapter function not working at the current build.
Best regards
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]

Solved issue with Bridge locking up

Similar Messages

Maybe you are looking for