Please Address issue with

Hello All,
I have purchased a MuVo TX FM and have great things to say about it! The MediaSource software on the other hand has an issue i would like to see addressed. While using the "smart fit" option the software creates a temp folder in the root of the "application data" folder under the current user instead of inside of the "creative" sub-folder. It uses this folder to store the new, smaller, file until it is transferred to the player. The issue is that I have encrypted the application data folder and as such get an error when the software tries to transfer the new file. I have no complaints about un-encrypting the "creative" folder but would like to keep every thing else in the parent fold encrypted. In the next release of the software would someone please address users who encrypt their home folders. Thank you.
Setup
Windows XP SP2
Creative MuVo TX FM
Creative MediaSource 3.30.2
Athalon XP 2700+
768MB RAM
Abit mb
Seagate ATA00 hdd
Source files are on a network dri've

Hi bernwa
We are able to reproduce the issue. We are working on the fix. Will keep you posted.
Thanks
Manigandan

Similar Messages

Help please! Issues with Superdrive.

I was ahving huge issues with my MBA these past days. Now I was able to boot with the OS X dvd and reinstall the OS. the installation went well, but now I have an eject symbol in the upper right corner of the system bar and it seems my USB port is either fried or locked. I can not use any other USB devices (wanted to hook up to my external HD to backup all my stuff and then zero out my MBA and clean install). its strange. I can restart the MBA pressing C and then the Superdrive runs. Guess this speaks against the USB port being fried.
Would appreciate any help given soon!!

Sorry if this is too basic and you have tried it but here goes:
to eject the superdrive select the icon for it on the desk top (with the s-drive connected) then press and hold down the eject button on the keyboard upper most right on keyboard.
You may even need to have the disc in the drive but I doubt that.
Or go to iTunes or Finder, select the drive and eject from there.

Please help - issue with ng sound when scrolling

Heya all,
I have an ASUS P5B Deluxe Wi-Fi board with the latest BIOS (26), Vista Ultimate 32bit, a P82 case, E6400 @ 3.2GHz, 2GB RAM, 8800GTS and a lovely x-fi xtreme-music soundcard, which sits in the bottom PCI slot - the gfx card is obviously in the top PCI-E slot.
Basically, whenever I'm listening to music via my PC (usual app Winamp, although WMP is used too at times) or watching DVDs etc, any movement of the mouse, or rather the scroll wheel of the mouse, results in a loud crackling and breakup of audio.
In fact, after some further testing, it seems like whenever something graphically changes on the screen (whether it be scrolling, a web page loading, a window opening etc), anything at all, this loud and ultra annoying issue occurs. The sound at start-up also crackles and breaks up.
I've tried reinstalling drivers for the x-fi and for my gfx card - neither helped. I've tried different drivers for both my GFX and x-fi. Again, no joy.
I'm now using the Creative official vista drivers CD and we updated the drivers to 2.5.002. GFX-wise I'm using the latest NVidia publically released drivers as per their site.
I'm at my wits end - can anyone help or throw any light on the issue please?
Oddly, I've only just re-installed Vista as I've fitted a new HDD. The installation before, with exactly the same board, drivers etc etc, worked fine.
Perhaps I should reformat Vista and try again?

Amit,
Thank you so much for your response. I also never thought that it would behave differently.
I am just using one variable called CurrYear in my BR.
Yes, I am guessing something is going wrong with the second point that you mentioned. That I have 0 level members selected in Page/POV and in EAS it is manually taking parent values.
Well, I did a comparision but didn't see any differences though. I am using SETUPDATE CALC ON statement in my BR.
Can you suggest me on how can I fix this?
Thank you !
~ Adella

IP Address Issue with eth0 and xenbr0

Hi All
Last sunday I bought new machine with AMD 6 core processor and 16gb RAM. I installed Vmserver 2.2.1 successfully but I am not able to access the vmserver from other machines.
Network card detected and shows status up and running.
One thing I observed that the assigned IP address for management NIC is getting assigned to xenbr0, this might be the issue.
I tried assigning ip address back to eth0 but as soon as I restart the server it will go back default to xenbr0 means IP address is getting assigned to xenbr0 instead of eth0.
Any suggetions here highly appreciated I struck with this issue.
Let me know if you have any suggestion to make it work so that I can access vm server from other machines.
how to make the default ip address to be assigned after reboot and what would be the ip address for xendr0 ?
Regards
Anandkumar S.M.

