Sending mail slow

All of a sudden, it seems like it takes forever to send a small simple (Text only email)* (Apple Mail: Version 3.0 (912.1/912).
I'm hooked up to "Super road runner". I just did a speed test and the results were: Download= 9185 kbps, Upload 956 kbps. Any ideas??

jabidof wrote:
Maybe this can be helpful to others.
I solved this weird problem by adding manually some DNS server IP addresses to my Airport configuration. This happened to solve the slow sending mail issue.
I'm still a bit puzzled why this can happen on a 21st century OS... Should be smarter than that to my opinion.
Anyway, Mail.app is back on tracks
Great suggestion! To flesh it out some more, I'd be sure to use the ISP's DNS numbers, rather than some third party, in the System Preferences » Network control panel. Then if it doesn't work, call the ISP and get some feedback from them...

Similar Messages

Sending mail slowed down

Last few days, when sending mail, the wheel spins fpr a good 20 to 30 seconds before the router shows sending mail, ie flicking wireless light. Although our speeds are possibly the worlds slowest, it normally starts going straight away. I am on a 384kbps line. ISP is Mweb. They say my line is fine. Line via Telkom. They tell me all is well. Speedtest.net shows ping, .94ms , download , .38Mbps and upload is .11Mbps. It might be my imagination but it could be that when I click ' check mail ' after ' send ' it seems faster. Maybe thats just a timing thing. Any ideas? Thanks, Duncan

Clicking ' check mail ' makes no difference at all. Whatever I send, the wheel next to' sent' spins first for 35 seconds before 'mail activity' shows it's going. Since new, September '08, it's shown in 'mail activity' and went instantly. Or at least started going instantly, time dependant on size. Everything else is fine. Websites as quick as normal etc.

Send Mail is very... very slow!!!

Over the past week I have noticed that when I go to send a message or reply to a message... it is very slow. It is almost similar to when you send a large attachment... the only problem... I am not sending anything except the email.
Any thoughts or suggestions? I just did a fresh OSX install and it is still the same. Very slow. I have a 15/2 internet connection... I have tested that and it is good.
Thanks,
Ronnie

Same problem and found that the a feature in leopard mail accounts caused the problem .. I work from several places and to make it easier to send mail rather than selecting new from everytime I changed the account to allow other servers to be used .. it was slow to send all the time .....then today 4-5 weeks later I decided to change the setting back to this server only. voila.... speed again..
go to mail preferences accounts and tick the outgoing server to use only this server....
I made the change when i got my new Macbook pro....(should have left alone)

Sending mail very slow

Besides the notebook described below in the signature I have a MacBook right next to it. On both, the same three email accounts are configured exactly the same. One account is the IMAP MobileMe (aka .mac) account. The other two are POP accounts, for one of which I have a digital certificate. When I send mail through that account, it can take up a minute before the "busy" icon next to the Sent mailbox for the account disappears and the "whoosh" sound is heard. On the MacBook, the same mail is sent almost instantly. The digital certificate is in a password-protected part of my keychain, so on both notebooks I am prompted -- with almost no delay between pressing the Send button and receiving the prompt -- for that password before the actual send operation begins.
By the way, both notebooks are connected wirelessly to the same Apple AirPort Extreme, so I suspect that the problem is unrelated to the network infrastructure.

Hello Niken:
I fixed a similar problem by using OpenDNS.
http://www.opendns.com/
I think the problem might have been with my ISP, but using open DNS solved the slow mail transmission on both of my macs.
Barry

Everything running extremely slow, cannot send mail

My MacBook Pro (2009) is running extremely slow. I used Disk Utilities and verified and repaired permissions, only 2 found. Everything launches so very slow. Spinning beach ball is there forever. webpages take forever to load and applications take forever to start. Mail is very slow and it appears I cant send mail?????

Hi Linc,
I am using iMac [OS X Yosemite V. 10.10.2] and using Mail app for my email account via Outlook 365 office [Exchange].
Suddenly today, when I send an email, a new folder pop-up under Outbox folder named "on my mac" and the email stays in this folder for at least 15-30 minutes before it goes, and once it's being sent, my "sent folder" doesn't update the sent emails. I have repeated many test emails and run connection doctor but nothing happened!
I did the following steps, non of them worked:
1. Deleted the account and re-created it over 3 times.
2. Restarted the machine.
3. Signed out from iCloud.
4. Moved out com.apple.mail.plist folder while creating the account again.
5. Moved out com.apple.mailServiceAgent.plist folder.
6. Changed the internal & external ports to 25, 465 & 587.
7. Rebuilding.
8. Deleted Cache.db
9. Checked & unchecked "Automatically detect and maintain account settings".
10. Checked & unchecked "Use SSL".
However, I run test emails on MS Outlook app and it worked perfectly, which means that the exchange service is working.
Your help is highly appreciated.
Baz
P.S. Attached some screenshots of my journey!

Mail App sending mail super slow.. ??

I am trying to send mail using my @me account and it sending super slow even for small text. as a test i just wrote test and sent and it was a couple minutes to send. Anyone else experiencing this problem?
I have restarted mail several times and restarted my macbook..
went to gmail to test and sent to my mac address and was instant. but all outgoings from mail app are like syrup
Any help would be greatly appreciated. Having a bit of a meltdown at the moment and would love my mac not to fail me at the worst time as well.....aarrggghh

An issue with DNS can arise when sending via the SMTP, and it will likely be different for different ISPs. To confirm this is the problem, please prepare two new messages for sending, before sending either of them. Then click to send the first one, and as soon as you hear the swoosh that it has gone out, click to send the second one. If the second goes out almost instantaneously, then it is correctable with a change in DNS.
Two citations, different approaches, but really both addressing DNS:
http://discussions.apple.com/thread.jspa?messageID=9641256&#9641256
and
http://discussions.apple.com/thread.jspa?messageID=8974547&#8974547
This happened for many people with the beginning of Mail 3 in Leopard, but some may only experience in Snow Leopard and Mail 4.x.
Two recent experiences people had can be found at:
http://discussions.apple.com/thread.jspa?messageID=11962726&#11962726
and
http://discussions.apple.com/message.jspa?messageID=12099641#12099641
I am not sure how to advise you in New Zealand, but your ISP should be able to provide you with explicit DNS addresses to enter. This not impact webmail sending, btw.
Keep us posted.
Ernie

Sending mail very slow after 10.9.5 upgrade.

I upgraded to 10.9.5 yesterday and ever since then, sending mail (using Mail.app) is very, very slow or the emails do not get sent and stay stuck in my Outbox.
Is anyone else experiencing this?
I've deleted my iCloud account and re-added it and it didn't help.

Troubleshooting sending and receiving email messages
Troubleshooting sending email messages

Sending Mail is getting slower and slower.

When I try to send mail it takes 3 tries for it to go through. i have to click in use selected server twice and then it will send. the problem se3ems to be getting worse. i assume there is a folder someshere I need to trash in order to fix this but I don't know which one.
Thanks for your help

What ISP are you trying to reach?
Did you check with connection doctor from the menu Window?

Sending mail is very slow

Recently sending mail from my pop account mailbox seems to be taking ages, even for short messages. It has always been pretty quick until just recently, when the rotating cog keeps rotating for about a minute or two for one small message. Is this something I can fix on my computer or is it the server? Linda

This sounds like the same thing that's happening here at my job. Just in the past few weeks everyone has noticed that when they send an email it takes several minutes for the email to actually be sent.
An like the other poster said, there doesn't seem to be any problems when using webmail. I tested it out and sent a message from my account on webmail and I was watching the mail queue on the server. As soon as I sent it from webmail it was in the queue. When I send a message using the Mail App it doesn't appear in the server queue until it is actually sent from the Mail App, which can take over a minute for me, and I've heard other people say it's taking up to 2 hours from their computers!
I hope there's some sort of fix for this. I'm willing to bet it's not just us having this problem...

Can send mail but it's very slow

Why does OS 10.5.8 mail (3.6) send the simplest e-mail so slowly? Is there a fix for this?

I have the same issue however none of the DNS numbers I have tried changed anything. I have two computers that use bellsouth accounts. Both machines are on the same network but only one sends mail slowly. ????? It takes 30 seconds to contact and send a mail message on one machine and 1 second on the other. I changed DNS numbers from OPEN, bellsouth and Google without any change.
Any help/thought are welcome.

Cannot send mail after upgrading to Lion

Can anyone help.
I upgraded to OS X Lion, and since then I cannot send mail from any of my accounts.
Nothing wrong with them. I can access, receive and send with othe Mail programs, as well as from my iPhone and iPad.
I have deleted, and reconfigured my accounts, and no luck.

I am having the exact same problem as Steve Kennedy a few posts back.
"When I press send I watch the fan for a couple of minutes before seeing the error message that invites me to select another server or try later. The outgoing mail server that shows up as being unusable is MobileMe (MobileMe). When I select smtp.me.com, I can send. Sometimes I can even send a couple of messages before the problem returns.
I'm using Lion and Mail 5.0 (1244.2/1244.3) on my iMac (mid-2010) and Verizon FIOS. Never had this problem with Snow Leopard or earlier. Don't have it with my MacPro running Snow Leopard on the home wireless network. Don't have it when using MobileMe mail on the Web, but that's a slow alternative."
I am getting REAL tired of the Lion quirks. <y desktop rearranges itself when it feels like it. Nothing consistent or repeatable. The folders just all appear on the right side and disregard how I have them organized on the desktop. I have set all of the recommended settings to no avail. A mind of it's own.
Help us Apple. Mail is almost unusable.

Leopard Mail and Filemaker pro - "Send Mail" is s-l-o-w

When I upgraded to Leopard, I began having a problem with the "Send Mail" function in Filemaker Pro, even after I upgraded to the latest version. Previously, sending mail with an attachment to 300 BCC addresses went very quickly - about 10 seconds. Since Leopard, I have begun seeing each address get loaded into the BCC line, an operation taking 20 minutes or more. Has anyone else seen this, and are there any suggestions on how to remedy it?

You might try this.
MAC Mail, for some reason, wants a DNS server setting in the network setup.
Under System Preferences, go to Network and add your DNS numbers for your ISP Server. Get the right numbers from your ISP. I did a search for "DNS" on the ATT/YAHOO member web site.
This fixes the slow checking and sending of mail....It also fixes problems where mail sends slow and may give Authentication errors.
I spent many hours on this and finally the answer was posted on this forum.
Public DNS servers are less likely to be changed. They have been tried and do work. Nobody knows why.
For Public DNS servers look at.
http://www.tech-faq.com/public-dns-servers.shtml

Send Mail with Multiple Attachment

How to send mail with multiple attachment. The documents are in a table column BLOB. Read and attach in to mail directly.
We dont want save the documents into hard disk and attach to mail. Please Help
If you have java procedure or Pl/Sql Procedure. I think pl/sql cant. So please mail me code to [email protected] mail id. Thank you.
Thanks in advance
Selvam

Hi all
Thanks for your reply, already tried this methods, Its not working for my requirements. Because my attachment is can be any type like pdf,doc,txt,xls,jpg,.
And also the Utl_mail is very slow. Its using RAW type.
I can use the javamail package to solve this problem, this javamail package needs to download into server from there you can attach thus documents into mail. But I want fetch the documents and ate the same time I want attach to a mail. Like yahoo attach or msn attachment.
Thank you,
Selvam

Setting Up Mailserver to received and Send Mail for external Network

I have a G5 currenty running 10.3.9 Server with Mail services run and working fine, we are upgrading to 10.4 Server and would like our Sales Reps the ability to send and Receive mail from outside the office. How do I configure my server, Router, ISP and/or Mail clients to do this??? we are currently able to recieve mail from outside just not send.

I cannot find the Line #submission inet n - n -- smtpd in the Main.CF file...here is what I get when I open it
# Global Postfix configuration file. This file lists only a subset
# of all 250+ parameters. See the sample-xxx.cf files for a full list.
# The general format is lines with parameter = value pairs. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
# POSTFIX STILL WORKS AFTER EVERY CHANGE.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
#soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /private/var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
# Note: you need to stop/start Postfix when this parameter changes.
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4
# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain.
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see sample-virtual.cf).
# 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
# sample-smtpd.cf).
# 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
#mydestination = $myhostname, localhost.$mydomain $mydomain
#mydestination = $myhostname, localhost.$mydomain, $mydomain,
# mail.$mydomain, www.$mydomain, ftp.$mydomain
# REJECTING MAIL FOR UNKNOWN LOCAL USERS
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination and $inet_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 sample-local.cf).
# 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
# $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
unknown_local_recipient_reject_code = 450
# 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 file sample-smtpd.cf.
# 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 restriction in the
# file sample-smtpd.cf 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,
# - 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 in the file sample-smtpd.cf.
#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 = uucphost
#relayhost = [an.ip.add.ress]
# REJECTING UNKNOWN RELAY USERS
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a [email protected] address.
#relay_recipient_maps = hash:/etc/postfix/relay_recipients
# INPUT RATE CONTROL
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 50 SMTP server process
# limit, this limits the mail inflow to 50 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
# Insert text from sample-rewrite.cf if you need to do address
# masquerading.
# Insert text from sample-canonical.cf if you need to do address
# rewriting, or if you need username->Firstname.Lastname mapping.
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
# Insert text from sample-virtual.cf if you need virtual domain support.
# "USER HAS MOVED" BOUNCE MESSAGES
# Insert text from sample-relocated.cf if you need "user has moved"
# style bounce messages. Alternatively, you can bounce recipients
# with an SMTP server access table. See sample-smtpd.cf.
# TRANSPORT MAP
# Insert text from sample-transport.cf if you need explicit routing.
# ALIAS DATABASE
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
# It will take a minute or so before changes become visible. Use
# "postfix reload" to eliminate the delay.
#alias_maps = dbm:/etc/aliases
#alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases
# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi". This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
#alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
# ADDRESS EXTENSIONS (e.g., user+foo)
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5) 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".
#mailbox_transport = lmtp:unix:/file/name
#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
# and unknown@[$inet_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. See the file
# sample-smtpd.cf for an elaborate list of anti-UCE controls.
# 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 the sample-filter.cf file.
#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".
# By default, Postfix maintains deferred mail logfile information
# only for destinations that Postfix is willing to relay to (as
# specified in the relay_domains parameter). For other destinations,
# Postfix attempts to deliver ALL queued mail after receiving the
# SMTP "ETRN domain.tld" command, or after execution of "sendmail
# -qRdomain.tld". This can be slow when a lot of mail is queued.
# The fast_flush_domains parameter controls what destinations are
# eligible for this "fast ETRN/sendmail -qR" service.
#fast_flush_domains = $relay_domains
#fast_flush_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 = 10
# 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
xxgdb $daemon_directory/$process_name $process_id & sleep 5
# If you don't have X installed on the Postfix machine, try:
# 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
# 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/sbin/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
# 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.
sample_directory = /usr/share/doc/postfix/examples
# readme_directory: The location of the Postfix README files.
readme_directory = /usr/share/doc/postfix
# THE FOLLOWING DEFAULTS ARE SET BY APPLE
# bind to localhost only
inet_interfaces = all
# turn off relaying for local subnet
mynetworks_style = host
# mydomain_fallback: optional domain to use if mydomain is not set and
# myhostname is not fully qualified. It is ignored if neither are true.
mydomain_fallback = localhost
myhostname = jamestownpress.com
mailbox_transport = cyrus
enable_server_options = yes
luser_relay =
maps_rbl_domains = dun.dnsrbl.net
message_size_limit = 0
mydestination = $myhostname,localhost.$mydomain
smtpd_use_tls = no
smtpd_enforce_tls = no
smtpd_tls_loglevel = 0
smtpd_sasl_auth_enable = yes
smtpd_use_pw_server = yes
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination,permit
smtpd_pw_server_security_options = plain
server_enabled = 1
relayhost =
smtpd_client_restrictions = permit_mynetworks reject_rbl_client dun.dnsrbl.net permit
always_bcc =
mynetworks = 127.0.0.1/32,192.168.0.0/16,192.168.1.98,192.168.1.3,192.168.1.13,192.168.1.5,1 92.168.1.22,192.168.1.18,192.168.1.41
content_filter = smtp-amavis:[127.0.0.1]:10024
so what do I need to change

