ARCHIVE=BCC: only working on internal emails?

[NamCigam]

Hi,

I'm just about setting up a scalix system and wanted to try the archiving function by adding

ARCHIVE=bcc:mailbox@domain.com

to the general.cfg.

It works fine if I send an email from one user to another on the scalix server, but if I send an email from scalix (using webaccess) to an email acocunt outside, then no bcc is generated.

Any idea what's going wrong?

Thanks in advance!

Uwe

[NamCigam]

Hi, me once more...

I have an additional question: can anyone explain me, how this archive mechanism is working? Where is the bcc taken?

Maybe it's due to my installation that I do not receive a bcc copy as I am using scalix smtp on an port other than the normal smtp port and having exim running on the machine for accepting mails and delivering them to scalix. Scalix is sending out mails through the normal port 25 on localhost and therefore speaking with exim when sending out an email.

If the ARCHIVE is taken in the smtp part of scalix, then this could be some explanation why it is only working for internal mails...

Uwe

[NamCigam]

Hi,

no answers at all? Does no one have the same problem as I do?

Or is nobody using this bcc option? Any reply is highly welcome...

Thanks a lot,

Uwe

[davidz]

Sorry that I can't really solve your problem but we use the BCC option with the default configuration of sendmail with no problems. Except that the mailbox gets really big :wink:
See:
http://www.scalix.com/forums/viewtopic.php?t=7921&highlight=

[adhodgson]

Hi,

I use the BCC option also with no issues running on the default configuration.

I think in some cases users may be sending mails through your Exim, and they are going outside, and they aren't getting touched by Scalix. SWA may be one example of this, as it uses SMTP to send out its mail (though I think it uses SMTP authentication, which Exim on your box may not be configured for).

Why are you running in this setup, when you can set SMTPD to pass all mail through
your MTA? Also, how is outgoing mail from Scalix handled - does it go via Exim's Sendmail shim?

Thanks.
Andrew.

[NamCigam]

Hi,

thanks for your feedbacks.

Well, my problem is still existing, but I can describe a little more of what I was able to find out and how my setup is exactly.

First of all, I just set up a new box with SuSE 10.1 and Scalix usning sendmail and indeed this option is working fine either on internal mails or on mails send to external MTAs. In both cases Scalix is only accessed by SWA.

In both setups I did also try to use the ARCHIVE=arch: option as I thougt it could be some strange bcc syntax which exim doesn't understand that could cause my problem. Well on both setups the behavious is the same, meaning that on the newly installed setup all mails are stored in the archive directory whereas in the problematic setup only internal mails are stored... So I tend to think that it is not a problem of Scalix cooperating with Exim.

At this point it could be very helpful if one of the Scalix team could explain shortly how the archiver is working and if there are some possibilites of logging the activities.

I did some ohter changes in the problematic setup and it must be that some of these caused my problem. The next step now will be, that I am going to do the same changes on the newly setup and I will hopefully find out which of these changes cause the problem.

To explain the setup a little bit more:
I'm running scalix on a so called root server where also some web sites of me are running on. The box has currently one IP address. Scalix shall mainly be accessed using SWA. Unfortunately, in the standard setup, Scalix is "taking over" the complete http accesses, so that all the other websites did "dissappear" after installing scalix. For that reason I did sucessfully change the port by which SWA is accessed to another port beside the standard port 80. Took me a while but if anyone is interested I can post the instructions. Maybe this is causing my problems, I don't know...
Mail is handled externally by exim and forwarded internally to a dummy interface ip address where the scalix smtpd is listening. Scalix is still set up to send the outgoing emails throug the normal smtp port on localhost, where also exim is listening.
The advantage of running SWA on a different port for me is that I can controll the accesses additionally in the firewall while normal http connects can access from everywhere.

Well, thats about the setup, maybe someone can help me with switching on debugging information in the archiver and in the meantime I will try to change the newly installed machine step by step to the same setup that has currently these problems.

For the scalix experts another thing that I experienced: sending an email on behalf of someone else leads to an "Sender: " header in the mail headers in the problematic setup scenario regardless of the setting "add sender header". On the newly setup the setting "add sender header" controls the adding of the sender haeder... somethin is really strange on my "problematic setup" ... Any ideas are highly welcome...

Uwe

[adhodgson]

Hi,

Could you explain what you did to get Scalix to send mails via Exim?

Thanks.
Andrew.

[NamCigam]

Hi all,

by the time I think, that this is really something for the Scalix geeks among you...

First of all @adhodgson:
I used the instructions (partly) which have been posted here under the topic "Scalix Exim Succeeded". Just search for them.
I have an internal interface with an 172.xxx IP address where I change the Scalix smtpd to listen on port 26 (with smtpd.cfg):
LISTEN=172.16.16.1:26
and exim is installed to listen on the public IP. In unix.mapper I did not change anything (opposite to the posting mentioned above) as my exim is listening also on localhost 25 and sending out the emails.

I did also try other transport settings in unix.mapper like:
transport-service = /usr/sbin/sendmail -bs
transport-service = inet:172.16.16.1:26
but they do not change anything concerning my problem.

Well after reading a little bit, I found out that the archiver ist working somehow together with the service router. So I decided to increase the auit log level for both of them. In the audit log I get two output for "routing" and "archiver" if I send an email locally, but not if I send an email to an external address, although the email is delivered. It seems that the service router is not involved at all or is for some reason not running the same kind as when sending an internal email...

I thought that maybe the service router is only used when the email is sent via the smtpd of scalix, and therefore I do not get any logging. For that reason I tried the secont transport-service setting mentioned above, which lead scalix to drop the outgoing emails into its own smtpd (i guess at least) and which hopefully would solv my problem... unfortunately not.

The service router audit log flie doesn't help at all, as nothing is printed out for the emails send out to external email addresses.

So if anyone has any idea how to deeper log what is happening between my klick on "send email" and the not being used archiver - welcome

Uwe

[adhodgson]

Hi,

Are you using SWA to send the message or Outlook with the UAL client? If you are using SWA, I believe it may be sending direct to Exim. Could you send a message to an external address, then send the headers to the forum? If you like, send to andrew @ hodgsonfamily.org. SWA should send (by default) to the Scalix SMTPD listening on the public IP.

Andrew.