Tag Info

Hot answers tagged

9

The problem is your Amavis setup. Your quarantine destination seems to be a mail address. So Amavis injects the virus mail back into Postfix to be delivered to that address. Postfix now decides to scan the mail first and delegates to Amavis. Amavis recognizes the virus and tries to quarantine it by delivering to the quarantine mail address. So ... You get ...


5

Just send an email with the eicar test file attached. This file has a signature which any virus scanner should know and detect. As for the monitoring of the clamd process itself, there are many possibilities. I personally prefer using monit for it.


5

Amavis is in the default installation of Mac OS X. It can be used with SMTP server like Postfix (also installed with mac os x). But even if it comes with all Mac OS X installation, it is here to be used by Mac OS X server. But of course, by configuring manually postfix and amavis on mac os x client you could use them. There is a web page on Apple website ...


5

If your using amavisd-new, you can simply run the amavisd-release command, passing it the quarantine ID of the mail in question. It will take care of removing the email from the quarantine and injecting the email into Postfix, bypassing any content filtering. You can find out the details at ...


4

It calls it up via perl, no deamon required.


4

You need to provide more detailed logging output to solve that: Stop amavisd and restart it in debug mode (amavisd debug, on Debian/Ubuntu it's probably amavisd-new debug, but since you mention you configured amavisd with amavisd.conf and not /etc/amavis/conf.d/50-user, I guess you are not on Debian/Ubuntu). While you do that, you will probably want to ...


4

Silly me. Just found out about this page: http://www.postfix.org/addon.html ... and I quote: mailscanner system, works with Postfix and other MTAs. WARNING: This software uses unsupported methods to manipulate Postfix queue files directly. This will result in corruption or loss of mail. The mailscanner authors have sofar refused to discuss a proper ...


3

You order of rules is very bad. If you want to keep all of them and not add anything else, the order must be: smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_pipelining, reject_invalid_hostname, reject_non_fqdn_sender, reject_unknown_sender_domain, reject_unauth_destination, reject_unknown_recipient_domain, ...


3

Have you checked this parameter: @local_domains_acl It is defined on /etc/amavis/conf.d/05-domain_id. According to the Amavisd-new documentaion on http://www.ijs.si/software/amavisd/: No spam-related headers inserted? Here are some reasons: @local_domains_acl is not correctly set. These headers are only inserted for recipients matching ...


3

to disable milter processing after amavis, add to your master.cf in the after-amavis section 127.0.0.1:10025 inet n - - - - smtpd [....] -o smtpd_milters= if you want to run the milter after amavis, set the smtpd_milters= configuration option in main.cf to an empty string and add the inet:localhost:8891 configuration to ...


3

Since you want to disable virus checking entirely, the easiest way to do so is find the @bypass_virus_checks_maps line in the Amavis configuration files (amavis.conf or conf.d/50-user) and change it to this; bypass_virus_checks_maps => [1];


3

The logs above is expected behavior from postfix and amavis. For after queue content filter like amavis, the filter needs reinject email to postfix. For more info please refers to official documentation. Here some explanation of postfix and amavis action. Jul 19 07:59:06 mail postfix/smtpd[15492]: connect from unknown[37.215.63.185] Client from ...


3

Additionally to the explanations from masegaloeh, I want to point out, why the spammer got through in your case. Look at the following line in the logs: Jul 19 07:59:07 mail postfix/smtpd[15492]: NOQUEUE: reject_warning: RCPT from unknown[37.215.63.185]: 504 5.5.2 <37.215.63.185>: Helo command rejected: need fully-qualified hostname; from=<> ...


3

There are several options to accomplish this, and they all largely depend on the delivery agent you are using to do the final delivery to a user's virtual mailbox. If you are using the stock Postfix virtual(8) delivery agent, you can't accomplish this. If you are using either the Cyrus LDA or the Dovecot LDA, you habe two more options: You can either use ...


2

You might want to take a look at dspam. It integrates with Dovecot and does basically exactly what you want, but on the fly, as the move operations happen (moving into Junk => spam, moving out of Junk => false positive).


2

You can use the parameter %admin_maps_by_ccat to define whom amavisd-new sends Mails for each of its categories. With undef you can disable the mails. So you have to define a setting like the following if you don't want to get mails for all "unchecked" mails: $admin_maps_by_ccat{+CC_UNCHECKED} = undef;


2

Postfix has a header_check facility to allow you to scan headers and decide what to do with the email at that time. Docs: http://www.postfix.org/header_checks.5.html /^Date: .* (19[0-9][0-9]|200[0-9]|2010)/ REJECT Your email is stuck in a timewarp This is an example of a date check. Unfortunately, this is not dynamic. Postfix does support Sendmail ...


2

You may want to check that the users in the @spam_lovers_maps correspond to the user who needs to receive any and all spam, and that messages to him do not get caught in the $final_spam_destiny = D_DISCARD; trap. You may also want to ensure that the user does not have any .procmail files, or similar delivery time scripts that may discard the mail after ...


2

GNU Mailman has the "not metoo" and "no dupes" user config options, which do exactly what you're looking for. Additionally, Mailman is very easy to get working with postfix.


2

Solved on Amavis Users Group... Thanks Mark Martinec Requires two changes: In /etc/amavis/conf.d/50-user add this: ################## ---- CUSTOM SIGNATURES AS DISCLAIMERS ------- ############################### # uses altermime to insert a different signatue per users # signatures are located in teh /etc/postfix/signatures/ directory # also needs a small ...


2

Oh boy. So, I figured it out. Turns out it was a Nagios script that checks whether amavis is running, and more importantly for this particular issue, checks that the AV engine is working... by sending it the EICAR virus. http://exchange.nagios.org/directory/Plugins/Anti-2DVirus/Amavis/check_amavis/details is the script in question if anyone is interested. ...


2

Amavisd-new uses SpamAssassin's perl modules directly, so all the spam processing is done directly in the amavisd processes.


1

In the main.cf, set smtpd_data_restrictions = reject_unauth_pipelining,permit_sasl_authenticated,check_sender_access pcre:/etc/postfix/content_filter.pcre Do not set content_filter= in main.cf! /etc/postfix/content_filter.pcre should be something like: /^/ FILTER smtp-amavis:[127.0.0.1]:10024 Do not forget to run postmap ...


1

You'll need to setup something like procmail or maildrop to filter the mail into the correct folder when it gets delivered. Using maildrop you can have a default system wide config which will check the headers and filter spam into the correct location, with something like this in /etc/maildroprc: if (/^X-Spam-Status: yes) { to "Maildir/.Spam" } ...


1

strace one of the stuck processes. It might give you a hint what's wrong. strace -p PROCESSIDOFSTUCKPROCESS Cheers


1

You could write a script that crawl the users "Spam" folder and train dspam from those mails. You could also filter mail from amavisd-new with something like: (blow is just an example stub config, untested) /etc/postfix/dspam_filter_access /^<xxx-spam-regex-subject?,to?>.*$/ FILTER dspam:dspam /./ OK /etc/postfix/master.cf dspam ...


1

At startup, modern amavisd-new version look for a number of binaries in $PATH, including the dspam executable. If this one is found, dspam will automatically be trained with the results of all other spam checks configured in amavisd-new. The only downside is: All mail content is learned with only one user id (same as amavisd-new's SA integration). And, ...


1

You can delete emails with a particular tag in header. See Postfix Header Checks Man page for details. Example: In "/etc/postfix/main.cf", add header_checks = regexp:/etc/postfix/header_checks In "/etc/postfix/header_checks", have /^(Subject: \[SPAM\])(.+)$/ DISCARD The above will discard all emails whose Subject starts with "[SPAM]". EDIT: I ...


1

In your Spamassassin local.cf file (usually located in /etc/mail/spamassassin) add the following line: blacklist_from <person you wish to blacklist. wildcards are acceptable> You can get more information on Spamassassin whitelist/blacklist here Restart spamassassin when you are done.


1

Postfix has a always_bcc setting, which you might want to use or look into.



Only top voted, non community-wiki answers of a minimum length are eligible