Topic: Template Question

[tandum]

I'm adding the bcc plugin to qpsmtpd in SME 7 and it works fine but I have a template problem. If I create the config files to make it work the way I want it to in templates-user and then add my extra config files to the email-update event they don't expand when I triggered the event. If I add them to templates-custom they expand just fine. Am I doing something wrong?

[CharlieBrady]

I'm adding the bcc plugin to qpsmtpd in SME 7 and it works fine but I have a template problem. If I create the config files to make it work the way I want it to in templates-user and then add my extra config files to the email-update event they don't expand when I triggered the event. If I add them to templates-custom they expand just fine. Am I doing something wrong?

Yes. templates-user is for templates for files in people's home directories - e.g. the .qmail file which directs mail delivery. templates-custom is the correct place. I'm sure this is documented.

[tandum]

I'm sure this is documented.

Thanks Charlie, I found the document your thinking about.

http://mirror.contribs.org/smeserver/contribs//gordonr/devguide/html/devguide.html

[gordonr]

I'm adding the bcc plugin to qpsmtpd in SME 7 and it works fine but I have a template problem. If I create the config files to make it work the way I want it to

We've already added configuration for the bcc plugin (see bug 13).

If you have suggestions for improvements, please raise them in the bug tracker with what you changed, and why.

Custom templates are a last resort - let's get the features in the base, wherever it is sensible to do so.

BTW: The Developer's Guide is linked from the Development page:

http://no.longer.valid/phpwiki/index.php?Development

The copy in my contribs directory is my Work In Progress version and will move as the document becomes more final.

[tandum]

gordon,

I can't find bug 13, it's gone:  but,

If I want to screw around with config files, I'll do just that. If I come up with something others can use, then I'll share it, and I have in the past.

If what I find needs to go into the core then I'll recommend it goes there and outline why.

Regarding this bcc plugin,  I now see your version in pre3 and have over written it in tempates-custom to do what I want it to do.

The draw card in smeserver is the web interface. That is where you need to concentrate.

robin

[gordonr]

gordon,

I can't find bug 13, it's gone:  but,

No, it's not gone. It is just marked as Verified and so doesn't appear on the "Open bugs" list. You can always type a bug number into the box on any Bugzilla page:

http://bugs.contribs.org/show_bug.cgi?id=13

If I want to screw around with config files, I'll do just that. If I come up with something others can use, then I'll share it, and I have in the past.

If what I find needs to go into the core then I'll recommend it goes there and outline why.

No problems. I am trying to dissuade people from the all-too-common advice of putting in a custom template, and trying to encourage people to push up all of their work into a place where everyone can use it.

Regarding this bcc plugin,  I now see your version in pre3 and have over written it in tempates-custom to do what I want it to do.

Could you outline in what way you feel it isn't doing the right thing for you?

The draw card in smeserver is the web interface. That is where you need to concentrate.

robin

The web interface is very important, but getting the templates and other support right has to come first. Otherwise the web interface won't do anything useful. And just as you can muck around with config files, I will concentrate where I decide to concentrate...

[tandum]

Could you outline in what way you feel it isn't doing the right thing for you?

It depends on the client. One wants everyone to receive every email in and out while another wants an archive he can browse (via webmail) of everything in and out but neither want admin, cron, faxmaster, etc, etc. Both want the bcc option not cc. All I need to do is write the config files bcc asks for and put them in the right place. "templates-custom?"

The web interface is very important, but getting the templates and other support right has to come first. Otherwise the web interface won't do anything useful. And just as you can muck around with config files, I will concentrate where I decide to concentrate...

Agreed, but there is a lot of web interface from 6 that is still missing in 7. I would have thought providing a version which did at least what the last one did via the interface would have been a starting point. I've never worked on a software project where the new release removed features that existed in the preceeding one. But I am probably confusing contribs that have been around for years with the core package contents.

[byte]

The web interface is very important, but getting the templates and other support right has to come first. Otherwise the web interface won't do anything useful. And just as you can muck around with config files, I will concentrate where I decide to concentrate...

Agreed, but there is a lot of web interface from 6 that is still missing in 7. I would have thought providing a version which did at least what the last one did via the interface would have been a starting point. I've never worked on a software project where the new release removed features that existed in the preceeding one. But I am probably confusing contribs that have been around for years with the core package contents.

I think the big thing here is that they had alot of work moving to centos base and that's why they may be missing some GUI feature's although they have put them on the command line...[/quote]

[CharlieBrady]

Agreed, but there is a lot of web interface from 6 that is still missing in 7.

Really? Would you care to provide a list?

A few options have been knowingly removed from the web interface because they have been deprecated for security reasons. Significantly more changes have been made to the web interface by adding features (spam tagging/filtering, virus rejection/detection, finer grained DNS control).

[byte]

The web interface is very important, but getting the templates and other support right has to come first. Otherwise the web interface won't do anything useful. And just as you can muck around with config files, I will concentrate where I decide to concentrate...

Agreed, but there is a lot of web interface from 6 that is still missing in 7. I would have thought providing a version which did at least what the last one did via the interface would have been a starting point. I've never worked on a software project where the new release removed features that existed in the preceeding one. But I am probably confusing contribs that have been around for years with the core package contents.

I think the big thing here is that they had alot of work moving to centos base and that's why they may be missing some GUI feature's although they have put them on the command line... I thank Gordon/Charlie/Shad (other Dev's that I don't see) for there efforts to date

[gordonr]

It depends on the client. One wants everyone to receive every email in and out while another wants an archive he can browse (via webmail) of everything in and out but neither want admin, cron, faxmaster, etc, etc. Both want the bcc option not cc. All I need to do is write the config files bcc asks for and put them in the right place. "templates-custom?"

See the developer's guide - templates-custom should only be used if you need to override. You should use the templates hierarchy whenever possible.

We could make bcc/cc behaviour optional. I think that's an invasion of privacy, which is why the default is cc. The only difference is that it adds a header to inform people that the mail has been archived.

Adding exceptions for various senders (e.g. cron) would be a good idea. Please be sure to raise a bug with your changes so they can be incorporated in the base.

Agreed, but there is a lot of web interface from 6 that is still missing in 7. I would have thought providing a version which did at least what the last one did via the interface would have been a starting point.

If something is missing, raise a bug. I don't believe that anything which was in the base in 5.x or 6.x is missing in 7.0

I've never worked on a software project where the new release removed features that existed in the preceeding one.

We haven't.

But I am probably confusing contribs that have been around for years with the core package contents.

You are. I am not aware of anything missing from the SME7 web interface.  There is a lot of work to do to get the well known contribs compatible with SME7/CentOS and that requires buy-in from the contribs authors - we can't do it all.

[CharlieBrady]

Adding exceptions for various senders (e.g. cron) would be a good idea.

"cron" generated mail won't be archived because it doesn't pass through qpsmtpd.

[tandum]

Adding exceptions for various senders (e.g. cron) would be a good idea.

"cron" generated mail won't be archived because it doesn't pass through qpsmtpd.

It does when admin has a remote address.

[tandum]

Agreed, but there is a lot of web interface from 6 that is still missing in 7.

Really? Would you care to provide a list?

A few options have been knowingly removed from the web interface because they have been deprecated for security reasons. Significantly more changes have been made to the web interface by adding features (spam tagging/filtering, virus rejection/detection, finer grained DNS control).

A few options have been knowingly removed ... There's your list....

[tandum]

I upgraded a box from beta5 to pre3 tonight. It's a twin opteron box with mutiple scsii disks. All looks to be okydoky .....