meyer-jor...@t-online.de wrote:
Hi Noel!
Your error report is inconsistent with how postfix works,
which usually means the actual configuration isn't what you
think it is.
Please post "postconf -n" output, master.cf contents, and log
entries from the non-working system. It's best if you po
Hi Noel!
> Your error report is inconsistent with how postfix works,
> which usually means the actual configuration isn't what you
> think it is.
>
> Please post "postconf -n" output, master.cf contents, and log
> entries from the non-working system. It's best if you post
> unaltered entries
Ulrich Mierendorff a écrit :
> [snip]
> Ok, I am now using ex1.example.com as myhostname and it works perfectly.
> Mouss, Magnus, thank you so much!
> But I do not understand one thing: Do I also have to add ex1 to DNS?
>
yes. and make it resolve to the (public) IP of server B.
Otherwise, your m
Simon wrote:
Jun 8 07:15:19 mail-in1 postfix/trivial-rewrite[23183]: warning: mysql
query failed: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and
(utf8_general_ci,COERCIBLE) for operation '='
Jun 8 07:15:19 mail-in1 postfix/trivial-rewrite[23183]: fatal:
mysql:/etc/postfix/mysql-tr
Hi There,
We have postfix storing its transport and alias data in mysql, but we are
getting this error (which has just appeared out of knowwhere - yes well, OK,
not knowwhere, but we dont know where!)
# cat /etc/postfix/mysql-transport.cf
user = mail-in1
password = **
dbname = postfix
table =
mouss wrote:
Ulrich Mierendorff a écrit :
mouss wrote:
Ulrich Mierendorff a écrit :
Magnus Bäck wrote:
On Sunday, June 07, 2009 at 17:02 CEST,
Ulrich Mierendorff wrote:
My current configuration looks like this one:
...
myhostname = example.com
m
Ulrich Mierendorff a écrit :
> mouss wrote:
>> Ulrich Mierendorff a écrit :
>>
>>> Magnus Bäck wrote:
>>>
On Sunday, June 07, 2009 at 17:02 CEST,
Ulrich Mierendorff wrote:
> My current configuration looks like this one:
> ...
> myhostname = exa
Magnus Bäck wrote:
On Sunday, June 07, 2009 at 21:46 CEST,
Ulrich Mierendorff wrote:
mouss wrote:
Then change the hostname of server B. why do you set
myhostname = example.com
try with something like
myhostname = joe.example.com
where joe.example.com resolves in DNS. Ideally
On Sunday, June 07, 2009 at 21:46 CEST,
Ulrich Mierendorff wrote:
> mouss wrote:
>
> > Then change the hostname of server B. why do you set
> > myhostname = example.com
> >
> > try with something like
> >
> > myhostname = joe.example.com
> >
> > where joe.example.com resolves in DNS. Ideally
mouss wrote:
Ulrich Mierendorff a écrit :
Magnus Bäck wrote:
On Sunday, June 07, 2009 at 17:02 CEST,
Ulrich Mierendorff wrote:
My current configuration looks like this one:
...
myhostname = example.com
myorigin = /etc/mailname
mydomain = example.com
mydestination = $mydoma
Ulrich Mierendorff a écrit :
> Magnus Bäck wrote:
>> On Sunday, June 07, 2009 at 17:02 CEST,
>> Ulrich Mierendorff wrote:
>>
>>
>>> My current configuration looks like this one:
>>> ...
>>> myhostname = example.com
>>> myorigin = /etc/mailname
>>> mydomain = example.com
>>> mydestination =
Magnus Bäck wrote:
On Sunday, June 07, 2009 at 17:02 CEST,
Ulrich Mierendorff wrote:
My current configuration looks like this one:
...
myhostname = example.com
myorigin = /etc/mailname
mydomain = example.com
mydestination = $mydomain, localhost
Is this server B? If so, why does
On Sunday, June 07, 2009 at 17:02 CEST,
Ulrich Mierendorff wrote:
> mouss wrote:
>
> > if you don't configure B to deliver mail for example.com, then it
> > should lookup DNS and pass the mail to A.
> >
> > if at loss, you can still use transport_maps:
> >
> > example.com relay:[serverA]
> >
mouss wrote:
Ulrich Mierendorff a écrit :
Hi,
My email is handled by two servers A and B with different IPs.
If someone sends an email to my domain "example.com", it will be
received by server A and then stored on that server.
If I send an email to someone else from {userna...@example.com, I
Ulrich Mierendorff a écrit :
> Hi,
>
> My email is handled by two servers A and B with different IPs.
> If someone sends an email to my domain "example.com", it will be
> received by server A and then stored on that server.
> If I send an email to someone else from {userna...@example.com, I will
>
On Sunday, June 07, 2009 at 16:12 CEST,
Ulrich Mierendorff wrote:
> My email is handled by two servers A and B with different IPs.
> If someone sends an email to my domain "example.com", it will be
> received by server A and then stored on that server.
> If I send an email to someone else fr
Hi,
My email is handled by two servers A and B with different IPs.
If someone sends an email to my domain "example.com", it will be
received by server A and then stored on that server.
If I send an email to someone else from {userna...@example.com, I will
connect to server B that will then send
On Sunday, June 07, 2009 at 10:28 CEST,
Mike Robinson wrote:
[...]
> I'd be interested in knowing what's wrong with reusing the transport
> maps in the way that I have?
What would happen if you'd add some other domain to your transport
table? Say, hotmail.com in order to resolve a delivery
On Sunday 07 June 2009 09:14:24 mouss wrote:
>
> maybe be because you forgot to put that domain under relay_domains.
>
Ah, right, yes. Thanks!
>
> you don't have permit_mynetworks here. and btw, the order of your checks
> is dubious.
>
> smtpd_recipient_restrictions =
> reject_non_fqdn_r
Mike Robinson a écrit :
> Hi Magnus,
>
> Thanks for replying.
>
>> If that is the case, why isn't mydestination empty? You have emptied
>> local_recipient_maps, but this means that all addresses are accepted
>> (and then possibly bounced, which is bad).
>>
>
> Because I was getting messages in
20 matches
Mail list logo
