Please remove 'zip|' in '$banned_filename_re'.
I have, but it still doesn't work:
Feb 3 12:38:04 mail amavis[18960]: (18960-01) Blocked BANNED (.dat,image1.wmf) {NoBounceInternal},This is when sending .xlsx file created in Libreoffice
If will be easier to not use LetsEncrypte modified Apache config file, and just use default iRedMail ones. Then you can update Apache config file to use ssl cert by following this tutorial:
http://www.iredmail.org/docs/use.a.boug … icate.html
Zhang.....I've already installed the Lets Encrypt free certificate...but it's not working.....would I cause problems if I follow your instructions at the above link and install a bough SSL certificate from, say, Godaddy?
ZhangHuangbin wrote:Please remove 'zip|' in '$banned_filename_re'.
I have, but it still doesn't work:
Feb 3 12:38:04 mail amavis[18960]: (18960-01) Blocked BANNED (.dat,image1.wmf) {NoBounceInternal},This is when sending .xlsx file created in Libreoffice
Did you restart amavis after making the change?
dsp3 wrote:ZhangHuangbin wrote:Please remove 'zip|' in '$banned_filename_re'.
I have, but it still doesn't work:
Feb 3 12:38:04 mail amavis[18960]: (18960-01) Blocked BANNED (.dat,image1.wmf) {NoBounceInternal},This is when sending .xlsx file created in Libreoffice
Did you restart amavis after making the change?
Yes
I did it. It said that iredapd and amavisd databases were not found. I created the databases and granted logging in to users but got finally :"Programming error: relation "users" does not exist"
==== Required information ====
- iRedMail version (check /etc/iredmail-release): 0.9.6
- Linux/BSD distribution name and version: FreeBSD 11.0-RELEASE-p1
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro?
- Related log if you're reporting an issue:
====
I just set up a fresh installation of FreeBSD 11 zfs with digital ocean. The first thing I did on the server was follow the instructions here: http://www.iredmail.org/docs/install.ir … eebsd.html
However, after letting iRedMail.sh compile packages, I see errors like:
<< ERROR >> Port was not successfully installed, please fix it manually and then re-execute this script.
After installing the failed port manually, I'd run iRedMail.sh again and it would continue to the next package to install. I did this for several packages, but now I've gotten to a point where that won't work:
---
===> mysql57-client5.7.16 depends on package: perl5>=5.24<5.25 - not found
*** Error code 1
Stop.
make: stopped in /usr/ports/databases/mysql57-client
<< ERROR >> Port was not successfully installed, please fix it manually and then re-execute this script.
---
I can't find a way around this and can't find anything vaguely similar on the internet. What am I doing wrong? I've successfully installed iRedMail on a debian machine in the past but never FreeBSD.
TIA for any help
Hi dsp3,
you should enable administrator notifying about banned mails
change in /etc/amavis/conf.d/50-user:
$banned_admin = undef;,to
$banned_admin = "root\@$mydomain";,and then post the mail to postmaster in the forum.
I suppose the reason is:
[qr'T=x-(msdownload|msdos-program|msmetafile|wmf)(,|\t)'xmi => 'DISCARD'],Hi dsp3,
you should enable administrator notifying about banned mails
change in /etc/amavis/conf.d/50-user:
$banned_admin = undef;,to
$banned_admin = "root\@$mydomain";,and then post the mail to postmaster in the forum.
I suppose the reason is:
[qr'T=x-(msdownload|msdos-program|msmetafile|wmf)(,|\t)'xmi => 'DISCARD'],
Thanks for the reply ThASattler. Here is the postmaster message:
No viruses were found.
Banned name: .dat,image1.wmf
Content type: Banned
Internal reference code for the message is 24692-01/Zp-8Kcybv8KU
============ Required information ====
- iRedMail version (check /etc/iredmail-release): 0.9.6
- Linux/BSD distribution name and version: FreeBSD 11 (jail)
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MariaDB
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? NO
- Related log if you're reporting an issue:
==============================
Hi,
i've started the installation on the bash prompt with:
LOCAL_ADDRESS='10.0.0.2' bash iRedMail.shAfter installation of ports (successful) the following message appears:
********************************************************************
* Start iRedMail Configurations
********************************************************************
[ INFO ] Create self-signed SSL certification files (2048 bits).
[ INFO ] Generate Diffie Hellman Group with openssl, please wait.
[ INFO ] Create required system account: vmail, iredadmin, iredapd.
[ INFO ] Configure Nginx web server and uWSGI.
[ INFO ] Configure PHP.
[ INFO ] Configure MariaDB database server.
tail: /root/.mysql_secret: No such file or directory
Enter password:
ERROR 1045 (28000): Access denied for user 'root'@'mail.xxxxx.yy' (using password: YES)
ERROR 1045 (28000): Access denied for user 'root'@'mail.xxxxx.yy' (using password: YES)
ERROR 1045 (28000): Access denied for user 'root'@'mail.xxxxx.yy' (using password: YES)
ERROR 1045 (28000): Access denied for user 'root'@'mail.xxxxx.yy' (using password: YES)
ERROR 1045 (28000): Access denied for user 'root'@'mail.xxxxx.yy' (using password: YES)
ERROR 1045 (28000): Access denied for user 'root'@'mail.xxxxx.yy' (using password: YES)
ERROR 1045 (28000): Access denied for user 'root'@'mail.xxxxx.yy' (using password: YES)
[ INFO ] Setup daily cron job to backup SQL databases with /var/vmail/backup/backup_mysql.sh
[ INFO ] Configure Postfix (MTA).Any help is highly appreciated.
regards pylox
==== Required information ====
- iRedMail version (check /etc/iredmail-release): 0.9.6
- Linux/BSD distribution name and version: Debian 8
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): Mysql
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? No
- Related log if you're reporting an issue:
====
Hi,
After upgrading to the last version:
/etc/cron.daily/logrotate:
error: syslog:1 unknown option 'add' -- ignoring line
/etc/cron.daily/spamassassin:
Job for spamassassin.service failed. See 'systemctl status spamassassin.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript spamassassin, action "reload" failed.
/etc/cron.daily/tmpreaper:
Please read /usr/share/doc/tmpreaper/README.security.gz first;
edit /etc/tmpreaper.conf to remove this message (look for SHOWWARNING).
Thx
==== Required information ====
- iRedMail version (check /etc/iredmail-release):
- Linux/BSD distribution name and version:
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Web server (Apache or Nginx):
- Manage mail accounts with iRedAdmin-Pro?
- Related log if you're reporting an issue:
======== Required information ====
- iRedMail version (check /etc/iredmail-release):
- Linux/BSD distribution name and version:
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Web server (Apache or Nginx):
- Manage mail accounts with iRedAdmin-Pro?
- Related log if you're reporting an issue:
======== Required information ====
- iRedMail version (check /etc/iredmail-release): 0.9.6
- Linux/BSD distribution name and version: FreeBSD 11.0-RELEASE-p2
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? no
- Related log if you're reporting an issue:
====
From /var/log/maillog:
Feb 1 08:26:10 mail amavis[13931]: (13931-17) (!!)TROUBLE in check_mail, but must continue (1): update_snmp FAILED: update_snmp_variables: BDB S c_get: BDB0061 PANIC: Invalid argument, No such process. at (eval 93) line 140.
Feb 1 08:26:10 mail amavis[13931]: (13931-17) (!!)TROUBLE in process_request: register_proc: BDB N db_cursor: BDB0060 PANIC: fatal region error detected; run recovery, . at (eval 93) line 220.
Feb 1 08:26:10 mail amavis[13931]: (13931-17) (!)Requesting process rundown after fatal error
Feb 1 08:26:10 mail amavis[13931]: (13931-17) (!)TempDir removal: tempdir is to be PRESERVED: /var/amavis/tmp/amavis-20170201T075849-13931-A_gIx1Y7
Feb 1 08:26:10 mail amavis[13931]: (13931-17) (!)_DIE: register_proc: BDB N db_cursor: BDB0060 PANIC: fatal region error detected; run recovery, . at (eval 93) line 220.
Feb 1 08:26:10 mail amavis[13931]: (13931-17) (!)Amavis::END: DB unregistering failed:This is the error that starts the issue each time.
After that, this error appears several times per second:
Feb 4 04:19:09 mail amavis[60847]: (!!)TROUBLE in child_init_hook: BDB can't connect db env. at /var/amavis/db: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery, No such file or directory. at (eval 93) line 338.
Feb 4 04:19:09 mail amavis[60847]: (!)_DIE: Suicide in child_init_hook: BDB can't connect db env. at /var/amavis/db: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery, No such file or directory. at (eval 93) line 338.Only solution is first to stop the amavisd service.
Then perform kill -9 on the surviving amavisd process.
My users are not happy that their mail is being queued several times per week 
This seems the same as http://www.iredmail.org/forum/topic1203 … t-var.html , which was also on FreeBSD 11
I upgraded recently from FreeBSD 10 to 11, and then installed iredmail. This issue never occurred on FreeBSD 10...
Kind regards,
Wim
Thanks for the reply ThASattler. Here is the postmaster message:
No viruses were found.
Banned name: .dat,image1.wmf
The reason of banning this mail is there is an attached file with file extension .wmf.
You can remove 'wmf|' in section of '# Dangerous file name extensions' in Amavisd config file.
IredMail working just fine, we getting all emails in/out but i have another email server for system alerts which other servers connects to via smtp
this is how i have it set and works just fine before until we switch from exchange to ired
1. IredMail Server Domain: domain.com
2. 2nd email Server Domain: e.domain.com
Both servers are using internal IP's, but Ired server has a NAT static ip and other email server does not is only for internal use
NOTE: in Ired, i edit file /etc/postfix/main.cf and added my local ip x.x.x.x/24 and still does not receive email from 2nd mailer server.
any help will be great
dsp3 wrote:Thanks for the reply ThASattler. Here is the postmaster message:
No viruses were found.
Banned name: .dat,image1.wmf
The reason of banning this mail is there is an attached file with file extension .wmf.
You can remove 'wmf|' in section of '# Dangerous file name extensions' in Amavisd config file.
There isn't a .wmf attachment. There is only an .xlsx file attached. As this is a test email, I know what is in it.
This new feature I will be keeping off our production server until I can explore further.
There isn't a .wmf attachment. There is only an .xlsx file attached. As this is a test email, I know what is in it.
This new feature I will be keeping off our production server until I can explore further.
A .xlsx file is virtually a zip archive containing a number of files so maybe the .xlsx zip archive contains a .wmf file inside?
There isn't a .wmf attachment. There is only an .xlsx file attached. As this is a test email, I know what is in it.
This new feature I will be keeping off our production server until I can explore further.
A "Strict open xml-document (xlsx)" is a zip archiv which could contain a windows meta file picture.
But in my case an excel file example.xlsx with a wmf-picture isn't banned whereas the same file renamed to example.wmf is banned.
Hii all,
Iam facing a problem with my iredmail : 0.8.6 and using ubuntu 12.04 and LDAP backend
every three or two days at this week dovecot service suddenly stop
email (pop3 / imap) stop responding, so i need to start manually
when i check to mail.log :
Feb 5 07:12:22 colo postfix/smtpd[6996]: warning: SASL: Connect to dovecot-auth failed: Connection refused
Feb 5 07:12:22 colo postfix/smtpd[6996]: fatal: no SASL authentication mechanisms
Feb 5 07:12:22 colo postfix/master[454]: warning: process /usr/lib/postfix/smtpd pid 6983 exit status 1
Feb 5 07:12:22 colo postfix/master[454]: warning: process /usr/lib/postfix/smtpd pid 6985 exit status 1
this is my main.cf (part of : dovecot auth config )
I-------
167 dovecot_destination_recipient_limit = 1
168 smtpd_sasl_type = dovecot
169 smtpd_sasl_path = ./dovecot-auth
170 content_filter = smtp-amavis:[xxx.xxx.xxx.xxx]:10051
-------
using that configuration work normally over a years, and start problem since 2 weeks a go, dovecot always stop every 3 days, and then 2 days and now every day ..
should i change line 169 to : smtpd_sasl_path = /private/dovecot-auth ?
or maybe any other way ?
please help
thanks
PS :
log from mail.err
root@colo:/var/log# tail f /var/log/mail.err.1
tail: cannot open `f' for reading: No such file or directory
==> /var/log/mail.err.1 <==
Feb 5 06:39:04 colo postfix/smtpd[5120]: fatal: no SASL authentication mechanisms
Feb 5 06:39:04 colo postfix/smtpd[5124]: fatal: no SASL authentication mechanisms
Feb 5 06:39:04 colo postfix/smtpd[5125]: fatal: no SASL authentication mechanisms
Feb 5 06:39:08 colo postfix/smtpd[5112]: fatal: no SASL authentication mechanisms
Feb 5 06:39:14 colo postfix/smtpd[5118]: fatal: no SASL authentication mechanisms
Feb 5 06:39:14 colo postfix/smtpd[5122]: fatal: no SASL authentication mechanisms
Feb 5 06:39:14 colo postfix/smtpd[5126]: fatal: no SASL authentication mechanisms
Feb 5 06:39:19 colo postfix/smtpd[5115]: fatal: no SASL authentication mechanisms
Feb 5 06:39:19 colo postfix/smtpd[5116]: fatal: no SASL authentication mechanisms
Feb 5 06:39:19 colo postfix/smtpd[5121]: fatal: no SASL authentication mechanisms
thanks guys
iredmail fans - indonesia
----
should i change line 169 to : smtpd_sasl_path = /private/dovecot-auth ?
It's relative path under /var/spool/postfix/. In iRedMail-0.8.6, i suppose it's "./dovecot-auth". You can do a quick check.
Feb 5 06:39:04 colo postfix/smtpd[5120]: fatal: no SASL authentication mechanisms
Did you upgrade Postfix or Dovecot 2 weeks ago? Any other changes 2 weeks ago?
Thanks for the feedback and help. Repacked iRedMail-0.9.6 with this fix, also updated upgrade tutorial.
Any related error message in Postfix log files on both servers? Cannot help without related log.