07:37 bapt 

remove unmaintained expired ports from mail

2011-05-01 mail/biabam: Upstream disapear and distfile is no more available
2011-05-01 mail/crashecho: Upstream disapear and distfile is no more available
2011-05-01 mail/drbl: Upstream disapear and distfile is no more available
2011-05-01 mail/glbiff: Upstream disapear and distfile is no more available
2011-05-01 mail/libsrs: Upstream disapear and distfile is no more available
2011-05-01 mail/majorcool: Upstream disapear and distfile is no more available
2011-05-01 mail/messagewall: Upstream disapear and distfile is no more available
2011-05-01 mail/pgen: Upstream disapear and distfile is no more available
2011-05-01 mail/regm: Upstream disapear and distfile is no more available
2011-05-01 mail/ricochet: Upstream disapear and distfile is no more available
2011-05-01 mail/smtpclient: Upstream disapear and distfile is no more available
2011-05-01 mail/smtpproxy: Upstream disapear and distfile is no more available
2011-05-01 mail/solidpop3d: Upstream disapear and distfile is no more available
2011-05-01 mail/spruce: Upstream disapear and distfile is no more available
2011-05-01 mail/teapop-devel: Upstream disapear and distfile is no more
available
2011-05-01 mail/wmmail: Upstream disapear and distfile is no more available
2011-05-01 mail/wmmultipop3: Upstream disapear and distfile is no more available
2011-05-01 mail/wmymail: Upstream disapear and distfile is no more available
2011-05-01 mail/xpbiff: Upstream disapear and distfile is no more available

14:43 nork 

 There is a problem with the interaction between MessageWall and Microsoft
Exchange server.  The MS Exchange server gets upset that MessageWall sends
the "250 2.0.0 h1Q0Qc907062 Message accepted for delivery" and the "\r\n"
in different packets.  The first patch works around this MS problem.

See
http://messagewall.org/cgi-bin/ezmlm-browse.cgi?command=showthread&list=messagewall-discuss&month=200302&threadid=nnoiaogojliciagmgpbk

 The other patch changes how MessageWall behaves when there are multiple
recipients to a message.  MessageWall accepts the first recipient, but
defers the second with a temporary SMTP error.  This can take some time
for all recipients to get the message when the sending side has a long
queue time.  MessageWall does this since different recipients of a message
can have different profiles.  We, along with a number of sites, use a
single profile for all inbound email.  This patch, which must be enabled
when the port is built with -DMESSAGEWALL_ALLOW_MULT_RCPT, allows multiple
recipients, using the profile of the first recipient.

See:
http://www.messagewall.org/cgi-bin/ezmlm-browse.cgi?command=showthread&list=messagewall-discuss&month=200303&threadid=lcjcimckfmdphlhpjjhn

PR:             ports/50296
Submitted by:   Douglas K. Rand <rand@meridian-enviro.com>
Approved by:    maintainer timeout (12 days)