| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Approved by: portmgr blanket
Notes:
svn path=/head/; revision=415499
|
|
|
|
| |
Notes:
svn path=/head/; revision=393480
|
|
|
|
|
|
|
|
|
| |
that it will work when installed from binary pkg.
Bump PORTREVISION on all plugins for this.
Notes:
svn path=/head/; revision=366415
|
|
|
|
|
|
|
| |
- While here cleanup some whitespaces / dependencys
Notes:
svn path=/head/; revision=344880
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
broke PKGORIGIN, which is created in bsd.port.pre.mk. Oops.
So, I've added CATEGORIES back to all the plugins, and bumped
PORTREVISION so that packages with correct origins can be
created.
Thanks to: Stefan Bethke <stb@lassitu.de>
Notes:
svn path=/head/; revision=336240
|
|
|
|
|
|
|
|
|
|
|
| |
<morinaga@riken.jp>: host postmangw2.riken.jp[134.160.33.164] said: 550 5.1.1
<morinaga@riken.jp>: Recipient address rejected: undeliverable address:
host 134.160.33.167[134.160.33.167] said: 550 5.1.1 <morinaga@riken.jp>:
Recipient address rejected: User unknown in local recipient table (in reply
to RCPT TO command) (in reply to RCPT TO command)
Notes:
svn path=/head/; revision=336160
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Make sure that bsd.port.pre.mk is included before bsd.squirrelmail.mk.
For ports with maintainers, I haven't switched you to the new
PKGMESSAGE, but I have corrected paths in pkg-message.in where
necessary. I also got a little over-zealous in cleaning redundant
definitions from the headers. Apologies in advance if this rubs
you the wrong way.
Notes:
svn path=/head/; revision=335921
|
|
|
|
|
|
|
| |
mail)
Notes:
svn path=/head/; revision=327742
|
|
|
|
|
|
|
|
|
|
|
|
| |
.mk inclusion leading to PKGORIGIN not being set when needed.
Nothing requires bsd.squirrelmail to be loaded after bsd.port.pre.mk but the PORTDIR.
Convert "${PORTDIR}/mail" to ${.CURDIR}/.. and remove all the pre.mk/post.mk dancine
Reported by: erwin
Notes:
svn path=/head/; revision=321853
|
|
|
|
| |
Notes:
svn path=/head/; revision=276989
|
|
You can choose to log to a database, a file, your system log, or any
combination thereof. You can also choose which kinds of events to log,
including login events, logout events, login error events, all outgoing
messages, possible outgoing spam messages, and other error events.
Also included is monitoring functionality that will send alert emails to
the administrator when certain events trigger.
If you use the timeout_user plugin, logout events caused by user timeouts
will be captured.
Log message format is also completely custom-defined to meet your needs
in the configuration file.
WWW: http://www.squirrelmail.org/plugin_view.php?id=52
PR: ports/148587
Submitted by: Satoru Suzuki <xsuzu at yokohama.riken.jp>
Notes:
svn path=/head/; revision=258810
|