[SOLVED] Issue with eth0 (eth0: timed out)
Hi there people, just installed Arch on my PC (again). The first time I had no problems with this, but now it is really bothering me. Well, my PC only access the net via wireless, so I have no wired connection for it. Here's my /etc/rc.conf:
# /etc/rc.conf
eth0="dhcp"
wlan0="dhcp"
wlan_wlan0="wlan0 essid MySpot key ABCDEFABCDEF1234567ABCDEFC"
INTERFACES=(eth0 wlan0)
Well, everything is working fine, I can get access to the internet on bootup. My only concern is that my system is taking awfully long to boot. It takes about 1-2 minutes on "::Starting Network", then it shows me "eth0: timed out". Then it takes about 10 secs to start my wlan0 interface and the system finishes booting. I had previously installed Arch 2008.12, and the Starting Network only took about 10 secs to start my wlan0. I have already tried commenting out the eth0 line and putting a ! in front of eth0 on INTERFACES, but doing that only shows me an error message for my wlan0 and render my internet unusable on system bootup. So, my questions are:
1) Do I really need the eth0 interface for my connection (since I'm using wlan0 for wireless connection) ? Why can't I comment it out?
2) If I really need eth0, how can I make my boot time go faster, or how can I make it not time out?
Thanks in advance for any help given...
EDIT: problem solved, see Post 8 below for answers...
Last edited by gabscic (2009-03-25 03:40:43)
Thanks for answering. Well, I think eth0 is being detected correctly. Here is the output for ifconfig:
eth0 Link encap: Ethernet Hwaddr 00:18:F3:87:97:41
UP BROADCAST MULTICAST MTU: 1500 Metric: 1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:19
lo Link encap: Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU: 16436 Metric: 1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wlan0 Link encap: Ethernet Hwaddr 00:15:AF:09:BC:E7
inet addr: 192.168.0.100 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU: 1500 Metric: 1
RX packets:1903 errors:0 dropped:0 overruns:0 frame:0
TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:615024 (606.6 Kb) TX bytes:1020 (1020.0 b)
wmaster0 Link encap: UNSPEC Hwaddr 00-15-AF-09-BC-E7-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU: 1500 Metric: 1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Well, I hope that can help. Searched the net and the forums, and every problem related to this is with people who are actually trying to use the eth0 interface for connection. In my case, I don't think I need it, I only need the wlan0. What I'm trying to do is get rid of eth0 while letting wlan0 work.
Similar Messages
-
"NETDEV WATCHDOG: eth0: transmit timed out" proble
Hi all,
I did a "pacman -Syu" and had to upgrade a lot of packages. After I rebooted this machine, I'm have problem with its network connection...
When I do a scp of a big file to this machine, say 500+ MB, the copy progress will stall for a couple of seconds (2 to 10) and I receive the following errors in /var/log/messages.log: "NETDEV WATCHDOG: eth0: transmit timed out". This happens once or twice in this scp session. If I start a second, both it will stall several times and sometimes don't even finish (e.g; times out completely). I did not have this problem before all the upgrades.
Has anybody seen this before? Is my network broken and happened to be this right after the upgrade by coincidence?
Regardson some intel chipsets i've had a similar problem. try passing:
pci=noacpi
to the kernel. if that does not help either turn acpi off alltogether with:
acpi=off
then again, this is just a guess on what might solve the problem since i do not know which driver you use. -
Nexus 7K SVI interaction with if-mgr timed out
try to create a new SVI in 7K , but got this information
int vlan 120
ERROR: Vlan 120 interaction with if-mgr timed out
any one have the same issue?
by the way , there are 200 other SVI in this 7KHi,
Do these 2 problematic 2960 switches running the same IOS as all the other switches?
Is there anything in the logs?
HTH -
When I go to download tunes and/or music videos, each attempt concludes with a "Session Timed Out" message, asking me to "try again." I do -- and the same thing happens.
I am working with iTunes 10.4.1 on an iMac with OS 10.4.11.
Thanks,
Peter CavanaughDelete and redownload them if doing so is free in your country.
(106637) -
ipod nano 7th generation having issues with the UI. Out of box everything worked great. Once I snyc the device and it finished, the UI becomes unuesable. You have to double tap every icon in order to open music, videos, etc. I cannot swipe to the second page of icons, black box appears around an icon and then switches to a different one anytime I swipe. A box even appears around the time and battery power. iPod & iTunes are both updated. What is the FIX on this issue?
I had this problem as well. This is what I found by searching online. I tried the fix on my nano 7th gen and it worked. I hope this helps you. Make sure to use two fingers for sliding and double-click the icons to get into settings. Good luck.
It would seem that Voiceover has been enabled on your iPod Nano. The following article contains information regarding Voiceover, and how to disable it once it's been enabled.
iPod nano (6th generation and later): How to use VoiceOver
http://support.apple.com/kb/HT4317
To turn off VoiceOver on iPod nano using VoiceOver gestures
From the Home Screen, swipe right or left with two fingers until you see or hear "Page 2 of 2" on iPod nano (7th generation) or "Settings" on iPod (6th generation).
If the icons have been rearranged, or if there are more than four Home screens, you may hear something different.
Slide one finger around the screen until you hear Settings.
Double-tap to open Settings.
Slide your finger up or down the screen until you see or hear General, then double- tap.
Slide your finger up or down the screen until you see or hear Accessibility, then double-tap.
Slide your finger up or down the screen until you see or hear VoiceOver, then double-tap.
Double-tap when you hear "VoiceOver switch button on."
You'll hear "VoiceOver off" to confirm the setting. Now you can use standard gestures to control iPod nano.
Note: You can also turn off VoiceOver by resetting your iPod. -
Is anyone else having issues with Lightening cables wearing out fast
Is anyone else having issues with Lightening cables wearing out fast
It does happen. Search Google and you will find many instances.
-
NWDS (7.31) issue at first load - timed out
Hello,
we upgraded our Portal to 7.40. According to note 1791485 - NWDS 7.3 EHP1 as development environment for SAP NetWeaver 7.4
I installed NWDS 7.31.
Problem is that first load of NWDS takes 40 minutes !!! With a lot of Timed Out message. But if I close NWDS (when finally loaded) and restart it the load is in less then 1 minute...
According to this documentation:
Viewing the Error Log File
http://help.sap.com/saphelp_nwce10/helpdata/en/46/8bf063332600fde10000000a11466f/content.htm
I checked the log file. And I found Timed Out messages:
!SESSION 2015-03-18 11:36:51.846 -----------------------------------------------
eclipse.buildId=@qualifier@
java.version=1.6.0_31
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en
Command-line arguments: -os win32 -ws win32 -arch x86
!ENTRY org.eclipse.osgi 2 1 2015-03-18 11:38:29.790
!MESSAGE NLS missing message: SERVICE_REFERENCE_BOUND in: org.eclipse.equinox.internal.ds.SCRmessages
!ENTRY org.eclipse.osgi 2 0 2015-03-18 11:38:51.281
!MESSAGE While loading class "org.eclipse.ui.application.WorkbenchAdvisor", thread "Thread[main,5,main]" timed out waiting (5000ms) for thread "Thread[Component Resolve Thread,5,main]" to finish starting bundle "org.eclipse.ui.workbench_3.5.2.M20100113-0800 [1375]". To avoid deadlock, thread "Thread[main,5,main]" is proceeding but "org.eclipse.ui.application.WorkbenchAdvisor" may not be fully initialized.
!STACK 0
!ENTRY org.eclipse.osgi 2 0 2015-03-18 11:38:59.317
!MESSAGE While loading class "org.eclipse.ui.PlatformUI", thread "Thread[main,5,main]" timed out waiting (5000ms) for thread "Thread[Component Resolve Thread,5,main]" to finish starting bundle "org.eclipse.ui.workbench_3.5.2.M20100113-0800 [1375]". To avoid deadlock, thread "Thread[main,5,main]" is proceeding but "org.eclipse.ui.PlatformUI" may not be fully initialized.
!STACK 0
!ENTRY org.eclipse.osgi 2 0 2015-03-18 11:57:51.476
!MESSAGE While loading class "com.sap.ide.dii05.lib.internal.dc.core.EmfDcUtil", thread "Thread[main,6,main]" for thread "Thread[org.eclipse.jdt.internal.ui.text.JavaReconciler,1,main]" to finish starting bundle "com.sap.ide.dii05.lib_2.0.0.141209113915 [197]". To avoid deadlock, thread "Thread[main,6,main]" is proceeding but "com.sap.ide.dii05.lib.internal.dc.core.EmfDcUtil" may not be fully initialized.
!STACK 0
... and at the end:
!ENTRY com.sap.ide.jvm.check 1 0 2015-03-18 12:03:34.055
!MESSAGE JVM Version Check succeeded.
And the second run:
!SESSION 2015-03-18 12:20:19.226 -----------------------------------------------
eclipse.buildId=@qualifier@
java.version=1.6.0_31
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en
Command-line arguments: -os win32 -ws win32 -arch x86
!ENTRY org.eclipse.ui 2 0 2015-03-18 12:20:24.956
!MESSAGE Warnings while parsing the key bindings from the 'org.eclipse.ui.commands' extension point
!SUBENTRY 1 org.eclipse.ui 2 0 2015-03-18 12:20:24.956
!MESSAGE Cannot bind to an undefined command: plug-in='com.sap.ide.esr.tools.core.ui', id='com.sap.ide.esr.tools.ui.runchecks'
!ENTRY com.sap.ide.jvm.check 1 0 2015-03-18 12:20:37.161
!MESSAGE JVM Version Check succeeded.
!ENTRY com.tssap.util.ui 1 0 2015-03-18 12:20:37.754
!MESSAGE Sap NetWeaver Developer Studio - Platform Feature Version: UNKNOWN
!ENTRY com.tssap.util.ui 1 0 2015-03-18 12:15:37.974
!MESSAGE Sap NetWeaver Developer Studio - Platform Feature Version: UNKNOWN
==> Any idea ?
Best regards.
Vincent.Solved.
It was due to anti-virus... -
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 -
Issues with Agents being logged out.
All the agents on aperticular PIM were logged out and could logback in after approx 7 minutes.Wheni check teh CTIOS logs now its full of the below error message
12.333 ClientMgr[1]::DistributeEvent(eOnNewSkillGroupStatisticsEvent), FAILED to find
Client[0006].
Can you please let me know if this is service affecting or its something critical ?-We are seeing issues with agents trying to log in and getting timeout errors, taking 3-5 times to actually login/JTAPI errors. Supervisor application is having the same issues. We have full IP Visibility from all subnets. The CUCM/CCX servers were put in last August, and we had zero issue up until the past few weeks. Ive validated the agent settings, JTAPI users etc and Ive rebooted the UCCX server as well
-
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. -
IR - Connection Issue to Essbase, client timed out
Ref: essbase server problem
Ref2: Unable to add Essbase Server from Administration Services
I have the same problem as the posts above. There are no conclusions for above posts, does anyone here know how to fix this problem as it seems very common.
In my situation, I'm sure essbase is setup well and everything ran well. I started using IR connecting to essbase and done about 10 reports.
Until today, I am trying to test these reports by sending huge amount of data to Essbase.
Then retrieving the problem below when downloading to results:
Network error [10061]:unable to connect to [server c-noia-131 1423]
the client timed out waiting to connect to analytic services agent using TCP/IP check your connections also make sure that server and port values are correct
Any ideas how to solve this problem?Hey.
Adapter unable to recorginise the Jar file you have deployed, Did you mentioned the JAR file in Provider.xml file ?
Are you able to ping the DB2 server ?
Cheers
Agasthuri -
Share with Vimeo is timing out
I recently upgraded to Yosemite OSX and Final Cut Pro X will not Share with Vimeo. I get a "Vimeo timed out" error. I have been using that for a year now flawlessly and now it won't upload large files. I am a Vimeo Pro user. Size is not a problem.
Any help? I have tried resigning in on Vimeo inside FCPX but it still won't upload.Sorry not to be clearer. I meant the library bundle. When you share>Vimeo, FCP first compresses the movie as an H.264 MOV. That file is saved in the Share Items folder in the library until the upload is complete an the session has been closed out. I've never run into a timed out message with Vimeo – although I don't upload files as large as yours and I usually use the Vimeo uploader after exporting a master file.
Russ -
[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 -
How do I fix problems with iTunes Store timing out when I search for music?
So, I downloaded iOS 7 not too long ago. However, when I tried to do a search on the iTunes Store app, it keeps timing out (it also stalls when I attempt view a song list on a specific album. My phone has no cosmetic or liquid damage, and. I have already performed a soft reset on the phone. Does anybody have a solution, or is this just a bug in the new software that needs to be fixed?
Also having problems connecting to the App Store without it timing out.
Maybe you are looking for
-
I had almost 30 different seasons of tv shows in my library, alot. Now there all gone, my library is blank. My purchases are in my purchasd section on the store but I dont have enough space to download them all over again. I cant figure out what happ
-
Suggestions for "fixes" in next version?
Hi there, I just got my iPhone 3G, I live in Germany but come from Bulgaria and when I type in bulgarian mobile numbers on my iPhone it divides the numbers wrong - it knows the OLD mobile number pattern which is: +359 XX XXXXXX, now the new numbers t
-
How to raise ringer volume on Samsung S4 mini
-
After Yosemite upgrade iMovie won't load iMovie Theater from data drive.
I have my iMovie Lib and Theater on a data disk and the os on an SSD. When I updated to Yosemite and new iMovie, it will no longer us the iMovie Theater on the data disk. It always makes a new file on the SSD in Movies folder. My SSD is not large
-
I am trying to see how the BC4J Tester works. I am using the same project which comes as the sample with JDev. While running It displays a connect window where I specified the connection info and there is another text box at the bottom of the connect