Restrict by recipient

Is it possible to restrict functionality to a group by the person they are collaborating with?
For example, if there were three groups, developers, testers, and support. And we wanted to set it up so:
developers could only initiate a chat with support support
but
support could initiate a chat or screen share or whiteboard with developers
and
developers could initiate a chat or screen share or whiteboard with testers
but
testers could initiate only a chat with developers
So it is a different set of permissions based on who you wanted to collaborate with. Is this possible with just Lync 2013?

Hi,
For Lync 2013, it is not supported the functions you said above. On Lync Server 2013, you can only use the AD attribute called msRTCSIP-GroupingID to separate by groups. The users with different value of msRTCSIP-GroupingID can’t search others with user
name but only the complete sip address.
More details:
http://blogs.msdn.com/b/jcalev/archive/2012/06/07/partitioning-lync-address-book-using-msrtcsip-groupingid.aspx
For your requirement, you may use Lync Server SDK and you can post a case on MSDN forum and there are more developing experts will help to confirm if it could be achieved. Thank you for your understanding:
http://social.msdn.microsoft.com/Forums/en-US/communicatorsdk/threads
Best Regards,
Eason Huang
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Eason Huang
TechNet Community Support

Similar Messages

Restrict Goods Recipient Field in MIGO "MSEG-WEMPF" to 10 Characteristics

Hi Experts,
The field length of "Goods Recipient field - MSEG-WEMPF" in GR (MIGO Transaction) is 12.
I need to restrict the user to enter only 10 characteristics for Goods Receipent field.
If User Enters more than 10 characterisics system should through an Error Message.
Is there any way to meet this requirement.
Any Input is Highly appreciable.
Thanks and Regards,
Selvakumar.M

Hi,
For this you have to take help of ABAPer.
Since field 'WEMPF" is SAP Standard and is of 12 character.
Go to SE11, here enter field "WEMPF" in Table and click on "Display"
It will show you domain as "WEMPF", double click on this, under Formatting Subscreen, you will get No. characters as 12
Here ABAPer can change it to 10 which will restrict users to 10 character only.
But to change this, you need Access Code.

Restricting email recipient domain with content filter

Gents,
I am looking to restrict email receipient domain to two with the help of content filter instead of using RAT table.
Please help me out.

I understand that you want mail to be rejected for all but 2 Recipient users/domains. You also want to declare the users/domains via a Filter instead of in the RAT. This is not recommended, here is why:
- If you set the RAT to 'All Other Recipients' to 'Accept', other hosts may believe the ESA is an 'Open Relay' and may refuse mail from its IP.
- Bouncing mail after acceptance can cause 'backscatter' emails. This is where a mail server redistributes spam via bounces and it will cause some hosts to reject your mail.
- If done incorrectly, can cause valid mail to bounce.
- If done incorrectly, can make your ESA an Open Relay that can be abused by others.
If you still wish to proceed knowing that the above risks, here are the high-level steps:
1) Set 'All Other Recipients' to 'Accept' in RAT
2) Create a new Incoming Mail Policy
- Add the valid users and/or domains to this new Policy
3) Create new Incoming Content Filter:
- Rule: leave empty
- Action: Bounce
4) Disable all scanning on Default Incoming Mail Policy
5) Apply the new Filter to the Default Incoming Mail Policy
6) Verify that the new Incoming Mail Policy has appropriate scanning enabled
This method works by accepting all mail sent to the ESA, even if it is for a domain you do not control or for an invalid recipient for a domain you do control. When the messages reach the Incoming Mail Policies, valid recipients will match on the new Policy while every other address matches the Default Incoming Mail Policy. Using the Policies in this way is required so that the message is 'splintered' before processing through most scanning features. Now only users/domain that do not match your new Policy will be Bounced by the Content Filter.
Again, I wish to stress that I do _not_ recommend this approach: it is far safer to simply list the valid users or domains directly in the RAT.
- Jackie

How to Restrict Max Recipient for Inbound in Exchange 2010

