Em 2017-07-07 13:58, Informatico Iberostar Ensenachos (Armando Ramos
Roche) escreveu:
Estimados, tengo la siguiente situacion,
Actualmente tengo en mi empresa el Surf Control y Exchange montado, y
quiero cambiar el surf control por el postfix y aquí les tengo la
siguiente situacion.
Ya tengo una pc virtual montada con Ubuntu Server Ubuntu 16.04.2 LTS
(GNU/Linux 4.4.0-84-generic x86_64) y le instale el postfix 3.1.0 +
spamassasin 3.4.1 y ClamAV 0.99.2 funciona perfectamente, pero no se
como hacer algo que con el Surf Control hacia muy facilmente y son sus
reglas.
En el surf control tengo reglas de que por ejemplo todos los correos
que lleguen hacia una direccion especifica se ponga en copia a otra
direccion, ejemplo le llega un coreo a pep...@dominio.cu se haga una
copia a juan...@dominio.cu.. solo he encontrado la opcion redirect
pero eso lo que hace es redirigir y no le llega al destinatario
original.
Otra de las reglas que uso en el surf control es que si llega un coreo
desde un dominio externo sin importar a quien se envie, se ponga en
copia a otra direccion.
Quedo a la esperar de su ayuda.
Saludos
______________________________________________________________________
Lista de correos del Grupo de Usuarios de Tecnologías Libres de Cuba.
Gutl-l@jovenclub.cu
https://listas.jovenclub.cu/cgi-bin/mailman/listinfo/gutl-l
Hecha un ojo a las opciones
always_bcc
always_bcc (default: empty)
Optional address that receives a "blind carbon copy" of each message
that is received by the Postfix mail system.
Note: with Postfix 2.3 and later the BCC address is added as if it
was specified with NOTIFY=NONE. The sender will not be notified when the
BCC address is undeliverable, as long as all down-stream software
implements RFC 3461.
Note: with Postfix 2.2 and earlier the sender will be notified when
the BCC address is undeliverable.
Note: automatic BCC recipients are produced only for new mail. To
avoid mailer loops, automatic BCC recipients are not generated after
Postfix forwards mail internally, or after Postfix generates mail itself
recipient_bcc_maps (default: empty)
Optional BCC (blind carbon-copy) address lookup tables, indexed by
recipient address. The BCC address (multiple results are not supported)
is added when mail enters from outside of Postfix.
Specify zero or more "type:name" lookup tables, separated by
whitespace or comma. Tables will be searched in the specified order
until a match is found.
The table search order is as follows:
Look up the "user+extens...@domain.tld" address including the
optional address extension.
Look up the "u...@domain.tld" address without the optional
address extension.
Look up the "user+extension" address local part when the
recipient domain equals $myorigin, $mydestination, $inet_interfaces or
$proxy_interfaces.
Look up the "user" address local part when the recipient domain
equals $myorigin, $mydestination, $inet_interfaces or $proxy_interfaces.
Look up the "@domain.tld" part.
Note: with Postfix 2.3 and later the BCC address is added as if it
was specified with NOTIFY=NONE. The sender will not be notified when the
BCC address is undeliverable, as long as all down-stream software
implements RFC 3461.
Note: with Postfix 2.2 and earlier the sender will unconditionally
be notified when the BCC address is undeliverable.
Note: automatic BCC recipients are produced only for new mail. To
avoid mailer loops, automatic BCC recipients are not generated after
Postfix forwards mail internally, or after Postfix generates mail
itself.
Example:
recipient_bcc_maps = hash:/etc/postfix/recipient_bcc
After a change, run "postmap /etc/postfix/recipient_bcc".
This feature is available in Postfix 2.1 and later.
sender_bcc_maps (default: empty)
Optional BCC (blind carbon-copy) address lookup tables, indexed by
sender address. The BCC address (multiple results are not supported) is
added when mail enters from outside of Postfix.
Specify zero or more "type:name" lookup tables, separated by
whitespace or comma. Tables will be searched in the specified order
until a match is found.
The table search order is as follows:
Look up the "user+extens...@domain.tld" address including the
optional address extension.
Look up the "u...@domain.tld" address without the optional
address extension.
Look up the "user+extension" address local part when the sender
domain equals $myorigin, $mydestination, $inet_interfaces or
$proxy_interfaces.
Look up the "user" address local part when the sender domain
equals $myorigin, $mydestination, $inet_interfaces or $proxy_interfaces.
Look up the "@domain.tld" part.
Note: with Postfix 2.3 and later the BCC address is added as if it
was specified with NOTIFY=NONE. The sender will not be notified when the
BCC address is undeliverable, as long as all down-stream software
implements RFC 3461.
Note: with Postfix 2.2 and earlier the sender will be notified when
the BCC address is undeliverable.
Note: automatic BCC recipients are produced only for new mail. To
avoid mailer loops, automatic BCC recipients are not generated after
Postfix forwards mail internally, or after Postfix generates mail
itself.
Example:
sender_bcc_maps = hash:/etc/postfix/sender_bcc
After a change, run "postmap /etc/postfix/sender_bcc".
This feature is available in Postfix 2.1 and later.
En general casi todos resuelven con always_bcc
--
Salu2, Ulinx
"En un problema con n ecuaciones
siempre habrá al menos n+1 incógnitas"
Linux user 366775
______________________________________________________________________
Lista de correos del Grupo de Usuarios de Tecnologías Libres de Cuba.
Gutl-l@jovenclub.cu
https://listas.jovenclub.cu/cgi-bin/mailman/listinfo/gutl-l
