Zitat von Reindl Harald :
Hm, OK, i will start my IDE and develop something nice
local_recipient_maps = mysql:/etc/postfix/mysql-recipients.cf
virtual_alias_maps = mysql:/etc/postfix/mysql-virtual_alias.cf
Can i use both as above because "mysql-recipients.cf" are from
the dbmail-alias-table an
* lst_ho...@kwsoft.de :
> virtual_alias_maps is used for domains listed in
> virtual_alias_domains (= virtual alias domain class)
No, it's always applied!
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benjamin Franklin
Hindenbur
Zitat von Ralf Hildebrandt :
* lst_ho...@kwsoft.de :
virtual_alias_maps is used for domains listed in
virtual_alias_domains (= virtual alias domain class)
No, it's always applied!
Upps, yes. This has confused me some time ago already...
Regards
Andreas
smime.p7s
Description: S/MIME C
Quanah Gibson-Mount:
> Unlike previous postfix releases, postconf changes the ownership of the
> "main.cf" file when it is executed. This breaks things that specifically
> set the ownership on main.cf prior to executing postconf.
Postfix main.cf and master.cf MUST BE OWNED BY ROOT.
Wie
Thanks Jeroen,
I checked the documentation and I think smtpd_sender_login_maps might do
the trick.
Does anyone know if a many-to-many (M-to-M) mapping is allowed in these
maps? That is, the following example is valid (a hash file)?
ma...@example.com user1
ma...@example.com u
* Nikolaos Milas :
> Thanks Jeroen,
>
> I checked the documentation and I think smtpd_sender_login_maps might
> do the trick.
>
> Does anyone know if a many-to-many (M-to-M) mapping is allowed in
> these maps? That is, the following example is valid (a hash file)?
No
>ma...@example.com
Hi All,
I need to rewrite the envelope field "MAIL FROM:" but only for emails which
come
from particular smtp client IP.
Is there any possibility how to do it?
Regards,
Peter Micunek
---
Stavebna fakulta STU, Bratislava
Faculty of Civil Engineering
Peter Micunek:
> Hi All,
>
> I need to rewrite the envelope field "MAIL FROM:" but only for
> emails which come
> from particular smtp client IP.
> Is there any possibility how to do it?
Can you describe the problem, instead of the solution (per
client rewriting)?
Wietse
Thanks Ralf,
That means that the following format should be OK?
ma...@example.com user1,user2,user3
ma...@example.com user1,user2
ma...@example.com user1,user3
This is still a M-to-M mapping (many mail addresses are mapped to many
SASL login usernames), it's just format
* Nikolaos Milas :
> Thanks Ralf,
>
> That means that the following format should be OK?
>
>ma...@example.com user1,user2,user3
>ma...@example.com user1,user2
>ma...@example.com user1,user3
>
> This is still a M-to-M mapping (many mail addresses are mapped to
> many SA
Wietse,
problem is that I need to have one domain in the field "MAIL FROM:" for all
emails
come from particular client for example 10.10.10.10 to my postfix server.
The mail header field "From:" will be preserved.
I need to do because these emails is routed via transport map to the
destinati
Peter Micunek:
> Wietse,
>
> problem is that I need to have one domain in the field "MAIL FROM:"
> for all emails come from particular client for example 10.10.10.10
> to my postfix server. The mail header field "From:" will be
> preserved.
You need to configure as follows:
1) Configure Postfix
On 2/8/2011 8:08 AM, Peter Micunek wrote:
Wietse,
problem is that I need to have one domain in the field "MAIL FROM:" for all
emails
come from particular client for example 10.10.10.10 to my postfix server.
The mail header field "From:" will be preserved.
I need to do because these emails is ro
Wietse Venema:
> Peter Micunek:
> > Wietse,
> >
> > problem is that I need to have one domain in the field "MAIL FROM:"
> > for all emails come from particular client for example 10.10.10.10
> > to my postfix server. The mail header field "From:" will be
> > preserved.
>
> You need to configure
Wietse,
It seems that you helped me.
Thanks a lot
PM
On Tue, 8 Feb 2011 10:26:19 -0500 (EST), Wietse Venema wrote
> Wietse Venema:
> > Peter Micunek:
> > > Wietse,
> > >
> > > problem is that I need to have one domain in the field "MAIL FROM:"
> > > for all emails come from particular client
On Tue, Feb 08, 2011 at 09:25:06AM +0100, lst_ho...@kwsoft.de wrote:
> local_recipient_maps is used for recipients with domain part listed in
> mydestination (= local domain class)
> virtual_alias_maps is used for domains listed in virtual_alias_domains (=
> virtual alias domain class)
NO, virt
Peter Micunek:
> Wietse,
>
> It seems that you helped me.
>
> Thanks a lot
Good. for posteriority, the examples below uses smtp_header_checks
syntax instead of smtp_generic_checks syntax. Either feature should
do the job, when used appropriately.
Wietse
> PM
>
> On Tue, 8 Feb 2011 10
OpenSSL.org states:
aNULL
the cipher suites offering no authentication. This is currently the
anonymous DH algorithms. These cipher suites are vulnerable to a ``man in
the middle'' attack and so their use is normally discouraged.
However, this cipher suite is enabled by default with postfix
--On Tuesday, February 08, 2011 11:39 AM -0800 Quanah Gibson-Mount
wrote:
OpenSSL.org states:
aNULL
the cipher suites offering no authentication. This is currently the
anonymous DH algorithms. These cipher suites are vulnerable to a ``man in
the middle'' attack and so their use is normally d
Hello,
I noticed after configuring sender_dependent_relayhost_maps and
expecting it to forward mail to my listed destination does not work as
expected.
I need sender_dependent_relayhost_maps to forward mail depending what
the the source is.
Our team has split into 2 so since we have 2 relays I fi
On Tue, Feb 08, 2011 at 11:39:14AM -0800, Quanah Gibson-Mount wrote:
> OpenSSL.org states:
>
> aNULL
>
> the cipher suites offering no authentication. This is currently the
> anonymous DH algorithms. These cipher suites are vulnerable to a ``man in
> the middle'' attack and so their use is norma
On Tue, Feb 08, 2011 at 02:01:43PM -0500, Wietse Venema wrote:
> Good. for posteriority, the examples below uses smtp_header_checks
> syntax instead of smtp_generic_checks syntax. Either feature should
> do the job, when used appropriately.
That would be smtp_generic_maps of course, which rewrite
On 02/08/2011 08:47 PM, GB GB wrote:
Hello,
I noticed after configuring sender_dependent_relayhost_maps and
expecting it to forward mail to my listed destination does not work as
expected.
I need sender_dependent_relayhost_maps to forward mail depending what
the the source is.
Our team has spli
Hi, geotrust
has changed ssl procedures
for this in i.e apache
i have to add intermediate in a extra
SSLCACertificateFile
like written here
http://www.geotrust.com/resources/extended-validation-ssl/installation-instructions.html
for some browsers
so now comes the question related to postfix before
Zitat von Victor Duchovni :
On Tue, Feb 08, 2011 at 09:25:06AM +0100, lst_ho...@kwsoft.de wrote:
local_recipient_maps is used for recipients with domain part listed in
mydestination (= local domain class)
virtual_alias_maps is used for domains listed in virtual_alias_domains (=
virtual alias d
My apologies, the sender_relay contains
/r...@ltest01.domain.com/ [1.2.3.4]
Regxp is what I will use for this map
Regards,
On 2011-02-08, at 3:48 PM, Jeroen Geilman wrote:
> On 02/08/2011 08:47 PM, GB GB wrote:
>> Hello,
>>
>> I noticed after configuring sender_dependent_relayhost_maps an
gbcy...@gmail.com:
> My apologies, the sender_relay contains
> /r...@ltest01.domain.com/ [1.2.3.4]
>
> Regxp is what I will use for this map
Please show COMPLETE postconf -n output. As documented at
http://www.postfix.org/postconf.5.html#sender_dependent_relayhost_maps
the sender_dependent_r
On 2011-02-07 8:28 PM, Noel Jones wrote:
> On 2/7/2011 5:44 PM, Reindl Harald wrote:
>> "mysql-recipients.cf" is querying dbmail for valid addresses
>> dbmail do not have domain-aliases and so postfix should handle
>> this by saying "thelounge.at is an alias for the lounge.net
>> and if someone sen
Am 08.02.2011 22:32, schrieb Charles Marcus:
>> Don't use "domain aliases".
>>
>> Wildcard address rewrites disable recipient validation.
>
> Postfixadmin (2.3.2+) has working recipient verification with alias
> domains...
Hm - I will take a look what they do if i find no simple solution
exter
On 2/8/2011 3:32 PM, Charles Marcus wrote:
On 2011-02-07 8:28 PM, Noel Jones wrote:
On 2/7/2011 5:44 PM, Reindl Harald wrote:
"mysql-recipients.cf" is querying dbmail for valid addresses
dbmail do not have domain-aliases and so postfix should handle
this by saying "thelounge.at is an alias for
On 2011-02-08 4:39 PM, Noel Jones wrote:
> On 2/8/2011 3:32 PM, Charles Marcus wrote:
>> On 2011-02-07 8:28 PM, Noel Jones wrote:
>>> Don't use "domain aliases".
>>>
>>> Wildcard address rewrites disable recipient validation.
>> Postfixadmin (2.3.2+) has working recipient verification with alias
>
here is the outputthe current version of postfix is 2.3.19
2bounce_notice_recipient = postmaster
access_map_reject_code = 554
address_verify_default_transport = $default_transport
address_verify_local_transport = $local_transport
address_verify_map =
address_verify_negative_cache = yes
address
GB GB:
> here is the outputthe current version of postfix is 2.3.19
>
I asked for "postconf -n" output.
I did not ask for hundreds of parameter settings.
Wietse
Un message de Mickael t'attend...
L'expéditeur et le contenu seront visibles seulement par toi et tu peux le
supprimer à tout moment. Tu peux aussi y répondre directement au travers du
messenger. Pour découvrir qui est à l'origine du message, suis simplement ce
lien:
http://eu1.badoo.com/019942
postconf -n -c /etc/postfix-hd will render the output I sent in the
earlier mail
regards,
On Tue, Feb 8, 2011 at 5:20 PM, Wietse Venema wrote:
> GB GB:
>> here is the outputthe current version of postfix is 2.3.19
>>
>
> I asked for "postconf -n" output.
>
> I did not ask for hundreds of
On 2/8/2011 5:39 PM, GB GB wrote:
postconf -n -c /etc/postfix-hd will render the output I sent in the
earlier mail
regards,
On Tue, Feb 8, 2011 at 5:20 PM, Wietse Venema wrote:
GB GB:
here is the outputthe current version of postfix is 2.3.19
I asked for "postconf -n" output.
I di
GB GB:
> postconf -n -c /etc/postfix-hd will render the output I sent in the
> earlier mail
I don't have time for people with hundreds of parameters
in their main.cf file.
You can find out for yourself if the requirements for
sender_dependent_relayhost_maps are met: no transport_maps,
no rel
When I search for those clauses I come up with the following
address_verify_relayhost = $relayhost
address_verify_transport_maps = $transport_maps
proxy_read_maps = $local_recipient_maps $mydestination
$virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps
$virtual_mailbox_domains $relay
On Tue, 2011-02-08 at 22:04:38 +0100, Robert Schetterer wrote:
> Hi, geotrust
> has changed ssl procedures
> for this in i.e apache
> i have to add intermediate in a extra
> SSLCACertificateFile
[ .. ]
> i am not quite sure if or how i should include
> intermediate ca in postfix
The TLS_README
On 2/3/11 11:52 AM, Reindl Harald wrote:
>> When someone reports a problem with mail from a given server, I can
>> grep for the ip address of the server, then re-grep for the connection
>> ids associated with that address and get everything that was ever logged
>> about mail from that server.
>
>
On 2/4/11 3:31 AM, Alokat wrote:
> On 02/03/2011 08:10 PM, Reindl Harald wrote:
>> AFAIK this is a problem that does not exist in the real world
>> We are hosting 200 mail domains and there is one hostname
>> and one certificate for all of them
> yeah I guess I will just use one certificate for a
> I'm afraid Wolfgang's method is the only one, then - you'd have to
> correlate all recipients by incoming queue-id.
> A perl array could probably do this moderately efficiently, but I know
> of no ready-made tools that do this - especially since, as you said, the
> Subject: logging was customi
GB GB put forth on 2/8/2011 4:52 PM:
> so if I understand correctly, when I use
> sender_dependent_relayhost_maps transport and relayhost need to be
> empty
GB GB put forth on 2/8/2011 4:10 PM:
> here is the outputthe current version of postfix is 2.3.19
>
> mail_release_date = 20040915
>
meyer-jor...@t-online.de put forth on 2/8/2011 11:59 PM:
>> I'm afraid Wolfgang's method is the only one, then - you'd have to
>> correlate all recipients by incoming queue-id.
>> A perl array could probably do this moderately efficiently, but I know
>> of no ready-made tools that do this - espec
44 matches
Mail list logo
