1 Topic by fabrifaa

  • fabrifaa
  • Member
  • Offline
  • Registered: 2014-01-28
  • Posts: 3

Topic: Disable amavisd

==== Required information ====
- iRedMail version:
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Linux/BSD distribution name and version:
- Related log if you're reporting an issue:
======== Required information ====
- iRedMail version: 0.8.5 i think - not sure how i updated if at all
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Linux/BSD distribution name and version: Debian 7
- Related log if you're reporting an issue:
====

Hi,

I am in the same situation as this one: http://www.iredmail.org/forum/topic3708 … avisd.html

however, I can't seem to flush the mails, if that was the working solution (the guy didn't write his solution).

I tried the command    postfix flush   as root but mailq shows again all the emails there, nothing happened

I'd be very grateful if you could help, thanks.

ps it used to work till last month, I only realised it now. Since November I disabled amavisd and it has always worked.. Since December this log shows up

Fab

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,091

Re: Disable amavisd

Please, could you please clearly explain what your issue is?

If you want to completely disable Amavisd + SpamAssassin + ClamAV, here's tutorial:
http://www.iredmail.org/wiki/index.php? … amAssassin

3 Reply by fabrifaa

  • fabrifaa
  • Member
  • Offline
  • Registered: 2014-01-28
  • Posts: 3

Re: Disable amavisd

Sorry for not being clear, I will write it better.

I installed iRedMail around September and followed the tutorial you posted for disabling amavis & clamd. Everything was working fine.

Since around December I have the same issues as described in http://www.iredmail.org/forum/topic2626 … virus.html AND described in http://www.iredmail.org/forum/topic3708 … avisd.html

In particular, the latter post seems the most similar to my situation: after disabling everything needed, I still have emails in queue (read your reply http://www.iredmail.org/forum/post17195.html#p17195). Unfortunately the guy didn't write how he solved the issue, i.e. how did he flush his queue (I guess), so I am asking how could I solve my problem.

So the problem is that logs still show "connect to 127.0.0.1[127.0.0.1]:10024: Connection refused" despite I have disabled amavisd and restarted postfix with the configuration content_filter equal to blank.

Thanks!
Fab

4 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,091

Re: Disable amavisd

I guess you have some emails in Postfix mail queue before disabling Amavisd, these emails were set to be submitted to Amavisd for content-based scanning. So no matter how many times you flush Postfix queue, Postfix will try to submit them to Amavisd again and again.

You can try this:

*) Start Amavisd/ClamAV services, but don't enable 'content_filter=' in Postfix.
*) Flush Postfix queue with command "postqueue -f".
*) When you don't have mail stalled in queue, since you don't have "content_filter=" in Postfix, newly received emails won't be submitted to Amavisd for content-based scanning anymore, so it's now safe to disable Amavisd/ClamAV service.

That's all. Hope it helps.

Again, please always clearly explain what your issue is, paste related error log, paste related Postfix/Dovecot settings if necessary.
Do not refer to other's topic for issue explanation, it's hard to understand what your issue is.

5 Reply by fabrifaa

  • fabrifaa
  • Member
  • Offline
  • Registered: 2014-01-28
  • Posts: 3

Re: Disable amavisd

I can't test because my mail queue was reset after a timeout, but I now understand that procedure, and I think that'd have solved the issue - thanks very much.


Sorry, I thought that linking other similar issues would make it more clear :v