Mailing List Archive: DBMail: dev

Domain alias problem

Index | Next | Previous | View Threaded

michael.monnerie at is

Jun 23, 2009, 9:52 AM

Post #1 of 5 (1139 views)
Permalink

Domain alias problem

I've just setup for the first time a domain forward with
dbmail-users -x @gabl.gv.at -t @gabl-bruck.at

and this made it correctly into the database. But when sending to
foo [at] gabl, LMTP delivers the message somewhere into dbmail, instead
of back to postfix in order to deliver it to another server (gabl-
bruck.at is not local on this system).

Maybe this forward should be done at the postfix level already, but for
management reasons I'd prefer dbmail does it, as I don't want to store
such redirects in an external table.

Trace 5 of lmtp attached.

mfg zmi
--
// Michael Monnerie, Ing.BSc ----- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4

Attachments:

lmtp.log (25.1 KB)

signature.asc (0.19 KB)

paul at nfg

Jun 23, 2009, 2:06 PM

Post #2 of 5 (1064 views)
Permalink

Re: Domain alias problem [In reply to]

Michael Monnerie wrote:
> I've just setup for the first time a domain forward with
> dbmail-users -x @gabl.gv.at -t @gabl-bruck.at

This is currently *not* supported.

insert_messages(+644): deliver [1] messages to external addresses
insert_messages(+649): delivering to external addresses
send_forward_list(+217): delivering to [1] external addresses
parse_and_escape(+54): parsing address [@gabl-bruck.at]
parse_and_escape(+57): unable to parse email address [@gabl-bruck.at]
send_mail(+125): could not prepare 'to' address.

> Maybe this forward should be done at the postfix level already, but for
> management reasons I'd prefer dbmail does it, as I don't want to store
> such redirects in an external table.

What's wrong with letting postfix have read-access to the dbmail_aliases
table? Saves you the whole database-injection-and-forward hoopla to boot.

--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev

James at host-it

Jun 23, 2009, 2:30 PM

Post #3 of 5 (1056 views)
Permalink

Re: Domain alias problem [In reply to]

I Have to agree with Paul on this one - You're much better off doing this at the postfix level. Infact, we have a separate table within dbmail called dbmail_redirect which holds maps/forwarders it's unnecessary additional work for dbmail long term anyway.

James Greig

-----Original Message-----
From: dbmail-dev-bounces [at] dbmail [mailto:dbmail-dev-bounces [at] dbmail] On Behalf Of Paul J Stevens
Sent: 23 June 2009 22:06
To: DBMAIL Developers Mailinglist
Subject: Re: [Dbmail-dev] Domain alias problem

Michael Monnerie wrote:
> I've just setup for the first time a domain forward with
> dbmail-users -x @gabl.gv.at -t @gabl-bruck.at

This is currently *not* supported.

insert_messages(+644): deliver [1] messages to external addresses
insert_messages(+649): delivering to external addresses
send_forward_list(+217): delivering to [1] external addresses
parse_and_escape(+54): parsing address [@gabl-bruck.at]
parse_and_escape(+57): unable to parse email address [@gabl-bruck.at]
send_mail(+125): could not prepare 'to' address.

> Maybe this forward should be done at the postfix level already, but for
> management reasons I'd prefer dbmail does it, as I don't want to store
> such redirects in an external table.

What's wrong with letting postfix have read-access to the dbmail_aliases
table? Saves you the whole database-injection-and-forward hoopla to boot.

--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev

michael.monnerie at is

Jun 23, 2009, 3:18 PM

Post #4 of 5 (1063 views)
Permalink

Re: Domain alias problem [In reply to]

On Dienstag 23 Juni 2009 Paul J Stevens wrote:
> This is currently *not* supported.

OK, so I need to do some MTA magic. I just sent a mail explaining our
domains/customers extensions. For that reason, we never needed this
magic.

But now we have a special case: Customers having Exchange often find it
hard to define alias domains. So in order to simplify that, we want to
accept mails for @alias1.at, and resend the mail to @realdomain.at
(which is on the customers Exchange server).
I wanted to keep that in dbmail. We solved such "aliasdomains" within
our system, but making the "primarydomain" on an external server was
never done until now.

Maybe I'll just setup new sql table as James suggested.

mfg zmi
--
// Michael Monnerie, Ing.BSc ----- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4

Attachments:

signature.asc (0.19 KB)

michael.monnerie at is

Jun 23, 2009, 4:05 PM

Post #5 of 5 (1058 views)
Permalink

Re: Domain alias problem [In reply to]

On Dienstag 23 Juni 2009 James Greig wrote:
> I Have to agree with Paul on this one - You're much better off doing
> this at the postfix level. Infact, we have a separate table within
> dbmail called dbmail_redirect which holds maps/forwarders it's
> unnecessary additional work for dbmail long term anyway.

Thanks Greg, I created a table zmi_rewritedomains with simply "oldname",
"newname" and changed

recipient_canonical_maps = pgsql:/etc/postfix/rewritedomains.sql,
pgsql:/etc/postfix/recipients-rewrite.sql

so that rewritedomains.sql looks like:
query = SELECT '%u@' || newname FROM zmi_rewritedomains WHERE oldname =
'%d'

Quite simple, but I wanted to prevent a schema extension just for this.

mfg zmi
--
// Michael Monnerie, Ing.BSc ----- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4

Attachments:

signature.asc (0.19 KB)

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads