Tag Info

Hot answers tagged

10

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 ...


6

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

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 ...


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 ...


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 ...


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

It calls it up via perl, no deamon required.


4

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, ...


4

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 ...


4

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 ...


4

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=<> ...


4

If you are sure, that all mails to amavis are going to your users and you don't want to lookup your database, then disable your SQL parameters and set @local_domains_maps = ( ["."] ); With that setting every mail amavis receives is considered to have a local user as destination.


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 ...


3

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 ...


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

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];


2

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


2

@spam_admin_map uses also a hash lookup table and lookup is done with a per-recipient key. Therefore you can replace the spam_admin_maps line in the policy bank with something like this: ... spam_admin_maps => [ {"abuse\@spam.spamcop.net" => undef}, "spamalert\@example.com" ], ... Examples can be found in the file amavisd.conf-sample which is ...


2

I would suggest a smtpd_recipient_restriction similar to the following: smtpd_recipient_restricdtions = # Whitelisting or blacklisting: check_recipient_access proxy:mysql:/etc/postfix/mysql-virtual_recipient.cf, # Everyone should play after rules: reject_non_fqdn_recipient, reject_non_fqdn_sender, reject_unknown_recipient_domain, ...


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

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 ...


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

I have resolved this question with OpenDKIM by using SigningTable, KeyTable and TrustedHost parameters. /etc/opendkim/KeyTable – a list of keys available for signing /etc/opendkim/SigningTable - a list of domains and accounts allowed to sign /etc/opendkim/TrustedHosts – a list of servers to trust when signing or verifying The guide I used can be found on ...


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

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 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

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

Amavis/Amavisd-new works as a filtering service. The general flow is Internet -> Postfix (or other) -> Amavisd-new -> Antispam -> Amavis -> A/V -> Postfix -> mailbox. In the specific case of spamassassin the default config of amavisd is to invoke it directly via the perl module Mail::SpamAssassin. If memory serves right the examples (at least on debian) had ...


2

In clamd.conf AllowSupplementaryGroups is default false try this: AllowSupplementaryGroups true


2

Maybe this case was same as yours. Anyway, you can fix it with steps as explained in this batv page. In main.cf, define canonical_maps = regexp:/etc/postfix/batv.regexp In /etc/postfix/batv.regexp, add this line /^prvs=[0-9]{4}[0-9A-Fa-f]{6}=(.*)$/ $1 If it doesn't work please provide the sample of batv address that you encounter in the system. For ...



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