Hi,
I want to restrict my inbound mails which is having more than 10 recipients (it may be TO,CC & BCC) in my Exchange 2010.
I set the limit to 10 in the following area.
1.Mailbox
2.Organization
3.Connector (for Receive connectors only)
4.Transport server
But still external users send a mail to more than 10 of our users.
Accepted domain is configured as an internal relay domain.

Hi,
Based on my knowledge, we can't restrict the inbound recipients number in Exchange server. What we can do is restrict the outbound recipients number. For an example, if you set the value of RecipientLimits to 10 for user1, then user1 can't send an message
with more than 10 recipients, but the setting can't have an effect on receiving messages. Your understanding will be appreciated.
Hope my clarification can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

SRM recipient role restricted to plants

Hi
In SRM the organizational levels available in authorizations to the 'Recipient role' consist of 'Purch.org' and 'Purch.grp'.
How do I restrict the role to certain plants?
I tried adding the authorization object M_BBP_IM_1 to restrict actions according to plant but anyone with the recipient role can still see all purch.orders.

Hi
Sorry for the delay - I had to get back to my costumer to try out your suggestion.
Unfortunately it does not solve the problem. The goods recipient role does not automatically check for Plant. - then I would have to use the BADI too - and it would take a lot of maintenance, since we eventually will have 12 different hospitals with each 3 plants.
I need to create som recipientroles, that can be restricted to different plants.
Do you or anyone?? have guidelines to creating an authorization object, that restricts that role to certain plants?
BR
Astrid

Restrict recipient in Extended Notification

Hi Gurus,
We have configured extended notifications and its working fine. We recently done roll out for some other countries as well and dont want the exteneded notificatins for few countries.
Can I use the class CL_HRASR00_WF_NOTIFICATION_EX and method IS_RECIPIENT to do this? Please help.
Thanks,
Vijay

Hi,
This is fairly well documented in the online help
http://help.sap.com/erp2005_ehp_05/helpdata/EN/d5/581ee8d56f1247bf34cfcd66d16d81/frameset.htm
So please check this source first and if things are still unclear feel free to post a followup message.
Kind regards, Rob Dielemans

Lion Server postfix mail not being delivered to mailboxes. "SMTP restriction `reject_invalid_helo_hostname' after `permit' is ignored" and "connect to private/policy: Connection refused" errors.

All, Im stumped. In fact I have been on the phone with Apple Support and this has been escalated to the top engineers, as I think its got them too..
Anyway, here is my problem..
I'm running an Mac Mini with OS X 10.7.4 Server. I have had mail running on it for 2 months or so, without any issues. The mail was actually migrated from 10.6 in March, and It actually went smoothly. I have 3 domains which all recieve mail and they all work (or did up until 2 weeks ago)..
So the story is this.. I can send mail from my domains, without issue. imap and dovecot must be working.. cause all the stored mail, can be read with the mail IMAP client.. I can even transfer mail messages from one mailbox to another with Mail client. Sending mail is a breeze, it still works and the recipients still recieve their mail. But I noticed I wasnt getting any mail at all from those mailboxes... no mail, no spam, nothing.. which is unusal. I fired up Server admin and checked out the SMTP log, and this is what it showed for every email recieved: (xxxxxx is just me hiding sensitive info)
Jul 21 14:25:20 xxxxxxxx postfix/postscreen[65857]: CONNECT from [17.158.233.225]:41909
Jul 21 14:25:26 xxxxxxxx postfix/postscreen[65857]: PASS OLD [17.158.233.225]:41909
Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: connect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: warning: restriction `reject_invalid_helo_hostname' after `permit' is ignored
Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: NOQUEUE: reject: RCPT from nk11p03mm-asmtp994.mac.com[17.158.233.225]: 451 4.3.5 Server configuration problem; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<nk11p99mm-asmtpout004.mac.com>
Jul 21 14:25:28 azathoth postfix/smtpd[65858]: disconnect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
Ok, now what is odd, is these rejected messages are not even appearing in the mail queue in Server Admin. I have no idea why there are not being delivered
Ive checked my postfix main.cf file and master.cf files they both look ok.. Ive even replaced them with the main.cf.defualt.10.7 and master.cf.default.10.7 files and to no avail... same problem..
So in summary
I can send mail out
IMAP is working on the client end (thus dovecot is) exsisting stored emails can be accessed, read, moved unread etc..
mail is coming into the sever, but its being rejected. there is NO rejection email sent back to the sender.
mail is recieved by postfix, but cyrus isnt doing anything with it.. I have no idea where it goes...
Could anyone shed light on this...
my main.cf file:
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
# The general format of each line is: parameter = value. 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,
azathoth:postfix root#
azathoth:postfix root# less main.cf
azathoth:postfix root# more main.cf
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
# The general format of each line is: parameter = value. 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 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,
#       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]
# 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
# 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

