When configuring with exim, since the addresses used by og2list are not real system users, if the exim has "verify = recipeint" in it's ACL for RCPT (which many distributions will), it is neccessary to add the following before it:

  # og2list
  accept condition = \
  ${run{OG2LIST_HOME/valid-recipient.pl $local_part}{1}{0}}
  endpass

This causes the valid-recipient.pl to be fired to check if the address is a drupal og2list address before it is rejected as an invalid recipient.

Files: 
CommentFileSizeAuthor
#4 exim.INSTALL_patch1.38 KBajwwong

Comments

ajwwong’s picture

Another modification to the exim documentation for INSTALL --

install MAIL::Verp

should be changed to

install Mail::Verp

it appears as if cpan is case sensitive.

Thanks!

Albert

ajwwong’s picture

Addiitonally, the line:

install DBI

should come *before*

install DBD::mysql

I think that DBD::mysql needs DBI to be installed before it can be installed.

[At least this is what I found on my system.]

Thanks, everyone.

Albert
www.ithou.org

ajwwong’s picture

Also, I've gotten the errors

2006-08-09 18:08:04 Exim configuration error in line 584 of /usr/local/etc/exim/
configure:
  missing "=" after debug_print
2006-08-09 18:08:56 Exim configuration error in line 675 of /usr/local/etc/exim/
configure:
  group og2list was not found

I've solved these errors by

(1) adding an equals sign after debug_print in the exim configure file

and

(2) making sure that user og2list was in the group called og2list

[Still trying to make my system work ;-) ]

Thanks everyone for your efforts here...

Albert
www.ithou.org

ajwwong’s picture

FileSize
1.38 KB

Here's a small patch that takes care of a couple of minor documentation issues for exim.INSTALL, most of which I have listed above:

(1) Using cpan, DBI installation should happen before DBD::mysql , I believe. [When I tried to install it in the reverse order as recommended by the install instructions, DBD::mysql would not install]

(2) MAIL::Verp should become Mail::Verp

(3) Missing "equals sign" after debug_print caused Exim parsing error with Exim 4.62 [some one might want to check this]

(4) The database server and name of database comments were reversed.

Hope this is helpful!

Best wishes,
Albert

Amazon’s picture

Status: Active » Closed (fixed)

Patch applied 2 days ago.

PunkCut25’s picture

The patch didnt seem to apply for me. When applied to a fresh checkout of exim.install all 4 hunks failed.