Please help, how to send mails faster / send more mails per hour

hello,
in my application i am using mail sender class i have created to send mail to the users to participate in a survey. following is the code for it. i would like to know if there is anything wrong in it coz it takes to much time to send the mails it is taking 2 minustes to send 6 mails i.e 360 mails per hour only.
following is how i instantiate the mail sender class and then generate a http link string dynamically as it is different for all the user.
//////////class where mail sender is instantiated////////////////////
try
setConnection();
st=con.createStatement();
rs=st.executeQuery("select * from "+CNAME+"_campaign");
String SurveyT = new String();
while(rs.next())
     SurveyT = rs.getString(2);
rs.close();
rs=st.executeQuery("select * from "+CNAME+"_user");
ss = new MailSender();
while(rs.next())
     String userid = rs.getString("userid");
     String password = rs.getString("password");
StringBuffer message = new StringBuffer(BodyText.getText().trim());
if(SurveyT.equals("invitational") || SurveyT.equals("single"))
                                        message.append( "\n" + "http://"+IPadd.getText().trim()+"/"+CNAME+"/servlet/login?username="+userid+"&passw="+password);
                                        ss.send(FromField.getText().trim(),userid,SmtpServerID.getText().trim(),MailSub.getText().trim(),message.toString());
else if(SurveyT.equals("general"))
message.append( "\n" + "http://"+IPadd.getText().trim()+"/"+CNAME+"/Index.html");
ss.send(FromField.getText().trim(),userid,SmtpServerID.getText().trim(),MailSub.getText().trim(),message.toString());
st.close();
this.dispose();
catch(SQLException sqlex)
JOptionPane.showMessageDialog(null,sqlex.getMessage());
//Mail Sender class/////////////////
import javax.mail.*;
import javax.mail.internet.*;
import java.util.*;
import javax.swing.*;
public class MailSender
     String sentAddr,fromAddr,smtpServer,body,subject;
     public MailSender()
     //function send to send the mail