Ok 1st one. The warning restriction message relates to this line in main.cf:
smtpd_helo_restrictions = permit_sasl_authenticated permit_mynetworks check_helo_access hash:/etc/postfix/helo_access reject_non_fqdn_hostname reject_invalid_hostname permit reject_invalid_helo_hostname
The last reject occurs after the single word "permit" and is ignored.
However, that's not the problem.
I'm not exactly sure what's happening, but this might be a clue.
It would appear that either postfix is not being able to create the socket for private/policy or it's somehow created with the wrong permissions. You might need to ramp up the debug level to get a better idea.
You could check if it's being created by "netstat -a | grep private/policy" in terminal.
My guess is that it's not being created because there is no setup statement in your master.cf file, but I don't understand why postfix would be looking for it if it isn't set up. Private/policy I think relates to grey listing. Maybe gives you a hint.

How to restrict unwanted customer in Rebate.

Hi Friends,
When Rebate Agreement is created, in the Sales Volume Screen, few other customers other than the Rebate Recipients are also featuring.
How can I restrict the other customer (other than the Rebate recepient in the Agreement) in the Sales volume screen of the Rebate Agreement?
Regards

Hi,
Not sure this would help, but you can check;
Is the rebate condition type access sequence assigned with different keys like customer group etc?
If so, then check the rebate recipient that you intent to provide rebate has customer group (in customer master data) similar to other customers which are also seen in rebate condition type sales volume.
Regards,

Post 03- 10 Migration multiple Relay not Permitted errors from recipient

Hello all - I recently just started a new job in an organization that just recently upgraded from an Exchange 2003 environment, to Exchange 2010. Just within the past week, we finally took down our last 2003 system. Since then, we have received
a good number of bounce back messages from recipient servers with various specific error messages, but with a common theme "smtp relay not permitted". What's strange is at my last employer, we migrated from 2003 to 2007 and I recall having a similar
situation, but I can't for the life of me recall what the solution was.
So far, through a few hours of Google searching, all I have found are sources suggesting that this issue is a recipient server config problem, but I have a very hard time believing that it isn't a problem on my end, with this many of essentially the same
errors popping up. Also - I have noticed that if a user attempts to re-send an email to the recipient that previously bounced back, it will work.
I'm not sure what sort of config info from my server / local network I should share here, but i'll gladly share whatever may be necessary.
Here are a few of the bounce message that we have received (names/email addresses removed)
From: Microsoft Outlook
Sent: Monday, May 02, 2011 8:28 AM
To: name_removed
Subject: Undeliverable: FW: Dodson upkeep
pop-borzoi.atl.sa.earthlink.net rejected your message to the following e-mail addresses:
(recipient removed)
pop-borzoi.atl.sa.earthlink.net gave this error:
Authentication required. Help at http://www.earthlink.net/go/emailsettings
A problem occurred during the delivery of this message to this e-mail address. Try sending this message again. If the problem continues, please contact your helpdesk.
Diagnostic information for administrators:
Generating server: my_server
(recipient removed)
pop-borzoi.atl.sa.earthlink.net #550 Authentication required. Help at http://www.earthlink.net/go/emailsettings ##
From: Microsoft Outlook
Sent: Monday, May 02, 2011 9:47 AM
To: name removed
Subject: Undeliverable: RE: open invoice
mustang.ws9100.net rejected your message to the following e-mail addresses:
recipient removed
mustang.ws9100.net gave this error:
webmail.twgi.net (myserver.twgi.net) [65.242.24.100]:40159 is currently not permitted to relay through this server. Perhaps you have not logged into the pop/imap server in the last 30 minutes or do not have SMTP Authentication turned on in your email client.
A problem occurred during the delivery of this message to this e-mail address. Try sending this message again. If the problem continues, please contact your helpdesk.
Diagnostic information for administrators:
Generating server: myserver.twgi.net
recipient_removed
mustang.ws9100.net #550-webmail.twgi.net (myserver.twgi.net) [65.242.24.100]:40159 is currently not 550-permitted to relay through this server. Perhaps you have not logged into 550-the pop/imap server in the last 30 minutes or do not have SMTP 550 Authentication
turned on in your email client. ##
From: Microsoft Outlook
Sent: Monday, May 02, 2011 5:10 PM
To: name removed
Subject: Undeliverable: message subject removed
UNUSED-216-37-170-254.UNUSED.epix.net rejected your message to the following e-mail addresses:
recipient removed @cargas.com
UNUSED-216-37-170-254.UNUSED.epix.net gave this error:
Unable to relay for [email protected]
Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept e-mail from certain senders, or another restriction may be preventing delivery.
Diagnostic information for administrators:
Generating server: myserver.twgi.net
[email protected]
UNUSED-216-37-170-254.UNUSED.epix.net #550 5.7.1 Unable to relay for [email protected] ##
From: Microsoft Outlook
Sent: Tuesday, May 03, 2011 12:31 PM
To: name removed
Subject: Undeliverable: RE: SMO Destwin Implementation
cpanel-2.host.chi1.int-i.net rejected your message to the following e-mail addresses:
recipient [email protected]
cpanel-2.host.chi1.int-i.net gave this error:
webmail.twgi.net (myserver.twgi.net) [65.242.24.100]:27609 is currently not permitted to relay through this server. Perhaps you have not logged into the pop/imap server in the last 30 minutes or do not have SMTP Authentication turned on in your email client.
A problem occurred during the delivery of this message to this e-mail address. Try sending this message again. If the problem continues, please contact your helpdesk.
Diagnostic information for administrators:
Generating server: twgiex.twgi.net
[email protected]
cpanel-2.host.chi1.int-i.net #550-webmail.twgi.net (myserver.twgi.net) [65.242.24.100]:27609 is currently not 550-permitted to relay through this server. Perhaps you have not logged into 550-the pop/imap server in the last 30 minutes or do not have SMTP
550 Authentication turned on in your email client. ##
From: Microsoft Outlook
Sent: Tuesday, May 03, 2011 5:29 PM
To: name removed
Subject: Undeliverable: FW: Landscaping
host.clearimaging4.com rejected your message to the following e-mail addresses:
[email protected]
host.clearimaging4.com gave this error:
sorry, that domain isn't in my list of allowed rcpthosts; no valid cert for gatewaying (#5.7.1)
A problem occurred during the delivery of this message to this e-mail address. Try sending this message again. If the problem continues, please contact your helpdesk.
Diagnostic information for administrators:
Generating server: myserver.twgi.net
[email protected]
host.clearimaging4.com #553 sorry, that domain isn't in my list of allowed rcpthosts; no valid cert for gatewaying (#5.7.1) ##
From: Microsoft Outlook
Sent: Wednesday, May 04, 2011 8:39 AM
To: name removed
Subject: Undeliverable: FW: Proof of Insurance request
n22.c07.mtsvc.net rejected your message to the following e-mail addresses:
[email protected]
n22.c07.mtsvc.net gave this error:
relay not permitted
A problem occurred during the delivery of this message to this e-mail address. Try sending this message again. If the problem continues, please contact your helpdesk.
Diagnostic information for administrators:
Generating server: myserver.twgi.net
[email protected]
n22.c07.mtsvc.net #550 relay not permitted ##

