You could use an SMTP transaction filter to reject mail with invalid addresses.

This would not let the mail continue on it's way, but the sender would get an immediate failure, and may become more interested in sanitising their own address list :)

> Our company currently has a dedicated mail host in house that emails out directly to the clouds.  We do not relay to another mail host or
> anything.  We want to implement a feature where we can email clients who have missed their last month's payment when we print their
> current statement.  As such, I'm wondering - how many emails per day can be sent this way before being blacklisted by Spamhaus and the
> like?  Many of them say they don't blacklist based on volume, but by practice, but I'm unsure of other sites.  At a previous job, our
> admin said that AOL would blacklist us for sending out something like 500 1 recipient emails per day, or any number with more than 75
> recipients.  We may have gone through AOL for our mail hosting, however.

BTW, you can register you server with AOL and they'll not block but send you a message showing where an AOL user complained about your mail.  I registered my server with AOL and they do run a pretty professional operation.  The postmaster really does answer the mail at AOL, that's more that I can same for most ISPs.

>
> We typically have around 400 clients who miss a payment each month (usually not the SAME 400, of course).  However, this can jump up
> and down a couple hundred, and many will probably opt out.  How likely does this seem to get us blacklisted?

Probably never if each person was getting a separate, tailored e-mail message.  The number of messages sent generally has nothing to do with getting blacklisted by Spamhaus and others.  Most of the blacklists look at the content and not the process.  

That said if you are trying to send the same message to 400 RCPT TO addresses and it looked at all spammy then you're getting on at least someone's blacklist.  ;-(

Hi, I've set up the mailbe webmail pro correctly, but, a question came to my mind, I intend to use only webmail pro to some users outside my organization, but how can I convert the pegasus files to Afterlogic webmail?? I know that I can copy the arquives, but the entries at the database I have to create also, don't I?

Can somebody help me?

Thanks [:)]

No problem.  All installed now and good to go.  Love your software.  Thanks for the help.

Thomas it works perfectly !!!  Also other options are very interesting.

I have no words to say thank you ... Mercury/32 reserves allways a lot of nice surprises ... [:D]

Alex Bromo

> Could I have a second Mercury install, that POPs a domain mailbox from my original Mercury?
>
>  And then have this second Mercury forward with mercuryE to the server I'm trying to reach internally?

Sure but you might be able to do the same thing with WSMTPEx without the second instance.


The program WSMTPEx.exe (SMTPEX.NLM for Netware)  and this a separate program that takes mail for a email account and forwards it to any port and any hostname/IP address.  I use this with my domains to forward the mail to a Linux system (must use high ports as non-root) and to a second instance of Mercury/32 running on my system (can't share port 25)  Here's a sample of the ini file I use for forwarding all mail to Mercury/32 running on Ubuntu and Wine.   

 #  You can rename this tool, but name of following section must remain [WSMTPEx]
[WSMTPEx]
Version=0.10
#  TCP port, on which SMTP server listens
Port=8025
#  Number of seconds to delay between searches for emails
LoopDelay=30
#  Folder, under which is most of user's mailboxes
UserFolder=
Domains=1
# Users mail address domain part
Domain1=linux-tstephenson.com
LogName=c:\Mercury\WSMTPEx.log
SMTPServer=192.168.1.4
MailBoxes=1
Badmails=c:\pmail\mail\BadMail

[linux-tstephenson.com]
# When user name start with "DM:", WSMTPEx will try to find SMTP envelope address in mail file
Mb1addr=dm:ubunto
Mb1dir=c:\pmail\mail\ubunto


This takes all the mail in the domain account "UBUNTO"  and sends it to port 8025 on
192.168.1.4 to be received by MercuryS.  The directory BADMAIL I have specified
must exist.  You can run multiple instances of this tool and and it can be run as a
service.  If run as a service and running multiple instances the name of the program
should be changed.  I use WSE-UBUNTO to rename the program and ini file for this
one.  

Many thanks to Petr Jaklin for the development of these tools.  You can get these
tools at the community download areas or directly from Petr Jaklin's site
http://www.3net.cz/software/softe.htm  

> Am I the only one apparently having this problem?

Since I get Hotmail all the time to my domains I do not see a problem here.  I also quickly went through the MercuryS logs and did not see any rejections of Hotmail connections.  FWIW, they all used the proper <> around the RCPT TO address. FWIW, if MercuryS was rejecting for the lack of the <> around the address then you should see it in the logs.  If you do not see any rejections then the MS comment is spurious.

Also, I went through two months of mail in the MercuryS log looking for hotmail.com and found that most of the connections using this host name did not have an IP address associated with MS (Hotmail, MSN)  at all and were blacklisted IP addresses.

> 1 - Why is the 'Internet name for this system' not automatically also used as a local domain? wouldn't that make sense?

Not in a lot of cases.  The system name may be what you want to maiser and postmaster domain to be but it may not be a domain that has any local user other that the postmaster account.  If this is used as the connecting host name there can be real problems if this is not in the domains list.  There is nothing added to the domains be default since it's expected that the system admin only list the domains where there is a set of local users or aliases.

> 2 - other mailboxes got corrupted, blank messages appeared. Deleting those resulted in more errors regarding files that could not be
> deleted from some queue.

Not sure what you mean here.


> 3 - if observation 1 has a valid reason, I think Mercury should still not crash

If it trying to deliver a message to a local user with the domain matching the name of the system and not listed in the domains list then this would be a major configuration error.  When you start getting bounces of huge messages then it's quite possible that the OS could be running out of handles trying to handle the configuration error.

OK. Database restored from backup. Vacuum and reindex commands completed successfully. GW is working now.

 [:)]

