headers
James Reid | 1 May 2008 13:42

RE: DBMail / Postfix / LDAP / SASL2 AUTH

Hi Paul,

Thanks for your help - very much appreciated!

BUT!!!

I get the following error in mailog when I try to send a message to myself:
May  1 20:50:34 fs02 dbmail/lmtpd[11626]: Error:[message]
dbmail-message.c,dbmail_message_store(+786): unable to find user_idnr for
user [__ <at> !internal_delivery_user! <at> __]. Make sure this system user is in the
database!
May  1 20:50:34 fs02 dbmail/lmtpd[11626]: Error:[delivery]
pipe.c,insert_messages(+545): failed to store temporary message.

I've traced the delivery through and can see that I've successfully
authenticated.

Can someone give me some suggestions on how to fix this?

Thanks!
James.

-----Original Message-----
From: dbmail-bounces <at> dbmail.org [mailto:dbmail-bounces <at> dbmail.org] On Behalf
Of Paul J Stevens
Sent: Wednesday, 30 April 2008 10:41 PM
To: DBMail mailinglist
Subject: Re: [Dbmail] DBMail / Postfix / LDAP / SASL2 AUTH

James Reid wrote:
(Continue reading)

Permalink | Reply | 1 comment |
headers
Jorge Bastos | 1 May 2008 14:50
Picon

RE: DBMail / Postfix / LDAP / SASL2 AUTH

That is a system user for DBMail wich has to exist.

Insert this SQL's:

# create the user for the delivery chain
INSERT INTO dbmail_users (userid, passwd, encryption_type)
        VALUES ('__ <at> !internal_delivery_user! <at> __', '', 'md5');
# create the 'anyone' user for ACLs
INSERT INTO dbmail_users (userid, passwd, encryption_type)
        VALUES ('anyone', '', 'md5');
# create the user to own #Public mailboxes
INSERT INTO dbmail_users (userid, passwd, encryption_type)
        VALUES ('__public__', '', 'md5');

You can find it in sql/*your database*/create_tables.sql

> -----Original Message-----
> From: dbmail-bounces <at> dbmail.org [mailto:dbmail-bounces <at> dbmail.org] On
> Behalf Of James Reid
> Sent: quinta-feira, 1 de Maio de 2008 12:42
> To: 'DBMail mailinglist'
> Subject: RE: [Dbmail] DBMail / Postfix / LDAP / SASL2 AUTH
> 
> Hi Paul,
> 
> Thanks for your help - very much appreciated!
> 
> BUT!!!
> 
> I get the following error in mailog when I try to send a message to
(Continue reading)

Permalink | Reply | 0 comments |
headers
John Fawcett | 2 May 2008 19:57

Re: Local Recipient Verification


dbmail <at> bobich.net wrote:
| On Wed, 30 Apr 2008, Alan Hodgson wrote:
|
|>> Tis a good question ... I don't know what causes it offhand, if the
|>> resolver otherwise seems to work.  It sounds familiar, though .. it
|>> seems like you generally use 127.0.0.1 rather than "localhost" for
|>> whatever the reason is.
|>>
|>
|> If the lmtp process is running chroot it may be using different hosts and
|> resolv.conf files than normal system processes.
|
| It doesn't seem to be running chroot (note the 5th field is "n"):
| dbmail-lmtp unix - - n - - lmtp -o disable_dns_lookups=yes
|
| Any other ideas?
|

Postfix by default uses dns via system library calls, what
that returns will depend on resolv.conf. The behaviour
of dig is not always representative of what the system
libraries would return (for example dig does not use
the search list of resolv.conf by default).

disble_dns_lookups changes that behaviour and postfix uses
getaddrinfo() which should also look in /etc/hosts,
depending on the setting of /etc/nsswitch.conf or
equivalent on your system.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Thomas Raschbacher | 5 May 2008 13:15

Re: announce: dbmail 2.2.10 released

any reason why this is not announced on the main dbmail page yet?
On Mon, 2008-03-24 at 16:28 +0100, Paul J Stevens wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> Hi all,
> 
> I'm happy to announce the availability of the latest stable release for
> dbmail.
> 
> No changes since rc2 were applied.
> 
> Changes since 2.2.9:
> 
> - - PostgreSQL 8.3 compatibility (# 676).
> - - Duplicate key errors and other insertion problems ( #685, #686).
> 
> 
> Download:
> http://www.dbmail.org/download/2.2/dbmail-2.2.10.tar.gz
> 
> Debian etch backport:
> deb http://debian.nfgd.net/debian stable main
> 
> Full changelog:
> http://git.dbmail.eu/?p=paul/dbmail;a=shortlog;h=v2.2.10
> 
> 
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Paul J Stevens | 5 May 2008 14:15
Picon
Favicon
Gravatar

Re: announce: dbmail 2.2.10 released

Thomas Raschbacher wrote:
> any reason why this is not announced on the main dbmail page yet?

Yes there was...

fixed now.

--

-- 
  ________________________________________________________________
  Paul Stevens                                      paul at nfg.nl
  NET FACILITIES GROUP                     GPG/PGP: 1024D/11F8CD31
  The Netherlands________________________________http://www.nfg.nl
Permalink | Reply | 0 comments |
headers
Gordon Hay | 6 May 2008 11:30

Upgrade led to mysql conflicts

I upgraded my server from Fedora FC6 to FC8, and all seemed OK at the
end of the process.  DBMAIL (2.2.10) continues to work as expected.  But
a subsequent "yum update" to catch all the post-FC8 updates threw up a
number of errors like this:

                file /usr/bin/msql2mysql from install of
                mysql-5.0.45-6.fc8.x86_64 conflicts with file from
                package
        mysql-5.0.27-1.fc6.i386

Apparently there are conflicts between the FC8 64-bit packages and the
FC6 32-bit packages.

How can I get past this?  
I've asked on the Fedora list, but with no luck yet... 

I'm reluctant to simply "yum remove" the old MYSQL then "yum install"
the new one, in case my DBMAIL database get lost in the process...

Are there MYSQL experts here who can advise?

Any help will be most welcome!
Permalink | Reply | 1 comment |
headers
dbmail | 6 May 2008 11:42

Re: Upgrade led to mysql conflicts (fwd)

On Tue, 6 May 2008, Gordon Hay wrote:

> I upgraded my server from Fedora FC6 to FC8, and all seemed OK at the
> end of the process.  DBMAIL (2.2.10) continues to work as expected.  But
> a subsequent "yum update" to catch all the post-FC8 updates threw up a
> number of errors like this:
>
>                file /usr/bin/msql2mysql from install of
>                mysql-5.0.45-6.fc8.x86_64 conflicts with file from
>                package
>        mysql-5.0.27-1.fc6.i386
> 
> Apparently there are conflicts between the FC8 64-bit packages and the
> FC6 32-bit packages.
> 
> How can I get past this?
> I've asked on the Fedora list, but with no luck yet...
> 
> I'm reluctant to simply "yum remove" the old MYSQL then "yum install"
> the new one, in case my DBMAIL database get lost in the process...

So back it up first.

> Are there MYSQL experts here who can advise?

Mixing 32-bit and 64-bit packages is ill advised at best. Since you just 
upgraded the distro and are using FC, I am assuming that this is not a 
production system. If you are concerned about losing the DB, back it up first, 
but traditionally, removing the mysql package doesn't result in 
/var/lib/mysql/* getting dropped.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Aleksander Kamenik | 6 May 2008 11:43
Picon
Favicon

Re: Upgrade led to mysql conflicts

Gordon Hay wrote:
> I upgraded my server from Fedora FC6 to FC8, and all seemed OK at the
> end of the process.  DBMAIL (2.2.10) continues to work as expected.  But
> a subsequent "yum update" to catch all the post-FC8 updates threw up a
> number of errors like this:
> 
>                 file /usr/bin/msql2mysql from install of
>                 mysql-5.0.45-6.fc8.x86_64 conflicts with file from
>                 package
>         mysql-5.0.27-1.fc6.i386
>         
> Apparently there are conflicts between the FC8 64-bit packages and the
> FC6 32-bit packages.

> I'm reluctant to simply "yum remove" the old MYSQL then "yum install"
> the new one, in case my DBMAIL database get lost in the process...

It won't, rpm will only remove packages that belong to it, try:

rpm -q -filesbypkg mysql-version-release.arch

You should see that the database files don't belong to the package.

Although doing a backup is still a good idea before you start deleting 
stuff.

If 'yum remove' wants to delete too many packages as dependencies, then 
remove the offending packages by hand, that is with 'rpm -e -nodeps 
packagename-version-release.arch'.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Gordon Hay | 6 May 2008 12:28

Upgrade led to mysql conflicts

On Tue, 6 May 2008, Gordon Hay wrote:

> > I upgraded my server from Fedora FC6 to FC8, and all seemed OK at
the
> > end of the process.  DBMAIL (2.2.10) continues to work as expected.
But
> > a subsequent "yum update" to catch all the post-FC8 updates threw up
a
> > number of errors like this:
> >
> >                file /usr/bin/msql2mysql from install of
> >                mysql-5.0.45-6.fc8.x86_64 conflicts with file from
> >                package
> >        mysql-5.0.27-1.fc6.i386
> > 
> > Apparently there are conflicts between the FC8 64-bit packages and
the
> > FC6 32-bit packages.
> > 
> > How can I get past this?
> > I've asked on the Fedora list, but with no luck yet...
> > 
> > I'm reluctant to simply "yum remove" the old MYSQL then "yum
install"
> > the new one, in case my DBMAIL database get lost in the process...
> 
> So back it up first.
> 
> > Are there MYSQL experts here who can advise?
>
(Continue reading)

Permalink | Reply | 501 comments |
headers
dbmail | 6 May 2008 12:35

Re: Upgrade led to mysql conflicts

On Tue, 6 May 2008, Gordon Hay wrote:

> On Tue, 6 May 2008, Gordon Hay wrote:
>
>>> I upgraded my server from Fedora FC6 to FC8, and all seemed OK at
> the
>>> end of the process.  DBMAIL (2.2.10) continues to work as expected.
> But
>>> a subsequent "yum update" to catch all the post-FC8 updates threw up
> a
>>> number of errors like this:
>>>
>>>                file /usr/bin/msql2mysql from install of
>>>                mysql-5.0.45-6.fc8.x86_64 conflicts with file from
>>>                package
>>>        mysql-5.0.27-1.fc6.i386
>>>
>>> Apparently there are conflicts between the FC8 64-bit packages and
> the
>>> FC6 32-bit packages.
>>>
>>> How can I get past this?
>>> I've asked on the Fedora list, but with no luck yet...
>>>
>>> I'm reluctant to simply "yum remove" the old MYSQL then "yum
> install"
>>> the new one, in case my DBMAIL database get lost in the process...
>>
>> So back it up first.
>>
(Continue reading)

Permalink | Reply | 501 comments |

Gmane