Also, i FINALLY have an excerpt from our send logfile that matches up to an email bounce:
Bounce message:
From: Microsoft Outlook
Sent: Sunday, May 08, 2011 9:43 AM
To: sender removed
Subject: Undeliverable: RE: Load of gas
server1.cbayhosting.com rejected your message to the following e-mail addresses:
recipient removed ([email protected])
server1.cbayhosting.com gave this error:
<[email protected]>... Relaying denied. Proper authentication required.
Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept e-mail from certain senders, or another restriction may be preventing delivery.
Diagnostic information for administrators:
Generating server: myserver.twgi.net
[email protected]
server1.cbayhosting.com #550 5.7.1 <[email protected]>... Relaying denied. Proper authentication required. ##
Send connector log file:
2011-05-08T13:43:01.761Z,Send mail to Internet,08CDAB5926F2B37D,2,15.32.0.46:9323,69.94.111.23:25,<,"220 server1.cbayhosting.com ESMTP Sendmail 8.13.7/8.13.7; Sun, 8 May 2011 09:43:02 -0400",
2011-05-08T13:43:01.761Z,Send mail to Internet,08CDAB5926F2B37D,3,15.32.0.46:9323,69.94.111.23:25,>,EHLO myserver.twgi.net,
2011-05-08T13:43:01.761Z,Send mail to Internet,08CDAB5926F2B37F,0,,64.18.4.10:25,*,,attempting to connect
2011-05-08T13:43:01.793Z,Send mail to Internet,08CDAB5926F2B37D,4,15.32.0.46:9323,69.94.111.23:25,<,"250-server1.cbayhosting.com Hello webmail.twgi.net [65.242.24.100], pleased to meet you",
2011-05-08T13:43:01.793Z,Send mail to Internet,08CDAB5926F2B37D,5,15.32.0.46:9323,69.94.111.23:25,<,250-ENHANCEDSTATUSCODES,
2011-05-08T13:43:01.793Z,Send mail to Internet,08CDAB5926F2B37D,6,15.32.0.46:9323,69.94.111.23:25,<,250-PIPELINING,
2011-05-08T13:43:01.793Z,Send mail to Internet,08CDAB5926F2B37D,7,15.32.0.46:9323,69.94.111.23:25,<,250-8BITMIME,
2011-05-08T13:43:01.793Z,Send mail to Internet,08CDAB5926F2B37D,8,15.32.0.46:9323,69.94.111.23:25,<,250-SIZE,
2011-05-08T13:43:01.793Z,Send mail to Internet,08CDAB5926F2B37D,9,15.32.0.46:9323,69.94.111.23:25,<,250-DSN,
2011-05-08T13:43:01.793Z,Send mail to Internet,08CDAB5926F2B37D,10,15.32.0.46:9323,69.94.111.23:25,<,250-ETRN,
2011-05-08T13:43:01.793Z,Send mail to Internet,08CDAB5926F2B37D,11,15.32.0.46:9323,69.94.111.23:25,<,250-AUTH LOGIN PLAIN,
2011-05-08T13:43:01.793Z,Send mail to Internet,08CDAB5926F2B37D,12,15.32.0.46:9323,69.94.111.23:25,<,250-DELIVERBY,
2011-05-08T13:43:01.793Z,Send mail to Internet,08CDAB5926F2B37D,13,15.32.0.46:9323,69.94.111.23:25,<,250 HELP,
2011-05-08T13:43:01.793Z,Send mail to Internet,08CDAB5926F2B37D,14,15.32.0.46:9323,69.94.111.23:25,*,2722844,sending message
2011-05-08T13:43:01.793Z,Send mail to Internet,08CDAB5926F2B37D,15,15.32.0.46:9323,69.94.111.23:25,>,MAIL FROM:[email protected] SIZE=8054,
2011-05-08T13:43:01.793Z,Send mail to Internet,08CDAB5926F2B37D,16,15.32.0.46:9323,69.94.111.23:25,>,RCPT TO:<[email protected]>,
2011-05-08T13:43:01.855Z,Send mail to Internet,08CDAB5926F2B37F,1,15.32.0.46:9324,64.18.4.10:25,+,,
2011-05-08T13:43:01.886Z,Send mail to Internet,08CDAB5926F2B37D,17,15.32.0.46:9323,69.94.111.23:25,<,250 2.1.0 <[email protected]>... Sender ok,
2011-05-08T13:43:01.886Z,Send mail to Internet,08CDAB5926F2B37D,18,15.32.0.46:9323,69.94.111.23:25,<,550 5.7.1 <[email protected]>... Relaying denied. Proper authentication required.,
2011-05-08T13:43:01.902Z,Send mail to Internet,08CDAB5926F2B37D,19,15.32.0.46:9323,69.94.111.23:25,>,QUIT,
2011-05-08T13:43:01.918Z,Send mail to Internet,08CDAB5926F2B37D,20,15.32.0.46:9323,69.94.111.23:25,<,221 2.0.0 server1.cbayhosting.com closing connection,
It looks like the address that exchange is attempting to connect to, to send to chesapeake.net is at IP: 69.94.111.23. However, MX lookup for chesapeaeke.net returns mx: mxsrv.chesapeake.net 216.240.101.22