Hi,
actually the IP address is bound to the bridge (not to eth0).
This works as designed.
Even if you setup the network manually you assign the IP to the bridge - not to eth0.
Maybe the underground manual for OVM can give you more information:
http://itnewscast.com/underground-oracle-vm-manual
Regards
Sebastian

Help Please! -- issue with Mad Catz controller

Can anyone help me out here? I have a Mad Catz Wireless PC Con and I'm having trouble getting it to work. After plugging it into a USB port, when I go to the System Profiler and go to the USB section, the PC Con is listed as hooked up to the USB port like it should be, so I know the computer is reading it properly, but I can't get it to work. When I open the apps I want to use it with, the buttons don't do anything. The obvious reason for this would be that the PC Con isn't compatible with those applications, but that's not the issue here because I have an application (USB Overdrive) that allows joysticks (or controllers or whatever) to be set up to work with any application, and this always worked for me perfectly when I had Tiger. With Tiger I used to use the PC Con with the emulator applications all the time, but now that I've upgraded to Leopard, nothing happens when I hit the buttons. There were no decent instructions with the PC Con. Is there anything I need to to do install the controller first before I can use it or something like that? Does anyone have any ideas for me? Any help is greatly appreciated. Thanks alot.

In your Preferences menu, Type section, what Text Engine Option have you chosen?
-Noel

Can anybody Assist, please ? Issue with running Prem Pro 1.5 on 'new' pc with Win XP Pro

After some years of faithful service my PC died and I am not able to get Premiere Pro 1.5 to work on the new PC. I had several HDD with my video files on and the C: drive died. I have reinstalled the original drives so all my files are recovered and I can see/open them in Premiere BUT I cannot setup to capture anything.
System is Win XP Pro, Pentium Dual core, 2.7GHz, 2Mb RAM, Capture device is Canopus with DV Storm 2 drivers, Sony DR1000 deck connected by firewire.
When I go to capture settings there is an IEEE1394 option and DV Capture. If I select Canopus the PD INSTANTLY reboots. I don't know where to start looking for the issue . . . is anybody able to help ?
Would be much appreciated . . .

Ian
Did you replace the whole PC or just the boot drive?
I may be totally wrong but I had a Storm card years ago and it worked with Premiere up to the old verions 6 or 6.5, Premiere 6.5 is when it became realtime and hence the Storm card was no longer necessary for anything other than faster mpeg encoding
I seem to remember that Canopus introduced Lets Edit which then became Edius at this time and they dropped bundling Abobe products so I am surprized that Premiere Pro 1.5 worked with the Storm
If the Storm cannot be got to work and you do not have a firewire port on the Mobo go to your local PC component supplier and obtain a firewire PCI card with Texas chipset and install it. the card should cost about $20-$30. The Storms worked a treat but the Mobo had to be right and it did not like certain chipsets on the boards, not only that the installation process was a total pain

External IP address issue with ix2

Hi, I recently contacted my ISP in order to get a fix IP address.Ports are well defined and redirection is set. In addition, I fixed the local IP on the router. Despite this, I am not able to access the NAS via Internet and I am still getting a totally different external IP address (previous configuration – before fixing the IP). Furthermore, I haven’t been able to reset to factory setting (instructions in the manual are not so much clear). I can only reset username and password settings. How can I change the external IP address so I could access the NAS from internet (outside the office)? Thanks in advance,Sam

Hello samfar,
You cannot change your external IP address, that must be done by your ISP.
If you enter your IP address into the URL of a browser from outside of your network with the scenario you have described, then you should be able to access the UI.
If you cannot, something is blocking the traffic.

Domain name/ip address issue with web server

My problem is the reverse of what is normally expected... I can access a website by domain name but not by ip address. Whenever I substitute the website's ip address for the domain name I get 404's.
I'm stumped by this. I can access other websites on the web at large by ip address, but none of the websites hosted on my server will work this way. The domain name works:
http://domain/filename
but
http://ipaddress/filename
returns 404's
Any idea what the problem is?

