Re: [qmailtoaster] segmentation fault in ezmlm-send

2017-07-31 Thread Eric Broch 

Hi Eric. Thanks for all your help. I finally got it to work with this:

SENDER=“f...@bar.com " ezmlm-send 
/home/vpopmail/domains/DOMAIN.COM/LISTNAME  
< LISTNAME/mod/pending/1501468655.5150


Not sure whether the quotes around the address mattered, or leaving off 
the trailing slash after LISTNAME… but it went through at last and that 
was the secret sauce.


Again, thanks very much for your help.

Cheers,

Steve

Forwarded so there's a record of this on the list

On Jul 31, 2017, at 1:53 PM, Eric Broch > wrote:


Hi Steve,

I did this

export SENDER="u...@domain.com"

a user in the mailing list

ezmlm-send /home/vpopmail/domains/domain.com/domain-list 
 < ./mail.msg


It worked.

Eric



On 7/31/2017 11:36 AM, Steve Linberg wrote:


On Jul 31, 2017, at 1:06 PM, Eric Broch > wrote:


Could you try sending the message using qmail-local from the command 
line of the server in question, or using the mail command?


Hi Eric. I did manage to get this to work after some experimenting, 
via qmail-local:


/var/qmail/bin/qmail-local steve 
/home/vpopmail/domains/silicongoblin.com/steve/ 
 steve "" "" silicongoblin.com 
 f...@bar.com 
 ./Maildir/ < LISTDIR/mod/pending/1501468655.5150


I left my own info exposed :) f...@bar.com  is 
what I tried to set SENDER to in the ezmlm-send line, and LISTDIR is 
the directory for the mailing list.


Can I extrapolate from this somehow to a successful ezmlm-send? I’d 
think it would mean that $SENDER should be f...@bar.com 
, but when I did it previously, nothing happened:


SENDER=f...@bar.com  ezmlm-send LISTNAME/ < 
LISTNAME/mod/pending/1501468655.5150



--
Steve Linberg, Chief Goblin
Silicon Goblin Technologies
http://silicongoblin.com 
Be kind.  Remember, everyone you meet is fighting a hard battle.



--
Eric Broch
White Horse Technical Consulting (WHTC)


--
Steve Linberg, Chief Goblin
Silicon Goblin Technologies
http://silicongoblin.com
Be kind.  Remember, everyone you meet is fighting a hard battle.

Re: [qmailtoaster] segmentation fault in ezmlm-send

2017-07-31 Thread Eric Broch 

Hi Steve,

I did this

export SENDER="u...@domain.com"

a user in the mailing list

ezmlm-send /home/vpopmail/domains/domain.com/domain-list < ./mail.msg

It worked.

Eric

Sent so there's a record of this on the qmailtoaster-list


On 7/31/2017 11:36 AM, Steve Linberg wrote:


On Jul 31, 2017, at 1:06 PM, Eric Broch > wrote:


Could you try sending the message using qmail-local from the command 
line of the server in question, or using the mail command?


Hi Eric. I did manage to get this to work after some experimenting, 
via qmail-local:


/var/qmail/bin/qmail-local steve 
/home/vpopmail/domains/silicongoblin.com/steve/ 
 steve "" "" silicongoblin.com 
 f...@bar.com  ./Maildir/ 
< LISTDIR/mod/pending/1501468655.5150


I left my own info exposed :) f...@bar.com  is what 
I tried to set SENDER to in the ezmlm-send line, and LISTDIR is the 
directory for the mailing list.


Can I extrapolate from this somehow to a successful ezmlm-send? I’d 
think it would mean that $SENDER should be f...@bar.com 
, but when I did it previously, nothing happened:


SENDER=f...@bar.com  ezmlm-send LISTNAME/ < 
LISTNAME/mod/pending/1501468655.5150



--
Steve Linberg, Chief Goblin
Silicon Goblin Technologies
http://silicongoblin.com
Be kind.  Remember, everyone you meet is fighting a hard battle.



--
Eric Broch
White Horse Technical Consulting (WHTC)

Re: [qmailtoaster] segmentation fault in ezmlm-send

2017-07-31 Thread Eric Broch 

Steve,

Could you try sending the message using qmail-local from the command 
line of the server in question, or using the mail command?


Eric


