Sending with other IP address

Hi,
I'm planning to develop an network audit tool and I'd like to know if it's possible to send udp datagrams using another IP address as the source address.
In relation with this: is this possible to do some "editing" in outbound ip packets?
Thanks in advance,
chabral

I could be wrong but I dont think java can manipulate lower OSI layers. I beleive java creates the packet and hands it off to the OS for processing, and THAT'S where the header info comes in.
Spoofing UDP is a trivial thing using c on a linux box.. Anyone ever successfully spoof TCP with ANY os/programming language thru a router using a current OSPF/RIP protocol? By successful, i mean you receive the ACK's AND don't knock the spoofed IP's owner off the network. THAT would be a noteworthy feat..

Similar Messages

My outlook is sending two invites in the icloud calandar. How can I stop this? I ony want the email send with my email address not the apple email

My MS outlook on the PC is sending two invites in the icloud calandar. How can I stop this? I ony want the email send with my email address not the apple email.

My phone is the 4. Not the 4s. And I went there but it's nowhere the option to delete from server.
I only see: ask before deleting and it's on.

Exchange 2007 Sending with Second Email Address (trying to use Send As)

I support a company who just bought another company. I'm trying to bring a couple of users' old email addresses in to Exchange and have it work with their old and new addresses. They can receive mail under old and new accounts just fine. Sending
under the old address is the problem. They still need to send under the old address for existing contracts.
My first attempt was to create a distribution group, give it the user's old email address, and then give the user "send as" rights for the group using the Exchange Management Shell. I ended up with the same error I'll detail below.
My next (and current) attempt was to set up a shadow user in AD with the old email address and then give the user "send as" rights to the shadow mailbox. I assigned the "send as" permission by right-clicking on the mailbox and choosing
"Manage Send As Permission" and then adding the real user to the list. In Outlook, I clicked From and then choose the shadow user account from the Global Address Book. This added the address to the From drop down box.
This works, once... Every time I restart the Information Store service, I can get one email to send out successfully. Here is the error I get on every other attempt. Notice it says "send on behalf" in the error. Maybe I'm not
setting it up correctly in Outlook? I didn't make Outlook screenshots but you'll find my AD and Exchange setup screenshots below.
Thanks for the help.
(also posted at http://forums.msexchange.org/m_1800602162/mpage_1/key_/tm.htm#1800602162)
***ERROR START***
Delivery has failed to these recipients or distribution lists:
Tripp Beasley
You are not allowed to send this message because you are trying to send on behalf of another sender without permission to do so. Please verify that you are sending on behalf of the correct sender, or ask your system administrator to help you get the required
permission.
Diagnostic information for administrators:
Generating server:
[email protected]
#MSEXCH:MSExchangeIS:/DC=local/DC=XXXXXXXXXX:XXXXXXXXXX[578:0x000004DC:0x0000001D] #SMTP#
***ERROR END***

open the list of previous recipients and select the ones you need by holding the command button. then press "add to address book".

Msmtp sends with empty FROM address

Hello,
I set up msmtp, and the php mail function sends messages successfully, but the FROM address is missing.
I followed the howto at http://forum.slicehost.com/comments.php … ionID=2338.
Here's my sysconfig /etc/msmtprc:
account default
host smtp.mydomain.com
port 25
timeout 30
auth on
user [email protected]
password secret
auto_from off
from [email protected]
maildomain mydomain.com
tls off
logfile /var/log/msmtp.log
and the php code for sendmail:
<?php mail('[email protected]', 'test', 'hi, this is a test!'); ?>
Here's the mail I received using the php mail function:
From - Fri Sep 25 00:21:41 2009
X-Account-Key: account6
X-UIDL: 1253830343.5295.mail6.worldserver.net,S=426
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
X-Mozilla-Keys:
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: (qmail 5293 invoked by uid 89); 24 Sep 2009 22:12:23 -0000
Received: by simscan 1.3.1 ppid: 5252, pid: 5286, t: 0.5040s
scanners: attach: 1.3.1 clamav: 0.91.1/m:44/d:4513
Received: from unknown (HELO localhost) ([email protected]@some-ip-address-i-dont-want-to-show)
by 0 with ESMTPA; 24 Sep 2009 22:12:22 -0000
To: [email protected]
Subject: test
hi, this is a test!
As you can see, the return address is correct, but the FROM envelope is missing the address.
Finally, here's the /var/log/msmtp.log entry:
Sep 25 00:21:39 host=smtp.mydomain.com tls=off auth=on user=[email protected] from=[email protected] recipients=[email protected] mailsize=58 smtpstatus=250 smtpmsg='250 ok 1254068455 qp 23429' exitcode=EX_OK
I also tried auto_from on in the config with the same results. What's wrong here?
Last edited by bitpal (2009-09-27 16:34:38)

bitpal wrote:
Great, that works!
Another thing: If I have several accounts in my msmtprc file how can I select the one I want when I call the mail function?
not sure how php fits in... but
msmpt -a accountName
works for me. and adding to the bottom of ~/.msmtprc:
default : accountName
will set accountName to be used when no -a is passed.

HT5538 Why is my iMessage not working with other email address just says verifying but nothing happens been a week, 4 devices only I

iMessage not working on all my 4 devices use separate emails now cannot use them it just says verifying same with FaceTime?

Hey Mgpr,
There's an article that helps with troubleshooting steps for issues activating iMessage that I think is worth a look. See if any of the suggested steps work for you:
iOS: Troubleshooting FaceTime and iMessage activation
http://support.apple.com/kb/TS4268
Sincerely,
Delgadoh

Use Gmail to send from your other email addresses

hello,
i have setup gmail account on my Q10, but i can not use it's "send from other email addresses" functionality.
description of the situation:
i have my own domain with configured email forwarding to gmail account. i publically use only domain email address so in fact no body knows that this really goes to google. on the other side i have configured google to send from different account, so i use SMTP of my domain. in general it looks like gmail is just my mail application and mail storage - my domain has really thin limits. it has the advantage that i really send form my domain address, receiver sees only my domain address but the mail goes through google, so i use gmail's interface which i like and also message is stored in "Sent" folder of gmail.
the only idea which comes to me to configure similar setup on Q10 is to configure same account twice, but with different "from" address on the other account, but won't it be than i get double notification per one email?
regards,
mark

Hi all,
This can be also a general question without any connection to the Gmail service, and I formulate itt following way:
Is the email client of the bbq10 capable for sending emails with different from email adresses?
All the most popular email clients are capable for that, on a special way the former blackberry bold was also capable for that function!! I know, i used this function.
I have ca 10 email adresses, which are only aliases and all email will forwarded to one mailbox. That means only once downloaded, and when i reply to or forward an email i can always choose the from adress, as i would write from a different email account.
So whatsup dear blackberry service provider, are you one step back as also with the disappearing of the good old BIS service?
Despite of this i like bbq10 very much
Thanks for all kind of help

Hi, I have just set up my domain email address with google and Im trying to set up mail on my mac. Its receiving mail but its not letting me send emails from that address. I have tried quite a few solution but cant figure it out. Can anyone help

Hi, I have just set up my domain email address with google and Im trying to set up mail on my mac. Its receiving mail but its not letting me send emails from that address. I have tried quite a few solution but cant figure it out. Can anyone help

Hi Lawrence1981,
Thanks for visiting Apple Support Communities.
You may want to check this article for additional troubleshooting steps:
OS X Mail: Troubleshooting sending and receiving email messages
http://support.apple.com/kb/ts3276
Cheers,
Jeremy

[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

My daughters imessage on her ipod touch has just stopped working - to get it going again I reset it with my email address but this doesn't allow her to send messages to any of her contacts. When I try and put her email back in it says it can't verify it

My daughters imessage & face time on her ipod touch has suddenly stopped working. The only way i could get it going again was to reset it up with my email address. This will not allow her to send messages to any of her contacts in her addess book. I have tried to set up her email (which she previously used successfully) but it will not allow this it states 'unable to verify email because it is already in use' - anyone any ideas its is driving me mad !!

Try here:
iOS: FaceTime is 'Unable to verify email because it is in use'

How do I send an email with a group address and not show the addresses/names of the recipients?

How do I send an email with a group address and not show the addresses/names of the recipients?

Use BCC. That's blind carbon copy. And copy paste the address into the BCC field. It really depends what e-mail program you use how to enable BCC.

Sending Email with current IP address in it

I have done scripting in LotusScript for Lotus Notes. When I was younger, I did BASIC, Pascal, Assembler. I am trying to figure out Applescript and how it relates with each application.
Currently, I am trying to create an Applescript which will, upon a receipt of an email from a particular user (me) and a particular subject, would send an email back to the user with the current external IP address of my machine. I already have the "hard" part of getting the IP from a script created by Koert Bonte but modified by me:
set GetIP to do shell script "/usr/bin/curl http://checkip.dyndns.org/"
This will receive something like this:
<html><head><title>Current IP Check</title></head><body>Current IP Adress: 1.2.3.4</body></html>
set AppleScript's text item delimiters to ":"
set temp to the second text item of GetIP
This will return with:
1.2.3.4</body></html>
set Applescript's text item delimiters to "<"
set theIP to the first text item of temp
(* This gets the IP address:
1.2.3.4
Now, I can create a rule in Mail to look for my name and subject, what I have not been able to figure out is how to send either a new message back with the IP address or a reply back with same. I would like to see examples of both .<br>
Cube, G4 TiPB, iMac

Hi Zeff,
With Applescripts called from Mail rules you need to use 'on perform mail action' to get the list of messages that triggered the rule. This needs to be in a 'using terms from application "Mail"' block so the processor will understand what 'on perform mail action' means. Generally you would loop through the list of messages (it will be a list even if there is only one iten in it).
So you would wrap a Mail rule script in something like:
using terms from application "Mail"
on perform mail action with messages myMessages
repeat with myMessage in myMessages
-- the body of your script goes here
end repeat
end perform mail action with messages
end using terms from
Using the above, you need to tell Mail as usual if you want it to do something:
using terms from application "Mail"
on perform mail action with messages myMessages
repeat with myMessage in myMessages
-- get ip
set myIP to my fetchIP()
tell application "Mail"
-- make new outgoing message
set mymail to (make new outgoing message at the beginning of outgoing messages with properties {subject:"My IP", content:myIP})
-- add recipient
tell mymail to make new to recipient at beginning of to recipients with properties {address:extract address from (sender of myMessage)}
-- send it now
send mymail
end tell
end repeat
end perform mail action with messages
end using terms from
on fetchIP()
try
set myIP to word 25 of (do shell script "curl checkip.dyndns.org")
on error
try
set myIP to word 1 of (do shell script "curl www.showmyip.com/simple/")
on error
display dialog "External IP check failed."
end try
end try
return myIP
end fetchIP
I used a handler called fetchIP to call the machine's IP. Note this is similar, but different to yours. Then make a message in Mail with the subject 'MyIP' and the body of the message as the IP. Then add the recipient as the sender of the message which triggered the rule. Finally send the message.
To add the contents of the original message take a look at Mail's Applescript dictionary for 'content'.
Best wishes
John M

When I try to send mail to multiple addresses, it tells me it cant send with selected server. It sends mail to one address fine.

When I try to send mail to multiple addresses, it tells me it cant send with selected server. It sends mail to one address fine.

contact your email service provider and ask them (it might treat multiple e-mails as SPAM)

HT5557 since i updated my Apple ID with correct email address I can now only send imessages to email addresses and not iphone numbers - any idea how to fix this problem ?

since i updated my Apple ID with correct email address I can now only send imessages to email addresses and not iphone numbers - any idea how to fix this problem ?

You might want to try contacting Apple for assistance by going to https://expresslane.apple.com, then click See All Products and Services>iTunes>iTunes Store>Passwords & Security Questions>Lost or Forgotten Apple ID password. They should be able to explain what's going on and help you reset the password for the old ID if necessary. The call should be free.

I updated my iPhone 4S weeks ago and today it said I needed to update it again, so I did. Now when I send iMessage it comes up with my email address and not my number. How do I fix this?

I updated my iPhone 4S weeks ago and today it said I needed to update it again, so I did. Now when I send iMessage it comes up with my email address and not my number. How do I fix this?

The Snow Leopard 10.6 DVD should still be available from Apple for $20. You will have to call Apple Customer Care 1-800-692-7753 or 1-800-676-2775 to purchase it. It may still be in the Legacy Products list. The App Store which is required to download 10.7 or 10.8 is part of the 10.6.6 update.
If they no longer have any in stock you will have to buy it from eBay or Apple resellers that still have stock. But you will have to pay a premium since the DVDs are no longer being made. Snow Leopard DVDs are already up to $100 on Amazon.
http://www.ebay.com/sch/i.html?_nkw=10.6+snow+leopard&_sacat=0&_odkw=mac+os+10.6 &_osacat=0

Send from other e-mail address in Mail

I've some e-mailaddresses from domains (f.e. [email protected]) that do nothing more than forward to my private e-mailadress (f.e. [email protected]). Can I configure Mac Mail so that I can send e-mails with this forwarding-address (being [email protected]) in the FROM field as well as in the REPLY to field? How can I do that?

You should be able to do this, except in rare cases where the SMTP of your private address is a factor. What have you tried? See:
http://docs.info.apple.com/article.html?path=Mail/4.0/en/9973.html
The in the pull down beneath addresses you can choose. You have to think about what you want in the Full Name entry alongside the alias. Also, depending upon the way your SMTP works, look in the Long Headers to see if your private email is revealed somewhere.
If those Domains addresses could receive email, then you could set up the account separately, and select to have it never check for New Mail, and only send with it. That would be the best way.
Ernie

Sending with other IP address

Similar Messages

Maybe you are looking for