How Do I Secure an Emailed PDF to the Recipient's PC?

Hi All,
How can an emailed PDF be tied to a recipient's PC so that it can only be viewed on that PC?
I do not want to use password control or high-end 3rd party systems, e.g. FileOpen, LockLizard, etc.
I only care about restricting access (viewing), not distribution, editing, renaming, etc. In fact, I'd prefer that
the secured PDF could still be edited and resaved by the recipient, just not viewable on another machine.
Thanks for any help!

It can't be done without using a Digital Rights Management solution (using a server and expensive software).

Problem using distribute form - A recipient is ambiguous

Hello all,
We prepared a form and use distribute form option to send to our coworkers and collect results. They received the email, complete the form and when they try to send back they receive "A recipient is ambiguous" message.
We try to prepare the form in diferent versions with similar results. They are using the Acrobat 8.0, Windows XP and MS Outlook 2003 and 2007.
We tested only using Acrobat Reader and WORKS!!!. My questions is we are planing to send this form to a lot of people and we need some ideas how can people can handled that, because if they have a Acrobat (full version) will be have the same problem.
Now other option or idea is: It if possible to use some URL and add in paremeter to open only with Acrobat Reader???
Thanks in advance for your information, ideas or solution.
Oscar Calagua

It is not possible to restrict to Reader users. More importantly, since users are not supposed to have Reader and Acrobat on the same computer, you may prevent people who need to fill out the form that need to.

Library Size Limit & Recipient IDs

This looks like a better alternative to services like
yousendit, but I was wondering if the 1GB library size limit will
be retained once the service is out of beta, and if we would be
able to purchase more storage space.
Also, will the recipient always have to create an Adobe ID in
order to retrieve the file? Some of my clients may shy away from
using the service if they have to create an ID. Thanks!

During the beta period the library size is limited to 1GB per
user. We will share additional information regarding storage space,
additional features etc in the next few months.
Regarding the Adobe ID. You clients will need to sign-up for
an Adobe ID if you share a file with them with restricted access.
The service uses the Adobe ID to ensure that only the recipients
with the valid e-mail addresses are allowed to access your shared
documents.

Goods recipient cannot see PO to do confirmation in SRM

Hi Experts!
I have modified the Goods recipient of my purchase order in SRM. But the goods recipient cannot see the purchase order to do confirmation.
Does my goods recipient need to have extra authorisations to be able to see such a pruchase order ?
Do I need to do some configuration (on partner role) so that my goods recipient can see the PO and eventually do confirmation ?
THanks in advance!
Regards,
Mahesh

Run:-
CLEAN_REQREQ_UP &
BBP_GET_STATUS_2
For performance reasons, it is generally the case for transactions BBPCF01 and BBPCF03, that the proposal list contains a maximum of 50 purchase orders. In addition - also due to performance reasons - no backend orders are selected via selection option 'All' if all other selection parameters are initial. However, the number of purchase orders in the proposal list of transaction BBPCF02 is not restricted.
(See also note 361545,549846 ).
I guess the environment is SRM 5.0
Regards,
Vivek
Edited by: Vivek B on May 27, 2009 2:15 PM