That's to be expected if you have more than one website configured in IIS. Each website must have a unique identity, made up of the host address, ip address and port number, so in most cases where the webserver only has a single IP address and will obviously
be using port 80 the host name must be different.
If you have only one website, or your website has it's own IP address you can make it accessible via IP. Simply add another identity (like you might have one for mydomain.com and another for
www.mydomain.com), but this time only assign it the IP address and port number, leave the host header value empty. As long as that combination is unique you'll be able to access the website using the IP address. If it's
not unique you'll get an error preventing you from adding the identity, at which point you'll need to find which site it's conflicting with.

IP or DHCP address issue with VPN

setup: Mac server 10.6.8, VPN service L2TP, Airpot Extreme software fully updated in company LAN set to DHCP: IP range is 10.0.0/24, DHCP service is OFF in server admin...
VPN IP range is 10.0.0/24
I noticed sometimes when I VPN into my company network via L2TP (which I do IT support for) that someone on the company LAN gets a notice that another device on the network is using the same IP as their machine.
All clients in the company LAN are set to DHCP and the remote connecting Mac is set to DHCP, and the remote LAN is a different network than the company LAN.
This instance once interrupted remote server access (via VPN) because the remote connecting client somehow attain the IP of the companys' Drobo File server , which itself has a manual IP.
Do I need to set the VPN IP range to a different scope than the company DHCP range? ie. Company DHCP range (in AE) to 10.0.0.1 - 10.0.200 and in VPN IP range settings 10.0.0.201 - 10.0.0.254
Is there a setting I've missed?
Can anyone help?
Thx

Do I need to set the VPN IP range to a different scope than the company DHCP range? ie. Company DHCP range (in AE) to 10.0.0.1 - 10.0.200 and in VPN IP range settings 10.0.0.201 - 10.0.0.254
Yes, You need TWO pools of IP addresses in your LAN.
One is kept by the DHCP server and addresses from this pool are assigned to DHCP clients on the LAN.
The other range is handled by the VPN server and clients connecting to the VPN are assigned one of these addresses. VPN clients do NOT get a DHCP address from the LAN DHCP server.

Urgent please: Percentage issue with more data

Hi,
I am trying to calculate percentage but it is throwing error. Any help on calculating percentage type reports?
Thanks,
Sri

Your statement "Looks like VO2 is not being attached to the adv table in PFR?" holds the key to your issue.
Are you trying to attach the VO in PFR? Only a selected properties can be modified for beans in PFR. Put your code in processRequest and it should work.
--Shiv

Apple: Please, fix issue with QT playback within Keynote!

How can it be that a QT movie plays back fine on a Powerpoint presentation but not on Keynote? Isn’t this an obvious bug? So many people have complained about it for so long...Please Apple, deliver us from this problem!

Be sure to send your feedback here as well.
http://www.apple.com/feedback/keynote.html
These discussions are user to user. To get Apple's ear, use the above link.

Issue with EAN/UPC field in "BAPI_MATERIAL_SAVEDATA"

Hello guys,
I have a requirement where I am using the BAPI_MATERIAL_SAVEDATA to create a new material by using a reference material. The question is how can i pass EAN/UPC field into it?
This field exists in Basic Data1 tab in MM01 screens. I am not getting how to pass values into the INTERNATIONALARTNOS type BAPI_MEAN ?? This is there as table parameters in the BAPI?
Please advice

Hi
Issue with BAPI_MATERIAL_SAVEDATA
Bapi_material_savedata help with parameters
Regards
Pavan

HT1222 I have an iPhone and new iPad. Epost mail will not open on my devices. Epost says Safari is not compatible with epost. Please address this issue. It is most annoying.

I have an iPhone and new iPad. Epost mail will not open on my devices. Epost says Safari is not compatible with epost. Please address this issue. It is most annoying.

Hello:
You need to contact "epost." The issue is not an Apple issue....the epost software needs, I assume, to be updated.
Barry

Please enter at most 70 letters or numbers for street address, i am facing this issue with that i am unable to downloads few apps, as it is asking for this question and again and again,

please enter at most 70 letters or numbers for street address, i am facing this issue with that i am unable to downloads few apps, as it is asking for this question and again and again,
i tried all letters and address more 100 hundred also nut no of use,

please enter at most 70 letters or numbers for street address, i am facing this issue with that i am unable to downloads few apps, as it is asking for this question and again and again,
i tried all letters and address more 100 hundred also nut no of use,

[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

Please Address issue with

Similar Messages

Maybe you are looking for