Dual WAN and Log mail SMTP on RV082 ?

I use a RV082 with dual Wan and I cannot configure two SMTP.
Without authentication; a SMTP is specific of the provider.
When WAN1 comes down, SMTP to be used is the SMTP corresponding to WAN2 and vice versa.
Implementation of authentication with the mail server wil be useful.
Possibility of two mail servers with indication of the corresponding WAN is also useful.

I don't know how or if it's possible to set up two SMTP servers, but I know that may ISPs block SMTP traffic that is not directed to one of their SMTP servers.  You could try picking just one SMTP server, and find out if it can be conacted on a non-standard port.  A lot of SMTP providers allow for this.
If you can configure a single SMTP server on a non-standard port, you should be able to conatct that SMTP server from anywhere on the internet because the traffic won't be blocked (at least not port-based blocking, which is what most ISPs use).
So in a scenario where WAN1 is the ISP who owns the SMTP server and WAN2 is a diferent ISP that blocks standard SMTP traffic...
1) If both WANs are working, SMTP traffic goes out WAN1.  No problem.
2) If only WAN1 is working, SMTP traffic goes out WAN1.  No problem.
3) If only WAN2 is working, SMTP traffic goes out WAN2, but is not blocked because it is on a non-standard port.  No problem.
I hope that helps.

