Dustin wrote:
> Guys,
> Thanx for the comments...
> I think the light is starting to dimly glow above my head! However, if
> I add these IP hosts to $mynetworks, wouldn't I then need to create some
> type of access map that explicitly denies any sender addresses from the
> domains we protect. I
Guys,
Thanx for the comments...
I think the light is starting to dimly glow above my head! However, if
I add these IP hosts to $mynetworks, wouldn't I then need to create some
type of access map that explicitly denies any sender addresses from the
domains we protect. In other words:
smtpd_sende
Mark,
in amavisd.conf-defaults are shown defaults for the following:
# $banned_admin = [EMAIL PROTECTED]; # for compatibility with pre-2.2.1
# $bad_header_admin = [EMAIL PROTECTED]; # for compatibility with pre-2.2.1
# @banned_admin_maps= (\$banned_admin);
# @bad_header_admin_maps= (\$b
Hi,
I updated my environment from amavis 2.2 to 2.3.3 and Postfix from
2.2.5 to 2.2.9.
I have a user who gets his mail from a multidrop account. He uses the
X-ORIGINAL-TO Header to distribute the mails on his mailserver.
Before upgrade: The X-original-to header has the original email, after
the
Dustin wrote:
> This would be true if our server was directly attached to or hosted all
> the mailboxes for the protected domains...we, however, are only using
> this solution as a gateway for incoming mail for all the domains we
> protect...which postfix then forwards (after filtering, etc.) to t
At 12:23 PM 3/16/2006, Dustin Humm wrote:
This would be true if our server was directly attached to
or hosted all
the mailboxes for the protected domains...we, however, are
only using
this solution as a gateway for incoming mail for all the
domains we
protect...which postfix then forwards (afte
Maurizio wrote:
> i want a certain domain (eg datalogica.com) using my mailgw could send zipped
> attaches with password and containing .exe files
> i searched docs
> http://www.ijs.si/software/amavisd/amavisd-new-docs.html#wblist
> and i find that to whitelist a domain i should add it to this l
This would be true if our server was directly attached to or hosted all
the mailboxes for the protected domains...we, however, are only using
this solution as a gateway for incoming mail for all the domains we
protect...which postfix then forwards (after filtering, etc.) to the
'real' mail host for
Quoting Mark Martinec <[EMAIL PROTECTED]>:
Jesus,
Hello all, i get this error in a postfix-amavisd system after upgrade some
modules:
Mar 16 16:41:32 gate postfix/smtp[9005]: 5F8191F1969: to=<[EMAIL PROTECTED]>,
relay=127.0.0.1[127.0.0.1], delay=6, status=deferred (host
127.0.0.1[127.0.0.1] s
Jesus,
> Hello all, i get this error in a postfix-amavisd system after upgrade some
> modules:
>
> Mar 16 16:41:32 gate postfix/smtp[9005]: 5F8191F1969: to=<[EMAIL PROTECTED]>,
> relay=127.0.0.1[127.0.0.1], delay=6, status=deferred (host
> 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error in processing,
Hello all, i get this error in a postfix-amavisd system after upgrade some
modules:
Mar 16 16:41:32 gate postfix/smtp[9005]: 5F8191F1969: to=<[EMAIL PROTECTED]>,
relay=127.0.0.1[127.0.0.1], delay=6, status=deferred (host 127.0.0.1[127.0.0.1]
said: 451 4.5.0 Error in processing, id=08909-07, parts_
At 06:51 PM 3/15/2006, Dustin Humm wrote:
We protect roughly 25 domains with
postfix/amavis/spamassassin. All of
these domains need to be able to talk to one another.
Although we are
using this system for incoming mail only, we, obviously,
need to allow
communication between the domains that
Felix,
Thanx for the input. I would actually agree that this seems like more
of an MTA issue than anything else, but I'm not sure how to enforce
tests against both TO & FROM address (at the same time - like a SA meta
rule) within postfix...
Additionally, we are using SPF...however, I have been w
i want a certain domain (eg datalogica.com) using my mailgw could send zipped
attaches with password and containing .exe files
i searched docs
http://www.ijs.si/software/amavisd/amavisd-new-docs.html#wblist
and i find that to whitelist a domain i should add it to this lookup list:
@whitelist_send
Hi,
since spamassassin 3.1.1, sa-update permit to update spamassassin rules
and put them in /var/lib/spamassassin/3.001001/updates_spamassassin_org.
The spamd process read this directory and all rules there overwrite the
ones of /usr/share/spamassassin.
amavisd-new doesn't seen to read this direct
Maurizio,
> Mar 16 13:15:18 mailgw1 amavis[8918]: (08884-03) run_command: child process
> [8918]: Failed to exec SCALAR(0x88046d8)
> lq /var/lib/amavis/tmp/amavis-20060316T131342-08884/parts/p003.exe: No such
> file or directory at /usr/sbin/amavisd-new line 1886.\n
Looks like a bad specification
debian unstable
ii amavisd-new 2.3.3-4Interface between MTA
and virus scanner/cont
I get this error in /var/log/syslog
Mar 16 13:15:18 mailgw1 amavis[8918]: (08884-03) run_command: child process
[8918]: Failed to exec SCALAR(0x88046d8)
lq /var/lib/amavis/tmp/a
17 matches
Mail list logo