public void send(String from,String to,String smtps,String subj,String messagetext)
          fromAddr=new String(from);
          sentAddr=new String(to);
          smtpServer=new String(smtps);
          body=new String(messagetext);
          subject=new String(subj);
          try
               Properties props = System.getProperties();
               props.put("mail.smtp.host",smtpServer);
     Session session = Session.getDefaultInstance(props,null);
Message msg = new MimeMessage(session);
               msg.setFrom(new InternetAddress(fromAddr));
msg.setRecipients(Message.RecipientType.TO,InternetAddress.parse(sentAddr,false));
     msg.setSubject(subject);
     msg.setText(body);
msg.setHeader("Survey","MailCheck");
msg.setSentDate(new Date());
     Transport.send(msg);
     catch(MessagingException mex)
          JOptionPane.showMessageDialog(null,mex.getMessage());
}

Lots of variables here....Also my maths says only 180 per hour.... i.e. three a minute.
1) you are using a database to get info from. What is the average response time of the DB server? Looks like you are doing one SQL then reading the result table but does the initial SQL take a while?
2) how much data are you passing on to the SMTP server and how fast/slow is the link to that SMTP server? Work out the absolute max amount of data you can transfer over the link then get your average message size and work out a VERY theoretical Max number of messages a minute. Note that real life might approach 80% of this taking TCP/IP and SMTP overheads into account.
3) What sort of load is the SMTP server under? If it's busy you will be only getting a fraction of whatever bandwidth is available. Depending on its design it may be trying to deliver the first message you sent it while you are still pumping more messages down to it. SMTP servers may limit the number of connections per minute from another machine in order to defeat a denial of service attack. Your code makes a connection per email so this may have relevence here.
4) Raw horsepower always helps. When I write stuff to do things like this there is no nice GUI screen etc. Just basic Java that if it has to will write a log if something goes wrong. Maybe just maybe a counter on STD out to show it is still actually doing something. Keep the number of classes used down to the bare minimum. In the old days we used to spend days paring code to the bone - a skill somewhat lost these days.
Hope this gives you some help in finding the bottleneck.
Cheers,
SH

Sending mail slow

Similar Messages

Maybe you are looking for