Similar Messages

  • Dual Wan and port routing

    Hi,
    I am setting up a configuration with SA520W and 2 Wan, in load balancing. But I face a problem that I could not understand.
    Traffic is HTTP, SIP and 2 servers.
    Servers are for a VPN tunnel and a mail server with ActiveSync
    Both services absolutely need port 443 on the external IP, and that's one of the dual wan reason.
    The 2 wan are running, load balancing mode is enable and NAt routing in firewall tab as follow :
    443  Enabled     WAN     LAN     ALU_OpenVPN     ALLOW always     Any         192.168.0.150     WAN1     Always    
    443   Enabled     WAN     LAN     ActiveSync     ALLOW always     Any         192.168.0.254     WAN2     Always 
    If load balanced
    Port 443 is NOT routed from wan1 to 192.168.0.150
    Port 443 is routed from wan2 to 192.168.0.254
    If only WAN 1
    Port 443 is routed  from wan1 to 192.168.0.150
    If only WAN 2
    Port 443 is routed  from wan2 to 192.168.0.254
    In fact I did other testing and no port routing with WAN1 when load balancing is enable, even on port that is not used at all on Wan2.
    With a FTP filezilla server, it's OK if on wan2, and it stop before logging if on a wan1 (on laod balancing, ok on both case if only one wan)
    Firmware : latest 2.1.18
    Any Clue ??

    Hello,
    I confirm, there is a strange behaviour.
    Simple test :
    Dual Wan configured.
    A FTP server on the LAN (192.168.0.254) port 21
    Firewall , ipv4 config :
    WAN   to   LAN     FTP     ALLOW always     Any         192.168.0.254     WAN1
    WAN   to   LAN     FTP     ALLOW always     Any         192.168.0.254     WAN2
    Then some testing using a FTP client outside the LAN, connection from Internet.
    Then, changing ONLY the Wan Mode :
    1/ Use only single WAN port : Dedicated WAN
    ==> FTP connect through WAN1
    2/ Use only single WAN port : Optional WAN
    ==>FTP connect through WAN2
    3/ Load Balancing
    ==>FTP connect through WAN1
    ==>FTP DO NOT connect through WAN1
    Is that a bug or do I have some strange stuff somewhere ?
    I will pick up another SA520W from stock, brand new, update the firmware, configure the 2 WAN (invering the 2 provider just in case) and do the same test.

  • RV82 Dual WAN and online banking. Packets from two IP's

    Hi all
    I have a RV082 set up with two different ISP's (load balancing). A while ago the users started to get problems with online banking. It looks like the bank system set up more than one "channel" to/from the end user, and that the bank systems will not accept that packets are coming from 2 different public IP's. I have solved this by binding all HTTPS traffic to WAN1.
    Is this a good solution or is there a better way to deal with this? I'm afraid this will "unbalance" my network as many services like Netflix and Youtube is HTTPS.
    Are there any other online services that may have problems with a load balancing setup?
    If WAN1 goes down. Will WAN2 start to transport HTTPS even though HTTPS is bound to WAN1?
    I also have a similar issue with alert mail from the router (goes to wrong ISP every second time), but this seems to be fixed in the last firmware:
    "Email account authentication is configurable for email alert."
    Thanks in advance
    Jone

    Hello Jone,
    Your solution is correct.  Certain types of secure connection like HTTPS or SSH will not work if you keep switching the source IP, because it breaks the three-way handshake.  To prevent that you setup protocol binding as you have.  You can do the same thing for any other traffic that always needs to go out a certain WAN port.  
    If the WAN connection you have selected to protocol bind traffic to goes down, it will failover to the other WAN until the connection recovers.  
    I haven't seen too many online services that have issues with load balancing, it is mostly with secure connections, namely HTTPS.  I did try to get Netflix into HTTPS mode, but I could never get an encrypted connection, but your best bet is to monitor and observe the network to see how it affects you.
    I want to say the line you are quoting has to do with configuring authentication to an SMTP server to send e-mail alerts, rather then selecting a WAN port to use, however if you protocol bind SMTP to the WAN you would like it to use that should no longer be an issue.
    Hope that helps,
    Christopher Ebert - Advanced Network Support Engineer
    Cisco Small Business Support Center
    *please rate helpful posts*

  • RV082 used dual wan download speed slow

    Hi
      I have a RV082 and I used dual wan , every ISP downstream is 10MB/s. two ISP downstream total 20Mb/s.Rv082 use loadblance mode,but total Lan PC download speed was 30kb/s-90kb/s,is very slowly .I find similar question inthe forum ,but i can not .please help me
      thanks

    Ok, several things here:
    - Make sure that when you connect every individual LAN you get the full downstream speed.
    - Make sure that it is not a PC problem, check with different PC's to see if the speed is the same on all of them.
    - Download latest version of Firmware, you can get it from the cisco website, here is the link: http://tools.cisco.com/support/downloads/go/PlatformList.x?sftType=Small+Business+Router+Firmware&mdfid=282414011&treeName=&mdfLevel=null&url=null&modelName=Cisco+RV082+8-port+10%2F100+VPN+Router+-+Dual+WAN&isPlatform=N&treeMdfId=&modifmdfid=null&imname=&hybrid=Y&imst=N
    - If you have to apply the new firmware make sure that you reste the device to factory defaults aftre the upgrade.
    - Disable SPI under the firewall settings.
    Hope this helps.

  • Mail.App and wifi intermittent SMTP issues

    We're having a strange mail sending problem with our PowerBooks. When hooked up to wifi in either of our offices, Mail.App intermittently stops sending mail. It prompts you to try another SMTP account which also fails. At this point, you can still browse the web and receive mail no probs. Then if you plug an Ethernet cable in it starts sending again straight away. You can then pull the Ethernet cable back out and it will continue to send messages over wireless for a while. Some of our staff using Thunderbird don't have this problem. The PowerBooks are running 10.4.7 (though we've had this issue since the day we bought them at about 10.4.2).
    I've found these threads which describe the same problem:
    http://forums.macnn.com/archive/index.php/t-208373.html
    http://macosx.com/forums/showthread.php?t=264759
    http://lists.apple.com/archives/macos-x-server/2005/Jun/msg01475.html
    http://www.deadmime.org/~dank/blog/archives/2003/09/index.html
    Because other parts of the net (and receiving through Mail.app) still work, it's hard to fault the hardware. Add to this we have different APs in these offices. Since it's intermittent, it's not likely to be a hardware setup issue. We've looked at the firewall log in both offices and checked the mail log, and nothing is being blocked.
    Anyone seen this before?
    Xserve G5, PowerBook 15" G4 Mac OS X (10.4.7)
    Xserve G5 Mac OS X (10.4.2)
    Xserve G5   Mac OS X (10.4.2)  

    My bad, was a combination of several things clouding my vision. Just had the SMTPS port (465) blocked on the firewall. Would help if Apple firewall would use the standard SMTPS port in their firewall list instead of their own SMTPS port (5xx).

  • How can I lock out my iCloud? Because of forget my old password and I have do a new Apple ID but when wan to log out my iCloud it call me to logout find my iphone but already forget the password . Have any solution ?

    How can I lock out my iCloud?
    Because of forget my old password I have create a new Apple ID
    But when I wan to log out my iCloud,it call me to logout Find My iPhone.
    I had already forget the password that why I create a new Apple ID.
    Have any solution for problem like this ?

    Apps and Music are not from iCloud. Are from iTunes and App Store.
    You can change this from: Settings>iTunes and App Stores>Sign out and sign in with new ID, but you will have to pay again to download apps that you already have in your old account. Or leave it as it is to share purchases with your son.

  • VPN and a Dual Wan router confusion

    I am running a Border Manager 3.9 server with a Dual Wan router supplying the 2 ISPs load balancing to a single NIC on the Border Manager Server. I want to try setting up a VPN.
    Whats the easiest most pain free way of doing this?
    Just wondering,
    [email protected]

    In article <[email protected]>, Rlmillies wrote:
    > Whats the easiest most pain free way of doing this?
    >
    Hah! Well, inbound traffic in general can be problematical on a
    dual-wan system.
    Here you have two issues, if the router is like ones I've worked on.
    First, load balancing. You can't (probably - this is based on my
    experience) set up a static NAT of one of the public IP addresses to
    the BM 'public' address and still load balance. My experience is that
    as soon as you do that, it forces both inbound and outbound traffic
    onto that particular WAN link, so it kills load balancing/failover.
    Which means you need to do port forwarding on the router for all the
    VPN ports. You will need TCP and UPD 353, and UPD 500 and 4500 inbound
    (and replies outbound). If using a site-site VPN, you also need TCP
    213 inbound.
    You will have to configure the VPN address in BMgr to use one of the
    WAN public IP's. The VPN will only work on that one WAN link.
    Craig Johnson
    Novell Support Connection SysOp
    *** For a current patch list, tips, handy files and books on
    BorderManager, go to http://www.craigjconsulting.com ***

  • Mac OS X Leopard Mail SMTP server keeps going offline and won't come on

    My SMTP in mail on my email accounts keeps going offline and I can't work out how to get it working again. My internet connection is fine. I am receiving emails. I was able to send earlier on my business email account but now my .mac account has gone offline and then my business on went on me.
    I only started using my business email account in mail today and loaded the account into mail. Does anyone have any answers for this as I can see there have been some other people who might have had a similar problem but I can't see any fixes?
    I have deleted and reloaded both my .mac and work account a couple of times now and restarted my computer but still no good.
    Can anyone help?

    I have that offline mail smtp server when I try to send emails from work with my macbook. I've always been able to send emails away from home using the login and password in the smtp configurations. It's a real pain since I use one email account for work and personal business. I can receive email but cannot send any. Everytime I have to answer an email while I'm working, I have to go to the browser, go to my provider's mail page, login and send from there my emails.
    Do we have the same problem?

  • Not able to log out of Yahoo mail and AOL mail

    This started happening about two days ago. I am able to log into my Yahoo mail and Aol mail accounts but I cannot sign out.

    Please post ADF questions to the JDeveloper forum. ADF is a component of JDeveloper and all the experts in ADF are in the JDeveloper forum.
    -steve-

  • URGENT::Status returned by Transport.send() and problem with mail.smtp.host

    Hello,
    I am writing a code to send an email using JavaMail. I have added mail.jar and activation.jar in the classpath. Also I would like to mention that I am using Weblogic6.1 SP4.
    A bunch of questions:
    1. After calling Transport.send(), how do i know if the mail was sent successfully or not ?? Is there anyway I can handle that?
    2. I am using props.put(mail.smtp.host, <some-value>). What should be this <some-value> ?? Where can I get this value from??
    And is this value sufficient for the code to know that which server we are using for it? Do we need to give any URL/Port etc? How does this work?
    3. Is there anything else other than smtp host, username and password to be added to props?? Do we need to create a properties file??
    4. After doing these things, do I need to create a mail session in the Weblogic server also or is it a different method?
    Please help me in resolving these issues.
    Thanks

    Thanks for your kind answers, Dr. Clap..!!
    However, I will again like to ask u this:
    1. As i said that I installed Weblogic 6.1 in my local machine, can I use it as the mail server? As the server is local to my machine, i know that its only me who is the incharge of it. How do I know what smtp host to use.
    2. I am using this code:
    public callService(ServiceRequest request) throws Exception {
         EmailRequest req = (EmailRequest) request;
         Session session = null;
         MimeMessage msg = new MimeMessage(session);
         String accNum = req.getAccountNumber();
         String toAddress = req.getToAddress().trim();
         String fromAddress = generalConfig.FROM_EMAIL_ADDRESS;
         String subject = req.getSubject().trim();
         String message = req.getMessage().trim();
         String [] arrToAddress = null;
         String fileName = "./"+accNum+".htm";
         if (toAddress != null) {
    arrToAddress = convertToArray(toAddress);
         Properties props = System.getProperties();
         props.put("mail.smtp.host", "MYSERVER"); //STILL NEED TO FIGURE OUT WHAT VALUE TO PUT HERE
    session = Session.getDefaultInstance(props);
         setRecipientsTo(msg,arrToAddress);
         msg.setFrom(new InternetAddress(fromAddress));
         msg.setSubject(subject);
         msg.setText(message);
    MimeMultipart mp = new MimeMultipart();
    MimeBodyPart text = new MimeBodyPart();
         text.setDisposition(Part.INLINE);
         text.setContent(message, "text/html");
         mp.addBodyPart(text);
         MimeBodyPart file_part = new MimeBodyPart();
         File file = new File(fileName);
         FileDataSource fds = new FileDataSource(file);
         DataHandler dh = new DataHandler(fds);
         file_part.setFileName(file.getName());
         file_part.setDisposition(Part.ATTACHMENT);
         file_part.setDescription("Attached file: " + file.getName());
         file_part.setDataHandler(dh);
         mp.addBodyPart(file_part);
         msg.setContent(mp);
    Transport.send(msg); //send message
    In this code, like I am using Properties class, will this code work fine(as it is) even if I dont make any Properties text file?? or is it mandatory for me to make the properties text file and to add some values to it?
    I am sorry, I may sound a bit dumb, but I just need to learn it somehow.
    Thanks.
    P.S: convertToArray() and setRecipientsTo() are my own defined private methods.

  • LRT224 and Spotify/port forwarding on dual WAN set-up.

    Very pleased with the  LRT224, which was easy to set up (dual WAN, one cable modem, one VDSL). I'm using it for a small home-based business with several PC's, and it's worked a dream in the load-balancing mode.  My request is beyond my current technical knowledge, however: we have Spotify on one PC for "background entertainment". It's a total bandwidth-hog, so I'd like to set it up to use the slower of the two WANs (VDSL) only.  I'm something of a newbie to the techniques of port forwarding, so I'd be really grateful if someone could describe the steps to bond all Spotify inbound/outbound traffic to WAN2. Is this even possible...?  Thanks in advance - Steve

    You can define a specific IP addresses or specific application service ports to go through a user-assigned WAN for external connections via Protocol Binding. Just bind the MAC address of your device to an IP address to properly route traffic to the specific device by IP and MAC binding.

  • 867VAE dual WAN SDSL and ADSL failover

    Hello,
    I have the 867VAE router, and I'm looking for configuration example to implement the SDSL as the primary WAN and the ADSL for the backup.
    Could you send me plz an example of configuration?
    Cheer
    BR
    A.Aziz

    Pleas see as bellow :
    AIST#sh ip route 0.0.0.0
    Routing entry for 0.0.0.0/0, supernet
      Known via "static", distance 253, metric 0 (connected), candidate default path
      Routing Descriptor Blocks:
      * directly connected, via Dialer1
          Route metric is 0, traffic share count is 1
    AIST#sh track 1
    Track 1
      IP SLA 1 reachability
      Reachability is Down
        3 changes, last change 03:14:29
      Latest operation return code: Timeout
      Tracked by:
        STATIC-IP-ROUTING 0
    BR

  • Trend Micro Dual WAN Issue

    Question from a partner:
    Has Trend fixed the hosted issue with two WAN connections?  It used to be that even though your device had dual WANs, Trend would only forward the emails to one of the connections.  If it went down, you had to submit an email request to move it to the other connection and it could be 12-24 hours before it went into effect and 99 times out of 100, the original WAN port would be back online.  It does slightly defeat the purpose of having Dual WANs if you cannot receive email in this day and age.
    Any help out there?
    Art

    I got with Trend on this because I thought it was something very interesting....
    here is what they said...
    I think  you’re talking about the same setup as a customer having 2 mail servers, right?  If so we have had a solution for this for a while.
    They  want us to send email to 1.1.1.1, but if that is down, send it to  2.2.2.2.
    They  would use the MX record method.
    A  customer would need to create a hostname that points to two MX  records.
    Give the  primary site IN MX 10 and the backup IN MX 20.
    Then we  change the IMHS configuration to use the hostname they  created.
    >cat  imhs.multiple.customer.mailservers
    Hello,
    Our  postfix servers will only allow us to configure 1 IP address or 1 hostname in  our transport file to deliver email back to the customer.  If the customer has 2  or more mail servers they want us to use, they will need to create a new  hostname DNS entry and point it to their multiple servers.
    If they  want our servers to try to deliver the email to their mail servers in a specific  order, say mailserver1 and if that server is not available then try to deliver  the email to the mailserver2, then they would need to setup the following DNS  entries as an example:
    mailserver1.customerdomain.com.    IN  A  1.2.3.4
    mailserver2.customerdomain.com.    IN  A  2.3.4.5
    imhs.customerdomain.com.   IN MX 10 mailserver1.customerdomain.com.
    imhs.customerdomain.com.   IN MX 20 mailserver2.customerdomain.com.
    Then we  setup our server to deliver to  imhs.customerdomain.com.
    customerdomain.com     smtp:imhs.customerdomain.com:25
    If a  specific order is not important then they can just make imhs.customerdomain.com  point to multiple IP addresses:
    imhs.customerdomain.com.   IN A 1.2.3.4
    imhs.customerdomain.com.   IN A 1.2.3.5
    This  will make our server send an email to 1.2.3.4 and the next email to 1.2.3.5,  then to 1.2.3.4, etc.
    Then we  setup our server to deliver to  imhs.customerdomain.com.
    customerdomain.com     smtp:[imhs.customerdomain.com]:25
    Our  servers will only deliver the email to the first server that will accept the  email.  They will not deliver the same email to both mail  servers.
    I hope  that is detail enough,
    Regards,
    Nosa

  • "securely" use one ethernet interface for WAN and other for the LAN

    I am reconfiguring our dual 2.7 Intel Xserve running MacOSXServer 10.5.4, and had a question.
    Is it possible (or advisable) to use en0 to perform LAN services, and then configure en1 to only allow access to very limited service. VPN, FTP, CALDAV and later Mail.
    I imagine that this is possible via a firewall configuration, but first I do not know how to specify interface in addition to ports, and second I don't know how advisable this would be.
    Currently I have a DSL package from ATT with 5 static IP addresses. I have an Airport Extreme set up as one of those addresses providing DHCP and NAT to the LAN. I am using the LAN ports on the back of that to bridge my three switches (2 managed [clients and oce print server 100 base-T] and 1 unmanaged [ laser printers and copier 10 base-T]).
    I have the LAN based on 192.168.0.x, with the Xserve at 192.168.0.5. I have DNS configured and working (Thank you Antonio Rocco)
    I have 20 LAN clients, 18 mac 1 PC and one PC via Parallels. I will have no more than 1 or 2 WAN clients at any one time
    I provide AFP, SMB, Directory Services currently. As part of the reconfigure, I desire to take better advantage of the collaboration tools to provide wikis and CALDAV services. I also want to allow our employees to publish their individual calendars, so that they can subscribe to them at home, or vice versa.
    I would like to configure VPN, one for me to access configurations when I am away using Remote Desktop (I have used command line to some extent, but still feel more comfortable with the GUI tools) and second for limited access to content for certain users.
    It would also be very helpful for us to have a FTP site. It is unnecessary for this the be a FQDN service, sending the IP address is perfectly acceptable as we only use a service like this 10-15 times a year.
    (Related but unimportant in the grand scheme, is there a way to generate a link to the FTP server that you could email that not only is a link, but also a temporary username and password?)
    Thank you in advance,
    Ion Webster

    First, I missed a zero in the network speeds, I have two managed GbE switches that have all of the GbE capable machines connected to them, and an unmanaged GbE switch that has all the 10 or 100Base-T connections. My apologies for the mistake. That was one of the reasons I went with the GbE capable Airport to bridge the switches.
    Ok, I had been leaning towards a separate hardware firewall, but here is also where there is a hole in my knowledge. Do I need to look at something like the Linksys RVS4000 which bills itself as a +"4-Port Gigabit Security Router with VPN. Secure, smart Gigabit networking for growing business"+ I would like easy configuration, as I take care of these systems in addition to my job, rather than full time. This will be the first time I have set up a VPN connection, so even though I have spent a lot of time researching the manuals, and reading Schoun Regan (Apple Training Series) I don't have real world experience here. So if I buy more hardware, I want it to be the product that will provide the protection, and also allow me to configure it so that I can get these services running. All my VPN clients are running Macs, most on an AIrport connection and have their IP ranges in the 10.0.1.x range. all but one is on OS 10.5.x so I have a fairly homogeneous set of machines to make work together.
    I will review the links you provided regarding static routing, but I do believe the hardware solution is a better one, and wish to pursue it, for all the reasons you give, and that in the brief perusal of the links, it is more than I want to tackle.
    As far as FTP vs sFTP, I have no preference. I simply want a way to have online storage for transfer of large files on occasion. Ideally I want a folder, or a series of folders that are accessible for my LAN users to put items in and take them out, and for my (s)FTP users to do the same
    So long story short, the hardware solution I would like to purchase, I need to be able to do the following:
    VPN connections for content access and ARD access ( knew about and will ensure differing IP ranges)
    (s)FTP
    Calendar publishing
    mail(at a later time)
    Thank you for your help thus far.
    Ion Webster

  • Setting Up Mailserver to received and Send Mail for external Network

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

    I cannot find the Line #submission inet n - n -- smtpd in the Main.CF file...here is what I get when I open it
    # Global Postfix configuration file. This file lists only a subset
    # of all 250+ parameters. See the sample-xxx.cf files for a full list.
    # The general format is lines with parameter = value pairs. Lines
    # that begin with whitespace continue the previous line. A value can
    # contain references to other $names or ${name}s.
    # NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
    # POSTFIX STILL WORKS AFTER EVERY CHANGE.
    # SOFT BOUNCE
    # The soft_bounce parameter provides a limited safety net for
    # testing. When soft_bounce is enabled, mail will remain queued that
    # would otherwise bounce. This parameter disables locally-generated
    # bounces, and prevents the SMTP server from rejecting mail permanently
    # (by changing 5xx replies into 4xx replies). However, soft_bounce
    # is no cure for address rewriting mistakes or mail routing mistakes.
    #soft_bounce = no
    # LOCAL PATHNAME INFORMATION
    # The queue_directory specifies the location of the Postfix queue.
    # This is also the root directory of Postfix daemons that run chrooted.
    # See the files in examples/chroot-setup for setting up Postfix chroot
    # environments on different UNIX systems.
    queue_directory = /private/var/spool/postfix
    # The command_directory parameter specifies the location of all
    # postXXX commands.
    command_directory = /usr/sbin
    # The daemon_directory parameter specifies the location of all Postfix
    # daemon programs (i.e. programs listed in the master.cf file). This
    # directory must be owned by root.
    daemon_directory = /usr/libexec/postfix
    # QUEUE AND PROCESS OWNERSHIP
    # The mail_owner parameter specifies the owner of the Postfix queue
    # and of most Postfix daemon processes. Specify the name of a user
    # account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
    # AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
    # particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
    # USER.
    mail_owner = postfix
    # The default_privs parameter specifies the default rights used by
    # the local delivery agent for delivery to external file or command.
    # These rights are used in the absence of a recipient user context.
    # DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
    #default_privs = nobody
    # INTERNET HOST AND DOMAIN NAMES
    # The myhostname parameter specifies the internet hostname of this
    # mail system. The default is to use the fully-qualified domain name
    # from gethostname(). $myhostname is used as a default value for many
    # other configuration parameters.
    #myhostname = host.domain.tld
    #myhostname = virtual.domain.tld
    # The mydomain parameter specifies the local internet domain name.
    # The default is to use $myhostname minus the first component.
    # $mydomain is used as a default value for many other configuration
    # parameters.
    #mydomain = domain.tld
    # SENDING MAIL
    # The myorigin parameter specifies the domain that locally-posted
    # mail appears to come from. The default is to append $myhostname,
    # which is fine for small sites. If you run a domain with multiple
    # machines, you should (1) change this to $mydomain and (2) set up
    # a domain-wide alias database that aliases each user to
    # [email protected].
    # For the sake of consistency between sender and recipient addresses,
    # myorigin also specifies the default domain name that is appended
    # to recipient addresses that have no @domain part.
    #myorigin = $myhostname
    #myorigin = $mydomain
    # RECEIVING MAIL
    # The inet_interfaces parameter specifies the network interface
    # addresses that this mail system receives mail on. By default,
    # the software claims all active interfaces on the machine. The
    # parameter also controls delivery of mail to user@[ip.address].
    # See also the proxy_interfaces parameter, for network addresses that
    # are forwarded to us via a proxy or network address translator.
    # Note: you need to stop/start Postfix when this parameter changes.
    #inet_interfaces = all
    #inet_interfaces = $myhostname
    #inet_interfaces = $myhostname, localhost
    # The proxy_interfaces parameter specifies the network interface
    # addresses that this mail system receives mail on by way of a
    # proxy or network address translation unit. This setting extends
    # the address list specified with the inet_interfaces parameter.
    # You must specify your proxy/NAT addresses when your system is a
    # backup MX host for other domains, otherwise mail delivery loops
    # will happen when the primary MX host is down.
    #proxy_interfaces =
    #proxy_interfaces = 1.2.3.4
    # The mydestination parameter specifies the list of domains that this
    # machine considers itself the final destination for.
    # These domains are routed to the delivery agent specified with the
    # local_transport parameter setting. By default, that is the UNIX
    # compatible delivery agent that lookups all recipients in /etc/passwd
    # and /etc/aliases or their equivalent.
    # The default is $myhostname + localhost.$mydomain. On a mail domain
    # gateway, you should also include $mydomain.
    # Do not specify the names of virtual domains - those domains are
    # specified elsewhere (see sample-virtual.cf).
    # Do not specify the names of domains that this machine is backup MX
    # host for. Specify those names via the relay_domains settings for
    # the SMTP server, or use permit_mx_backup if you are lazy (see
    # sample-smtpd.cf).
    # The local machine is always the final destination for mail addressed
    # to user@[the.net.work.address] of an interface that the mail system
    # receives mail on (see the inet_interfaces parameter).
    # Specify a list of host or domain names, /file/name or type:table
    # patterns, separated by commas and/or whitespace. A /file/name
    # pattern is replaced by its contents; a type:table is matched when
    # a name matches a lookup key (the right-hand side is ignored).
    # Continue long lines by starting the next line with whitespace.
    # See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
    #mydestination = $myhostname, localhost.$mydomain
    #mydestination = $myhostname, localhost.$mydomain $mydomain
    #mydestination = $myhostname, localhost.$mydomain, $mydomain,
    # mail.$mydomain, www.$mydomain, ftp.$mydomain
    # REJECTING MAIL FOR UNKNOWN LOCAL USERS
    # The local_recipient_maps parameter specifies optional lookup tables
    # with all names or addresses of users that are local with respect
    # to $mydestination and $inet_interfaces.
    # If this parameter is defined, then the SMTP server will reject
    # mail for unknown local users. This parameter is defined by default.
    # To turn off local recipient checking in the SMTP server, specify
    # local_recipient_maps = (i.e. empty).
    # The default setting assumes that you use the default Postfix local
    # delivery agent for local delivery. You need to update the
    # local_recipient_maps setting if:
    # - You define $mydestination domain recipients in files other than
    # /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
    # For example, you define $mydestination domain recipients in
    # the $virtual_mailbox_maps files.
    # - You redefine the local delivery agent in master.cf.
    # - You redefine the "local_transport" setting in main.cf.
    # - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
    # feature of the Postfix local delivery agent (see sample-local.cf).
    # Details are described in the LOCAL_RECIPIENT_README file.
    # Beware: if the Postfix SMTP server runs chrooted, you probably have
    # to access the passwd file via the proxymap service, in order to
    # overcome chroot restrictions. The alternative, having a copy of
    # the system passwd file in the chroot jail is just not practical.
    # The right-hand side of the lookup tables is conveniently ignored.
    # In the left-hand side, specify a bare username, an @domain.tld
    # wild-card, or specify a [email protected] address.
    #local_recipient_maps = unix:passwd.byname $alias_maps
    #local_recipient_maps = proxy:unix:passwd.byname $alias_maps
    #local_recipient_maps =
    # The unknown_local_recipient_reject_code specifies the SMTP server
    # response code when a recipient domain matches $mydestination or
    # $inet_interfaces, while $local_recipient_maps is non-empty and the
    # recipient address or address local-part is not found.
    # The default setting is 550 (reject mail) but it is safer to start
    # with 450 (try again later) until you are certain that your
    # local_recipient_maps settings are OK.
    #unknown_local_recipient_reject_code = 550
    unknown_local_recipient_reject_code = 450
    # TRUST AND RELAY CONTROL
    # The mynetworks parameter specifies the list of "trusted" SMTP
    # clients that have more privileges than "strangers".
    # In particular, "trusted" SMTP clients are allowed to relay mail
    # through Postfix. See the smtpd_recipient_restrictions parameter
    # in file sample-smtpd.cf.
    # You can specify the list of "trusted" network addresses by hand
    # or you can let Postfix do it for you (which is the default).
    # By default (mynetworks_style = subnet), Postfix "trusts" SMTP
    # clients in the same IP subnetworks as the local machine.
    # On Linux, this does works correctly only with interfaces specified
    # with the "ifconfig" command.
    # Specify "mynetworks_style = class" when Postfix should "trust" SMTP
    # clients in the same IP class A/B/C networks as the local machine.
    # Don't do this with a dialup site - it would cause Postfix to "trust"
    # your entire provider's network. Instead, specify an explicit
    # mynetworks list by hand, as described below.
    # Specify "mynetworks_style = host" when Postfix should "trust"
    # only the local machine.
    #mynetworks_style = class
    #mynetworks_style = subnet
    #mynetworks_style = host
    # Alternatively, you can specify the mynetworks list by hand, in
    # which case Postfix ignores the mynetworks_style setting.
    # Specify an explicit list of network/netmask patterns, where the
    # mask specifies the number of bits in the network part of a host
    # address.
    # You can also specify the absolute pathname of a pattern file instead
    # of listing the patterns here. Specify type:table for table-based lookups
    # (the value on the table right-hand side is not used).
    #mynetworks = 168.100.189.0/28, 127.0.0.0/8
    #mynetworks = $config_directory/mynetworks
    #mynetworks = hash:/etc/postfix/network_table
    # The relay_domains parameter restricts what destinations this system will
    # relay mail to. See the smtpd_recipient_restrictions restriction in the
    # file sample-smtpd.cf for detailed information.
    # By default, Postfix relays mail
    # - from "trusted" clients (IP address matches $mynetworks) to any destination,
    # - from "untrusted" clients to destinations that match $relay_domains or
    # subdomains thereof, except addresses with sender-specified routing.
    # The default relay_domains value is $mydestination.
    # In addition to the above, the Postfix SMTP server by default accepts mail
    # that Postfix is final destination for:
    # - destinations that match $inet_interfaces,
    # - destinations that match $mydestination
    # - destinations that match $virtual_alias_domains,
    # - destinations that match $virtual_mailbox_domains.
    # These destinations do not need to be listed in $relay_domains.
    # Specify a list of hosts or domains, /file/name patterns or type:name
    # lookup tables, separated by commas and/or whitespace. Continue
    # long lines by starting the next line with whitespace. A file name
    # is replaced by its contents; a type:name table is matched when a
    # (parent) domain appears as lookup key.
    # NOTE: Postfix will not automatically forward mail for domains that
    # list this system as their primary or backup MX host. See the
    # permit_mx_backup restriction in the file sample-smtpd.cf.
    #relay_domains = $mydestination
    # INTERNET OR INTRANET
    # The relayhost parameter specifies the default host to send mail to
    # when no entry is matched in the optional transport(5) table. When
    # no relayhost is given, mail is routed directly to the destination.
    # On an intranet, specify the organizational domain name. If your
    # internal DNS uses no MX records, specify the name of the intranet
    # gateway host instead.
    # In the case of SMTP, specify a domain, host, host:port, [host]:port,
    # [address] or [address]:port; the form [host] turns off MX lookups.
    # If you're connected via UUCP, see also the default_transport parameter.
    #relayhost = $mydomain
    #relayhost = gateway.my.domain
    #relayhost = uucphost
    #relayhost = [an.ip.add.ress]
    # REJECTING UNKNOWN RELAY USERS
    # The relay_recipient_maps parameter specifies optional lookup tables
    # with all addresses in the domains that match $relay_domains.
    # If this parameter is defined, then the SMTP server will reject
    # mail for unknown relay users. This feature is off by default.
    # The right-hand side of the lookup tables is conveniently ignored.
    # In the left-hand side, specify an @domain.tld wild-card, or specify
    # a [email protected] address.
    #relay_recipient_maps = hash:/etc/postfix/relay_recipients
    # INPUT RATE CONTROL
    # The in_flow_delay configuration parameter implements mail input
    # flow control. This feature is turned on by default, although it
    # still needs further development (it's disabled on SCO UNIX due
    # to an SCO bug).
    # A Postfix process will pause for $in_flow_delay seconds before
    # accepting a new message, when the message arrival rate exceeds the
    # message delivery rate. With the default 50 SMTP server process
    # limit, this limits the mail inflow to 50 messages a second more
    # than the number of messages delivered per second.
    # Specify 0 to disable the feature. Valid delays are 0..10.
    #in_flow_delay = 1s
    # ADDRESS REWRITING
    # Insert text from sample-rewrite.cf if you need to do address
    # masquerading.
    # Insert text from sample-canonical.cf if you need to do address
    # rewriting, or if you need username->Firstname.Lastname mapping.
    # ADDRESS REDIRECTION (VIRTUAL DOMAIN)
    # Insert text from sample-virtual.cf if you need virtual domain support.
    # "USER HAS MOVED" BOUNCE MESSAGES
    # Insert text from sample-relocated.cf if you need "user has moved"
    # style bounce messages. Alternatively, you can bounce recipients
    # with an SMTP server access table. See sample-smtpd.cf.
    # TRANSPORT MAP
    # Insert text from sample-transport.cf if you need explicit routing.
    # ALIAS DATABASE
    # The alias_maps parameter specifies the list of alias databases used
    # by the local delivery agent. The default list is system dependent.
    # On systems with NIS, the default is to search the local alias
    # database, then the NIS alias database. See aliases(5) for syntax
    # details.
    # If you change the alias database, run "postalias /etc/aliases" (or
    # wherever your system stores the mail alias file), or simply run
    # "newaliases" to build the necessary DBM or DB file.
    # It will take a minute or so before changes become visible. Use
    # "postfix reload" to eliminate the delay.
    #alias_maps = dbm:/etc/aliases
    #alias_maps = hash:/etc/aliases
    #alias_maps = hash:/etc/aliases, nis:mail.aliases
    #alias_maps = netinfo:/aliases
    # The alias_database parameter specifies the alias database(s) that
    # are built with "newaliases" or "sendmail -bi". This is a separate
    # configuration parameter, because alias_maps (see above) may specify
    # tables that are not necessarily all under control by Postfix.
    #alias_database = dbm:/etc/aliases
    #alias_database = dbm:/etc/mail/aliases
    #alias_database = hash:/etc/aliases
    #alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
    # ADDRESS EXTENSIONS (e.g., user+foo)
    # The recipient_delimiter parameter specifies the separator between
    # user names and address extensions (user+foo). See canonical(5),
    # local(8), relocated(5) and virtual(5) for the effects this has on
    # aliases, canonical, virtual, relocated and .forward file lookups.
    # Basically, the software tries user+foo and .forward+foo before
    # trying user and .forward.
    #recipient_delimiter = +
    # DELIVERY TO MAILBOX
    # The home_mailbox parameter specifies the optional pathname of a
    # mailbox file relative to a user's home directory. The default
    # mailbox file is /var/spool/mail/user or /var/mail/user. Specify
    # "Maildir/" for qmail-style delivery (the / is required).
    #home_mailbox = Mailbox
    #home_mailbox = Maildir/
    # The mail_spool_directory parameter specifies the directory where
    # UNIX-style mailboxes are kept. The default setting depends on the
    # system type.
    #mail_spool_directory = /var/mail
    #mail_spool_directory = /var/spool/mail
    # The mailbox_command parameter specifies the optional external
    # command to use instead of mailbox delivery. The command is run as
    # the recipient with proper HOME, SHELL and LOGNAME environment settings.
    # Exception: delivery for root is done as $default_user.
    # Other environment variables of interest: USER (recipient username),
    # EXTENSION (address extension), DOMAIN (domain part of address),
    # and LOCAL (the address localpart).
    # Unlike other Postfix configuration parameters, the mailbox_command
    # parameter is not subjected to $parameter substitutions. This is to
    # make it easier to specify shell syntax (see example below).
    # Avoid shell meta characters because they will force Postfix to run
    # an expensive shell process. Procmail alone is expensive enough.
    # IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
    # ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
    #mailbox_command = /some/where/procmail
    #mailbox_command = /some/where/procmail -a "$EXTENSION"
    # The mailbox_transport specifies the optional transport in master.cf
    # to use after processing aliases and .forward files. This parameter
    # has precedence over the mailbox_command, fallback_transport and
    # luser_relay parameters.
    # Specify a string of the form transport:nexthop, where transport is
    # the name of a mail delivery transport defined in master.cf. The
    # :nexthop part is optional. For more details see the sample transport
    # configuration file.
    # NOTE: if you use this feature for accounts not in the UNIX password
    # file, then you must update the "local_recipient_maps" setting in
    # the main.cf file, otherwise the SMTP server will reject mail for
    # non-UNIX accounts with "User unknown in local recipient table".
    #mailbox_transport = lmtp:unix:/file/name
    #mailbox_transport = cyrus
    # The fallback_transport specifies the optional transport in master.cf
    # to use for recipients that are not found in the UNIX passwd database.
    # This parameter has precedence over the luser_relay parameter.
    # Specify a string of the form transport:nexthop, where transport is
    # the name of a mail delivery transport defined in master.cf. The
    # :nexthop part is optional. For more details see the sample transport
    # configuration file.
    # NOTE: if you use this feature for accounts not in the UNIX password
    # file, then you must update the "local_recipient_maps" setting in
    # the main.cf file, otherwise the SMTP server will reject mail for
    # non-UNIX accounts with "User unknown in local recipient table".
    #fallback_transport = lmtp:unix:/file/name
    #fallback_transport = cyrus
    #fallback_transport =
    # The luser_relay parameter specifies an optional destination address
    # for unknown recipients. By default, mail for unknown@$mydestination
    # and unknown@[$inet_interfaces] is returned as undeliverable.
    # The following expansions are done on luser_relay: $user (recipient
    # username), $shell (recipient shell), $home (recipient home directory),
    # $recipient (full recipient address), $extension (recipient address
    # extension), $domain (recipient domain), $local (entire recipient
    # localpart), $recipient_delimiter. Specify ${name?value} or
    # ${name:value} to expand value only when $name does (does not) exist.
    # luser_relay works only for the default Postfix local delivery agent.
    # NOTE: if you use this feature for accounts not in the UNIX password
    # file, then you must specify "local_recipient_maps =" (i.e. empty) in
    # the main.cf file, otherwise the SMTP server will reject mail for
    # non-UNIX accounts with "User unknown in local recipient table".
    #luser_relay = [email protected]
    #luser_relay = [email protected]
    #luser_relay = admin+$local
    # JUNK MAIL CONTROLS
    # The controls listed here are only a very small subset. See the file
    # sample-smtpd.cf for an elaborate list of anti-UCE controls.
    # The header_checks parameter specifies an optional table with patterns
    # that each logical message header is matched against, including
    # headers that span multiple physical lines.
    # By default, these patterns also apply to MIME headers and to the
    # headers of attached messages. With older Postfix versions, MIME and
    # attached message headers were treated as body text.
    # For details, see the sample-filter.cf file.
    #header_checks = regexp:/etc/postfix/header_checks
    # FAST ETRN SERVICE
    # Postfix maintains per-destination logfiles with information about
    # deferred mail, so that mail can be flushed quickly with the SMTP
    # "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
    # By default, Postfix maintains deferred mail logfile information
    # only for destinations that Postfix is willing to relay to (as
    # specified in the relay_domains parameter). For other destinations,
    # Postfix attempts to deliver ALL queued mail after receiving the
    # SMTP "ETRN domain.tld" command, or after execution of "sendmail
    # -qRdomain.tld". This can be slow when a lot of mail is queued.
    # The fast_flush_domains parameter controls what destinations are
    # eligible for this "fast ETRN/sendmail -qR" service.
    #fast_flush_domains = $relay_domains
    #fast_flush_domains =
    # SHOW SOFTWARE VERSION OR NOT
    # The smtpd_banner parameter specifies the text that follows the 220
    # code in the SMTP server's greeting banner. Some people like to see
    # the mail version advertised. By default, Postfix shows no version.
    # You MUST specify $myhostname at the start of the text. That is an
    # RFC requirement. Postfix itself does not care.
    #smtpd_banner = $myhostname ESMTP $mail_name
    #smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
    # PARALLEL DELIVERY TO THE SAME DESTINATION
    # How many parallel deliveries to the same user or domain? With local
    # delivery, it does not make sense to do massively parallel delivery
    # to the same user, because mailbox updates must happen sequentially,
    # and expensive pipelines in .forward files can cause disasters when
    # too many are run at the same time. With SMTP deliveries, 10
    # simultaneous connections to the same domain could be sufficient to
    # raise eyebrows.
    # Each message delivery transport has its XXX_destination_concurrency_limit
    # parameter. The default is $default_destination_concurrency_limit for
    # most delivery transports. For the local delivery agent the default is 2.
    #local_destination_concurrency_limit = 2
    #default_destination_concurrency_limit = 10
    # DEBUGGING CONTROL
    # The debug_peer_level parameter specifies the increment in verbose
    # logging level when an SMTP client or server host name or address
    # matches a pattern in the debug_peer_list parameter.
    debug_peer_level = 2
    # The debug_peer_list parameter specifies an optional list of domain
    # or network patterns, /file/name patterns or type:name tables. When
    # an SMTP client or server host name or address matches a pattern,
    # increase the verbose logging level by the amount specified in the
    # debug_peer_level parameter.
    #debug_peer_list = 127.0.0.1
    #debug_peer_list = some.domain
    # The debugger_command specifies the external command that is executed
    # when a Postfix daemon program is run with the -D option.
    # Use "command .. & sleep 5" so that the debugger can attach before
    # the process marches on. If you use an X-based debugger, be sure to
    # set up your XAUTHORITY environment variable before starting Postfix.
    debugger_command =
    PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
    xxgdb $daemon_directory/$process_name $process_id & sleep 5
    # If you don't have X installed on the Postfix machine, try:
    # debugger_command =
    # PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
    # echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
    # >$config_directory/$process_name.$process_id.log & sleep 5
    # INSTALL-TIME CONFIGURATION INFORMATION
    # The following parameters are used when installing a new Postfix version.
    # sendmail_path: The full pathname of the Postfix sendmail command.
    # This is the Sendmail-compatible mail posting interface.
    sendmail_path = /usr/sbin/sendmail
    # newaliases_path: The full pathname of the Postfix newaliases command.
    # This is the Sendmail-compatible command to build alias databases.
    newaliases_path = /usr/bin/newaliases
    # mailq_path: The full pathname of the Postfix mailq command. This
    # is the Sendmail-compatible mail queue listing command.
    mailq_path = /usr/bin/mailq
    # setgid_group: The group for mail submission and queue management
    # commands. This must be a group name with a numerical group ID that
    # is not shared with other accounts, not even with the Postfix account.
    setgid_group = postdrop
    # manpage_directory: The location of the Postfix on-line manual pages.
    manpage_directory = /usr/share/man
    # sample_directory: The location of the Postfix sample configuration files.
    sample_directory = /usr/share/doc/postfix/examples
    # readme_directory: The location of the Postfix README files.
    readme_directory = /usr/share/doc/postfix
    # THE FOLLOWING DEFAULTS ARE SET BY APPLE
    # bind to localhost only
    inet_interfaces = all
    # turn off relaying for local subnet
    mynetworks_style = host
    # mydomain_fallback: optional domain to use if mydomain is not set and
    # myhostname is not fully qualified. It is ignored if neither are true.
    mydomain_fallback = localhost
    myhostname = jamestownpress.com
    mailbox_transport = cyrus
    enable_server_options = yes
    luser_relay =
    maps_rbl_domains = dun.dnsrbl.net
    message_size_limit = 0
    mydestination = $myhostname,localhost.$mydomain
    smtpd_use_tls = no
    smtpd_enforce_tls = no
    smtpd_tls_loglevel = 0
    smtpd_sasl_auth_enable = yes
    smtpd_use_pw_server = yes
    smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination,permit
    smtpd_pw_server_security_options = plain
    server_enabled = 1
    relayhost =
    smtpd_client_restrictions = permit_mynetworks reject_rbl_client dun.dnsrbl.net permit
    always_bcc =
    mynetworks = 127.0.0.1/32,192.168.0.0/16,192.168.1.98,192.168.1.3,192.168.1.13,192.168.1.5,1 92.168.1.22,192.168.1.18,192.168.1.41
    content_filter = smtp-amavis:[127.0.0.1]:10024
    so what do I need to change

Maybe you are looking for

  • There was a problem connecting to the server (...)

    Hello, all. First time posting here, so I'd like to greet the community. I've been having this small problem for some months and never managed to fix it. I've searched the forums countless times and found many discussions related to the same message,

  • I have problem with buying from iTunes Store

    I have problem with buying from iTunes ??!! I've put all of my info cards What can i do ?!

  • Java mapping - Linkage Error

    Hello, We are on PI 7.0 SP10. Currently we are migrating the XI servers from Solaris to AIX IBM. When I try to run Java mapping, I get following error: <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap

  • JSP accesing data from inside a servlet

    Is there any way. I dont want to have to forward anything Is there any include I can do and the contents would be parsed then I could run servlet methods and display the data on the JSP?

  • The shortcut key of comment lines does not work

    In SAP NetWeaver 04s,the shortcut key of comment lines (CTRL + \ and CTRL + SHIFT + \)does not work in the abap new editor Message was edited by: ming yu