> > Depending on what character set you are using, it could be a problem
> > but the fix is simple, UPPER(%s) or LOWER(%s) (based on how your data is
> stored).
> > I agree to dumping LIKE for performance reasons
>
> the tables are all UTF8, but there is no relevant non-ascii data i choosed
> lik
Am 23.02.2011 18:36, schrieb Gary Smith:
>> cool - this means i do not need any like in any postfix-mysql-config what is
>> faster because keys are used, nice to know, i wanted to get sure that there
>> nothing fails while making this setup a year ago
>
> Depending on what character set you are us
> cool - this means i do not need any like in any postfix-mysql-config what is
> faster because keys are used, nice to know, i wanted to get sure that there
> nothing fails while making this setup a year ago
Depending on what character set you are using, it could be a problem but the
fix is simpl
Am 23.02.2011 18:29, schrieb Victor Duchovni:
> On Wed, Feb 23, 2011 at 06:25:56PM +0100, Reindl Harald wrote:
>
sender dependent relay hosts
>>>
>>> What's wrong with "mydestination = '%s'"? Why are you using "like '%s'"?
>>> Surely the destination domain is not a wildcard pattern, but is
On Wed, Feb 23, 2011 at 06:25:56PM +0100, Reindl Harald wrote:
> >> sender dependent relay hosts
> >
> > What's wrong with "mydestination = '%s'"? Why are you using "like '%s'"?
> > Surely the destination domain is not a wildcard pattern, but is rather
> > a literal string.
>
> Example:
>
> %s
Am 23.02.2011 18:16, schrieb Victor Duchovni:
> On Wed, Feb 23, 2011 at 05:56:35PM +0100, Reindl Harald wrote:
>
mysql-transport.cf:
select transport from
dbma_transports where mydestination like '%s'
or mydestination like '%d'
order by transport desc limit 1;
>>>
>>>
On Wed, Feb 23, 2011 at 05:56:35PM +0100, Reindl Harald wrote:
> >> mysql-transport.cf:
> >> select transport from
> >> dbma_transports where mydestination like '%s'
> >> or mydestination like '%d'
> >> order by transport desc limit 1;
> >
> > This type of fuzzy "like" query is highly question
Am 23.02.2011 17:49, schrieb Wietse Venema:
> Reindl Harald:
>> Sorry, here the output of "postconf -n" and some more information
>> "de.bp.com" does not exist anywhere and so why the sceond log entry?
>
> Obviously, the address does not resolve to the default_transport.
this was not clear for
Am 23.02.2011 17:47, schrieb Victor Duchovni:
> On Wed, Feb 23, 2011 at 05:32:16PM +0100, Reindl Harald wrote:
>
>> "de.bp.com" does not exist anywhere and so why the sceond log entry?
>
> Subdomains of domains in mydestination are by default relay domains.
> Set "relay_domains = " (empty) if you
Reindl Harald:
> Sorry, here the output of "postconf -n" and some more information
> "de.bp.com" does not exist anywhere and so why the sceond log entry?
Obviously, the address does not resolve to the default_transport.
To find out what the address DOES resolve to:
- Does the domain match $mydes
On Wed, Feb 23, 2011 at 05:32:16PM +0100, Reindl Harald wrote:
> "de.bp.com" does not exist anywhere and so why the sceond log entry?
Subdomains of domains in mydestination are by default relay domains.
Set "relay_domains = " (empty) if you have no relay domains. For
relay_domains, Postfix uses "
Sorry, here the output of "postconf -n" and some more information
"de.bp.com" does not exist anywhere and so why the sceond log entry?
Feb 21 13:23:05 postfix/smtpd[13782]: NOQUEUE: reject: RCPT from
localhost[127.0.0.1]: 550 5.1.2
: Recipient address rejected: mail to remote domains not
permitt
Reindl Harald:
> Sorry that was the wrong line :-(
>
> default_transport = error:5.1.2 mail to remote domains not permitted
>
See http://www.postfix.org/DEBUG_README.html#mail for how to submit
a proper error report.
You violated rule number 1: provide "postconf -n" output instead
of pasting li
Sorry that was the wrong line :-(
default_transport = error:5.1.2 mail to remote domains not permitted
in my understanding postfix should never relay any message outside
after this is set, but it happens on some target domains / subdomains
Am 23.02.2011 15:27, schrieb Wietse Venema:
> Reindl Har
Wietse Venema:
> Reindl Harald:
> > Am 23.02.2011 14:44, schrieb Wietse Venema:
> >
> > > If you have a problem with Postfix, and you would like to see that
> > > problem fixed, then you need to provide ONE SIMPLE EXAMPLE that
> > > reproduces the problem.
> >
> > This is a example, i do not know
Reindl Harald:
> Am 23.02.2011 14:44, schrieb Wietse Venema:
>
> > If you have a problem with Postfix, and you would like to see that
> > problem fixed, then you need to provide ONE SIMPLE EXAMPLE that
> > reproduces the problem.
>
> This is a example, i do not know how to make it simpler
> becau
Am 23.02.2011 14:44, schrieb Wietse Venema:
> If you have a problem with Postfix, and you would like to see that
> problem fixed, then you need to provide ONE SIMPLE EXAMPLE that
> reproduces the problem.
This is a example, i do not know how to make it simpler
because there is only one line in
Reindl Harald:
> The same with postfix 1.8.1
>
> The first one respects "default_transport = error:5.1.2 mail to remote dom
>-ains not permitted" but the second one
> must be catched with "relayhost = 127.0.0.1" to prevent relay to the inter
>-net which is also active while sending
> the first tes
The same with postfix 1.8.1
The first one respects "default_transport = error:5.1.2 mail to remote domains
not permitted" but the second one
must be catched with "relayhost = 127.0.0.1" to prevent relay to the internet
which is also active while sending
the first testmail but "relayhost" should
It seems you did not read my mail
Am 21.02.2011 13:51, schrieb Charles Marcus:
> On 2011-02-21 7:43 AM, Reindl Harald wrote:
>> Feb 21 13:41:52 postfix/smtp[14418]: warning: relayhost configuration problem
>> Feb 21 13:41:52 postfix/smtp[14418]: 2D60D3DF7:
>> to=, relay=none, delay=0.05,
>> delay
On 2011-02-21 7:43 AM, Reindl Harald wrote:
> Feb 21 13:41:52 postfix/smtp[14418]: warning: relayhost configuration problem
> Feb 21 13:41:52 postfix/smtp[14418]: 2D60D3DF7: to=,
> relay=none, delay=0.05,
> delays=0.03/0.01/0/0, dsn=4.3.5, status=deferred (mail for 127.0.0.1 loops
> back to mysel
Hi
In a local machine i have the following setup to prevent sending outside
and catch some domain local, but why in the world is the second log-entry
relayed instead reject like the first one?
default_transport = error:5.1.2 mail to remote domains not permitted
Now i fixed this problem with "rel
22 matches
Mail list logo