On 7/31/2017 10:32 AM, Steve Linberg wrote:
Thanks very much Eric. I set the environment variable to the email 
address of the sender, but I’m not sure whether that’s correct; I 
can't find any actual examples in my googling, just manpages. It did 
stop the segfault, but nothing happened with the message and I don’t 
see any evidence of delivery in /var/log/qmail/*/current:


# export SENDER=f...@bar.com 
# ezmlm-send LISTNAME/ < LISTNAME/mod/pending/*
ezmlm-send: info: qp 11121

I’m not sure what that return code means. I’m assuming I must have set 
SENDER incorrectly? If the list name is LISTNAME, and messages are 
typically sent to the list from f...@bar.com , 
should the latter be the $SENDER? Or should it be something derived 
from LISTNAME?


When I run the above command, I get the following line 
in /var/log/qmail/send/current (LISTNAME and XXX replacing the list 
name and mailing list domain):


@4000597f56840322f0bc info msg 522248: bytes 20572 from 
-@[]> 
qp 11122 uid 0

@4000597f568403711c74 end msg 522248

Guessing that means something went wrong - probably with SENDER - but 
I can’t see any output describing what happened. Any idea?


Thanks again for your help,

Steve


On Jul 31, 2017, at 12:04 PM, Eric Broch > wrote:


Hi steve,

Have a look here: https://lists.gt.net/qmail/users/50317

There's an environment variable "SENDER" that needs to be set.

Eric


On 7/31/2017 8:48 AM, Steve Linberg wrote:
I run an ezmlm mailing list for a friend, which has always worked 
fine. The list is moderated and today the moderator tried to send a 
message to the list, but the moderator confirmation message didn’t 
reach her because her mail server blocked it (I checked and am not 
on any RBL lists, so have asked the ISP to investigate).


Meanwhile, I tried to push the message awaiting moderation via the 
instructions from the ezmlm FAQ. ezmlm-accept dies with a segfault. 
When I try to run ezmlm-send directly, which ezmlm-accept does, 
again the segfault:


segfault at 0 ip 004093d0 sp 7ffe72c0e2e8 error 4 in 
ezmlm-send[40+e000]


The command line is (with LISTDIR replacing the name of the vpopmail 
directory):


/usr/bin/ezmlm-send LISTDIR < LISTDIR/mod/pending/1501468655.5150

I’ve also done it with fully-qualified paths for LISTDIR and it 
didn’t make any difference.


This is on centos 7, all packages and kernel/glibc/etc up to date. 
Everything else is working normally, no other signs of problems that 
I can see, nothing in /var/log/messages except the segfault line 
above. I reinstalled the ezmlm yum package to make sure no binaries 
were corrupted.


I haven’t a clue what to do, but I really need to get this message 
out. Once something hits a segfault, I’m pretty stuck. I’ve rebooted 
the server twice, also, which I hate doing; didn’t help.


Any ideas for either a fix or a workaround so I can get this message 
out?


Thanks.


--
Steve Linberg, Chief Goblin
Silicon Goblin Technologies
http://silicongoblin.com 
Be kind.  Remember, everyone you meet is fighting a hard battle.



--
Eric Broch
White Horse Technical Consulting (WHTC)


--
Steve Linberg, Chief Goblin
Silicon Goblin Technologies
http://silicongoblin.com
Be kind.  Remember, everyone you meet is fighting a hard battle.



--
Eric Broch
White Horse Technical Consulting (WHTC)

Re: [qmailtoaster] segmentation fault in ezmlm-send

2017-07-31 Thread Eric Broch 

Hi steve,

Have a look here: https://lists.gt.net/qmail/users/50317

There's an environment variable "SENDER" that needs to be set.

Eric


On 7/31/2017 8:48 AM, Steve Linberg wrote:
I run an ezmlm mailing list for a friend, which has always worked 
fine. The list is moderated and today the moderator tried to send a 
message to the list, but the moderator confirmation message didn’t 
reach her because her mail server blocked it (I checked and am not on 
any RBL lists, so have asked the ISP to investigate).


Meanwhile, I tried to push the message awaiting moderation via the 
instructions from the ezmlm FAQ. ezmlm-accept dies with a segfault. 
When I try to run ezmlm-send directly, which ezmlm-accept does, again 
the segfault:


segfault at 0 ip 004093d0 sp 7ffe72c0e2e8 error 4 in 
ezmlm-send[40+e000]


The command line is (with LISTDIR replacing the name of the vpopmail 
directory):


/usr/bin/ezmlm-send LISTDIR < LISTDIR/mod/pending/1501468655.5150

I’ve also done it with fully-qualified paths for LISTDIR and it didn’t 
make any difference.


This is on centos 7, all packages and kernel/glibc/etc up to date. 
Everything else is working normally, no other signs of problems that I 
can see, nothing in /var/log/messages except the segfault line above. 
I reinstalled the ezmlm yum package to make sure no binaries were 
corrupted.


I haven’t a clue what to do, but I really need to get this message 
out. Once something hits a segfault, I’m pretty stuck. I’ve rebooted 
the server twice, also, which I hate doing; didn’t help.


Any ideas for either a fix or a workaround so I can get this message out?

Thanks.


--
Steve Linberg, Chief Goblin
Silicon Goblin Technologies
http://silicongoblin.com
Be kind.  Remember, everyone you meet is fighting a hard battle.



--
Eric Broch
White Horse Technical Consulting (WHTC)