Arabic  Chinese (simplified)  Chinese (traditional)  French  German  Italian  Japanese  Korean  Portuguese  Russian  Spanish 

HOWTOS

From ASSPSMTP

Jump to: navigation, search

Return to Documentation Home

On This Page

HOW-TOs and notes for specific MTAs and Operating Systems

As folks write HOW-TOs or install notes for specific mail programs or operating systems we will link to them here. 2003-Sep-04 2:00pm jhanna



OS/2

 I had perl 5.8/OS2 installed and also i had wget and bzip2 and wget in my path. 
 Also i created a file updatednsbl.cmd for periodic updates
wget http://spfilter.openrbl.org/data/output/DEFAULT.octets.bz2 --output-document=dns.bz2 if not exist dns goto cont if exist dns.sav del dns.sav ren dns dns.sav  :cont bzip2 -d dns.bz2 perl dnsbl.pl dns
2003-Sep-04 2:04pm jhanna

Post.Office

 NT only: How do I change the SMTP Port 25 something else?
That information is stored in the registry and can be modified for Post.Office. 1. As a local NT Administrator for that host, open the Registry Editor. 2. Within HKEY_LOCAL_MACHINE select: SOFTWARE -> Software.com -> post.office -> SMTP-Accept -> Config 3. Double-click on the "Socket" Key to edit it. 4. Change the value from 25 to 26 (for example) and click on OK. 5. If you do not have permission to save this value, you will need to: select the Security Menu Option -> Owner…-> Take Ownership; select the Security Menu Option again -> Permissions -> ; highlight your administrative self; select the Type of Access Pull Down and select Full Control; select OK; now try the edit the Socket Key. 6.You will now need to stop and start the Post.Office service in your Control Panel - Services Window. 2003-Sep-04 2:07pm jhanna

Change the SMTP port for Lotus Notes

 For Release 4.6.1 or greater of IBM/Lotus Domino, you could add SMTPMTA_IPPORT=xxx to your notes.ini 
 and change that way the SMTPMTA lisener port. After you have changed this value, you need to restart 
 the SMTPMTA and the native Domino router.
 
For Release 5 of IBM/Lotus Domino you need to change the Internet Ports in the Server document. See attachment Domino_R5_Server_Document.jpg or Domino_R5_Server_Document.png After you have changed this value in the Server document, you only need to restart the Domino router.
For Release 6 of IBM/Lotus Domino you need to change the Internet Ports in the Server document. See attachment Domino_R6_Server_Document.jpg or Domino_R6_Server_Document.png After you have changed this value in the Server document, you only need to restart the Domino router.
Kind Regards from Switzerland
SteveB
2003-Sep-04 2:10pm jhanna
HOWTO Change the SMTP port for Lotus Notes
2004-Dec-26 7:48am lehoaet

