OpenEMM Technical Support Forum

On world mailing intermediate files are written to ~openemm/var/spool/META and then processed by the script pickdist.py. If there are still files in this directory, check the logfile for pickdist in var/log for further information. Perhaps the MySQL database driver part for python is missing here. -...

Are there any spoolfiles left in ~openemm/var/spool/ADMIN? Have you checked the sendmail log file (/var/log/maillog)?

-- ud

This problem occurs, when sendmail is running while openemm is not. So ensure that openemm is started at boot time. It should be possible to just remove sendmail from the auto start process and let openemm start sendmail, when it's started.

-- ud

As you can see, this is a VERBOSE message indicating only an unused feature You can optional install another configuration file which makes not much sense on a small installation base and is in fact a feature used primary by the commercial product.

-- ud

Where in the database is the information that writes to ~openemm/var/spool/bav/bav.conf The data from the database is located in the table mailloop_tbl . Domains are read from /etc/mail/mailertable . From these sources the main part of bav.conf is build (the files /etc/mail/local-host-names and /et...

If I understand you right, you want to send all mails over the exchange mail server? Then you can simply define this server as the smart host for sendmail (depending on your distribution, setting SMART_HOST in the /etc/mail/sendmail.mc file and running make can do this.)

-- ud

Please inspect the xmlback logfile which can be found in ~openemm/var/log/ for further error messages.

-- ud

ext_1@... is the first bounce filter you create in OpenEMM. Every further gets a new number, ext_2, ext_3, etc. So create this bounce filter in OpenEMM, then you should get an additional line in bav.conf like: ext_1@bounce.company.com accept:rid=1,cid=1,fwd=me@company.com Do not use your regular hos...

Ok, assuming the name of your machine is company.com , you can use sender addresses like noreply@bounce.company.com . You can add more subdomains, if you prefer, but add them to /etc/mail/relay-domains and /etc/mail/mailertable (and run make.) To forward the sender address to your bounce filter, you...

I think, you are alright, only your recipients have same problems. 1. case looks like a segmentation fault on the receiver side. 2. is a valid system without a running SMTP server (at least the relay has no server running.) 3. the destination user does not exist ( a "classic" hardbounce.) ...

The first case should be handled by slrtscn.py, be sure it is running and it has read access to the mail log file.

The second case may be a missing relay entry in /etc/mail/relay-domains. Make sure that all modifications are made in /etc/mail as written in the installation documentation.

-- ud

I'm afraid, you are right. The softbounce script seems to have some problems, so better don't use it in this version, a new release will have a reworked version.

-- ud

Did you look in your sendmail logfile for further information? Perhaps there is a hint, what went wrong, when sending to a corporate domain. If this does not help, you can try to scan the sendmail control files (typically found in ~openemm/var/spool/ADMIN and ~openemm/var/spool/QUEUE, starting with ...

Looks like a missing Python mysql module. You can test this by starting python in interactive mode and type which should not print anything except the input prompt on success. Otherwise install the proper package.

-- ud

If you start OpenEMM mail sending should work again, even with this modification.

-- ud