Restrict creation of customers according to account group and sales area.

Hey Guys,
I have this scenario wherein we have to restrict the creation of customers according to the sales area and account group. Here is an example.
Suppose I have a domestic customer say D01. Account group that I am using for this domestic customer is D001. Sales area is say D001/D1/D1. Now for exports I have E01 as customer. Account group is E001. Sales area is E001/E1/E1.
Scenario is
I should be able to create D01 only with account group D001 and in sales area D001/D1/D1. Customer D01 should not get created in account group E001 and sales area E001/E1/E1. Now to differentiate export and domestic customers we are using 'D' as a prefix for domestic customers and 'E' for export customers.
Same thing applies for Exports. Customer E01 should only get created with account group E001 and sales area E001/E1/E1.
Please advise on the same.
Appreciate a quick response.
Thanks in advance.
Z

2.1.1     Account Group
2.1.1.1       Maintain Number Range for Account Group
Use
The purpose of this activity is to control number range of Account Group.
Procedure
Access the activity using one of the following navigation options:
IMG --> Financial Accounting (New) --> Accounts Receivable and Accounts Payable --> Customer Accounts --> Master Data --> Preparations for Creating Customer Master Data --> Create Number Ranges for Customer Accounts --> Select the Icon to maintain Number Range
Transaction Code: SPRO
Data to be maintained:
No | From      | To | Current No | Ext (Tick in Check Box)
01 | 0000000001 | 0000099999 | 0 | No
02 | 0000100000 | 0000299999 | 0 | No
XX | A | ZZZZZZZZZZ |      Yes
2.1.1.2       Assign Number Range to Account Group
Use
The purpose of this activity is to maintain number range of Account Group.
Procedure
Access the activity using one of the following navigation options:
IMG > Financial Accounting (New) > Accounts Receivable and Accounts Payable > Customer Accounts > Master Data > Preparations for Creating Customer Master Data > Assign Number Ranges to Customer Account Groups
Transaction Code     : SPRO
Data to be maintained:
Group | Name | Number Range
0001 | Sold-to party | XX
0002 | Goods recipient | XX
0003 | Payer | XX
0004 | Bill-to party | XX
Use External Number Range for Account Group D001 and E001.
Regards,
Rajesh Banka
Edited by: Rajesh Banka on Aug 7, 2008 3:22 PM

Message Delivery Restrictions failed in Exchange 2010

Hi everyone
For a customer, I wanted to restrict the use of a distribution group so that only a few selected people can send to the list. When I tried adding these users under Mail Flow Settings -> Message Delivery Restrictions, it gave me the following error:
Microsoft Exchange Error
The following error(s) occurred while saving changes:
Set-DistributionGroup
Failed
Error:
Couldn't find object "<domain>/Users/Administrator". Please make sure that it was spelled correctly or specify a different object. Reason: The recipient <domain>/Users/Administrator isn't the expected type.
OK
I know of the problem when a user is disabled, but never have seen this one before. The administrator account is active and in use (I logged in with the administrator account to add the users).
Anyone who knows what to do?
Thanks!

That's what the error is saying - the administrator account has no mailbox, and I suspect that the EMC expects the account you are placing in that area to have one.
It's not the administrator that I want to add to the list, but the users of the board. But I'll try to create a mailbox for the administrator, for the sake of science :)
Unfortunately not, that's what I thought at first too, but I double checked and no mailbox for the administrator can be found.
Was the administrator account mail-enabled in the past however? I wonder if it was set as delegate or had send on behalf rights for one of the users you are trying to add and its ghost entry is still there.
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.
Any way how I can check this? As for as I know, the administrator account never had "send on behalf rights", but of course I don't know what they've been doing in all the time since I left.

Restrict by recipient

Similar Messages

Maybe you are looking for