Thank you for your help.

Jyrki

Hi,

thank you very much Mr. Stephenson!
Works great now.

Regards

If you have a mercury.lic file in the Mercury directory it should just be moved to the new location.

/Rolf

[quote user="gears"]i d abit of codeing, if its not to hard i could write one up, know where i might get a thing todo this with?[/quote]

If you are going to write a daemon to sort out every problem with mail clients that connect to your mail server, I think you've started an impossible task.  Far better to correct this mis-configured client to do what is wanted.

[quote user="cypherinfo"]

Hello, this is my first post here :-)

I run a website localhost with XAMPP 1.7.1 and Joomla. Mercurymail 4.6. I do not wanna use my ISP for SMTP I'll use MercuryMail.[/quote]

That means you are using MercuryE and not MercuryC for outgoing mail

[quote]I need to use the SMTP host (I need to enter it in a config file; what I have to write there?) of my mail server in another application.

Where I may find it in the settings? After having read the post in the forum I guess it may be my IP. Am I right?[/quote]

Is the application expecting a name or an IP address?  If it is running on the same machine, use localhost or 127.0.0.1, otherwise use the appropriate name or address.

[quote]What if I want to set a custom SMTP host name?[/quote]

I think that's a machine/network configuration issue.  Not Mercury

For Pegasus/Mercury setup this should be a good starting point:

Usernames in Mercury/32 is always just a simple name like jdoe. If the server handles multiple domains and you need to specifically connect it with one of them you will need to create aliases as well.

/Rolf 

I am interested in retrieving older manuals from Pegasus mail,

particularly from the 90s. Via Google, I was only able retrieve newer

manuals. Can somebody help me?

Not sure if these should be made available since in the '90's David was selling these as a part of the support contract.  You might want to contact him directly for these manuals though. .

Problem solved ....

somehow a wrong pconfig.

kai atle

Thanks, Rolf, that fixed it.

 Added the glue headers and blank line, renamed to .101   

Shortly after dropping into the QUEUE folder, Mercury picked it up and created the .QDF/.QCF pair, then it went.

Chris

So you want to use separate sender information in the email client for each user in your local network, but any message sent to an external recipient should have that information replaced with a common sender address? Sender information appear in the SMTP envelope of the message as well as in various message headers (From, Sender, Reply-To etc). To change it in outgoing messages you would need a special daemon, there are no standard tools for it. There is a Daemon Developer Kit available in the Downloads section, but some programming skills will be required.

/Rolf

When running as a service you will most likely need to enter the full path to the killfile (in Configuration / MercuryS SMTP Server / General) before clicking Edit.

You can probably find a lot of information about the anti-spam tools in the PDF manuals that are included with Mercury, Graywall and SpamHalter.

/Rolf

I have made this work in the past, but can't recall the specifics, sorry.

I also recall failing to make it work, more recently.

I usually just rename the *.qdf to *.101 and add the "glue headers" at the top

[quote]$ from@address

T recip@address

<blank line>

<existing message body>[/quote]

Then drop it back in the queue and it gets reprocessed as a new message.

edit: this also can be done to *.cnm files from a mailbox (for spam fp's etc)