[quote user="lwells"]Strange here too: Not sure what I did to break it?

Mercury v4.62 CPU useage starts out ok then pegs and stays at 99%.

Might be a bad message in the queue or a problem connection with MercuryE for sending mail.  Since you are using MercuryD it also could be a huge message file on the POP3 host.

Mercury is installed on a folder on a Netware 5.1 sp8 server and run from an XP Pro sp2 workstation.
Netware clients tried 4.83sp2 , 4.91 sp4, 4.91 sp5.

2 different workstations running XP pro sp2 become unbearably slow.

1 XP Home seems ok but CPU is still at 99% for Mercury.

XP- home still seems to run ok but CPU =90%

A partial WireShark packet trace (which is over my head) shows some questionable packets: <shapetype id="_x0000_t75" coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75"> </shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[   69 08:41:27.729190 192.168.1.68 192.168.1.195 NCP C Search for: Mercury]</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75"></shapetype>[  <shapetype id="_x0000_t75" coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75"> 70 08:41:27.729469 192.168.1.195 192.168.1.68 NCP R <b>No matching files or directories were found</b>]</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[  71 08:41:27.729537 192.168.1.68 192.168.1.195 NCP C Search for: Mercury]</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[  72 08:41:27.729883 192.168.1.195 192.168.1.68 NCP R OK]</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[  93 08:41:27.736452 192.168.1.68 192.168.1.195 NCP C Obtain Info for: APPS/MERCURY/MERCURY.EXE:ZONE.IDENTIFIER]</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[  94 08:41:27.736785 192.168.1.195 192.168.1.68 NCP R No matching files or directories were found]</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75"> </shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">Merury.ini</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[General]<br>myname:          tomcotexas.com    # Canonical name for this server<br>timezone:        -0600    # Time Zone to add to date fields<br>file_api:        1    # Use the file api instead of queues<br>mailqueue:       <a href="file://TOMCO1/SYS/SMTPMAIL" mce_href="file://TOMCO1/SYS/SMTPMAIL">\\TOMCO1\SYS\SMTPMAIL</a>    # Where mail should be put for delivery<br>smtpqueue:       <a href="file://TOMCO1/SYS/SMTPMAIL" mce_href="file://TOMCO1/SYS/SMTPMAIL">\\TOMCO1\SYS\SMTPMAIL</a>    # Where the SMTP client should look for mail<br>secondary_queue: <a href="file://TOMCO1/sys/SMTPMAIL" mce_href="file://TOMCO1/sys/SMTPMAIL">\\TOMCO1\sys\SMTPMAIL</a></shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[Protocols]<br>MERCURYS.DLL<br>MERCURYP.DLL<br>MERCURYE.DLL<br># MERCURYC.DLL<br>MERCURYD.DLL<br># MERCURYH.DLL<br># MERCURYF.DLL<br># MERCURYW.DLL<br># MERCURYX.DLL<br># MERCURYI.DLL<br># MERCURYB.DLL</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[Mercury]<br>failfile:      <a href="file://tomco1/main/apps/mercury/Mercury/FAILURE.MER" mce_href="file://tomco1/main/apps/mercury/Mercury/FAILURE.MER">\\tomco1\main\apps\mercury\Mercury\FAILURE.MER</a>    # Delivery failure notification template<br>aliasfile:     <a href="file://tomco1/main/apps/mercury/Mercury/ALIAS.MER" mce_href="file://tomco1/main/apps/mercury/Mercury/ALIAS.MER">\\tomco1\main\apps\mercury\Mercury\ALIAS.MER</a>    # System-wide alias file<br>synfile:       <a href="file://tomco1/main/apps/mercury/SYNONYM.MER" mce_href="file://tomco1/main/apps/mercury/SYNONYM.MER">\\tomco1\main\apps\mercury\SYNONYM.MER</a>    # User synonym database<br>listfile:      <a href="file://tomco1/main/apps/mercury/Mercury/LISTS.MER" mce_href="file://tomco1/main/apps/mercury/Mercury/LISTS.MER">\\tomco1\main\apps\mercury\Mercury\LISTS.MER</a>    # List of lists<br>logfile:       <a href="file://tomco1/main/apps/mercury/mercury.log" mce_href="file://tomco1/main/apps/mercury/mercury.log">\\tomco1\main\apps\mercury\mercury.log</a>    # Traffic logging file<br>logwidth:      30    # Width of address fields in logfile<br>retpath:       1    # Do/Don't use 'return-path' for errors<br>maxhops:       15    # Used to detect mailing loops<br>gullible:      0    # If NZ, don't validate 'From' fields<br>poll:          80   # Seconds between queue polling cycles<br>scratch:       <a href="file://tomco1/main/apps/mercury/Scratch" mce_href="file://tomco1/main/apps/mercury/Scratch">\\tomco1\main\apps\mercury\Scratch</a>    # Where we can write temp files</shapetype>

 

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">returnlines:   20    # How many lines of failed messages to return<br>postmaster:    lwells    # NetWare UIC of postmaster<br>broadcast:     0    # Yes, we want broadcast notifications, but<br>receipts:      0    # ... no broadcasts for receipt confirmations<br>PM_notify:     1    # Do/Don't send errors to the postmaster<br>change_owner:  1    # Change message ownership to recipient<br>auto_tzone:    1    # If NZ, obtain timezone information from OS<br>LogLevel:      10    # System message reporting level<br>LogMax:        100    # Maximum number of system messages to store<br>RetryPeriod:   4    # Period between job retries (minutes)<br>MaxRetries:    4    # Maximum number of times a job can fail<br>TwoPasses:     1    # If NZ, process submission queue in 2 passes<br>Autoaddress:   -128    # If NZ, auto-generate user addresses based on name<br>Daily_exit:    1    # If NZ, auto-restart each day after maintenance<br>No_Areply:     1    # If NZ, disable automatic replies system-wide<br>Alt_Forward:   0    # If NZ, allow alternate forwarding specification<br>Maint_hour:    23    # Hour for daily maintenance (24-hour clock)<br>Maint_min:     0    # Minute for daily maintenance<br>Retry_Mode:    0    # If NZ, use progressive backoff for queue retries<br>Local_DSNs:    0    # If NZ generate Delivery Status for local users only<br>DSN_time1:     10800    # Seconds deferred before first DSN is sent<br>DSN_time2:     86400    # Seconds deferred before second DSN is sent<br>DSN_time3:     259200    # Seconds deferred before third DSN is sent<br>Host_in_title: 1    # If NZ, show hostname in system tray and taskbar<br>Lingering:     0    # Enable or disable 'lingering mailboxes'<br>Linger_Timeout: 60   # Seconds before a lingering mailbox is shut down<br>Alert_Host:    notify.pmail.com    # Host to check for licensee advisories<br>Alert_Interval: 720   # Frequency in minutes (min 240) for checks<br>Alert_Flags:   3    # Flags controlling advisory checks</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[MercuryC]<br>Host : mail.tomcotexas.com<br>Failfile : <a href="file://tomco1/main/apps/mercury/Mercury/FAILURE.MER" mce_href="file://tomco1/main/apps/mercury/Mercury/FAILURE.MER">\\tomco1\main\apps\mercury\Mercury\FAILURE.MER</a><br>Poll : 120<br>Scratch : <a href="file://tomco1/main/apps/mercury/Mercury" mce_href="file://tomco1/main/apps/mercury/Mercury">\\tomco1\main\apps\mercury\Mercury</a><br>ReturnLines : 15<br>Timeout : 180<br>ESMTP : 1<br>Server_Port : 1025<br>SMTP_Username: <a href="mailto:xxxxxx@tomcotexas.com" mce_href="mailto:xxxxxx@tomcotexas.com">xxxxxx@tomcotexas.com</a><br>SMTP_Password: xxxxxx<br>POP3_Auth : 1<br>POP3_Host : mail.tomcotexas.com<br>POP3_Port : 1025<br>Logfile : MercCLog<br>Log_Verbose : 0<br>Session_logging : c:\temp<br>Session_logmode : 1</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[MercuryE]<br>Poll : 15<br>Timeout : 300<br>Nameservers : 68.94.156.1,68.94.157.1<br>Log_Verbose : 1<br>DNS_Timeout : 190<br>DNS_Retries : 5<br>Transcripts : 1<br>MaxThreads : 10</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[MercuryD]<br>Scratch : <a href="file://tomco1/main/apps/mercury/Mercury" mce_href="file://tomco1/main/apps/mercury/Mercury">\\tomco1\main\apps\mercury\Mercury</a><br>Timeout : 320<br>Poll : 240<br>Session_logging : c:\mercD.log<br>Session_logmode : 0</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[MercuryS]<br>Debug : 1<br>HELO : Mercury<br>Logfile : MercS.log<br>Timeout : 300<br>Relay : 0<br>Strict_Relay : 0<br>Server_Port : 1025<br>Interface : 192.168.1.170<br>Allow_Illegals : 0<br>SMTP_Authentication : 0<br>Auth_File : tomco<br>Session_logging : c:\temp<br>Session_logmode : 1<br>Compliance_Settings : 512<br>Maximum_Failed_Rcpts : 4<br>Max_Relay_Attempts : 4<br>SSL_Mode : 0<br>ST_Blacklisting : 0<br>No_VRFY : 0<br>SMTP_ConnFlags : 0</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[MercuryP]<br>Scratch : <a href="file://tomco1/main/apps/mercury/Mercury" mce_href="file://tomco1/main/apps/mercury/Mercury">\\tomco1\main\apps\mercury\Mercury</a><br>Logfile : MercPLog<br>Stack : 32768<br>Mark_Read : 1<br>SSL_Mode : 0<br>Login_Disabled : 0<br>UIDL_nul_list : 1<br>New_UIDs : 0<br>No_NUL_passwords : 1<br>Session_logging : c:\temp<br>Session_logmode : 0<br>Timeout : 180</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[MercuryX]<br>Cmd_Delay: 5<br>Cmd_Wait: 1<br>IE4_Dialling: 0<br>Use_ETRN: 0<br>Clients_only: 1<br>Drain_queues: 1<br>Sunday: 0900,1000,720,120,720,120<br>Monday: 0400,1845,0,0,500,30<br>Tuesday: 0440,1800,0,0,500,30<br>Wednesday: 0500,1900,0,0,500,30<br>Thursday: 0500,1745,0,0,500,30<br>Friday: 0500,1800,0,0,500,30<br>Saturday: 0700,1700,0,0,500,30</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[Domains]</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[Maiser]<br>Maiser:          Maiser   # 'Username' of mail server account<br>Helpfile:        <a href="file://tomco1/main/apps/mercury/Mercury/MAISER.HLP" mce_href="file://tomco1/main/apps/mercury/Mercury/MAISER.HLP">\\tomco1\main\apps\mercury\Mercury\MAISER.HLP</a>   # Help sent on failed maiser requests<br>Lookupfile:      <a href="file://tomco1/main/apps/mercury/Mercury/MAISER.LKP" mce_href="file://tomco1/main/apps/mercury/Mercury/MAISER.LKP">\\tomco1\main\apps\mercury\Mercury\MAISER.LKP</a>   # Format file for the 'lookup' command<br>Send_dir:        <a href="file://tomco1/main/apps/mercury/SENDABLE" mce_href="file://tomco1/main/apps/mercury/SENDABLE">\\tomco1\main\apps\mercury\SENDABLE</a>   # Directory for the 'send' command<br>Logfile:         <a href="file://tomco1/main/apps/mercury/Logs/MAISER.LOG" mce_href="file://tomco1/main/apps/mercury/Logs/MAISER.LOG">\\tomco1\main\apps\mercury\Logs\MAISER.LOG</a>   # Mail server log file<br>Notify:          <a href="file://tomco1/main/apps/mercury" mce_href="file://tomco1/main/apps/mercury">\\tomco1\main\apps\mercury</a>   # Dir. for pending 'notify' commands<br>NoList:          Y   # If 'Y', disable the 'list' command<br>Local_only:      N   # If 'Y', local 'notify' commands only</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[Groups]</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[Rewrite]</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[Statistics]<br>StatFlags:    0  # Statistical reporting settings<br>STF_Hours:    24  # How often to write stat log files<br>STM_Hours:    24  # How often to e-mail stat log files</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[MercuryH]<br>Timeout : 30</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75"><br>I am running out of hammers, and am missing something simple?</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">Larry Wells</shapetype>

<stroke joinstyle="miter"></stroke><formulas><f eqn="if lineDrawn pixelLineWidth 0"></f><f eqn="sum @0 1 0"></f><f eqn="sum 0 0 @1"></f><f eqn="prod @2 1 2"></f><f eqn="prod @3 21600 pixelWidth"></f><f eqn="prod @3 21600 pixelHeight"></f><f eqn="sum @0 0 1"></f><f eqn="prod @6 1 2"></f><f eqn="prod @7 21600 pixelWidth"></f><f eqn="sum @8 21600 0"></f><f eqn="prod @7 21600 pixelHeight"></f><f eqn="sum @10 21600 0"></f></formulas><path o:connecttype="rect" gradientshapeok="t" o:extrusionok="f"></path><lock aspectratio="t" v:ext="edit"></lock>[/quote]

[quote user="NFG"]

Pointing out exactly how much I suck after I melt down the email for a dozen people is just rubbing salt in the wounds, innit?  [/quote]

About as harsh as implying I suck for not telling you you should have a backup before trying new things on your production mail server.  [:P]

[quote]

I appreciate the info about the aliases file.  It has saved me a lot of work.  Wouldn't mind knowing why the transaction filters don't work though.

[/quote]

A good way to test your rules is to use the 'L' action which logs your specified text to the System Messages window when the rule triggers.

Can make it a bit easier to debug what is going on.

You can install over the top, just choose "upgrade" in the installer.

wp_mail() uses a 3rd party PHP class called , and it instructs that class to use PHP's built-in mail() function.

I looked through the PHPMailer function and there is a from$ variable for the MAIL TO: used as well as a from$ for the message body variable.  It might be that WordPress is using the same variable for both and if so this is a bug in WordPress.  The IAW RFC 2821 the MAIL FROM:  field is a simple SMTP email address in <>, i.e. <user@domain>, while IAW RFC 2822 the message From: field can be in the form  email@address, or "Personal Name"<email.address>, or email@address (Personal Name). 

It's hard to tell what WordPress is doing and why but I would report a bug to WordPress at least.  The way I see this working I have no idea why WordPress is using the "wordpress@localhost" <wordpress@localhost> since the data in both fields is a SMTP email address with no personal name at all.

 

Ahh, that's another issue, you need to look at proxy tunneling software, both server and client side. Start by looking at

[quote user="mer99"] I have a situation where I have some "shared" pop3 mail boxes.  A number of people will check the same mailbox (info@somedomain.com).  Each person has their e-mail client set to remove the e-mail from the server after it downloads the message.[/quote]

One way of dealing with inbound common mail, to f.ex. or support@dom.com is to install a common client such as a web mail client that is used by mulitple users.

Another way is to say that info@dom.com / support@dom.com is a mailing list that sends the mail to multiple users, and the users are instructed to respond both to the list and the sender so everyone has the same results.

What I know from write-back caching is that it is a CPU-feature. Is there a way of turning this feature off somehow?

It's a disk device driver function.  Right click on "My Computer", select Properties | Hardware | Device manager | Disk drive, select the drive and then use the "Policies" tab to turn off the caching.

Given that your ISP blocks port 80 it is highly likely they also block 25 so SMTP receiving might be problematic (unless zonedit can do a similar port redirect as your web server).

Probably your best move would be to continue with your current forwarding of all domain mails to your account and have MercuryD (POP3 distributing client) retrieve all mail from this account and sort it to each user you set up. You will also need to set up a user for youself and get your personal mail from Mercury. This user would need to be the 'default user' for the POP3 definition so you get ALL mail that is not recognised as belonging to another user.

You can test this without changing your DNS in any way, just make sure you have the default user set before downloading via POP3, as MercD will discard any mail it cannot find a user to deliver to.

Presumably port 110 is not blocked, so your external users will just need to setup their POP3 clients with your server address and the username & pw you assign.

 

I turned on the verbose logging and session logging for MercuryE module, but when I ran the system again yesterday, the problem seems to have fixed itself.  We actually have two systems that are identical except for their static IPs, and domains, which I believe were acquired via My DNS, and they both work fine; the messages are are processed and delivered in under a minute every time. I'm not sure what the difference is (something to do with the receiving servers I would guess), but if I see the problem again, I'll be sure to post what I obverser here for other people to use.

Keep up the good work.

 

~Jo-Jo

Create a proper local user and move the .CNM files from the queue directory to that user's mail directory.

/Rolf 

omg , im sooooooo stupid .... sorry [:$]

looks like a mail account that i made for testing purposes and deleted short time later  . Im very sorry that ive wasted ur time with this [:'(]

Anyway .. thx 4 the help as i now understand much more of the functionality of mercury now [8-|] , if someone of u guys ever visit duesseldorf , Germany i invite u for a Drink

>> there is no attempt made to distinguish between local or external SMTP connections.

I always thought that the "intent" was to do just that, so maybe there should be a mechanism similar to that used by SpamHalter.

Thank you for your time.  I consider this resolved.  You guys do great work here!

[pi]

[quote user="ryanj"]

I can understand how and why the delivery confirmation works as it stands now, but I can't help but think that it's incorrect behavior.

[/quote]

It is really the FORWARDing mechanism that is at fault. Delivery to the maildrop should be the end of the SMTP journey for a message. The issue occurs when it is resent (original headers intact) with a new SMTP envelope, effectively a new message, that is also requesting delivery confirmation.

A 'copy' rule is probably a "more correct" method than the FORWARD file "hack".

I found it.  I normally use IMAP so it wasn't there.  Thanks.

[quote user="mdowlin"]I think I'll just have to get specific. Kansas State University has two domains, ksu.edu and k-state.edu and if you send an email to either domain it will get to the person. The problem is we have them in the lists as @ksu.edu right now, but I'd like the system to be able to see that if it comes from either domain to go ahead and let them send to the list. So people that choose to be @k-state can't send to the list right now. What I don't want is to put them in twice and get duplicates or have one silent or have to maintain 500 aliases. Hope that clears it up some, was trying to be generic. [/quote]

Aha, now I understand and  the only way you can get this to work is to have the users subscribe twice and have one set to no mail. 

This happens to me all the time on the PMail lists and I have 4-5 email addresses that are involved.  It's a bit of a pain to do at first but there are not that many lists and they do not change all that much.  That said, I generally subscribe to most lists with unique addresses and then always send to the list with that address. 

 

There is a separate log file for each module in Mercury. For the SMPT client you select the module you use from the configuration menu. There is a field called "General log file" that controls this. If it contains a fixed file name (like C:\MERCURY\Logs\MercuryE\smtp.log) it will add new lines forever to the same file. You can however use some special parameters to have it create a new file at set times. For instance:

C:\MERCURY\Logs\MercuryE\~y-~m.log           <--- a new file every month

C:\MERCURY\Logs\MercuryE\~y-~w.log           <-- a new file every week

C:\MERCURY\Logs\MercuryE\~y-~m-~d.log      <-- a new file every day

 

/Rolf 

[quote user="cynist"]All of my users connect using IMAP.  The IMAP4 server shows no connections but by the licensing statement at the bottom it shows three are connected.  What could these three mysterious connections be or how could I figure out?[/quote]

In the current incarnations of Mercury, user counting is done solely on mail delivered. So, each time a message is delivered to a user who has not received mail since the last time Mercury started up, the user count is incremented. Connections to a mailbox, whether by POP3 or IMAP, do not affect the active user count (although clearly if we ever move to stricter licensing requirements, they will have to do so).

With this definition in mind, all the diagnostic you're seeing means is that three discrete users have received new mail since the last time Mercury started up.

Cheers!

-- David --

Thanks for your help so far

I've check and re check my router but I will check again as I am no expert, 'll do some searching online and check with my ISP to see if they are blocking port 25.

This will most likely take more than a day but I'll let you know how i get on 

Again thanks

>> "specifying the shortcut to start minimised"

Holy cow!  Years of using Windows, and I never realized I could change that right in the shortcut!  After you mentioned it, I had to go look for it... and I consider myself an advanced user of Windows!  I'm so embarrassed!  I always glommed the proper command-line switch on the target-line.

Thanks for your help... and STILL learning something new every day.

[:)] 

 

Well if it is a static IP, you have to have proper reverse dns for most deliveries to work. If the reverse zone does not match your forward lookup zone many will consider your IP a dynamic one.

But yes - talk to them - they are people too.