General instructions for any non-SMTP mail server (MS Exchange, Lotus Notes, etc)

 I’m writing specific instructions for how to install ASSP with Microsoft Exchange, 
 but the process is the same for other servers.
 
 You need to make some choices: Will ASSP run on the same box as Exchange? 
 ASSP requires a second mail server to deliver internet mail; will you use your ISP’s mail 
 relay host, or configure your own secondary mail server (in addition to Exchange)? 
 If so, what server will you use?
 
 I'll explain two ways to do this.
 
 The first way works best with two servers. I’ll assume you have Exchange running on one server and 
 that you run ASSP and qmail on a separate FreeBSD server. (You can use many other possibilities, but 
 I’ll describe this setup. Actually Windows with Mercury will work equally well.) This setup looks like this:
 
   Internet -> ASSP -> qmail -> exchange -> client
   and
   Client -> Exchange -> ASSP -> qmail -> Internet
 
 Set up your FreeBSD server with perl and qmail. (see http://www.freebsd.org/ ) Make sure it’s working on the network. 
 Edit /etc/services and change SMTP from 25 to 125. Create a group and user called assp. 
 Install ASSP to the assp user’s home. (These are suggestions – do something else if you prefer.) 
 Verify that qmail relays mail for 127.0.0.1. Configure any mail applications (web mail or local clients) 
 to use SMTP for delivery and not sendmail.
 
 Direct your DNS MX for Exchange’s domain to the ASSP / qmail box. Configure qmail to route mail for Exchange’s 
 domain to Exchange’s IP. (Depending on your mail server this may be tricky. One option might be to put the 
 Exchange's IP in the /etc/hosts or /winnt/services32/drivers/etc/hosts file associated with the mail host in your DNS MX.)
 
 Configure ASSP this way: Listen Port = 25, SMTP Destination = 125, Accept All Mail = exchange server, 127.0.0.1 
 and whatever else you like.
 
 Configure Exchange to route all Internet mail to the ASSP / qmail box.
 
 That’s it. Please read the documentation to know how to set up your spam and notspam collections, prime the whitelist, 
 rebuild your spamdb, customize ASSP’s configuration settings for your site, and more.
 
 This is the more complicated, but more flexible way.
 
 If you plan to run everything on one box and you’re not planning to use your ISP’s mail relay, you can use 
 Mercury (see http://www.pmail.com) or even IIS’s SMTP service. Be sure you’re familiar with their configuration 
 options and limitations.
 
 Incoming mail will follow this path:
 
   Internet Mail -> DNS MX record -> (port 25) ASSP -> Exchange -> Clients
 
 Outgoing mail will follow this path:
 
   Client -> Exchange (Smart host) -> (Relay port) ASSP -> ISP’s Mail Relay
   or
   Client -> Exchange (Smart host) -> (Relay port) ASSP -> local secondary SMTP
 
 If ASSP and Exchange are on the same box, you need to move Exchange’s SMTP port. Different mail servers allow 
 you to do this in different ways. You may find a configuration menu like 
 Domino / Notes: Ports -> Internet Ports -> Mail -> SMTP Inbound. 
 For Exchange you need to look in c:\winnt\system32\drivers\etc\services and edit the SMTP line so say 125 instead of 25. 
 (You can use any port you want, but use ports consistently and be sure that your firewall protects ports appropriately.) 
 Save the file (make sure your editor didn’t add a .txt). You may need to restart Exchange.
 
 In the ASSP Configuration web page (http://127.0.0.1:55555/) put Exchange’s address in the 
 SMTP Destination: 127.0.0.1:125 perhaps.
 
 If ASSP and Exchange are on the same box put your public IP : 25 in the "Listen Port" box. 
 For example, 220.1.2.3:25. Then put 127.0.0.2:25 in ASSP’s "Relay Port" and the address of 
 your ISP’s mail relay or your secondary SMTP server in the "Relay Host". 
 For example: smtp.localhosting.com:25 or 127.0.0.1:325. Configure Exchange to route all Internet mail to 127.0.0.2.
 
 If ASSP and Exchange are on separate boxes, you need to assign a second IP address (often called an alias) to the ASSP box. 
 (If Exchange is on a private network and your ASSP box is on both the public and private networks, so it already has 
 two addresses, you can skip this step.) Let’s assume you have given ASSP 220.1.2.3 and 220.1.2.4. Your Mail MX should 
 point to 220.1.2.3, and ASSP should have 220.1.2.3:25 for its "Listen Port". 220.1.2.4:25 should be the "Relay Port" 
 and your firewall should block external connections to 220:1.2.4:25. Configure Exchange to route all Internet mail to 220:1.2.4.
 
 Don’t forget to click submit on the ASSP configuration page to accept the changes.
 
 If you are using a secondary SMTP server, configure it to listen on port 325. (You can use any port you want, but use 
 ports consistently and be sure that your firewall protects ports appropriately.) Configure it to accept all 
 connections/mail from ASSP for relaying, and disable any message size limitations.
 
 See also the note on how to use the email interface with Exchange / Notes, etc at (Xref) How do I use the email 
 interface with Exchange, Notes, or a RelayHost / RelayPort setup? .
 
 
 2003-Sep-05 10:10am
 
 Check out the HowTo on Exchange 2003
  

TLS or secure SMTP.

TLS or Transport Layer Security is one method of securing SMTP connections. 
It is beyond the scope of the project to add TLS to the ASSP program. 
However you can use the free tool, Stunnel (see http://www.stunnel.org) to achieve the desired result.

Start by downloading and installing stunnel as described on their website. 
Note that in Windows you can use srvany.exe and ntinstsrv.exe to run stunnel as a service. 
Your "Parameters/Application" registery entry will be something like this:

c:\service\stunnel.exe -D 0 -d 465 -r 127.0.0.2:25 -p c:\service\stunnel.cer -n smtp

(I'm seeing now that version stunnel 4 can make it's own service and uses a config file -- use protocol = smtp.)

Set ASSP to "allow all mail" from 127.0.0.1 (if you like) but exclude 127.0.0.2. 
Stunnel will connect to ASSP on that port, and ASSP will treat these connections as non-local. 
Enable SMTP authentication on your email client. (Your mail transport must also support authentication.)

If your mail server doesn't support authentication you can run with ASSP "allow all mail" from the 
stunnel connection, but you create an open relay. Generally spammers haven't used TLS / port 465 / Secure SMTP 
as open relays, but they might start doing that at any time, so this configuration is not recommended.

''2003-Sep-04 2:23pm jhanna''

Change the SMTP port in Courier-MTA?

 Look in /etc/courier (maybe /usr/local/etc/courier) for a file esmtpd
 
 There should be a line PORT=smtp
 
 Change that to
 
  PORT=125
 
 (or whatever port you like)
 
 Restart courier.
 
 2003-Sep-04 2:24pm jhanna
 
 
 Randy writes:
 
 We're using courier-mta here on a bunch of machines and will be consolidating the SPAM analysis to a 
 single point of entry to simplify and unify the data. During the process of setting up a machine 
 (that acts as a firewall, i.e., two (2) nics) we found that courier happily binds to each nic for smtp listening.
 
 Actually, it's documented to work that way and it does.
 
 We had to get very specific with courier's etc/esmtpd file entry, using the following line:
 
  PORT=127.0.0.1.125
 
 ..to convince it to really only listen to your ASSP proxy on the one nic (inside). Otherwise, courier would 
 reject the socket bind attempt to 127.0.0.1:125 (Note: that courier's file uses 127.0.0.1.125 dotted only)
 
 It took a short while to grok that courier was the culprit, and now it behaves way better.
 
 We set up ASSP to be the real honest SMTP service for the machine; and it handles SMTP connections on 
 both nics without incident.
 
 Please, if you get a chance, update the FAQ thingy to add some words about telling courier to be very 
 specific (if it makes sense to you) because this was really the only issue here - and it was very 
 frustrating. Now, after the fact, it's pretty obvious - but, as you know, hindsight is..... and all that.
 2003-Nov-04 2:46pm jhanna
 
 

change the smtp port in sendmail

 Edit Sendmail.cf
 Change
 
  O DaemonPortOptions=Port=smtp,Addr=127.0.0.1, Name=MTA 
 
 to
 
  O DaemonPortOptions=Port=125,Addr=127.0.0.1, Name=MTA
 
 
 2003-Sep-04 2:25pm jhanna
 
 

Antivirus proxies

 Generally it's best to put mail through ASSP before going to antivirus proxies. I'll post more on why later.
 
 2003-Sep-19 10:23am jhanna
 
 I thought I would just give people a heads up in case I am not the only one who didn't think of it.
 
 If you use Norton Anti-virus for Exchange on your mail server and have recipient notification 
 turned on, you will add the virus sender's email address to the whitelist every time you receive 
 a virus, because NAV sends them a notification.
 
 This is of course easily fixed by turning this feature off which is probably fine, with the types 
 of viruses nowadays it probably isn't notifying the actual sender anyways. :-) 
 Or you can add the NAVMSE email address to the redlist.
 
 This caught me by surprise so I thought I would share it with the group. 
 I am probably the only one who didn't think of this before now. 
 But there you go anyways! :-)
 
 Ged West
 
 2003-Sep-19 10:23am jhanna
 
 

Mysql local domains

 I am looking into using ASSP for our organization, and ran into a 
 situation where I'm using Postfix/Mysql/Courier-Imap - Rather than using 
 your config file to specify local domains, I needed to be able to query 
 a table in a MySQL database.
 
 If you are interested in offering a similar feature for that config 
 entry or others, here is the diff output I used to patch the existing 
 codebase for 1.0.3.
 
 14a15,19
  > #20031007 BLF
  > #Note: Added Mysql local database query for domains
  >
  > my %cachedomain;
  >
 939a945,985
  > #Added by BLF
  > sub loaddatabase {
  >         use DBI;
  >         my $host = shift;
  >         my $result;
  >         my $count = keys %cachedomain;
  >         if ($count > 10000) {
  >                 %cachedomain = ();
  >         }
  >         if (!(exists $cachedomain{$host})) {
  >                 my (%data) = (
  >                         MySQL_Server => "localhost",
  >                         MySQL_Username => "myusername",
  >                         MySQL_Password => "mypassword",
  >                         MySQL_Transport => "transport",
  >                         MySQL_ServerDB => "postfix",
  >                 );
  >                 my $dbh = 
 DBI->connect("dbi:mysql:$data{MySQL_ServerDB}:$data{MySQL_Server}","$data{MySQL_Username}", 
 "$data{MySQL_Password}", { AutoCommit => 1 }) || { $errorcode= 
 $DBI::errstr };
  >                 if ($errorcode) {
  >                         return 0;
  >                 }
  >                 my $queryhost = $dbh->quote($host);
  >                 my $sth = $dbh->prepare("SELECT domain FROM 
 $data{MySQL_Transport} where domain = $queryhost");
  >                 $sth->execute;
  >                 ($result) = $sth->fetchrow_array;
  >         } else {
  >                 return $cachedomain{$host};
  >         }
  >         if ($result eq $host) {
  >                 $cachedomain{$host} = 1;
  >                 return 1;
  >         } else {
  >                 $cachedomain{$host} = 0;
  >                 return 0;
  >         }
  > }
  >
 944a991,994
  >
  > #Added by BLF
  >  return 1 if &loaddatabase($h);
  >
 
 
 -- 
 Brian Fields
 
 2003-Oct-08 9:58am jhanna
 
 

VPopMail PopBeforeSmtp

 I have modified the PopB4SMTP subroutine of ASSP.PL in order that ASSP is now compatible 
 with the "Pop before SMTP" implementation of VPOPMail (the virtual domain manager of Qmail).
 For those who are interested, here is the modified code:
 
  sub ok2Relay {
   my $ip=shift;
 
   # If you want to allow pop before smtp uncomment this line and implement the PopB4SMTP sub below
 
   # This must be done first...
 
   return 1 if PopB4SMTP($ip);
 
   return 1 if $acceptAllMail && $ip=~/^($acceptAllMail)/i;
 
   if($relayHostFile) {
    check4update(relayHostFile);
    return 1 if $relayHostFile{$ip};
   }
 
   # failed all tests -- return 0
   0;
 
 }
 
  # if you want to allow pop before smtp authentication then umcomment the line above
  # where this sub is called and edit this sub to be appropriate for your implementation
 
  # It sequentially test the text file /users/vpopmail/etc/open-smtp
  # maintained by vpopmail (Guy)
 
  sub PopB4SMTP {
   my $ip=shift; my $s; my $cip;
   open(PBSMTP,"<$PopB4SMTPFile") or return 0 ;
   while(<PBSMTP>) {
      $s=index($_,":");
      if ($s != 0) {
        $cip=substr($_,0,$s);
        if ($cip eq $ip) {
          mlog(0,"PopB4SMTP OK for $ip");
          close(PBSMTP);
          return 1;
        }
      }
   }
   close(PBSMTP);
   mlog(0,"PopB4SMTP NOT OK for $ip");
   return 0;
  }
 
 Guy LOUIS
 2003-Oct-08 2:01pm jhanna
 
 Thanks for posting Guy.
 Here's one that works with Merak mail, but it may work with others unaltered because of how it works.
 My first Perl app, yay!
 sub PopB4SMTP {
 
  return 0 unless $PopB4SMTPFile;
  my $ip=shift;
  my $ind; my $ipMatch; my $preByte; my $postByte;
 
         open(MKPOPSMTP,"<$PopB4SMTPFile") or return 0 ;
 
         while ($line = <MKPOPSMTP>) {
                 $ind = index($line,$ip);
                         if ($ind  != 0) {
                                 #find the match, and get it and the char before and after
                                 #if both of those aren't a number ord("0") & ord("9") 48 - 57 then I have the whole IP [ord is same as asc]
                                 #if not, this is a subset of a larger IP address and thus no good
                                 #ex: 66.35.250.203 I don't want to let 66.35.250.20 or 6.35.250.203 or 6.35.250.20 you get the idea
 
                                 $preByte = ord(substr($line, ($ind - 1), 1));
                                 $postByte = ord(substr($line, ($ind + length($ip)), 1)); #0 based, so no + 1
                                 
                                 if ( (($preByte < 48) || ($preByte > 57)) & (($postByte < 48) || ($postByte > 57)) ) {
                                         close(MKPOPSMTP);
                                         mlog(0,"PopB4SMTP OK for $ip");                         
                                         return 1;                               
                                 }       
                         }
         }
         close(MKPOPSMTP);
         mlog(0,"PopB4SMTP NOT OK for $ip");
         return 0;
 
 }
 2004-Feb-11 9:22pm chris
 
 sub PopB4SMTP { 
  return 0 unless $PopB4SMTPFile;
  my $ip=shift;
  my $ind; my $ipMatch; my $preByte; my $postByte;
         open(MKPOPSMTP,"<$PopB4SMTPFile") or return 0 ;
         while ($line = <MKPOPSMTP>) {
                 $ind = index($line,$ip);
                         # Here was my bug. I had Not 0, which was true for -1;
                         # Well, that just goes to show you
                         if ($ind  > 0) {
                                 #find the match, and get it and the char before and after
                                 #if both of those aren't a number ord("0") & ord("9") 48 - 57 then I have the whole IP [ord is same as asc]
                                 #if not, this is a subset of a larger IP address and thus no good
                                 #ex: 66.35.250.203 I don't want to let 66.35.250.20 or 6.35.250.203 or 6.35.250.20 you get the idea
                                 $preByte = ord(substr($line, ($ind - 1), 1));
                                 $postByte = ord(substr($line, ($ind + length($ip)), 1)); #0 based, so no + 1
                                 
                                 if ( (($preByte < 48) || ($preByte > 57)) & (($postByte < 48) || ($postByte > 57)) ) {
                                         close(MKPOPSMTP);
                                         mlog(0,"PopB4SMTP OK for $ip");                         
                                         return 1;                               
                                 }       
                         }
         }
         close(MKPOPSMTP);
         mlog(0,"PopB4SMTP NOT OK for $ip");
         return 0;
 } 
 
 2004-Feb-13 8:23pm chris
 
 If you are using vpopmail with mysql you will not have a tcp.smtp file. 
 The .cdb file is generated instead. You can use this patch to PopBeforeSmtp to
 check the cdb file directly. 
 
 Install CDB_File from http://cpan.org/modules/by-module/CDB_File/
 
 then patch -p0 < assp-vpopmail-cdb.patch
 
 --- ./assp.pl   2005-01-08 00:08:17.000000000 -0800
 +++ ./assp.pl   2005-01-08 01:07:04.000000000 -0800
 @@ -1023,16 +1023,16 @@
  # if you want to allow pop before smtp authentication then umcomment the line above
  # where this sub is called and edit this sub to be appropriate for your implementation
  sub PopB4SMTP {
 +# Vpopmail / cdb file
   return 0 unless $PopB4SMTPFile;
   unless ($TriedDBFileUse) {
 -  eval 'use DB_File';
 -  mlog(0,"Could not load module DB_File: $@") if $@;
 +  eval 'use CDB_File';
 +  mlog(0,"Could not load module CDB_File: $@") if $@;
    $TriedDBFileUse=1;
   }
   my $ip=shift;
 - my %hash;
 - tie %hash,  'DB_File', $PopB4SMTPFile, O_READ, 0400, $DB_HASH;
 - if($hash{$ip}) {
 + my $cdb = CDB_File->TIEHASH($PopB4SMTPFile);
 + if ($cdb->EXISTS($ip)) {
    return 1;
   } else {
    return 0;
 
 2005-Jan-08 1:50am ryanw
 
 

ASSP & SAV on the same server

 By: vreiner ( Victor Reiner )
 
  RE: can't send outbound mail   
 
 2003-10-10 16:41
 
 When I changed the setup as discussed, I still was unable to deliver outbound mail. 
 Strangely, the fix was to change the ASSP's "SMTP Destination" field from 
 127.0.0.1:125 to 10.100.10.54:125 (the assigned IP address). Everything is working fine now.
 
 -----------------------
 ASSP can't perform delivery to the destination mail servers because it's a proxy, not a mail transport. 
 Please re-read the page discussion how to setup assp with exchange.
 
 You must involve another mail transport to make this work, (note the new post in the online documentation 
 that apparently with exchange 2000 or better you can create a "virtual server" to handle this -- I'm no 
 exchange guru, so don't ask me how this works.)
 
 If you're going to use SAV in the process on both incoming and outgoing mail you must set it up like this:
 
 	Internet -> assp -> sav -> SMTP2 -> exchange -> clients
 
 	Clients -> exhcnage -> assp -> sav -> SMTP2 -> internet
 
 	Note that assp -> sav -> smtp2 is the same in both setups.
 
 SMTP2 is your second smtp server and can be IIS's smtp, or an exchange virtual server, or Mercury, but it 
 can't be the same SMTP that receives your internet mail for exchange users. (I duno, some exchange guru is 
 gona come up with some crazy way to get client mail out through a relay host throug assp and sav and back 
 into exchange's smtp connection then out to the internet, but that sounds pretty twisted to me. 
 I suppose that's what the virtual server does.)
 
 You don't need to use ASSP's relay port / relay host to do this.
 
 2003-Oct-10 2:10pm jhanna
 
 vreiner ( Victor Reiner ) 2003-10-31 20:25
 
 Not being an SMTP guru, what is the purpose of the "Send NOOP Info" option? I've searched the forums and 
 docs and not found anything enlightening. I'm hoping it will fix an error I get a LOT of in my 
 application error log:
 
  Event Type: Warning
  Event Source: Symantec AntiVirus for SMTP Gateways
  Event Category: None
  Event ID: 2
  Date: 10/31/2003
  Time: 12:05:42 PM
  User: N/A
  Computer: EMAILSERVER
  Description:
  Error 0 receiving data from remote host. (10.100.10.54) 
 
 It seems to occur with each message tagged as spam, and it occurs with Test Mode on and off.
 
 --------------
 
 vreiner ( Victor Reiner ) 2003-11-03 18:17
 
 I checked with Symantec on this, and it is neither possible to reduce the level of verbosity nor even turn 
 this warning off. I put it into them as a suggestion....
 
 You might want to place a note in the SAV section of the docs to warn people that this is "normal" for an 
 installation of ASSP with SAV and not changeable/fixable at least right now.
 
 2003-Nov-04 10:36am jhanna
 
 

Merak Mailserver

 ladylong ( Ruth Rogers ) wrote on 2003-10-15 00:59
 
 From someone who learned the hard way!
 
 Add 127.0.0.1 to the "bypass tarpitting" list, or else when things get busy Merak will Tarpit ASSP and 
 it won't be able to process mail for the next hour (or whatever your tarpitting timeout is set to).
 
 2003-Oct-15 8:20am jhanna
 
 

Fetchmail

 By: mfwiniberg
 
 Applicable to versions 1.0.6 onwards unless ASSP operation changes significantly!
 
 I have spent some time trying to make ASSP work on a linux system that fetches mail 
 from our ISP via fetchmail, and forwards it to our users via Sendmail. This is a fairly 
 common configuration for a linux mailserver that is not permanently connected to the internet.
 
 In our case this set-up is also used because our ISP has an excellent virus filtering system 
 for email which we could not economically replicate in-house.
 
 ASSP has a problem in this type of configuration though:
 
 To filter email, ASSP has to be interposed between fetchmail and sendmail. The problem arises 
 because, when running in it's full fitering mode (ie not testmode) ASSP tells fetchmail to send 
 a rejection message back to the SMTP server before discarding the mail - unfortunately, ASSP 
 then closes the socket which was opened for mail delivery in the first place, fetchmail sees 
 that its socket has closed and promptly shuts down. In testmode, however, as all mails are 
 delivered regardless, everything works as expected.
 
 It seemed obvious to me that the way to make ASSP work in these circumstances was to leave 
 it in test mode, and to get sendmail to deal with any mails marked as spam by ASSP. 
 Combine this with the ASSP spamtrap facility, and you can have all emails delivered, but 
 stop the spam reaching your end-users.
 
 So:
 
 Setup ASSP/Sendmail as describe in the ASSP documentation.
 
 Configure ASSP to run in testmode, have it mark all spam email Subject lines with something that 
 is almost certainly unique eg TRAPPEDSPAM.
 
 If you want to retain copies of all email regardless, configure a spam trap account and have ASSP 
 copy all identified SPAM to it - note that this happens before the header is changed and hence 
 the emails will be accepted by the altered sendmail configuration below, and placed in the trap.
 
 Add the following to your sendmail configuration file (usually /etc/sendmail.cf)
 
 in the FORMAT OF HEADER area add (<tab> represents a tab character - tabs are separators in sendmail)
 
 HSubject:<tab>$>75<tab>Used to sheck for spam mail marked by ASSP. Add a new rule set 75 (if this number 
 is already in use, pick one thatisn't and use that both here and in the above H line S75 
 
 	RS*TRAPPEDSPAM$*<tab>$#discard $: discard
 
 If you get this all correct, then emails identified by ASSP will have their headers marked with
 
  Subject: [TRAPPEDSPAM] ...
 
 Sendmail will see that in the subject and discard the mail!
 
 
 Note that this setup does mean that all email presented to your server will be downloaded - for 
 busy systems this may be too expensive in bandwith/server load, but it is perfect for us 
 (about 1000 email per day including spam).
 
 Mike

 2003-Oct-31 11:10am jhanna
 

SME Server 7

Here is a link to a howto:
http://www.sonoracomm.com/index.php?option=com_content&task=view&id=48
sonoracomm
9/29/07

Microsoft Exchange Server

Exchange 2003 or Microsoft_Exchange

Automatically restart ASSP if it dies in *nix

 #!/usr/pkg/bin/bash
 
 #
 # ASSP watchdog process.
 # This should be run from ROOTs crontab.
 # joehodge
 
 #
 # Start in the correct direcroty.
 #
 cd /usr/local/assp-1.0.7
 
 #
 # Check for a running ASSP process.
 #
 PROC=`pgrep -f -U 10000 assp`
 
 #
 # If ASSP is not running, start it.
 #
 if [ "${PROC}" = "" ]
 then {
 echo "Restarting ASSP."
 ulimit -d unlimited
 perl assp.pl `pwd`
 }
 fi
 
 

NAV for Gateways, IIS SMTP -> Exchange

 (Now called Symantec Anti-Virus for Gateways or SAVGW)
 
 This explains how to setup ASSP for on Windows 2000 Server running Norton's Anti-Virus for Gateways 
 with an a IIS SMTP Virtual Server forwarding to an internal Exchange 5.5 server.
 
 *************************************
 The route my mail takes -
 Incoming
 Internet->ASSP(25)->NAVGW(225)->SMTP Virtual Server(125)->Firewall->Exchange Server(25)->Clients
 
 Outgoing
 Clients->Exchange Server(25)->Firewall->ASSP(25-2nd IP)->NAVGW(225)->SMTP Virtual Server->Internet
 
 *****************************************
 
 The SMTP Virtual Server -
 Assign 2 IP addresses to your Windows 2000 mail server. As an example I will be use private addresses:
 
 192.168.0.1 This will be the address that ASSP listens on. It is also the address of the Default SMTP Virtual Server.
 192.168.0.2 This will be the address of the relay port used by Exchange as a "smart host" to forward all outgoing mail to.
 
 Install IIS.
 Open the Information Systems Manager.
 Right click on the Default SMTP Virtual Server and select Properties.
 Select the original IP address for your server. In our example this is 192.168.0.1.
 Click the Advanced button, then click the IP address in the list and click Edit. Change the port to 125. 
 Click OK, then Apply and OK.
 
 Right click on the Default SMTP Virtual Server and click New, and select Domain.
 In the "Create New Domain" Wizard choose "Remote" click next, type your local 
 email domain domain.com (you don't need the @ symbol) then click ok.
 
 In the left pane of the Information Systems Manager expand your Default SMTP Virtual Server, double 
 click on the "Domains" folder, right click on your domain name and choose Properties. 
 In the Properties choose "Allow all incoming mail to be relayed through this server." and 
 select "route all incoming mail to this host" and type in the IP address of your 
 Exchange Server(or the IP that answers for it on your firewall)and click ok.
 
 Right click on the Virtual server and stop it.
 
 
 Installing Norton anti-Virus for Gateways -
 
 Double click on the NAVGW icon. Logon and click on the "Configure" button.
 Configure notification - Do NOT SEND NOTIFICATION TO SENDER! That will add spammers 
 to your whitelist! Click save.
 Click on the SMTP Tab, set SMTP Port to 225 click save.
 Click on Relay tab, add 127.0.0.1 port 125 as the default relay host to route all mail to. 
 That will send everything to the SMTP Virtual server after being scanned. Click save.
   
 Setting up ASSP -
 
 Start ASSP.
 
 Goto http://localhost:55555
 
 Click "Show Advanced Configuration Options, scroll to the bottom and click  Apply Changes.
 
 in the "SMTP Destination" enter the IP:port of NAVGW - 127.0.0.1:225
 
 Add your local subnet to "Accept All Mail" - 192.168.
 Add your local Domains - i.e. domain.com
 
 In the "Relay Host" enter the NAVGW port - 127.0.0.1:225
 In "Relay Port" enter the 2rd address we created - 192.168.0.2:25.
 
 Configure all other parameters as you see fit and click "apply changes".
 
 Shut down ASSP.
 
 On your Exchange Server, in the "Connections" tab of the IMS, choose "Forward all messages 
 to Host:" and put 192.168.0.2 in the box.
 
 Start the Virtual SMTP server.
 
 Start ASSP.
 
 
 2003-Oct-16 4:32pm Ged West
 

Change the SMTP port for IMAIL

 In versions before 7.10 you have to change the listening port for SMTP in the Windows Registry.
 1: Run regedit
 2:Go to HKEY_LOCAL_MACHINES/System/CurrentControlSet/Services/SMTPD32/Parameters
 3:If you do not have a Value named "Port" on the right side, then you will need to create one.
 4:Click on edit | New | DWORD value , name it "Port" and hit enter(exclude the " marks).
 5:Double click on this new Port key and change the value to whatever port you want SMTP on. 
 Set the port number as decimal rather than hexadecimal.
 6:Stop and restart the SMTP service.
 Versions 7.10 and later you can change the SMTP port on the Advanced tab in the 
 IMAIL Administrator | Localhost | Services | SMTP .
 
 Hope this helps...
 Bill Somers
 
 2003-Dec-22 8:47pm bsomers
 
 

Postfix

In /etc/postfix/master.cf, there is a line that says:
smtp      inet  n       -       n       -       -       smtpd

Change that to be:
localhost:smtp   inet  n       -       n       -       -       smtpd

Then restart postfix.

Then, tell assp to listen to <youripaddress>:25 and forward to localhost:25.

''2004-Jan-15 7:51pm pfudd''

The above procedure is not entirely satisfactory, as it only catches incoming external mail; thus, the 
whitelist will never be updated and much of the power of ASSP is lost. 
You should change Postfix's SMTPD daemons to listen at another port, e.g. 10025. 
This is done by replacing 'smtp' by '10025' in the master.cf file:
10025 inet n - n - - smtpd
Don't touch the line further down in master.cf which ends with 'smtp' - it concerns outgoing SMTP connections.
Then tell ASSP that the SMTP destination is 127.0.0.1:10025 and that 
the listen port is 25 (without an interface or colon).

''2004-Aug-22 10:25am peter''

SMTP on Telstra Australia after April 2004

After mid-April, Telstra Australia is blocking outbound port 25 except for static ips and some business accounts.
This affects outbound mail only and is easily patched. It is evidenced by numerous bounce reports, delayed
queues (over and above the current worm slowdown). It has no bearing whatsoever on inbound mail and ASSP.
There is one and only one minor patch to be made.
Refer to the following Link for details on what and why;
Click Here
Next follow up to patch your specific mail server to use Telstra's smarthost feature.
Look Here

SIMS and ASSP on MacOS X

See http://www.maxlyth.com/whitepapers/SIMS_ASSP_HowTo/ until Max feels like it's done. :-)

Win32 Install

Quick start for Win32 Guide

Return to Documentation Home

These icons link to social bookmarking sites where readers can share and discover new web pages. Blinklist  del.icio.us  digg  Furl  Google  ma.gnolia  Reddit  Slashdot  Spurl  YahooMyWeb 
Personal tools